bitpontSubmitted, Confirmed or Completed? Understanding DeFi Transactions
Separate wallet approval, blockchain confirmation, protocol execution and destination delivery across Bitpont products.
On this page
One operation can have several outcomes
| Evidence | What it establishes | What it does not establish |
|---|---|---|
| Wallet connected | The selected account is accessible | Permission to move funds |
| Approval confirmed | A permission was recorded | A deposit or swap completed |
| Transaction included | A node reports a block containing it | Finality or the intended financial result |
| Order accepted | The venue recorded the order | The full quantity traded |
| Bridge source confirmed | The source step occurred | Destination funds arrived |
| Claim request recorded | A withdrawal process exists | Funds are already spendable |
Why repeated submission can be dangerous
A timeout describes a missing response, not necessarily a missing transaction. The original request may still be pending or may have succeeded. A second signature can create a second order or payment. Preserve the original identifiers and reconcile the specific operation before replacing it.
Read the evidence for the product
For a swap, inspect the transaction and resulting token changes. For a GMX request, inspect keeper execution and the resulting position. For a bridge or withdrawal, verify the destination chain, token, recipient and delivery evidence. For a delayed claim, check eligibility and the claim transaction. A generic green status is not a substitute for those product-specific results.
Keep a recovery record
Record wallet, network, product, order or request ID, transaction hashes and exact amounts. Local browser records help continue supported flows but are not an independent ledger or backup of your wallet. A different device may not have them. Do not erase pending records merely to dismiss a warning.