Deposits
The Vault monitors wallet addresses on all enabled networks for incoming transactions. When a deposit is detected, it is recorded in the transaction history and a webhook event is emitted.
How Deposit Detection Works
The Vault maintains a connection to a node (or node provider) for each enabled network. It uses the following detection methods:
| Network | Detection Method |
|---|---|
| Ethereum | Subscribes to event logs for native ETH transfers and ERC-20 Transfer events matching known wallet addresses |
| Bitcoin | Polls the Bitcoin node at configurable intervals for incoming transactions |
| TRON | Polls for account transactions; filters TRX and TRC-20 transfers |
Detection latency is typically under 30 seconds after the transaction is first seen by the network node.
Confirmation Policy
Deposits are recorded immediately on detection but are not considered confirmed until the required number of block confirmations is reached. Unconfirmed deposits appear in the transaction list with status detected.
Default confirmation thresholds (configurable per deployment):
| Network | Default Confirmations | Approximate Wait |
|---|---|---|
| Ethereum | 12 | ~2.5 minutes |
| Bitcoin | 1 | ~10 minutes |
| TRON | 19 | ~1 minute |
Confirmation thresholds are configurable per network. Lowering thresholds increases speed but reduces protection against chain reorganisations.
A TRANSACTION_DETECTED webhook fires when an incoming transaction is first seen; once it reaches the confirmation threshold and the balance updates, a BALANCE_UPDATED webhook fires.
Deposit Transaction Statuses
| Status | Meaning |
|---|---|
detected | Transaction seen on the network; below confirmation threshold |
confirmed | Confirmation threshold reached; balance updated |
failed | Transaction was dropped or reversed |
ERC-20 and TRC-20 Token Detection
ERC-20 and TRC-20 token deposits are detected automatically for any token contract listed in the Token Registry configuration. The token registry is a list of contract addresses and their metadata (symbol, decimals).
To add a token to the registry, contact your deployment administrator or update the token registry via the deployment configuration. Each token entry requires the token symbol, decimals, and contract address.
Webhook Notifications
Configure a webhook to receive deposit events in real time: TRANSACTION_DETECTED
fires when an incoming transaction is first seen on one of your addresses
(possibly unconfirmed), and BALANCE_UPDATED fires once it confirms and the
balance changes. Payload structure, signature verification, and retry behaviour
are documented in the Webhooks API reference.
Querying Deposits via API
Wallet balances and per-asset balances can be read programmatically — see the Wallets API reference.