| Pin | Token | Bridge | Bridge tx | Stage | Discovery took | Token entity | Labels |
|---|---|---|---|---|---|---|---|
| #73622 d ago | SEDA
0x306acd0c…a898c0
open
|
hyperlanebase → ethereum | 0x3b07bd36…8560de | processedSKIPPED_DUPLICATE | 9 h | SEDA | symbol_cluster |
| #63482 d ago | SEDA
0x14862c03…1afcd7
open
|
hyperlaneethereum → base | 0x796858dd…924e5d | processedSKIPPED_DUPLICATE | 1 h 19 min | SEDA | symbol_cluster |
| #62522 d ago | SEDA
0x14862c03…1afcd7
open
|
layerzeroethereum → hyperevm | 0x0a8c1d00…4cfb28 | processedSKIPPED_DUPLICATE | 31 min | SEDA | — |
| #62492 d ago | SEDA
0x306acd0c…a898c0
open
|
hyperlanebase → ethereum | 0x63ae10f4…721eb4 | processedSKIPPED_DUPLICATE | 32 min | SEDA | — |
| #62482 d ago | SEDA
0x14862c03…1afcd7
open
|
hyperlaneethereum → base | 0x5673760e…416cdc | processedSKIPPED_DUPLICATE | 32 min | SEDA | — |
| #62452 d ago | SEDA
0x306acd0c…a898c0
open
|
hyperlanebase → ethereum | 0x00a56f98…8b99c5 | processedSKIPPED_DUPLICATE | 33 min | SEDA | — |
| #62412 d ago | SEDA
0x14862c03…1afcd7
open
|
hyperlaneethereum → base | 0xe806f43c…5521e2 | processedSKIPPED_DUPLICATE | 33 min | SEDA | — |
| #61762 d ago | SEDA
0x306acd0c…a898c0
open
|
hyperlanebase → ethereum | 0x9197d8d9…dd318f | processedSKIPPED_DUPLICATE | 43 min | SEDA | — |
| #47352 d ago | SEDA
0x306acd0c…a898c0
open
|
hyperlanebase → ethereum | 0x02fc58d1…0b38b1 | processedSKIPPED_DUPLICATE | 3 h 23 min | SEDA | — |
| #44212 d ago | SEDA
0x306acd0c…a898c0
open
|
hyperlanebase → ethereum | 0xa02fe83b…082bfd | processedDISCOVERED | 4 h 1 min | SEDA | — |
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. |