Chains we are watching
How to read this
This page lists chains we are watching and not measuring. Three badges carry the difference: reported by means someone else wrote it and we are showing you where; from a document we hold means we read it out of a document we hold; we asked, it answered means we asked a question of an endpoint or of our own corpus today. Nothing here is a measurement of these chains, because we have never crawled any of them.
Chains we are watching 6 entries · 25 dated statements · KB as of 2026-11-18 08:37:10
The one worth reading first
DTCC → Solana (a connection, not a chain) Not a candidate announced — targeted second hal… as of 2026-11-14
Decision: Not a candidate — decided by (source: candidate-chain registry), on the card a named person authorised (first-party fetch, dtcc.com) on 2026-11-14.
This is the best institutional story the site has, and the chain inside it is one we MEASURE — which is why it leads a page about chains we do not.
What measuring it would take: The connection is not measurable: it does not exist yet. What is measurable is Solana today, and that is crawled nightly.
Coverage card: a watch dated 2027; no measurement claim is made about a connection that is not live
Not a claim that Solana is DTCC's chain. The distance between a target and a measurement is what this page exists to show.
2 dated statements · 1 measured what we have, where from, and when
What was measured below: endpoints and our own corpus, never chain state. The reachability of an endpoint, or the contents of our own corpus. Nothing below measured this chain, and none of it is evidence about activity on it.
| What we have | Kind | Source | Dated |
|---|---|---|---|
| The chain in that sentence is one we measure: Solana holds 17 contract rows, 0 of them without an issuer A dated observation, so it ages honestly in this row. The page also renders today's count live from the same table, so the number beside the press release is never older than the last crawl. | we asked, it answered | knowledge.db:contracts WHERE chain_id='solana' (our own locator — not a public URL) | source 2026-11-14 |
| DTCC press release: 'DTCC Tokenization Service to Connect with Solana', dated November 12, 2026, connection targeted for the second half of 2027 First-party. Fetched from dtcc.com by this card on 2026-11-14: the date and the phrase 'second half of 2027' were read off the page itself, not from a summary. A target, not a fact about 2027. | from a document we hold | www.dtcc.com/press-releases/2026/dtcc-token… | source 2026-11-12 seen 2026-11-14 |
The chain in that sentence, measured today
- Contracts we hold
- 17 rows on Solana, of which 0 have no issuer row yet
- Chain row as of
- 2026-11-11
- Endpoint proven
https://api.mainnet-beta.solana.com- What that means
- These are our own crawl rows, updated nightly — the counter-example that makes the rest of this page honest: where we measure, we can say a number and date it.
Candidates
Three chains, three different kinds of not-yet. Coverage here is a decision with an author, so every card says who decided, when, and what measuring would take. Nothing on a candidate card is a measurement of that chain.
Avalanche Cover it live mainnet; zero footprint in… as of 2026-11-14
Decision: Cover it — decided by a named person on 2026-11-14.
Eleven relevant mentions in five days and no crawler of ours reaches the chain: this week's biggest institutional-chain story is one we cannot check against our own data.
What measuring it would take: EVM-shaped, so existing crawl machinery ports. Public C-Chain RPC answered from this host on 2026-11-14.
Coverage card: (source: avalanche contracts work) — the seven-step chain recipe, run with Avalanche's scale in mind
Pre-NYSE institutional presence (BENJI, BUIDL, 'Avalanche 12') is recall-level and unverified — it has its own row saying so. The five-percent-of-tokenized-stocks line stays a claim until the chain is measured.
7 dated statements · 1 measured what we have, where from, and when
What was measured below: endpoints and our own corpus, never chain state. The reachability of an endpoint, or the contents of our own corpus. Nothing below measured this chain, and none of it is evidence about activity on it.
| What we have | Kind | Source | Dated |
|---|---|---|---|
| Public C-Chain RPC answered from this host: eth_chainId 0xa86a = 43114, eth_blockNumber = 100,302,491 A surface probe. It proves the endpoint is reachable and EVM-shaped from this network. It measures nothing ON the chain and licenses no Avalanche fact. | we asked, it answered | api.avax.network/ext/bc/C/rpc | source 2026-11-14 |
| AVAX One drops data center plans to go all in on Avalanche treasury strategy Treasury-company formation forming around the chain. | reported by | cryptobriefing.com/avax-one-avalanche-treasury-q3… | source 2026-11-13 seen 2026-11-14 |
| 'Avalanche Owns Five Percent of Tokenized Stocks' Quoted because it is a share-of-market CLAIM. We have no Avalanche measurement to check it against — (source: avalanche contracts work) is the card that would produce one. Verify against measurement, do not relay. | reported by | www.theblock.co/newsletters/tokenization-brief… | source 2026-11-12 seen 2026-11-14 |
| NYSE selects Avalanche technology for tokenized securities settlement platform Our own capture — an email digest, not a public URL. The page shows this citation without a link, because pointing an internal locator at a hyperlink would be a fake citation. | reported by | email://bitgo-market-pulse/2026-11-11/nyse-avalanche-tokenized-securities-settlement (our own locator — not a public URL) | source 2026-11-11 seen 2026-11-14 |
| Avalanche Won Over the NYSE. Now It Has to 'Capture Value' for AVAX The token-versus-chain tension, in the outlet's words. The underlying argument is not ours. | reported by | decrypt.co/382988/avalanche-won-over-the-… | source 2026-11-11 seen 2026-11-14 |
| NYSE Taps Avalanche to Settle Its Planned Tokenized Stock Platform Press. The named source in this account is Ava Labs. We have not reached NYSE or Ava Labs, so nothing on this card is confirmation from either. | reported by | decrypt.co/382833/nyse-avalanche-settle-t… | source 2026-11-09 seen 2026-11-14 |
| Avalanche Lands a Role in NYSE's Planned Tokenized Stock Venue, Ava Labs Says A second outlet, the same event, the same dependency on Ava Labs. Two press reports are two reports, not two confirmations. | reported by | unchainedcrypto.com/avalanche-lands-a-role-in-nyse… | source 2026-11-09 seen 2026-11-14 |
Not sourced, or withheld on purpose (1) Read this before repeating anything from this card elsewhere.
| What we have | Kind | Source | Dated |
|---|---|---|---|
| Franklin BENJI on Avalanche, BlackRock BUIDL's expansion, and an 'Avalanche 12' programme as pre-NYSE institutional presence on the chain NOT FACT, and the row exists so the absence stays visible. The seed doc carried all three at recall level and no fresh dated source has been found since. Our own gate ledger took 'no verified Avalanche 12 programme' as an accepted audit, not a re-verification. | reported by | recall — unverified; seeded without a source in an internal evidence file §Avalanche (our own locator — not a public URL) | source 2026-11-14 |
These rows are about our record: something we could not trace to a dated source, or chose not to publish because our own gate graded it too weak. They are listed last for a reason — the date on them is the day we searched, not the day anything happened.
Hyperliquid Research first live; what measuring it means i… as of 2026-11-14
Decision: Research first — decided by a named person on 2026-11-14.
Tokenization arriving sideways: equities volume through perp markets, not issuer token lists. The volume is reported and the surfaces are public; what 'a token on Hyperliquid' means for an issuer-attributed ledger is not yet a question with an answer.
What measuring it would take: HyperCore Info API and HyperEVM RPC both answered on 2026-11-14. Neither returns an issuer — the perp universe has no issuer field to attribute to.
Coverage card: none yet — a research pass defines what measuring would mean here before a coverage card is written
a named person, 2026-11-14: 'also, but it's a bit of a special beast'. A coverage decision here would import a token-list assumption this chain does not have.
8 dated statements · 3 measured what we have, where from, and when
What was measured below: endpoints and our own corpus, never chain state. The reachability of an endpoint, or the contents of our own corpus. Nothing below measured this chain, and none of it is evidence about activity on it.
| What we have | Kind | Source | Dated |
|---|---|---|---|
| HyperEVM RPC answered from this host: eth_chainId 0x3e7 = 999 A surface probe of the EVM companion chain. It licenses nothing about what is on it. | we asked, it answered | rpc.hyperliquid.xyz/evm | source 2026-11-14 |
| HyperCore POST /info {type:meta} returned 235 universe entries whose fields are marginTableId, maxLeverage, name and szDecimals — no issuer, owner, admin or token-address field anywhere in the record THE reason we cannot measure this chain today, measured rather than asserted: every crawl recipe we own ends in an issuer-attributed token row, and this registry contains no issuer identity to attribute to. Inventing one would be the fabrication, not the honest gap. | we asked, it answered | api.hyperliquid.xyz/info | source 2026-11-14 |
| POST /info {type:perpDexs} returned 11 entries (index 0 null — the default perp dex) The HIP-3 builder-deployed registries are public, which is why measurement here is plausible someday. A dex list is still not an issuer list. | we asked, it answered | api.hyperliquid.xyz/info | source 2026-11-14 |
| Binance, Hyperliquid now seen as stock trading platforms: Arca CIO An analyst's framing, dated. Not our characterisation of the chain. | reported by | cryptobriefing.com/binance-hyperliquid-stock-trad… | source 2026-11-12 seen 2026-11-14 |
| Hyperliquid's Nvidia perpetual futures hit $2B in 24-hour volume Equity EXPOSURE through a derivative — which is precisely what a token-state crawl does not see. | reported by | cryptobriefing.com/hyperliquids-nvidia-perpetual-… | source 2026-11-12 seen 2026-11-14 |
| Upbit lists Hyperliquid's HYPE token for trading on November 10 Exchange-listing news, carried because venue coverage is part of what an institution reads. | reported by | cryptobriefing.com/upbit-lists-hyperliquids-hype-… | source 2026-11-10 seen 2026-11-14 |
| Hyperliquid equities volume surpasses Bitcoin-native volume again Reported twice that day — a second mentions covers the same event. Tokenized-stock volume reaching a chain through perp markets rather than issuer token lists is the whole reason this chain is on the page. | reported by | cryptobriefing.com/hyperliquid-equities-volume-su… | source 2026-11-09 seen 2026-11-14 |
| SEC EDGAR 8-K filed by Hyperliquid Strategies Inc (CIK 0002078856) The only first-party row on this chain today: a filing exists at this URL on this date. We hold the URL and the date from our internal corroboration and have NOT read the filing — press coverage of the same event calls it an FCM application, which is the filer's claim, not ours. | from a document we hold | www.sec.gov/Archives/edgar/data/2078856/00… | source 2026-11-05 seen 2026-11-14 |
Not sourced, or withheld on purpose (1) Read this before repeating anything from this card elsewhere.
| What we have | Kind | Source | Dated |
|---|---|---|---|
| Two claims about this chain in our own seed doc — 'Bitwise, Hyperliquid seek SEC rule changes for token trading, airdrops' (dated 2026-11-05) and a '$4B HYPE supply burn (~5%)' (dated 2026-10-29) — could not be found in our internal corroboration at those dates, or at any date, on 2026-11-14 A NOT FOUND written down instead of being quietly dropped. Neither claim appears on this page as a fact. If a dated source turns up, it enters as a row of its own and this note retires. | from a document we hold | an internal evidence file §Hyperliquid (our own locator — not a public URL) | source 2026-11-14 |
These rows are about our record: something we could not trace to a dated source, or chose not to publish because our own gate graded it too weak. They are listed last for a reason — the date on them is the day we searched, not the day anything happened.
Zero Identity first identity unresolved as of 2026-11-14
Decision: Identity first — decided by a named person on 2026-11-14.
Cold start: our own corpus does not contain it. Nothing downstream of an identity is knowable — not stage, not date, not observability.
What measuring it would take: not attempted. You cannot probe an unnamed chain.
Coverage card: a fork, not a card: dated source + live → a measurement card; not live → the (source: emergence study) registry
The disambiguation is the content — see the fact rows. The circulating launch date is PRESS-ONLY in our own gate and stays off this page.
2 dated statements · 1 measured what we have, where from, and when
What was measured below: endpoints and our own corpus, never chain state. The reachability of an endpoint, or the contents of our own corpus. Nothing below measured this chain, and none of it is evidence about activity on it.
| What we have | Kind | Source | Dated |
|---|---|---|---|
| Our internal corroboration holds 154 mentions over 120 days whose title contains 'zero'; six of them also mention a chain, mainnet or layer in the body, and all six are a different referent — LayerZero, zero-XRP accounts, 'Zero KYC' marketing copy, a zero-knowledge toolkit, a 'zero-backend' payment gateway and one unrelated retweet A measurement of OUR corpus, not of any chain. Verdict: the institutional-privacy chain referred to as 'Zero' is not identifiable in anything we hold, so no stage, date or endpoint is knowable. | we asked, it answered | internal corroboration (a database host, read-only) — (source: candidate-chain registry) identity pass (our own locator — not a public URL) | source 2026-11-14 |
| zero.inc is an AI CRM for scaleups, not a chain Denial D6, sustained by a fetch of the site itself. One collision excluded on evidence rather than on suspicion. | from a document we hold | an internal evidence file (our own locator — not a public URL) | source 2026-11-14 |
Not sourced, or withheld on purpose (1) Read this before repeating anything from this card elsewhere.
| What we have | Kind | Source | Dated |
|---|---|---|---|
| A public-mainnet date of 2026-11-30 circulates for LayerZero Labs' 'Zero'; our own gate grades that claim PRESS-ONLY, so the date is deliberately absent from this page The card's rule: a scheduled launch date enters this page only as an internal work item-CONFIRMED, and PRESS-ONLY is not CONFIRMED. This row is a statement about our gate, not about Zero. | from a document we hold | an internal evidence file (our own locator — not a public URL) | source 2026-11-14 |
These rows are about our record: something we could not trace to a dated source, or chose not to publish because our own gate graded it too weak. They are listed last for a reason — the date on them is the day we searched, not the day anything happened.
The boundary
Entries that are not candidates, kept visible so the page's edge is drawn where it actually is. A chain we cover but do not measure, and a chain whose registry lives on another page, are different problems with different owners.
Adi Owned elsewhere live — one line only as of 2026-11-14
Decision: Owned elsewhere — decided by a named person ((source: emergence study) authorised 2026-11-14 08:12) on 2026-11-14.
It was the announced-not-built ring and it is now live. Its registry is (source: emergence study); this page cross-links rather than duplicating it.
What measuring it would take: RPC answered from this host on 2026-11-14 (chain id 36900).
Coverage card: (source: emergence study)
One line, no treatment, as the card requires. Treating liveness as coverage would be the exact laundering this page is built to prevent.
2 dated statements · 1 measured what we have, where from, and when
What was measured below: endpoints and our own corpus, never chain state. The reachability of an endpoint, or the contents of our own corpus. Nothing below measured this chain, and none of it is evidence about activity on it.
| What we have | Kind | Source | Dated |
|---|---|---|---|
| ADI Chain RPC answered from this host: eth_chainId 0x9024 = 36900 One line, per the card. A chain answering a request says nothing about institutional usage on it — no further treatment on this page, and none in (source: emergence study) beyond its own registry entry. | we asked, it answered | rpc.adifoundation.ai/ | source 2026-11-14 |
| Public developer docs, a maintained docs repo and an ethereum-lists/chains entry — graded CONFIRMED-FIRST-PARTY by our own gate Its registry home is (source: emergence study); this row exists so the cross-link is not a dead end. | from a document we hold | an internal evidence file (our own locator — not a public URL) | source 2026-11-14 |
Ethereum Not a candidate covered, not measured as of 2026-11-14
Decision: Not a candidate — decided by (source: candidate-chain registry), on the card a named person authorised on 2026-11-14.
Baseline tier: we carry Ethereum on the site and its chain page is honest about the gap. Listing it here would double-count a decision that has already been made.
What measuring it would take: the machinery exists; nobody has pointed it at Ethereum
Coverage card: (source: ethereum issuer evidence)
Here as a boundary, not a candidate: covered-but-unmeasured is a different problem with a different owner.
1 dated statement what we have, where from, and when
| What we have | Kind | Source | Dated |
|---|---|---|---|
| Ethereum has a chains row at access_tier 'baseline' whose last_proven_endpoint reads 'no crawler in P0-P1', and no contract rows at all Read out of our own database, dated as of the row rather than of today. Ethereum is on this page as an honest boundary: covered and unmeasured, which (source: ethereum issuer evidence) owns. | from a document we hold | knowledge.db:chains WHERE chain_id='ethereum' (row as_of 2026-11-11) (our own locator — not a public URL) | source 2026-11-11 seen 2026-11-14 |
What this registry is, and what it is not
- What counts as a row
- A statement, with a source and two dates: the date on the source, and the date we looked. A fact whose source is a memory does not enter the database — the writer refuses the shape.
- What we deliberately withhold
- A claim our own gate grades PRESS-ONLY does not enter this page, however quotable. Where we withheld one, an Not sourced, or withheld on purpose row says so.
- What measuring a chain would take
- The seven-step recipe the measured rings follow: endpoints proved from this host → an issuer-sourced contract list → a daily crawl → attribution → capabilities → stories → watches. No chain on this page has finished step one.
- Why no numbers
- We have zero contract rows for every candidate chain here. A "0" beside a chain would be a measurement of our own crawl, not of the chain, so the page prints the word instead.
- Refresh
- The registry is curated by an internal seeder; the measured baselines beside the lead are read live from
contracts, so they age with the crawl and not with the prose.
Written by an internal seeder; read here read-only. The claim kinds and the decisions are CHECK constraints in the schema, not conventions in this file.