← All posts
Jun 11, 2026t3rn talks

The t3rn Portal: One Surface for the Whole Protocol

For most of t3rn's life, using the protocol meant visiting half a dozen disconnected sites. Marketing lived on a Framer page. Bridging happened at bridge.t3rn.io. Docs sat on Docusaurus. Protocol stats existed in dashboards most people never found, and governance was somewhere else entirely. Each surface had its own design, its own wallet session, and its own idea of what t3rn is.

We replaced all of it with one portal: t3rn.io. This post explains why, what it actually gives you, and the rule we built it around.

Fragmentation Is a Trust Problem

A protocol you have to assemble from six browser tabs is a protocol you can't fully verify. When the swap UI, the order status page, and the explorer live on different stacks, they drift. Numbers disagree. Links rot. You end up trusting whichever tab loaded last.

That's not a branding issue. For a protocol whose entire pitch is verifiable cross-chain execution, it's a credibility issue. If we ask users to verify instead of trust, the place where they verify should be the same place where they act.

So the portal puts everything behind one wallet session, one design system, and one data layer:

  • Bridge — swap, per-account orders, and a live order timeline for every transfer. Each step of an order is observable, not inferred.

  • Stake — pools and rewards read from the contracts, including Symbiotic restaking.

  • Solve — the doorway for solver operators: API reference, webhooks, wallet registration.

  • Explorer — a live feed of network activity over SSE, with order drilldowns. Executor rankings and protocol metrics show honest unavailable states until the underlying data is trustworthy.

  • DAO — built, then deliberately unpublished. Governance is paused and the treasury data isn't live, so /dao redirects home. The pages exist in the codebase and return when both change — not before.

  • Build — SDK quickstart and integration guides for developers.

  • Blog — the full archive since 2021, migrated off the legacy CMS, including this post.

The Rule: Live Data or Nothing

Every number on the portal has to be backed by an endpoint or a contract read. If we can't back it, we don't render it.

This is not a slogan; it has already cost us features. We recently deleted a solver leaderboard from the portal because there was no live global solver data behind it. The table looked good. It was also fabricated, so it went. An honest empty state beats an impressive fake, every time.

The same rule shapes the pages that are still thin. Where trustworthy metrics don't exist yet, the portal says so instead of inventing them. We'd rather you saw a placeholder labeled as a placeholder than a chart we can't stand behind.

A Thin Window, on Purpose

The 2026 roadmap is about removing t3rn's operational dependencies: proofs replace servers, solvers discover work on-chain, coordination moves into smart contracts. The portal is designed for that end state.

It is deliberately a thin window onto protocol state — contract reads, on-chain data, live event streams — rather than a frontend for our backend. As the coordination layer decentralizes, the portal keeps working, because what it shows you is the chain, not our infrastructure. A portal that only works while our servers are up would contradict the protocol it presents.

What This Gives You, Concretely

  • If you bridge: one place to swap, watch the order settle step by step, and cross-check it in the explorer — same session, same data.

  • If you provide liquidity: staking positions and rewards read live from the contracts, not from a cached dashboard.

  • If you run a solver: registration, API docs, and the network activity you'd be competing for, side by side.

  • If you build: the SDK path from quickstart to a working integration without leaving the site.

  • If you hold TRN: no DAO dashboard yet, and we won't fake one. Governance is paused and the surfaces stay offline until every number on them is chain-sourced.

What's Next

The portal is not finished, and we won't pretend otherwise. More surfaces need live data wired in. Some pages are still placeholders. The list of what shipped and what's next is on the homepage, dated, and we update it as we go — that's the same build-in-public discipline this post is part of.

Use the bridge. Watch your order in the explorer. If something disagrees with the chain, file an issue — that's exactly the kind of bug this portal exists to make visible.