-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Withdrawal Not Received in Testnet #2302
Comments
There are currently two bugs on Mainnet (and i suspect also on Testnet) : Bug 1 : Withdrawals will only be picked up by 2 quorums instead of 24 (a bug in Core). Which means there is only a window of time of about 2 hours per day where withdrawals can be picked up by the first quorum. Of those 2 quorums we only have 1 quorum enabled (having 2 quorums enabled gave issues). So basically withdrawals can only be picked up 1 hour per day. This will be fixed in Core v22 (which is not on Testnet yet so far i know and also not on Mainnet yet) Bug 2 : If Core interfers during Platform quorum 22, the Platform quorum will skip picking up withdrawals at first quorum. Note : we currently have a Platform chain stall on Mainnet, right in the middle of updating to v1.5.0 and DCG is now trouble shooting the problem. This means on Testnet, it could take longer for withdrawals to get picked up by first quorum, then you perhaps expect. On the other hand it should also go faster on Testnet, compared to Mainnet. So give it some time. I just hope Platform on Testnet will not chain stall as well, due to perhaps Testnet Evonodes updating to Platform v1.5.0 |
@qwizzie I don't think thats the case, because the withdrawal transaction on platform happened on the 30 November, so I believe that should be enough for the completing it even in core chain. Another thing, is it marked as COMPLETED in the withdrawal document, which I assume should be only when transaction successfully added in the Core chain. We can see transactionSignHeight is 1131337, and transactionIndex: 81, but if we look at the block itself, there are no transaction except the coinbase one |
@pshenmic the sign height is not the block in which the transactions are in. It's the block that the Platform chain knows about when the withdrawal was authorized. It often is mined in the next block, as can be seen here: https://blockexplorer.one/dash/testnet/address/yTaP3dCsRFLsdp7ZRXamNCrjUNNy5kHq9h These withdrawals went through on testnet, I am closing this issue. |
Withdrawal Not Received in Testnet When Testing Functionality
Expected Behavior
When requesting a withdrawal on the Dash Platform testnet, the withdrawal should be processed successfully. The corresponding amount should be received in my Dash Electrum wallet, and the transaction should be visible on the blockchain.
Current Behavior
I requested a withdrawal from the platform, and the withdrawal document exists and has moved to the status completed. However, the funds have not been received in my wallet, and there is no corresponding transaction visible on the blockchain.
Transaction of Credit Withdrawal
https://testnet.platform-explorer.com/transaction/3422E84DF3C422A2357634AC3504944FD14A9B6787EB29DCAA0FA84BA6CD6926
Block on Insight
http://insight.testnet.networks.dash.org:3001/insight/block/00000182164fb0022d9d547472741407febba2c251297959536161d61dc99c55
Document on Platform:
Possible Solution
There may be an issue with the withdrawal process not broadcasting the transaction to the network, or the transaction might be stuck and not included in any block. Investigating the transaction broadcasting and inclusion in blocks might help identify the problem.
Steps to Reproduce (for bugs)
Context
I am testing the withdrawal functionality of the Dash Electrum wallet on testnet. This issue is preventing me from verifying that withdrawals are working correctly, which is essential for testing and development purposes.
The text was updated successfully, but these errors were encountered: