1. upgrade wallet (must be cold set up with controlling wallet) 2. sync wallet 3. on controlling wallet exec upgradesanc sancname 0 4. if everything is alright and no errors, then issues exec upgradesanc sancname 1 5. this sould give an output such as { "Command": "upgradesanc", "Summary": "Creating protx_register command for Sanctuary NM1 with IP nn.nn.nn.nn:40001 with TXID Xdf4d38dee8b4233d250b05Xd8773ec320292d16a6b2e7c008ffb58d976a259e", "bls_public_key": "0bd2ef8af156182399cac5d63e6e4f79a8877d79b514791178a9ffdd54e5378f31a28522033ec0e2519027845a15ef37", "bls_private_key": “X7a88a4311a2a585d0fd4ae4edb01f7915ca65926a4b73b02cc65176edcb0cb5", "pro_reg_txid": "03000100013192382d09b86b8c319be198bd7c6a8deefd03510d6bba7b4af809dfc2ce99350000000000feffffff01188aee05000000001976a914c74c6f15acc480a31e573536f096d59b777c480f88ac0000000000d10100000000009e256a978db5ff08c0e7b2a6162d2920c33e77d85db050d233428bee8dd3f40d0100000000000000000000000000ffff40b4c2ee9c41d6c75eb0fb7e29cf1c45891fa8955a94b4441d5b0bd2ef8af156182399cac5d63e6e4f79a8877d79b514791178a9ffdd54e5378f31a28522033ec0e2519027845a15ef37d6c75eb0fb7e29cf1c45891fa8955a94b4441d5b00001976a914c74c6f15acc480a31e573536f096d59b777c480f88ac2952e8b8981606d0c7c51bd69bc474dd5768bed4fe055715b00cefb4a3622f0300", "pro_reg_collateral_address": "yc5iiRK3bxSDRqziqMPNZ7qEHxnYzvckkH", "pro_reg_signed_message": "yeVEt6ivbyJnhR96Uh7ckt9j3gy3MRDaKF|0|yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE|yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE|384a84f97b9e064678c67d2227bb0286a947039a10982ff1afc7d8d0f5a61f2d", "pro_reg_signature": "H+/dW/qOor6gX7kQ7xTOej8bebcT019H/pLPsjWiuhHxfF2AbZxAP7nKLrM/Aw/9x2bGP43ZtesEXcs+EzU9yjk=", "sent_txid": "7b5c9e029fd9d220e244ab9516a6196ec98a6a5a22fab6890da2f20a80cc971c" } the sent-txid should be populated when 1 is appended and empty then 0 is appended to the above commands 6. copy this to the biblepay.conf on the remote sanc bls_private_key (from above ouput) to masternodeblsprivkey= (biblepay.conf on remote sanc config file) biblepay.mn 7. Wait for 5 confirmations { "account": "NM1-D", "address": "yeVEt6ivbyJnhR96Uh7ckt9j3gy3MRDaKF", "category": "receive", "amount": 1.00000000, "label": "NM1-D", "vout": 1, "confirmations": 29, "instantlock": false, "blockhash": "3aafecc03842e209a6f67a160aa0d16dc9715d798f471deaec84acc3736fe993", "blockindex": 2, "blocktime": 1557169264, "txid": "Xd117cdcdcba44dcc638562cdc221cd1ecb97935060e75b8df1e9fa0d5e7f81d", "walletconflicts": [ ], "time": 1557167627, "timereceived": 1557167627 } 8. check on remote sanc - masternode status - should be ready { "outpoint": "Xdf4d38dee8b4d33d250b05dd8773ec320292d16a6b2e7c008ffb58d976a259e-1", "service": "nn.nn.nn.nn:40001", "proTxHash": "7b5c9e029fd9d220e244ab9516a6196ec98a6a5a22fab6890da2f20a80cc971c", "collateralHash": "Xdf4d38dee8f4233d250b05fd87s3ec320292d16a6b2e7c008ffb58d976a259e", "collateralIndex": 1, "dmnState": { "service": "nn.nn.nn.nn:40001", "registeredHeight": 65407, "lastPaidHeight": 0, "PoSePenalty": 0, "PoSeRevivedHeight": -1, "PoSeBanHeight": -1, "revocationReason": 0, "ownerAddress": "yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE", "votingAddress": "yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE", "payoutAddress": "yeVEt6ivbyJnhR96Uh7ckt9j3gy3MRDaKF", "pubKeyOperator": "0bd2ef8af156182399cac5d63e6e4f79a8877d79b514791178a9ffdd54e5378f31a28522033ec0e2519027845a15ef37" }, "state": "READY", "status": "Ready" } There appears to be no need issue the start command from the controlling wallet. 9. Check masternode list status to find your sancs in the list with the ENABLED status Note to reader: ============== 10. We can help by sharing some of our excess computing infrastructure, such as a 1vCPU machine VPS per node and help you setup and run your remote (cold) BBP sanctuary for you. I have done this for someone already. You are responsible for your own controlling wallet and I will update the remote sanc for you when I update mine. 11. The locked funds remain in your controlling wallet and you can pay us whatever you feel comfortable with ($/BTC/BBP/donation to charity, prearranged to avoid misunderstandings).