External tokens registers a token your organisation's system did not issue, so operators track it beside the assets they issued. That includes a token another organisation issued on its own DALP system. Once registered, your organisation's holding of that token shows as its own, and its totals count the balance it holds, not the issuer's whole supply. Whether the holding can move stays with the issuing system's rules, so its compliance, its halt and its freezes still apply. All assets lists registered external tokens next to the issued ones.
A registration is a record, not a redeployment. The platform sends no transaction to the external contract and adds no DALP feature to it, and the token's page has no mint, burn, transfer or emergency halt control. Registration runs on the network you selected, and the token shows only on that network. It writes the address and token type to the on-chain registry from the wallet you act with. The registry has no removal, so a registration of the wrong address cannot be reversed. Dismiss only hides the token.
The External tokens page with its summary strip, its token table and the “Register external token” button.
The title row carries “Register external token”. The “Tokens” cell counts the registered tokens and how many were auto-detected, and “To review” reads “Nothing to review”. Each table row shows the token and its type, its status, the registration date with who registered it, and the supply at registration.
Steps
Read the table and the review findings
Open “Assets”, then External tokens. The page title is followed by the name of the network you selected. Below it, a summary strip has two cells. “Tokens” counts the tokens and shows how many were auto-detected and, for an account with the Asset manager role, how many are dismissed. “To review” counts the tokens that need a decision and splits them into lookalikes and tokens whose indexing stopped, or reads “Nothing to review”.
Under the strip, each lookalike and each token with stopped indexing has its own finding. A finding's title shows the short contract address of the token it is about, so two findings for tokens with the same name read differently. Every finding offers Open token, which opens the token's page. A lookalike finding also offers “Dismiss” to an account with the Asset manager role. On a narrow screen, two or more findings fold into one that reads “2 tokens need review”.
The table has four columns:
- Token shows the name, with the symbol and type under it, an “External” mark, and the “Lookalike” badge when it applies.
- Status shows one value, the first that applies of “Dismissed”, “Paused”, “Indexing stopped”, “Catching up” and “Active”.
- Registered shows the date and, under it, “Auto-detected” or the address that registered the token.
- Supply at registration shows the supply the contract reported when the token was registered, and does not update.
The View control can show “Contract address”, “Decimals”, “Standards”, “Indexing”, “Type”, “Origin”, and “State”. “Origin” is “Auto-detected” or “Manual”. “State” is “Active” or “Dismissed”. Only an account with the Asset manager role sees dismissed tokens here or can filter to them. Search the table by name, symbol, or address, and filter by status, type, origin, or state.
Select Register external token, which shows only to an account with the Asset manager role, to open the registration side panel. Without the role, an empty table reads “An asset manager registers them.”
Enter and check the contract
Choose Quick add a known token to pick from a built-in list of well-known tokens on the active network, or enter the deployed address in “Contract address”. The panel reads “Check a token contract on” followed by the network name. Quick add fills the address, and the type when it knows it, then runs the same eligibility check as manual entry. If you replace a suggested address, choose the type again because the field empties. About 350 milliseconds after you stop typing, the panel runs a live check against the chain and shows a preview card beneath the field. Once the contract answers ERC-20 metadata, the card shows its name, symbol, decimals and total supply, with a “Smart” badge when the contract implements DALP's SMART token standard.
The card ends in one of four states: still inspecting, unable to inspect the contract at all, eligible for registration, or blocked with one exact reason. An inspection failure is a lookup problem and says nothing about the contract. The check runs the same reads the registration runs, so an eligible card means those reads passed at that moment. A registration can still fail on chain after you sign, for example when someone registers the same token between the check and your signature. A blocked verdict names one of five causes:
- No contract at this address: no contract code at that address.
- Already registered: the organisation already registered the token by hand and it is active.
- Already managed by this platform: the token is one of your organisation's system's own factory-deployed or system contracts.
- Not a token contract: the contract does not answer the ERC-20 name, symbol and decimals a registration reads, as happens at a wallet contract.
- Token details too long: the contract reports a name longer than 50 characters or a symbol longer than 24, which DALP never shortens.
An auto-detected or dismissed token stays eligible, because registering it by hand brings it back. Compare the resolved name, symbol and decimals against the approved deployment record before continuing.
Use the Token type dropdown to choose from a fixed list: Bond, Equity, Fund, Stablecoin, Deposit, Cryptocurrency, or Other. The field has no default, so you must choose one. It sets a tracking category for this registration, and the chain enforces nothing based on it. “Register token” stays disabled until the address check resolves to eligible. A blocked contract names its single reason and keeps the button off until a different address clears the check. Selecting it with no type chosen shows “Choose the token type.”
The panel opens with the “Quick add a known token” list, then the required “Contract address” and “Token type” fields.
Register the token
Select Register token, then complete “Confirm registration” with your wallet. The Console records the existing contract in the external-token registry. Settlement lands one of three ways. An immediate success shows “External token registered successfully” and the table refreshes to include the new row. Historical indexing can continue after registration succeeds. An on-chain failure shows “Token registration failed on-chain. No changes were made.” Read the reported error and correct its cause before retrying. A still-pending transaction shows “Registration is still processing. Track progress in Actions.” instead, and the table updates once that transaction settles. Follow it on Actions.
The address check runs about 350 milliseconds after you stop typing, then an eligible contract turns “Register token” on and a blocked one names its single reason.
Review auto-detected tokens and lookalikes
Automatic registration is off by default. It runs only when your operator sets FEATURE_ to true (the features. setting). While it is off, a token sent to a managed wallet is not registered until an account with the Asset manager role registers it by hand, and no row shows Auto-detected.
With the setting on, when an ERC-20 token or an ERC-3643 permissioned token that this platform did not issue lands in a wallet the platform manages for your organisation, the platform registers it on its own, at most 20 per organisation per day. The organisation's operations signer writes it to the on-chain registry, and no person confirms it, so anyone can start this by sending a token to a managed wallet. A token over the daily cap is not registered until the cap allows. Such a row shows Auto-detected under its registration date and is active straight away.
When another of the organisation's tokens has the same symbol or name, ignoring letter case and Unicode look-alike forms, the row also carries a “Lookalike” badge, and the list and the token's page show the Possible lookalike token warning. The warning shows both values exactly as stored, names the existing token as “Name (SYMBOL)”, and links to its page. Compare the addresses before you use the token, because a lookalike can be a scam, and dismiss it when it is one.
Dismiss or restore an external token
A settled registration's address has no edit control. The per-row menu offers “Copy address” and, when the network has a block explorer configured, “View on Explorer”. An account with the Asset manager role also sees Dismiss, which hides the token from the organisation's holdings, portfolio, holder lists, token catalogue, token details and marks. Dismissing also stops the platform from registering it again. Accounts with the Asset manager role still see a dismissed token in this table. The registration itself stays on chain. The organisation's portfolio value drops the dismissed token once the next block is indexed, and later price changes or transfers of it no longer move that value.
To bring a dismissed token back, choose Restore in its row menu or in the header of its page. It opens the registration panel titled “Restore external token” with the address and type already filled in, and the token becomes active and returns to the portfolio value once you confirm with “Restore token”. Registering the same address by hand does the same, and registering an auto-detected token by hand accepts it the same way. In each case the token takes the type you choose. When your organisation's system already holds the token in its registry and that type differs from the one on chain, the platform also queues a transaction that updates the type in the on-chain registry. The table then shows the type the on-chain registry ends with, so if two type changes for the same token land close together, the later one wins. When indexing runs behind, the registration is reported as queued, and the new type appears once indexing catches up.
Read a registered token's page
Select a token's row to open its page. The header shows the token mark, the name, the ticker when it differs from the name, and one status badge. Select the badge to see the registry state, the contract state, and the indexing state. The “Actions” menu offers “Copy address” and, when the network has a block explorer, “View on Explorer”. An account with the Asset manager role also sees a “Dismiss” button in the header, or “Restore” on a dismissed token. While a lookalike warning shows, its “Dismiss” takes the place of the header button. A strip under the header shows “Supply at registration”, with the date it was read when the platform recorded one. When the token is paused or its indexing stopped, a finding above the tabs says so, and paused takes precedence. An auto-detected token that looks like another token also shows the “Possible lookalike token” warning.
The Overview tab has a “Token” card with the full contract address and a copy button, the status, the token type, and the standards with any detected interfaces. A “Registration” card shows the registration date and time, the registering account, the decimals, and the indexing state with the reason it stopped. A “Recent activity” card links to the “Activity” tab, which lists the token's events from the block your organisation's system registered it. Earlier transfers stay out, including those of your own wallets, and the same cut-off applies to the “Activity” page and to investor statements. An account without the Asset manager role reads the page without “Dismiss” and “Restore”, and the “Registration” card says that asset managers register, change, and dismiss external tokens.
Troubleshooting
Register token cannot be selected
Signal: the button stays disabled even though the address and token type fields look filled in. Cause: the eligibility check has not resolved yet, or it resolved blocked. A blocked verdict names one of the five reasons that Enter and check the contract lists. Fix: wait for the preview card to finish, then read the exact reason it names before assuming the form itself is wrong.
The preview card cannot inspect the contract
Signal: the card reports a lookup failure instead of naming an eligibility reason. Cause: usually the selected network differs from the network the contract is deployed on, or a read failed for a moment. Fix: confirm the selected network matches the deployment record, then retry the address.
Check whether an address is already registered
Paste the address into Contract address in the registration panel. When the organisation registered the token by hand and it is active, the preview card reads “Already registered”. An auto-detected or dismissed token stays eligible, so search the table by address to find it.
Nothing new appears after Register token
Signal: the confirmation completed, but the table still does not show the new row. Cause: settlement is not always immediate. A still-pending transaction shows “Registration is still processing. Track progress in Actions.” instead of the success message, and the table updates once it settles. Fix: check Actions for the pending transaction before you repeat the registration.
The resolved contract details do not match the approved deployment record
Signal: the preview card names a symbol, decimals, or supply that disagrees with the record you were given. Cause: usually the wrong address, sometimes a deployment record that is stale or wrong itself. Fix: stop and do not submit. A registration cannot be removed, on chain or in the Console, so resolve the mismatch against your organisation's own deployment record, or with whoever issued it, before you continue.
A token you dismissed is gone from the table
Signal: a dismissed token no longer appears in the table. Cause: only an account with the Asset manager role can see dismissed tokens, and it can filter “State” to “Dismissed”. Fix: sign in with an account that holds the role, filter “State” to “Dismissed”, and choose Restore in the token's row menu or on its page.
Frequently asked questions
Do I need to register the same contract again on another network?
Yes. Registration is per network, so a record applies only to the network selected in the account menu when you submit. Deploying the identical contract address on a second network is a separate registration with its own eligibility check and its own transaction, and it does not appear in this table until you register it while that network is active.
If I close the registration panel I opened from Issue asset, do I lose that entry point?
No. Closing the panel leaves you on the Issue asset step you opened it from, and the same button opens it again with the type set to Stablecoin. The panel never changes the page address, so reloading does not reopen it. Register external token on this page opens the same panel with no token type chosen, because the field has no default.