[Testnet] Dash Core v19.0.0 RC.10 : HPMN Pose Ban mismatch between Windows wallet & Dashmate status commands

[qwizzie]

Windows 10 Dash Core v19.0.0 RC.10 wallet
Ubuntu 18.04.6 LTS --> HPMN

My HPMN dashd.pid active since 7th of April and on v19.00 RC.10

debug.log

2023-04-07T11:30:23Z Dash Core version v19.0.0-rc.10 (release build)
2023-04-07T11:30:23Z InitParameterInteraction: parameter interaction: -externalip set -> setting -discover=0
2023-04-07T11:30:23Z InitParameterInteraction: parameter interaction: additional indexes -> setting -checklevel=4

Going through my debug.log i can't find a PoSe Ban on my Protx hash. I am now not sure if my HPMN is PoSe banned or not.
Dashmate status masternode returning a Pose Penalty 0 and me not finding a PoSe ban on my Protx hash in my debug.log makes me think perhaps my HPMN is not PoSe banned ?
I did find an error in the debug.log by the way, could be related to it

2023-04-10T12:06:15Z ERROR: ConnectBlock(DASH): coinbase pays too much at height 865848 (actual=6072799096 vs limit=1672799096), exceeded block reward, no triggered superblock detected

2023-04-10T12:06:15Z InvalidChainFound: invalid block=000000653fe0f3fb477b0e8bb4becc5220c2ede722fe2be5f8cac6f0cf8c09da height=865848 log2_work=57.50491778 date=2023-04-10T12:06:00Z
2023-04-10T12:06:15Z InvalidChainFound: current best=00000081ad7ef9edb15150bcc9ee6ca8a7cdc5a825b9f10793edbd5fe3a69b3f height=865847 log2_work=57.50491778 date=2023-04-10T12:01:40Z
2023-04-10T12:06:15Z ERROR: ConnectTip: ConnectBlock 000000653fe0f3fb477b0e8bb4becc5220c2ede722fe2be5f8cac6f0cf8c09da failed, bad-cb-amount (code 16)
2023-04-10T12:06:15Z InvalidChainFound: invalid block=000000653fe0f3fb477b0e8bb4becc5220c2ede722fe2be5f8cac6f0cf8c09da height=865848 log2_work=57.50491778 date=2023-04-10T12:06:00Z
2023-04-10T12:06:15Z InvalidChainFound: current best=00000081ad7ef9edb15150bcc9ee6ca8a7cdc5a825b9f10793edbd5fe3a69b3f height=865847 log2_work=57.50491778 date=2023-04-10T12:01:40Z
2023-04-10T12:06:15Z ProcessNewBlock : ACCEPTED
2023-04-10T12:06:15Z ERROR: AcceptBlockHeader: block 000000653fe0f3fb477b0e8bb4becc5220c2ede722fe2be5f8cac6f0cf8c09da is marked invalid

[qwizzie]

I decided to do a dashmate reset --hard to delete and download the Testnet blockchain from scratch and setup my hpmn again, as i don't trust dashmate core reindex command working correctly on Testnet with Platform v0.23 (gave me problems in the past / not engage in a reindex).

I suspect either Testnet forked or my hpmn forked locally.
I hope this is specific to Testnet and does not apply to Mainnet.

[qwizzie]

After dashmate reset --hard and dashmate setup

So stuck at block 865847.

I tried dashmate core reindex and got not further then this

I am currently stuck in reindex mode, debug log not increasing, failed reindex from start.
If there is a known problem with dashmate core reindex, then this should have been hotfixed for Platform v0.23 on Testnet !

I also tried setting reindex=1 in the dash.conf at location /home/user/dashmate/testnet/core/ but dashmate start command overwrites that to a reindex=0 according my debug.log so it triggers no reindex.

