Skip to main content
If your source-chain transaction is confirmed but the deposit has not shown up in your Intention balance yet, read this page before opening a ticket. Nine times out of ten the answer is “the bridge has not finished attesting yet, and it will resolve on its own.”
The Intention bridge has not yet launched on mainnet. The mechanics described below are the ones that will be in force once deposits are live. Testnet timings are shorter than the numbers given here.

​
How the bridge credits a deposit

A full description lives on the Bridge page, but the short version is this: validators run light clients against every supported source chain. When one of them observes a deposit transaction to the canonical bridge address, it signs an attestation that names the source-chain txid, the depositor, the asset, and the amount. Once attestations from a 2f+12f+1 stake-weighted set of validators have been collected on the Intention side, the deposit is credited to your account atomically inside a block. There is no human in the loop and no multi-sig to wait on. This means a deposit becomes visible on Intention only after two things have both happened:
  1. The source chain has produced enough confirmations for the bridge’s light-client logic to treat the deposit as final. Different chains use different confirmation rules; fast chains may take seconds, slower chains can take tens of minutes.
  2. Enough validators have broadcast their attestations and the aggregate crossed the threshold. In practice this is a small additional latency on top of the source-chain finality.

​
When to worry, and when to wait

Wait if either of these is still true:
  • The source-chain block that contains your deposit is inside the per-chain confirmation window documented on the Bridge page.
  • The source-chain finality clock has passed, but fewer than about fifteen minutes have gone by since then. Validator attestations can take this long in normal operation, and the exact ceiling is published per chain.
Open a ticket if all of the following are true:
  • Your source-chain transaction is well past the per-chain confirmation window.
  • The documented attestation budget has elapsed on top of that.
  • The destination address is correct and is one you actually control on Intention.
  • The asset is one that the bridge supports from that chain.

​
What to include in the ticket

Send the following to support@intention.xyz:
  • The source chain the deposit came from.
  • The source-chain transaction hash.
  • The source-chain block number at which the deposit was included.
  • The destination address on Intention you expected to receive the credit.
  • The asset and amount of the deposit.
  • Your account address on Intention, if it is different from the destination address.
  • A screenshot of the source-chain explorer showing the confirmed transaction.
With those fields we can look up the attestation state and tell you exactly where it is stuck.

​
What we cannot do

If the destination address in your source-chain transaction is wrong — for example, a typo, or an address that belongs to someone else, or an address on a chain the bridge does not observe — the bridge has nothing to attest, and credit will never be produced automatically. Those cases go through Wrong network or asset, not this page. The validator-attested process is deliberately strict so that only complete, well-formed deposits get credited.