Skip to content
Search Create account

Developers Forum for XinFin XDC Network

Developers Forum for XinFin XDC Network is a community of 7,775 amazing users

Developers Forum for XinFin XDC Network

Create account Log in
Twitter Facebook Github Instagram

Discussion on: XDC Masternode Backup and Migration Procedure for v2.6.8 and Later

View post

Replies for: Your three points are essentially correct, with two important additions and one ordering fix. 1. coinbase.txt — you are right, nothing to...

Collapse
pxinl444 profile image
PXI_Nl Author •

Thank you very much for your detailed and helpful explanation.

Before asking this question, I had already tested the migration process about four times using my own procedure, and each time the migration completed successfully and the node continued receiving rewards without any issues.

That said, I’m very glad I was able to confirm my understanding and the migration process again here, especially regarding coinbase.txt, the keystore directory, and the .pwd file, as well as the importance of fully stopping the old node before starting the new one.

Your explanation has helped me feel even more confident about the process. I really appreciate you taking the time to explain everything so carefully.

Thank you again for your support, Daniel.

Collapse
pxinl444 profile image
PXI_Nl Author •

I slightly modified the verification commands so that they work cleanly in my environment.

In particular, XDPoS.GetSigners() was not available, while XDPoS.getSigners() was. Since the full signer list is very long, I changed it to:

XDPoS.getSigners().indexOf(eth.coinbase) >= 0
Enter fullscreen mode Exit fullscreen mode

This simply returns true if my masternode address is included in the current signer list.

The full set of checks I am now using is:

./xdc-attach.sh

eth.coinbase
eth.getCandidateStatus(eth.coinbase, "latest")
XDPoS.getSigners().indexOf(eth.coinbase) >= 0
net.peerCount
eth.blockNumber
Enter fullscreen mode Exit fullscreen mode

This makes it easy to confirm the node address, masternode status, signer inclusion, peer connectivity, and block progress.