When I run the mainnet it expects a change in this file of the network magic number from testnet to mainnet
~/cardano-src/cardano-node/db/protocolMagicId
so I will have to follow our method. What do i populate the db folder with or does that happen by running the node again, I gather its going to have to re sync everything again ?
ok the mainnet node run and sync is stuck, I have done no config changes so not surprised.
Please can you tell me if I do the db move on Mainnet can I keep test net where it is kind of dont want to loose the sync on that if I can help it ,thanks for the help very appreaciated
That’s a bit ugly, because it leaves the socket in the db/ folder of testnet, but you can use cardano-cli as before and do not have to worry about export CARDANO_NODE_SOCKET_PATH. Trying to reduce your construction areas. …
Maybe your non-working mainnet node is still running and cardano-cli is still using that?
What does echo $CARDANO_NODE_SOCKET_PATH say in the same terminal that gives you that tip?
(export CARDANO_NODE_SOCKET_PATH="~/Library/Application Support/Daedalus Mainnet/cardano-node.socket" only influences the current terminal or – if it is put in .bashrc, .zshrc or something like that – every newly started terminal.)
You’ve done a lot of chaos, my friend. I don’t know.
If I followed our discussions correctly, the database in cardano-src/cardano-node/db is the one that was used but could not be completed, but it seems to be good for testnet. So, if you want to switch to testnet again, I would not delete that.
I am very grateful to you, the patience of a saint I hope I can buy you a very nice whatever your tipple is thank you. Once this is synced I will then immediately go an retry Testnet, I expect you will be asleep by then. LoL
Node activity is quite high it seems probably has peak times like anything.
Oh, that seems to be much easier on MacOS than on Linux.
On Linux, they provide a NixOS environment and you have to chroot into that. But that’s what I’m doing here:
Sorry, thought I’d spare you that information, since we had so many construction sites already going.
Attention: If you use that cardano-cli it’s an older version. Bundled with Daedalus is 1.30.1. And they changed the treatment of token names in 1.31.0. So, you do not need and do not want the base16 conversion in that version. In --mint and --tx-out you just write the token name in cleartext, instead.
I’ve run into that, when first trying it out.
Attention 2: Next week, there will be an update and Daedalus will ship 1.33.0 and Attention 1 will no longer hold, it will convert the chain for several hours, but afterwards will use less disk space.
Hi wow what an adventure this has been. My Mainnet Node has just 100% sync completed after a good 18hrs + while rendering my computer useless and consuming 20GB + disk space. I realise hosting a node would probably be better place in a VM now via this experience.
I have a different laptop now since the above that computer is unusable.
So am using the Deadalus Wallet approach this time on this different laptop.
I noticed just how much quicker the sync is on Deadalus compared to the node binary. Have you noticed a vast difference ?