TESSA FOUNDATION · PLATFORM DOSSIER
On-chain infrastructure, institutionally delivered.
The complete consumer layer for young blockchains — explorer, public API, trading terminal and deployment tooling over one indexer, one account and one design system.
SCAN · TRADE · DEPLOY — DOCUMENTED
CHAIN REGISTER · LIVE
TessaSCAN
FINALIZED-ONLY · RE-ORG SAFE
ROUTE PLAN · SELF-SIGNED
TessaDEX
NON-CUSTODIAL · USER-SIGNED
FAIR LAUNCH · ATOMIC BATCH
TessaDAPP
DEPLOY THE TOKEN — WE DELIVER THE DOSSIER
The indexer is the asset. Everything else is a view.
Everything users expect from a mature ecosystem — an explorer, a public API, a trading terminal, launch tooling — shares one heavy dependency: a complete, historical, real-time index of the chain.
TessaFORGE is built around that insight. One engine indexes each chain from its finalized head down to genesis; every product surface is a read-only view above it. The explorer, the API, the DEX terminal and the deployment tooling never touch a chain node in the request path — they read from the engine, and the engine reads from the chain.
This is what makes the platform portable. A young chain does not need to build an Etherscan, a Uniswap front-end and a launch suite — it needs one engine that already knows how, and a portal with its own name on the door.
Every chain. One trusted readout.
§1 multi-chain scanner
Explorer and public API. Blocks, extrinsics, events, accounts and transfers on every chain; validator and licence registries where they exist; universal search across the register. REST in the conventions integrators expect, GraphQL underneath.
§2 swap & transfer
A non-custodial trading terminal over on-chain AMMs: routing with price impact and slippage, pool analytics, cross-chain transfer routes. The engine plans the route; the user signs from their own wallet. No keys ever touch a server.
§3 deploy & audit-prep
Deployment tooling for fair launches: asset creation, pool seeding, liquidity lock and vesting composed into one atomic batch — with a public registry and badges that document exactly what was deployed, when, and under which terms.
Capabilities decide features — never chain names.
Onboarding a chain is a register entry, an indexing window and a brand pack — never a fork of the codebase. Products ask what a chain can do, not which chain it is; a feature renders where the capability exists and is absent where it does not.
The engine follows the finalized head, never the raw tip. A small lag, bought deliberately: re-organisations can never corrupt the index.
Public traffic reads the engine's database, never a chain node. Processors and enrichment jobs are the only RPC consumers.
Aggregates are computed from the raw record, not accumulated beside it — so a reindex can never double a number.
Everything that signs, the user signs. The engine holds no keys and never sits in the money path.
Joining is a configuration commit, not a rebuild.
A portal is the chain's own front door — its name, its domain, its accents — over the shared engine. Users, history and integrations accumulate at platform level, and every portal benefits.
WHAT A CHAIN GETS
Honest data builds the brand.
Tessa Foundation Ltd operates TessaFORGE as independent infrastructure: own codebase, own machines, arm's-length agreements with the chains it serves.
NEUTRAL
The platform shows unfavourable data with the same care as favourable data — missed blocks, failed transfers, idle validators. Neutrality is a product feature, not a promise.
NON-CUSTODIAL
Users sign from their own wallets, directly to the chain. The platform reads, documents and routes — it never holds.
INDEPENDENT
Separate entity, separate infrastructure, separate repositories. Chains are customers and partners — first among them, never owners.
DOCUMENTED
Every readout is traceable to the on-chain record it was derived from. Deploy the token; we deliver the dossier.
Running a young chain without a consumer layer — or building one and wishing you weren't? Talk to us about a portal.
TESSA FOUNDATION · RESPONSES WITHIN TWO BUSINESS DAYS