protx update_service WORKING COMMAND biblepay-cli protx update_service “XXXXX33185427856e07d7a966714d118c7434994b5d6a349c11558e79e290" "45.62.239.200:40001" XXXXX9587da071b3038ab816e07d4259252eca78c5fb1800daf8 "" yctpVgjqrKbLiXYaSX35nYjUEvvuM6sgpr # WORKING COMMAND BREAKDOWN AND COMMENTS cli protx update_service Pro-Reg-Sent-TxId This is the output “sent_txid” - this is the hash not the long output e.g. “XXXX35533185427856e07d7a966714d118c7434994b5d6a349c11558e79e290" IP:port(40000=prod,40001=testnet) e.g. “XXX.XXX.239.200:40001" 3. "operatorKey" (string, required) The operator private key belonging to the registered operator public key. "bls_private_key" e.g. XXXXXXbcdb7a789587da071b3038ab816e07d4259252eca78c5fb1800daf8 4. "operatorPayoutAddress" (string, optional) The address used for operator reward payments. Only allowed when the ProRegTx had a non-zero operatorReward value. If set to an empty string, the currently active payout address is reused. ### NOTE This should be AN EMPTY STRING as upgrade does not specify payout address (operator reward was 0) note this empty field is important => "" 5. "feeSourceAddress" (string, optional) If specified wallet will only use coins from this address to fund ProTx. If not specified, payoutAddress is the one that is going to be used. The private key belonging to this address must be known in your wallet. # This was the address that I generated from the new wallet (getnewaddress “payout”) which does NOT have the masternode collateral - that wallet was destroyed! and also sent some funds to e.g. yctpVgjqrKbLiXYaSX35nYjUEvvuM6sgpr Output of successful command: #Result: #"txid" (string) The transaction id. 3f9f9848a4f035491adc4a7843e48e9590bef0e53c61c0f8383e081b565b31b4