| Pin | Token | Bridge | Bridge tx | Stage | Discovery took | Token entity | Labels |
|---|---|---|---|---|---|---|---|
| #90552 d ago | ■AKITAAkita Share Token
v99fyv8k58…w44626
no explorer
|
layerzerosolana → base | 3a3LypXrn9…jboExv | processedSKIPPED_DUPLICATE | 16 h | ■AKITA | — |
| #90332 d ago | ■AKITAAkita Share Token
a6hb5fwrjk…9dazsh
open
|
layerzerosolana → base | 5SchknU1pj…BXmnZu | processedSKIPPED_DUPLICATE | 16 h | ■AKITA | — |
| #89742 d ago | ■AKITAAkita Share Token
0xe7e44b29…d74626
open
|
layerzerobase → robinhood | 0xa116806e…13293c | processedSKIPPED_DUPLICATE | 15 h | ■AKITA | — |
| #86302 d ago | ■AKITAAkita Share Token
0x44710150…e84626
open
|
layerzerobase → solana | 0x530d3af7…10f3d9 | processedDISCOVERED | 14 h | ■AKITA | — |
| #84312 d ago | ■AKITAAkita Share Token
0xe7e44b29…d74626
open
|
layerzerounichain → base | 0xdf16c6c8…65571d | processedSKIPPED_DUPLICATE | 13 h | ■AKITA | — |
| #84302 d ago | ■AKITAAkita Share Token
0xe7e44b29…d74626
open
|
layerzerorobinhood → base | 0x537e3a47…1c104c | processedSKIPPED_DUPLICATE | 13 h | ■AKITA | — |
| #84292 d ago | ■AKITAAkita Share Token
0xe7e44b29…d74626
open
|
layerzeroethereum → base | 0x46aed2af…5a521a | processedSKIPPED_DUPLICATE | 13 h | ■AKITA | — |
| #84282 d ago | ■AKITAAkita Share Token
0xe7e44b29…d74626
open
|
layerzeroarbitrum → base | 0x6930f032…f58e42 | processedSKIPPED_DUPLICATE | 13 h | ■AKITA | — |
| #81062 d ago | ■AKITAAkita Share Token
akosgujdaj…cm4626
no explorer
|
layerzerosolana → base | 3ZdGEt89SA…uZMyk7 | processedDISCOVERED | 11 h | ■AKITA | — |
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. |