LIVE · V5-PROOF ANCHORED · NO HALLUCINATIONS

INTEL · CATHEDRAL

Every figure here comes from a Taifoon spinner endpoint. The Nemotron narratives between sections are grounded in those numbers — no extrapolation, no fabrication. Solana and EVM bridges are reported separately because their economics diverge. Inspired by 1kx's report layout; extended with the dimensions they don't cover — fillers, traders, communities.

generated_at Sat, 16 May 2026 13:52:18 GMTendpoints 16/23bridges 11 Solana · 21 EVM

(01)

TODAY

What is the OS doing right now?

events_24h

protocols_tracked

active_anomalies

NOW endpoint not yet streaming — chapters 02–08 will fall back to per-endpoint snapshots.

sourced from /api/intel/now

(02)

WHO'S WINNING

Top protocols by 15m / 60m / 24h volume — and who rotated up

01T3RN LiquidityWellCompact

02Across Protocol V3

03Relay Protocol

04deBridge DLN

05Stargate V2

06Hop Protocol

07Li.Fi / Jumper

08Mayan Swift

09Wormhole

10Circle CCTP

11Chainlink CCIP

12LayerZero V2

13Synapse Bridge

14Celer cBridge

15Axelar GMP

16Hyperlane

17Socket Bridge

18Connext

19Allbridge Core

20Router Protocol

sourced from /api/intel/protocols/compare?hours=24 + /api/intel/now

(03)

BRIDGES — SOLANA vs EVM-ONLY

The two market structures, side by side. Different solvers, different economics, different latency profiles.

SOLANA-TOUCHING

Solana ⇄ EVM and Solana-native protocols

11 protocols

allbridgeoverride known solana—

axelaroverride known solana—

cctpoverride known solana—

debridgeoverride known solana—

layerzerooverride known solana—

lifioverride known solana—

mayan_swiftoverride known solana—

orbiter_financeoverride known solana—

squidoverride known solana—

synapseoverride known solana—

wormholeoverride known solana—

sourced from /api/intel/matrix + /api/intel/velocity + bridge-category.ts overrides

EVM-ONLY

Ethereum-family bridges and rollup canonicals

21 protocols

1inchoverride known evm only—

acrossoverride known evm only—

arbitrum_bridgeoverride known evm only—

bancoroverride known evm only—

ccipoverride known evm only—

celeroverride known evm only—

connextoverride known evm only—

hopoverride known evm only—

hyperlaneoverride known evm only—

mesonoverride known evm only—

optimism_bridgeoverride known evm only—

rangodefault evm only—

relayoverride known evm only—

router_protocoloverride known evm only—

socketdefault evm only—

stargateoverride known evm only—

sushiswapoverride known evm only—

symbiosisoverride known evm only—

t3rnoverride known evm only—

uniswap_v3override known evm only—

uniswap_v4override known evm only—

sourced from /api/intel/matrix + /api/intel/velocity + bridge-category.ts overrides

(04)

FILLERS

Taifoon white-space — who is executing the volume. 1kx's report doesn't cover this.

#addressprotocolfillsvolumep50_latencyspread

010xf8d2…3ad7(multi)25$00ms0.0 bps

020xad6c…d2f4(multi)24$00ms0.0 bps

030xfc05…9762(multi)19$00ms0.0 bps

040xfdff…ac85(multi)17$00ms0.0 bps

050x3bdb…3fd1(multi)16$0272000ms0.0 bps

060x5d98…def1(multi)15$00ms0.0 bps

070x4971…a452(multi)12$00ms0.0 bps

080x875d…8eca(multi)12$00ms0.0 bps

090x3d12…67d5(multi)11$00ms0.0 bps

100x7ddd…d07b(multi)11$00ms0.0 bps

Filler intelligence is Taifoon's wedge — 1kx's report attributes revenue to protocols, but the agent that *executed* the fill is the actor a solver trader needs to track. Latency and spread quantify the execution edge.

sourced from /api/intel/solvers + /api/intel/solvers/pnl + /api/intel/solvers/intents

