01 · Edge
The door
Clients, dApps, and backends hit one edge. It terminates TLS, checks auth, and holds the websocket fan-out so callers are not pinned to a single region.
How activity is read
From the chain to your cashback.
NFT and trade activity is read through an edge API, indexers, a cache, and an RPC pool. If one layer hiccups, the next one picks it up.
- ✓ Distributed metadata caching with IPFS gateway fallbacks
- ✓ Optimized routing with edge caching across supported chains
- ✓ One API with load balancing and automatic failover
- ✓ CDN-accelerated media and signed URLs for sensitive assets
Your dApp
Mobile
Backend
Edge API
Global CDN · WebSockets · Auth
Cache + Indexers
Metadata · Holders · Mints · Transfers
Hardened RPC pool
EVM · Solana · Bitcoin · Ordinals · L2s
Ethereum
Solana
Bitcoin
+10
What each layer is for
02 · Index
The memory
Metadata, holders, mints, and transfers are indexed ahead of the read. A cache miss falls through instead of failing the request.
03 · RPC
The pool
Hardened endpoints for EVM, Solana, Bitcoin, Ordinals, and L2s. Routing prefers the healthy path. The published edge target is under 20ms.
04 · Node
The link is the node
You generate a link. That link is the node. NFT buys, trades, and other on-chain actions on it are what cashback reads.
When something fails
Failover is the product, not a footnote. A slow indexer does not take down reads. A bad RPC is dropped from rotation. Signed media URLs expire instead of staying public.
- 1 Edge retries a healthy region.
- 2 Cache serves the last good metadata if the indexer is behind.
- 3 RPC pool ejects the endpoint that missed its health check.
- 4 IPFS gateways are the fallback when a primary media host is dark.