Rob, brother.
The wallet is crashed during the "exec upgradesanc AltareSanto 1" command.
Now the situation is changed to this.
11:02:52
exec upgradesanc AltareSanto 0
11:02:52
{
"Command": "upgradesanc",
"Summary": "Creating protx_register command for Sanctuary AltareSanto with IP *.*.*.66:40000 with TXID 13cb0827e303d05604481be19dab67ae401357a9c2fe48b15936cb48e03d29c6",
"bls_public_key": "b82a0249b0323c05f89448b9246b63ac2d3c91bec2431e8596581b664ea95484382c46c718c70a92c1016c089c838f2b",
"bls_private_key": "61a3a78031ebf958832fb960ded4160f353d64a16591e286a41a2713713133b8",
"pro_reg_txid": "0300010001df2ed6b028f35f75f28d21cb82bd415901acef3edcad869ea90f126bf1920f2a0100000000feffffff016c661903000000001976a914da266fc172389feffdd44105e460b996a3cd826588ac0000000000d1020000000000c6293de048cb3659b148fec2a9571340ae67ab9de11b480456d003e32708cb130100000000000000000000000000ffff5d37fc429c40a0761b3fffcf408d157197fa366d771db5835f0eb82a0249b0323c05f89448b9246b63ac2d3c91bec2431e8596581b664ea95484382c46c718c70a92c1016c089c838f2ba0761b3fffcf408d157197fa366d771db5835f0e00001976a914da266fc172389feffdd44105e460b996a3cd826588ac0db6b50e182f58cc86674b55a713e6304e94b86bd611f00da54793759a5072eb00",
"pro_reg_collateral_address": "BKcqLFDfZZUJWyaivmZR3WRMVdFCv1p6Qy",
"pro_reg_signed_message": "BQLYy9oNyiCdbym3Vd7dd8nqiP2xAipdYc|0|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|d8a79a5a10e600c12ee6c759e86772df3a3233de8326a72c7930d4eecc11c80b",
"pro_reg_signature": "IGBCLghtakvYladlI8To5LJiBqeZ1z7A5FjssRSB1756C5BEH4QY+TGVwD2Y7cphWE5k7vSepP5Xz4aKxdlDV0E=",
"sent_txid": ""
}
The IP add is masked by me
11:04:22
exec upgradesanc AltareSanto 1
11:04:22
bad-protx-collateral-01 (code -1)
The transaction message from wallet appear
11:05:44
masternode status
11:05:44
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "[::]:0",
"state": "ERROR",
"status": "Error. Can't detect valid external address. Please consider using the externalip configuration option if problem persists. Make sure to use IPv4 address only."
}
Is this a bug or something like it ?
Thanks
Ale
Hi Lalex,
So when you issue the command upgradesanc, usually, its not actually a "crash" (crash means that the wallet either threw an unhandled exception and ended the program), but instead was sitting there with no RPC response, right? Ive seen that behavior in this new RPC, and I believe we inherited a UI deadlock.
It does respond to me after 3 minutes however.
The bad-pro-tx-collateral error must be resolved first to get a fully functioning sanc. It means that your collateral has either not been sent or not matured. I would start over, and when you do your 'getrawtransaction txid ordinal' ensure it is actually there, has the right amount, and has matured a few blocks before going to the next step.
Recent Posts