Tessa Foundation · multi-chain engine

Every chain.
One trusted readout.

Scan. Trade. Deploy. Documented.

The complete consumer layer for young blockchains: explorer, public API, trading terminal and deployment tooling over one indexer, one account and one design system.

CHAIN REGISTER mosaic assethub polkadot hydration bifrost
0 SERVER-SIDE KEYS
FINALIZED-ONLY INGESTION

The thesis

One engine. Every surface.

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.

  • ONE INDEXERper chain, finalized-only, genesis-deep where it matters
  • ONE ACCOUNTservices travel with the user across every portal
  • ONE DESIGN SYSTEMevery surface reads as one platform

The platform

Three surfaces, one readout.

TessaSCAN

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.

  • Etherscan-convention public API
  • Validator & licence registries
  • Cross-chain universal search

TessaDEX

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.

  • Self-signed, non-custodial by design
  • Route planning incl. cross-chain
  • Pool charts & transaction feed

TessaDAPP

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.

  • Atomic fair-launch batches
  • Public launch registry & badges
  • Deploy the token. We deliver the dossier.

Architecture

A chain is configuration, not code.

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.

Finalized-only ingestion

The engine follows the finalized head, never the raw tip. A small lag, bought deliberately: re-organisations can never corrupt the index.

No RPC in the request path

Public traffic reads the engine's database, never a chain node. Processors and enrichment jobs are the only RPC consumers.

Derived, never stored

Aggregates are computed from the raw record, not accumulated beside it, so a reindex can never double a number.

Zero server-side keys

Everything that signs, the user signs. The engine holds no keys and never sits in the money path.

FIG. 03-A · THE ENGINE STACK

Portals & white-label

Your chain. Your brand. One engine.

A portal is the chain's own front door over the shared engine: its own name, its own domain, its own accents. Users, history and integrations accumulate at platform level, and every portal benefits.

  1. REGISTER probe the chain, confirm its capabilities, enter it in the register
  2. INDEX provision the processor pair, open the indexing window, backfill
  3. BRAND compose the portal: brand pack, products, features, domain
  4. LIVE smoke-checked against the parity list, then public

What a chain gets

An explorer-class consumer layer from day one: independently operated, documented to the block.

  • An explorer-class portal from day one, under its own brand
  • A public API its ecosystem can build against
  • Account services that grow with usage: watchlists, alerts, API keys
  • Readouts that are documented, neutral and independently operated
Request a portal

The foundation

Independent by design.

Tessa Foundation Ltd operates TessaFORGE as independent infrastructure: own codebase, own machines, arm's-length agreements with the chains it serves.

NEUTRAL

The record, unedited

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

Never in the money path

Users sign from their own wallets, directly to the chain. The platform reads, documents and routes. It never holds.

INDEPENDENT

Nobody's subsidiary

Separate entity, separate infrastructure, separate repositories. Chains are customers and partners: first among them, never owners.

DOCUMENTED

The dossier standard

Every readout is traceable to the on-chain record it was derived from. Deploy the token; we deliver the dossier.

Contact

Start the conversation.

Running a young chain without a consumer layer, or building one and wishing you weren't? Talk to us about a portal.

hello@tessa.foundation

TESSA FOUNDATION · RESPONSES WITHIN TWO BUSINESS DAYS

Or press ASK, bottom right, and question the dossier directly.