InstantSend not working - always confirms to 1 of 6

[sunk818]

InstantSend worked pre-evo. At some point InstantSend seemed to stop working. Any transaction I try to send (all inputs have 6 or more confirmations), will never confirm 6 of 6 on the next block confirmation. It will always be 1 of 6. I realize InstantSend is not guaranteed always, but it should work most of the times with the masternodes online.

Status: 3/unconfirmed (verified via InstantSend), broadcast through 7 nodes
Date: 9/21/2019 16:49
Total debit: -702 795.39167925 BBP
Total credit: 702 795.39167925 BBP
Transaction fee: -0.00376000 BBP
Net amount: -0.00376000 BBP
Transaction ID: 262b8e5253dd1bb48ab396be47da87801db7c7924311f4cd45685ded19ef9ae3
Output index: 0
Transaction total size: 375 bytes

Height: 146437
Difficulty: 3493.53
Time: 09-21-2019 23:58:25
Subsidy: 1374.2299

https://docs.dash.org/en/stable/wallets/dashcore/privatesend-instantsend.html#instantsend

[biblepay]

Reproduced - I confirm that I only receive one confirm after 1 block also.

Hmm, its hard to believe that no one complained about this yet. But I believe its not being used very often right now.

I remember when I sent BBP to Tokok I clicked instant send and it didn't go instantly and I assumed Tokok didn't accept IX, but now that I see this issue, its possible its broken.

Ill check into this.

[biblepay]

Please re-test after block 148,000 after Apollon upgrades.

[OrbisPictus]

I've tried to send those my sub 1 BBP tx to myself with instantsend (all txs had more than 6 confirmations) but Instantsend failed (InstantSend authentication failed).

[biblepay]

@OrbisPictus Checking.

[biblepay]

@sunk818 Yes, I see that, and whats the question? (I see that it appears like a normal transaction) - are you asking why it does not appear as 6 immediately? If thats the question its because IX is not handled in the GUI properly - and we need a code release. Im still testing the change in Testnet, but I believe at this early stage - IX works and all we have is a cosmetic problem. (Although I do believe we need a longer timeout on each IX sig, and, a different quorum size in prod to make IX reliable).

[biblepay]

I think our last release only resolved half of the problem; part of the problem is Dash has 4500 masternodes while we have 150. So they want 25 sigs in certain circumstances and we apparently cant sign 25 in only 60 seconds with our small farm.

Let me look into the quorum size next.

[biblepay]

I modified TestNet in 1.4.7.6 to give us more time before expiration. Lets test this in the next version in testnet.

[biblepay]

Fixed.