(05)

TRADERS

Who's moving — counterparty distribution, intent cohorts, pending vs filled. Another 1kx white-space.

PENDING ORDERS

orders_awaiting_fill

sourced from /api/intel/pending

FILL-RATE BY PROTOCOL

100%

96%

90%

87%

85%

83%

sourced from /api/intel/fill-rates

INTENT FLOW

recent_fills_24h

100

distinct_intent_paths

sourced from /api/intel/solvers/intents

(06)

COMMUNITY

Builder activity, governance turnout, contributor signal. Where humans show up.

Community signals are still partly off-chain — governance turnout, contributor commits, retention curves — but the addresses Taifoon's genome stream captures are the canonical anchor. The list below is the dossier coverage frontier; per-protocol community breakdowns live at /api/intel/ecosystem/:name and /api/intel/protocol/:slug.

1inch across allbridge arbitrum_bridge axelar bancor ccip cctp celer connext debridge hop hyperlane layerzero lifi mayan_swift meson multichain optimism_bridge orbiter_finance rango relay router_protocol socket

sourced from /api/intel/matrix → ecosystem coverage frontier

(07)

CONCENTRATION

Top-5 share, Gini, rotation. Are we becoming a one-protocol economy?

top_protocol_share_15m

0.0%

top_pair_share_15m

0.0%

gini_24h

0.000

1kx reports "top 5 capture 80%" once per quarter. Taifoon reports the same shape every 30 seconds. The Gini coefficient quantifies inequality across all tracked protocols — 0 is uniform, 1 is monopoly.

sourced from /api/intel/now → concentration{}

(08)

PROJECTIONS

What the next 24h likely looks like — grounded in the velocity series, not vibes.

projected_events_7d

projected_events_30d

These projections are deterministic— observed 24h rate × time. They do not model seasonality, regulatory shifts, or token launches. Use them as a baseline; the per-protocol shifts below show which way today's curve is bending.

ACCELERATING (0)

none in current window

DECELERATING (0)

none in current window

sourced from /api/intel/now → revenue_shifts[] (deterministic extrapolation)

GROUND TRUTH — every endpoint behind this page

GET/api/intel/_metathis discovery surface

GET/api/intel/healthrouter + tracker health + cardinality

GET/api/intel/matrixprotocols.xml record dump

GET/api/intel/coverageicp_ready coverage rows (owned by da-api)

GET/api/intel/protocol/:slugfull per-protocol dossier

GET/api/intel/protocol/:slug/volumevolume_30d breakdown

GET/api/intel/protocol/:slug/holdersERC-20 holder distribution (when applicable)

GET/api/intel/protocol/:slug/solversactive filler dossier per protocol

GET/api/intel/genomes/streamServer-Sent Events of live genomes

GET/api/intel/velocityrolling per-(protocol,route) windows

GET/api/intel/chain-pairsper-(src,dst,asset) live flow

GET/api/intel/nowsolver-grade NOW rollup (shifts, allocations, anomalies)

GET/api/intel/chains/cataloguecanonical chain registry (id, name, ecosystem, native_token, finality_model, explorer)

GET/api/intel/chains/:chain_idsingle chain record

GET/api/intel/assets/catalogueper-chain token registry with decimals + price hints. Supports ?chain_id=N&family=usd_stable&symbol=USDC

GET/api/intel/assets/lookupresolve a single (chain_id, address) to AssetRecord. ?chain_id=N&address=0x...; well-known zero/burn addresses resolve to chain native_token

POST/api/intel/search/queryNemotron proxy with optional dossier injection

Every number on this page derives from one of the endpoints above. Hit any of them directly to verify — Taifoon doesn't curate, it observes. The SuperRoot anchors the genome stream that feeds every aggregate.

Related systems

/intel/now

The shorter, solver-grade rollup

/search/oobe

Per-protocol deep analysis with V5 proof + Nemotron reasoning

/genomes

Raw genome SSE stream — the foundation everything else builds on

Wire the Cathedral into your stack →

Integrate this data into your protocol