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.
External token registration adds an existing EVM token contract to the platform's external token registry. Use this workflow when the token already exists on the active network and was not created through a DALP asset factory. The registration makes the token visible in the external token list, token detail views, and registry-backed flows that accept external assets. It does not prove the asset class, change token supply, or make the token a DALP-factory asset.
The operator requirement is to verify the address before submission, register the token through wallet verification, then confirm the registry result in the list, detail, and event evidence views. This page covers that complete dApp workflow.
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 does not deploy a new token contract, move balances, or import holder history by itself. It records an existing token in the external token registry.
Quickstart
- Open External Tokens.
- 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.
The sheet uses the contract preview as a submit gate. Submit stays disabled until the preview resolves and the address is eligible for registration. DALP blocks addresses with no deployed code, tokens already registered in the external registry, system-managed contracts, and tokens deployed through DALP factories.
Contract preview checks
The contract preview checks the address before you submit. It can show token name, symbol, decimals, total supply, SMART-family compatibility, and the registration verdict when those reads are available.
| 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.
If a prerequisite flow sends you to External Tokens because a prerequisite token is missing, the sheet can open with the token type already selected. Confirm the type before submitting. Unknown saved-link values fall back to Other so stale links do not block registration.
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.
Use the external token list to confirm the token appears with the expected contract address and assigned token type. The list can show token name, symbol, decimals, supply, status, registration time, detected interfaces, copy-address actions, block explorer actions, and a link to the token detail page when that data is available.
Open the token detail page to review the registration metadata, compatibility fields, and indexed events for the external token address. These views are based on the active registry and indexer state. They can show the registration and current token facts DALP has indexed, but they do not import historical balances, copy the issuer's compliance rules, or make the token equivalent to a DALP-created asset.
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. It does not infer the business type from the contract address alone.
- 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.