Register external tokens
Add an existing EVM token to DALP from the External Tokens workspace so operators can track it beside assets created in DALP.
Register an external token when an existing EVM token contract must appear in DALP beside assets created through DALP factories. Use this workflow when the token already exists on the active network and was not created through a DALP asset factory.
Registration makes the token visible in the list, detail views, and registry-backed flows that accept external assets. It leaves asset classification, supply, holder history, and issuer controls unchanged.
Verify the address before submission. Register the token through wallet verification, then confirm the registry result in the list, detail, and event evidence views.
Before you start
You need:
- access to External Tokens in the dApp
- a wallet or smart wallet executor with the system token manager role
- the token contract address on the active EVM network
- the correct token type, such as bond, equity, fund, stablecoin, deposit, cryptocurrency, or other
Registration keeps the existing contract in place. It does not deploy a new token, move balances, or import holder history.
For the registry model and control boundary, see external-token registration in the ERC-3643 compliance model.
Quickstart
- Open External Tokens from the token workspace.
- Select Register External Token.
- Enter the token contract address.
- Choose the token type that describes the asset.
- Wait for the contract preview to finish.
- Submit the form and complete wallet verification.
- Confirm the token appears in the list, then open the token detail page for registry evidence.
The sheet uses the contract preview as a submit gate. Submit stays disabled until the preview resolves and the address is eligible for registration. It also stays disabled while the form is unchanged, invalid, or waiting on the wallet submission.
DALP blocks addresses with no deployed code, entries already recorded in the external registry, system-managed contracts, and contracts deployed through DALP factories.
If you arrive from a prerequisite prompt, External Tokens can open the registration sheet automatically with a suggested token type. Review the suggested type before submission. Supported dApp choices are Bond, Equity, Fund, Stablecoin, Deposit, Cryptocurrency, and Other. If the saved link contains an unknown type, the form falls back to Other rather than failing the workflow.
Contract preview checks
The contract preview checks the address before you submit. The preview can show token name, symbol, decimals, total supply, SMART-family compatibility, and the registration verdict.
| Preview result | What DALP observed | What DALP does | What you should do | What it does not mean |
|---|---|---|---|---|
| Eligible | The address has deployed bytecode and is not already known as a blocked registration target. | Enables submit when the form is otherwise valid. | Continue with wallet verification. | Eligibility does not prove the token's business classification. Choose the token type deliberately. |
| No deployed code | The address has no deployed bytecode on the active chain. | Keeps submit disabled. | Confirm the active network and paste the deployed token contract address. | The external token registry is not necessarily unavailable. |
| Already registered | The address is already recorded in the external token registry. | Keeps submit disabled. | Search the external token list and open the existing token record. | The token does not need a second registration. |
| System-managed | The address belongs to a system-managed contract or a token created through DALP factories. | Keeps submit disabled. | Use the system-managed token workflow or the asset detail workspace for that token. | The token is not an external-token candidate. |
Compatibility detection is informational. SMART-family detection helps operators understand how the contract presents itself to DALP, but registration does not retrofit missing interfaces, holder rules, reserve evidence, or issuer controls.
Review the registered token
After registration, use the external token list to confirm the token appears with the expected contract address and token type. The newest registration appears first by default. If the list is filtered or paginated away from the new token, clear filters or search for the contract address before opening details.
Use the row options to complete the check:
| Option | Use it for | What to verify |
|---|---|---|
| View details | Open the external token detail page for the contract address. | Registration metadata, compatibility fields, and indexed event evidence match the token you intended to register. |
| Copy address | Copy the contract address without retyping it. | The copied address matches the source contract address used in approval packs or settlement setup. |
| View on explorer | Open the active network's block explorer for the contract address. | The explorer shows the expected deployed contract on the same network DALP is using. |
After submission
After wallet verification succeeds, the platform queues the registry transaction that calls the external token registry. When the request is accepted, the dApp refreshes the external token list, closes the sheet, and resets the form. If registration fails, the sheet stays open and shows the error message with a reference when one is available.
Open the token detail page from the row or View details option to review registration metadata, compatibility fields, and indexed events for the external token address. These views are based on the active registry and indexer state. They show the registration and current token facts DALP has indexed while leaving historical balances, issuer compliance rules, and DALP-created asset status outside the registry result.
Operational notes
- Choose the token type from the asset's business purpose. The platform accepts bond, equity, fund, stablecoin, deposit, cryptocurrency, and other as dApp choices. The contract address does not determine the business type.
- Register only addresses from the active EVM network. The preview and registry call use the active system context.
- External registration does not make a token system-managed. It keeps the token separate from assets deployed through DALP factories.
- API integrations can use the same preflight and registration flow through the External tokens API.
Related guides
Asset detail workspace
Review an issued asset, inspect token tabs, and understand which operator workflows are available for the current token.
Review address book contacts
Open a saved contact in DALP, confirm its wallet address and timestamps, then edit or delete the contact when the local address book entry is wrong.