The Dash bootstraps for Testnet (https://github.com/UdjinM6/dash-bootstrap) are out of date, so i cant use it right now.
reconsiderblock 00000081ad7ef9edb15150bcc9ee6ca8a7cdc5a825b9f10793edbd5fe3a69b3f (hash of block 865847) is also not working through Dashmate and its docker system.

Update : my hpmn finally synced passed block 865847 (i did another dashmate start and suddenly synced passed it) and is now in status 'running', so i can proceed with the next step (protx update_service_hpmn command).

I would still like some feedback on the 'dashmate core reindex' command problem, the sync problem after hitting block 865847 and the lack of options to reconsider a block, once we start using Dashmate. Also did Testnet fork or was it just my own hpmn ?

[thephez]

@qwizzie There should not have been any testnet forks in the last few days as far as I know (I didn't see issues with any of my nodes). Regarding dashmate-specific stuff, that tool is currently managed out of the platform repository. Issues related directly to it can be opened at https://github.com/dashpay/platform/issues.

[qwizzie]

@thephez

So what does this mean in my debug.log ? xkcd thought it indicated a fork, maybe a local fork ?

2023-04-10T12:06:15Z ERROR: ConnectBlock(DASH): coinbase pays too much at height 865848 (actual=6072799096 vs limit=1672799096), exceeded block reward, no triggered superblock detected

2023-04-10T12:06:15Z InvalidChainFound: invalid block=000000653fe0f3fb477b0e8bb4becc5220c2ede722fe2be5f8cac6f0cf8c09da height=865848 log2_work=57.50491778 date=2023-04-10T12:06:00Z
2023-04-10T12:06:15Z InvalidChainFound: current best=00000081ad7ef9edb15150bcc9ee6ca8a7cdc5a825b9f10793edbd5fe3a69b3f height=865847 log2_work=57.50491778 date=2023-04-10T12:01:40Z
2023-04-10T12:06:15Z ERROR: ConnectTip: ConnectBlock 000000653fe0f3fb477b0e8bb4becc5220c2ede722fe2be5f8cac6f0cf8c09da failed, bad-cb-amount (code 16)
2023-04-10T12:06:15Z InvalidChainFound: invalid

[shumkov]

@qwizzie v0.23 of Platform is abandoned while ago since it was multiple issues which are fixed in v0.24 but backporting is too time consuming. Please try to use dashmate v0.24.0-dev.17. BTW, you can still use DashCore RPC with dashmate to run the block reconsider command and others. Run dashmate status core and you'll see RPC port to connect to.

[qwizzie]

@shumkov

@qwizzie v0.23 of Platform is abandoned while ago since it was multiple issues which are fixed in v0.24 but backporting is too time consuming. Please try to use dashmate v0.24.0-dev.17. BTW, you can still use DashCore RPC with dashmate to run the block reconsider command and others. Run dashmate status core and you'll see RPC port to connect to.

Okay, will look into this. Thanks.

I do want to emphasize that i am only testing on Testnet and normally use 'npm update -g dashmate' & 'dashmate update' to update Dashmate to latest version on Testnet. With regards to the reconsiderblock command, I used it as follows

curl --user qwizzie --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "reconsiderblock", "params": ["00000081ad7ef9edb15150bcc9ee6ca8a7cdc5a825b9f10793edbd5fe3a69b3f"] }' -H 'content-type: text/plain;' http://127.0.0.1:9998/

But it gave an error (i think an RPC error). RPC port according 'dashmate status core' states RPC Service 127.0.0.1:19998 so that seems to match. Maybe it needed it without the http://

[thephez]

@thephez

So what does this mean in my debug.log ? xkcd thought it indicated a fork, maybe a local fork ?

2023-04-10T12:06:15Z ERROR: ConnectBlock(DASH): coinbase pays too much at height 865848 (actual=6072799096 vs limit=1672799096), exceeded block reward, no triggered superblock detected

2023-04-10T12:06:15Z InvalidChainFound: invalid block=000000653fe0f3fb477b0e8bb4becc5220c2ede722fe2be5f8cac6f0cf8c09da height=865848 log2_work=57.50491778 date=2023-04-10T12:06:00Z
2023-04-10T12:06:15Z InvalidChainFound: current best=00000081ad7ef9edb15150bcc9ee6ca8a7cdc5a825b9f10793edbd5fe3a69b3f height=865847 log2_work=57.50491778 date=2023-04-10T12:01:40Z
2023-04-10T12:06:15Z ERROR: ConnectTip: ConnectBlock 000000653fe0f3fb477b0e8bb4becc5220c2ede722fe2be5f8cac6f0cf8c09da failed, bad-cb-amount (code 16)
2023-04-10T12:06:15Z InvalidChainFound: invalid

🤔 I'm not sure. Not seeing that here. Maybe @PastaPastaPasta @UdjinM6 will have some comment

[pshenmic]

Is core 19 supported on testnet (which runs v18)?

[shumkov]

Testnet runs v19-rc

[qwizzie]

Since i don't think i will get a response from Pasta or UdjinM6 with regards to the error in my debug.log (ConnectBlock(DASH): coinbase pays too much at height 865848, followed by a number of 'invalidchain found', which most likely caused my HPMN to get PoSe banned on Testnet), i will just close this Github issue.

My HPMN was most likely on a (local ?) forked off chain on Testnet and my Windows wallet on the correct chain, this could explain the mismatch in status between my Windows wallet (PoSe banned) and my HPMN through Dashmate (Running / Ready).