Deposit funding instructions
How an operator chooses which tokens investors can deposit and how the instructions API tells an investor where to send them.
An investor who opens a deposit screen needs to know two things: which wallet address to send funds to, and which token to send. A DALP InstanceA DALP Instance is one self-contained copy of the platform, deployed inside a boundary you choose and connected to ledger networks you approve.Read the concept answers both through one API read, which any front end built on the platform API can call to show the investor the same instructions. The Investor portal shows it in the Deposit dialog on the portfolio page; the Console does not read it yet.
The read lists one entry for each of the investor's active custody wallets and each token the organization accepts. Every wallet address belongs to that investor alone, so the address identifies the deposit and no separate reference is needed. The list is empty until the organization accepts at least one token.
Which tokens are accepted
A token is accepted for deposits in one of two ways.
| Source | Who sets it | What it covers |
|---|---|---|
Deployment setting custodyOps.depositAssets (environment variable CUSTODY_OPS_DEPOSIT_ASSETS) | The operator of the deployment | A JSON list of network and token address pairs. Only a token the indexer holds under the organization's own system is offered, so the setting can never expose a token that belongs to another organization. |
| Registered external token | An organization member with the tokenManager role | A token from outside the platform that the organization registered by hand on the network and has not dismissed. It is offered to that organization only, and only once the platform indexes the token's transfers, because a deposit of an unindexed token could not be credited. A token the platform detected automatically is not offered until someone registers it by hand. |
A token that qualifies both ways is listed once, with the details the indexer holds.
The feature is part of the custody operations surface and stays off until features.custodyOps is on for the deployment. Deposits to these wallets are credited only once deposit watching is running for them, which a later release adds, so keep the feature off in production until then.
Register an external token
Deposit instructions offer the organization's own external-token registry; custody operations keeps no token list of its own. Register a token on the External tokens page or with the external-token registration route in the generated API reference. Registration records the token in the on-chain registry and reads its name, symbol, and decimals from the contract; those are the details investors see. Registering a token the platform detected automatically accepts it without a new registration. Dismissing a token stops it from being offered, and registering it by hand again offers it again.
Read the instructions
An investor reads their own instructions with the deposit instructions route in the generated API reference. It also answers on a network where the organization has no system deployed yet, offering only its registered external tokens there. Each wallet is the investor's custody account on the requested network, and an account with a smart wallet lists the smart wallet rather than its signer. Each entry names the network, the wallet that receives the transfer, and the token to send with its address, name, symbol, and decimals. Send only the listed token on the listed network: a transfer of any other token to the wallet address is not credited as an accepted deposit.
SSO
Configure an external OIDC identity provider for the DALP Console, and understand that a complete entry replaces local sign-in for the whole deployment.
Observability
The OpenTelemetry pipeline a DALP instance exports by default: traces, metrics, and logs, and how the admin debug bundle auto-wires to an in-cluster stack.