| Pin | Token | Bridge | Bridge tx | Stage | Discovery took | Token entity | Labels |
|---|---|---|---|---|---|---|---|
| #86922 d ago | dmt-nat
0x600e3b55…a3f882
open
|
portal_bridgebinance → ethereum | 0x1c6c8d0d…0a3879 | processedSKIPPED_DUPLICATE | 14 h | dmt-nat | deployer_burst |
| #73192 d ago | dmt-nat
0x249130f5…ad1247
open
|
portal_bridgeethereum → binance | 0xf1523763…39f10d | processedSKIPPED_DUPLICATE | 9 h | dmt-nat | deployer_burst |
| #64042 d ago | dmt-nat
0x249130f5…ad1247
open
|
arbitrum_bridgeethereum → arbitrum | 0x7917401e…eed254 | processedDISCOVERED | 1 h 34 min | dmt-nat | — |
| #55212 d ago | dmt-nat
0x600e3b55…a3f882
open
|
portal_bridgebinance → ethereum | 0xb3d9b7ab…2ac8c2 | processedSKIPPED_DUPLICATE | 2 h 3 min | dmt-nat | deployer_burst |
| #55202 d ago | dmt-nat
0x600e3b55…a3f882
open
|
portal_bridgebinance → ethereum | 0xf2986939…687b53 | processedSKIPPED_DUPLICATE | 2 h 3 min | dmt-nat | deployer_burst |
| #55192 d ago | dmt-nat
0x600e3b55…a3f882
open
|
portal_bridgebinance → ethereum | 0x13b85159…bb39c1 | processedSKIPPED_DUPLICATE | 2 h 3 min | dmt-nat | deployer_burst |
| #49412 d ago | dmt-nat
0x249130f5…ad1247
open
|
portal_bridgeethereum → binance | 0x2efb257e…a2e8bf | processedSKIPPED_DUPLICATE | 3 h 9 min | dmt-nat | deployer_burst |
| #48472 d ago | dmt-nat
0x249130f5…ad1247
open
|
portal_bridgeethereum → binance | 0x17add83b…33d8e0 | processedSKIPPED_DUPLICATE | 3 h 29 min | dmt-nat | deployer_burst |
| #48462 d ago | dmt-nat
0x249130f5…ad1247
open
|
portal_bridgeethereum → binance | 0xf1cc26f7…9cd3c2 | processedSKIPPED_DUPLICATE | 3 h 29 min | dmt-nat | deployer_burst |
What the stages, outcomes and labels mean
Stages
| rejected | Ingest refused the record; the reason is stored and listed below. |
| waiting | Accepted and queued; discovery has not reported an outcome yet. |
| processed | Discovery reported an outcome, listed below. |
Discovery outcomes
| DISCOVERED | Contracts were found and written: a token entity was created, or an existing one gained a contract or a route. |
| SKIPPED_DUPLICATE | The token was already known; the pin was linked to the existing entity and no new search was run. |
| SKIPPED_MAJOR | The token is a major (stablecoin, wrapped native); discovery does not search for those. |
| SKIPPED_NO_SVM | A Solana pin arrived while the Solana reader was not configured, so it could not be resolved. |
| SKIPPED_NO_TOKEN | The pin named no token address, and the bridge index could not supply one. |
| SOLANA_UNRESOLVED | The Solana RPC could not say which mint the transaction moved; the pin is kept and can be reprocessed. |
| SKIPPED_BLOCKED | The mint was blocked outright; discovery wrote nothing. |
| SKIPPED_EXCLUDED | The token is excluded: the pin is recorded against it and nothing more is searched. |
| SKIPPED_DENIED | The operator detached this contract from the token it would have joined; nothing was written. |
| NOT_A_TOKEN | The address the pin named holds no ERC20 or SPL mint. |
| UNKNOWN | Discovery could not finish: an index or an RPC did not answer, or the run failed. Not a negative result; reprocess it to try again. |
| backfilled | Marked processed by the progress migration: the token already had a contract or evidence when the tracking columns were added. |
Reject reasons
| SELF_LOOP | Source and destination are the same chain, so nothing was bridged. |
| UNKNOWN_CHAIN_SLUG | The source or destination chain is not one in chains.json, so nothing could be looked up there. |
| MALFORMED_ADDRESS | The record failed format checks: an address is not a valid EVM or base58 address, or the record is not the shape the feed promised. |
| DUPLICATE | The same transfer (chain, transaction, log index) was already stored; there was nothing new to learn. |
| NOT_A_TOKEN | There is no ERC20 or SPL mint at the token address. |
| KNOWN_MAJOR | A stablecoin, wrapped native, or another major that is bridged constantly; excluded as noise. |
| BLOCKED | The contract was blocked outright. The pin is kept as a tombstone so the refusal stays countable. |
Labels
Accepted and sent to discovery like any other pin. Listed under "labelled" because it carries a cluster label, which lowers its priority and never rejects. A pin with two or more labels starts at normal priority instead of high, which only sets how soon discovery and the liquidity check get to it.
| round_supply | The amount sent is a 1 followed by 24 or more zeros in base units (with 18 decimals: exactly 1,000,000 tokens, 10,000,000, and so on): a whole minted supply moving at once. |
| deployer_burst | The same sender bridged three or more different tokens in the last 24 hours. |
| symbol_cluster | The symbol is within two edits of another token seen in the last 24 hours: a lookalike. |
| provider_known | Reserved for a token a provider already lists; nothing sets it today. |