why I have only one “In” peer?
- check the ufw on your producer, if u allowed both relays
- check the topology updater script from both relalys… if you added the Producer IP + port or if you are using coincashew guide then check inside the script relay-topology_pull.sh
New Core syncing with blockchain: 72.2% for 14 hours. Pretty fast …
Cardano Node - (Relay - Mainnet) : 1.29.0 [4c594429] <
┌────────────────────────┬────────────┬────────────────────────┐
│ Uptime: 14:09:12 │ Port: 6000 │ Guild LiveView v1.21.1 │
│------------------------└────────────┴────────────────────────┤
│ Epoch 265 [51.7%] (node) │
│ 1d 13:46:55 until epoch boundary (chain) │
│ ▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖ │
│ │
│ Block : 5712314 Tip (ref) : 40644785 │
│ Slot : 223192 Tip (node) : 29339992 │
│ Density : 4.951 Status : syncing (72.2%) │
│--------------------------------------------------------------│
│ Processed TX : 0 Out / In │
│ Mempool TX/Bytes : 0 / 0 Peers : 2 0 │
└──────────────────────────────────────────────────────────────┘
TG Announcement/Support channel: Telegram: Contact @guild_operators_official
[esc/q] Quit | [i] Info | [p] Peer Analysis
but you can copy the DB folder from synced node to the new Producer… and it will work
Thanks for advice!
I have working Core node (old). This command worked for me:
sudo ufw allow from relay IP proto tcp to any port 6000
> Cardano Node - (Core - Mainnet) : 1.29.0 [4c594429] <
┌────────────────────────┬────────────┬────────────────────────┐
│ Uptime: 1d 02:20:30 │ Port: 6000 │ Guild LiveView v1.21.1 │
│------------------------└────────────┴────────────────────────┤
│ Epoch 291 [69.1%] (node) │
│ 1d 13:07:44 until epoch boundary (chain) │
│ ▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖ │
│ │
│ Block : 6272080 Tip (ref) : 40647136 │
│ Slot : 298334 Tip (node) : 40647134 │
│ Density : 5.172 Tip (diff) : 2 
│
│--------------------------------------------------------------│
│ Processed TX : 83214 Out / In │
│ Mempool TX/Bytes : 2 / 1196 Peers : 2 2 │
├──────────────────────────────────────────────────────────────┤
│ KES current/remaining : 313 / 37 │
│ KES expiration date : 2021-11-14 21:44:51 UTC │
│ Missed slot leader checks : 89 (0.0941%) │
│--------------------------------------------------------------│
│ BLOCKS Leader | Adopted | Invalid │
│ Since node start 0 | 0 | 0 │
└──────────────────────────────────────────────────────────────┘
TG Announcement/Support channel: Telegram: Contact @guild_operators_official
[esc/q] Quit | [i] Info | [p] Peer Analysis
the default mode when you start CNTools Online - When all wallet and pool keys are available on the hot node.
This mode isn’t secure, right?
Why? Should be se ure if the node is secure…
now if u have a cold machine u can sign the transaction there and submit from the live producer…
I used in the past cntools online for my cloud Producer and everything was fine
I would go for using separate cold machine. I can’t really figure (Overview - Guild Operators) out how to do it practically.
Should I install Cardano Node on separate computer and disconnect it from internet forever) and run CNTools in offline mode?
It’s possible to hack cloud server. I will be responsible to millions of ADA. I want to provide highest security level…
Exactly, this is how a cold machine work
Yes, cloud servers can be hacked 
Millions? Do u have wallets with millions or what do u mean?
I worried about my pledge and harm to. my delegators
Delegators are safe… they will not lose the funds if ur server will be hack… only ur pledge will be lost if u are keeping the files on live servers
If u will build a cold machine will be safe for u, u will have the files on cold machine, create and sign the transactions on cold machine and upload to live server and submit them
first time will be hard… but then should be easy
New “core” sync is completed. I want to upload keys (renamed). I updated ENV file and added pool name CoolT.
Folder /opt/cardano/cnode/priv is empty…
Question: should I create folders:
- wallet
- pool
- CoolT?? where inside folders pool and wallet ??
yes, inside the priv create to folders named
- wallet
- pool
now, inside the pool create the folder CooIT where u should upload the files - node.cert → op.cert
- vrf.skey → change the priority to 400 - chmod 400 vrf.skey
- kes.skey → hot skey
then go to the env file and uncomment the line Pool name and add CooIT between “”
save the file and restart the node
now you should see it working as a Producer
PS: you can add all files inside the CooIT pool folder and test it
you can go to pool - rotate - to rotate the keys ; pool - modify to modify the pool (add the same parameters)
also you should create the wallet folder inside the wallet and upload the files… then go to cntools and test it… wallet - show… then try to create a small transaction for test - funds - send… if everything ins fine after all these tests it means u have renamed the files correctly and you can save also a bkp … don’t forget to delete the files (or encrypt them) after all these tests
files which should not be keep
- payment.skey
- stake.skey
- cold.skey
- cold.vkey
But again, if you will use a cold machine then you should keep on live producer only the:
- op.cert
- vrf.skey
- hot.skey
- and also vrf.vkey if you will use cncli for leader log
Cheers,
should I set privileges 600 on “priv” folder as per instruction: # Folder to store your keys (permission: 600)
nope, should not be any problems
I still do’n like the idea to put private key payment.skey, stake.skey, cold.skey,cold.vkey to live server.
Can I test new Core in Hydrid mode?
POOL >> LIST
CoolT
ID (hex) :
Registered : YES
KES expiration date : 2021-11-14 22:44:51 CET
press any key to proceed .. >> POOL >> SHOW
ERROR: pool-params query failed: option --stake-pool-id: cannot parse value `–mainnet’
Usage: cardano-cli query pool-params
[ --shelley-mode
| --byron-mode [–epoch-slots NATURAL]
| --cardano-mode [–epoch-slots NATURAL]
]
(–mainnet | --testnet-magic NATURAL)
–stake-pool-id STAKE-POOL-ID
Dump the pool parameters
(Ledger.NewEpochState.esLState._delegationState._pState._pParams – advanced
command)