Skip to content
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

Closed
LexxXell opened this issue Nov 2, 2024 · 3 comments
Closed

Withdrawal Not Received in Testnet #2302

LexxXell opened this issue Nov 2, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@LexxXell
Copy link

LexxXell commented Nov 2, 2024

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:

{
  '$id': 'E1FZpGixJSXmAwwEtCxqHpGM3XeFyFKLdNSCQMmzFJko',
  '$ownerId': '8eTDkBhpQjHeqgbVeriwLeZr1tCa6yBGw76SckvD1cwc',
  amount: 4000000,
  coreFeePerByte: 1,
  outputScript: 'dqkUT5vx/UWS1NGHPxErcfXG2a3sicmIrA==',
  pooling: 0,
  status: 3,
  transactionIndex: 81,
  transactionSignHeight: 1131337,
  '$revision': 4,
  '$createdAt': 1730311760674,
  '$updatedAt': 1730328609682,
  ***
  '$dataContract': {
    '$format_version': '0',
    id: '4fJLR2GYTPFdomuTVvNy3VRrvWgvkKPzqehEBpNf2nk6',
    config: {
      '$format_version': '0',
      canBeDeleted: false,
      readonly: false,
      keepsHistory: false,
      documentsKeepHistoryContractDefault: false,
      documentsMutableContractDefault: true,
      documentsCanBeDeletedContractDefault: true,
      requiresIdentityEncryptionBoundedKey: null,
      requiresIdentityDecryptionBoundedKey: null
    },
    version: 1,
    ownerId: '11111111111111111111111111111111',
    schemaDefs: null,
    documentSchemas: { withdrawal: [Object] }
  },
  '$type': 'withdrawal'
}

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)

  1. Request a withdrawal from the Dash Platform on testnet.
  2. Verify that the withdrawal document exists and reaches the completed status.
  3. Check the Dash Electrum wallet for incoming funds.
  4. Look for the transaction on the testnet blockchain explorer.

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.

@LexxXell LexxXell added the bug Something isn't working label Nov 2, 2024
@qwizzie
Copy link

qwizzie commented Nov 2, 2024

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.
This will be fixed in Platform v1.5.0 --> #2290

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

@pshenmic
Copy link
Collaborator

pshenmic commented Nov 2, 2024

@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

@QuantumExplorer
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants