• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

strange transaction

We had a few potential split situations when we had to disable mn payment enforcement (spork8) and turned out that some miners are trying to use this to their advantage (again, like in old days). To solve the issue with sync progress you can use "reconsiderblock" rpc.
 
UdjinM6 said:
We had a few potential split situations when we had to disable mn payment enforcement (spork8) and turned out that some miners are trying to use this to their advantage (again, like in old days). To solve the issue with sync progress you can use "reconsiderblock" rpc.
Click to expand...

Can you please explain more about how to use "reconsiderblock" rpc.

Thanks
 
bhkien said:
Can you please explain more about how to use "reconsiderblock" rpc.

Thanks
Click to expand...
Sure. Say your node stuck on block 767900 and rejects 767901 https://explorer.dash.org/block/000000000000002a3c26c452c9b7f84d8d1eba19c2e0d5bbd8d57f663e489794 due to invalid transaction or for whatever another reason - it could be that some rules were applied when node first received this block (and marked it as invalid to avoid re-checking) which you'd like to bypass now. So "reconsiderblock" is the way to say "pls check this block again" e.g.
Code: 
reconsiderblock 000000000000002a3c26c452c9b7f84d8d1eba19c2e0d5bbd8d57f663e489794
Rules for mn payments are relaxed for nodes that are still downloading blocks/syncing additional data (you trust the rest of the network to check payments for past blocks because you can't check blockchain before you received payment info), so you can use that to re-accept the block which was rejected due to spork8 for example i.e. (2 commands)
Code: 
mnsync reset
reconsiderblock 000000000000002a3c26c452c9b7f84d8d1eba19c2e0d5bbd8d57f663e489794
 
You must log in or register to reply here.
Back
Top