TENDER

Loading000
TENDER logoTENDER®
[ 012 / ROADMAP ]

Four phases.One rail at a time.

What is deployed, what is being built, and what is still a question. Each phase ships a primitive that stands on its own - nothing here needs a later phase to be useful.

PHASES
4
SHIPPED
T1
IN BUILD
T2
NETWORK
SOLANA · MAINNET-BETA
01

How to read this

Four statuses, and one rule about what they promise.

  1. T1SHIPPED
  2. T2IN BUILD
  3. T3PLANNED
  4. T4RESEARCH
SHIPPED
Deployed and settling on mainnet-beta today. Described in the whitepaper as built, not intended.
IN BUILD
Actively being written. The shape is settled; the surface may still move before it lands.
PLANNED
Committed in order and scope, not yet in build. Details are expected to change as the phase before it lands.
RESEARCH
An open question we intend to answer. Listed so the direction is public - not as a promise of a date.

The order of the phases is a commitment. The dates are not, and we do not publish them: each phase depends on the one before it landing cleanly, and on an eligible-asset universe that stakers - not us alone - decide how fast to widen.

02

The phases

Each block lists what actually ships and the one thing it unlocks.

PHASE T1SHIPPEDNOW

Elections & atomic settlement

The rail itself: a handle, an election, and a single transaction that honours it at receipt.

  • On-chain handle registry, consumed rather than forked
  • Elections expressed in basis points, summing to 100%
  • Single-recipient pay-by-handle, settled at receipt
  • Jupiter best-route execution under slippage caps
  • Pyth reference band checked before anything is signed
  • USDC safe-settle fallback on a breaching leg
UNLOCKS: ANY INBOUND TOKEN -> YOUR ELECTED MIX
PHASE T2IN BUILDNEXT

Splits & invoices

One payment, many receivers - each share landing in that receiver's own elected assets.

  • Multi-recipient handles, each share on its own election
  • Solana Pay QR and pay-links carrying amount, memo, expiry
  • Invoice status and settlement receipts in the terminal
  • Dual-provider quoting: Jupiter V6 and Relay.link V2
UNLOCKS: 1 PAYMENT -> N RECIPIENTS -> N ELECTIONS
PHASE T3PLANNEDLATER

Payroll vaults & token genesis

The same settlement, on a schedule - plus the token that pays the people securing it.

  • Funder vault with a roster and a schedule
  • Permissionless crank: anyone can trigger a due run
  • Per-recipient elections honoured on every run
  • $TNDR genesis, staker fee share and the buyback flow
UNLOCKS: VAULT -> CRANK -> ROSTER -> ELECTED ASSETS
PHASE T4RESEARCHLATER

Resolution & cross-chain pay-in

Widening what can address a handle, and what can arrive at one.

  • .sol domain resolution adapter
  • Cross-chain pay-in routes into the same election
  • A wider eligible-asset universe under staker governance
UNLOCKS: MORE WAYS IN · SAME ELECTION OUT
03

What doesn't move

The design laws hold across every phase. A roadmap item that would break one of them isn't on the roadmap.

NON-CUSTODIAL, ALWAYS
No phase introduces a pooled balance or a forwarding account. If a feature needs custody to work, it does not ship.
THE ELECTION IS LAW
Splits, vaults and cross-chain pay-in all resolve to the same rule: the receiver's election is honoured exactly, or the payment safe-settles.
THE FAST PATH STAYS FREE
Same-asset transfers convert nothing and cost nothing, in every phase, forever.
THE STANDARD STAYS UNFORKED
Identity keeps living in the on-chain handle registry, so a handle outlives any single interface - including ours.
04

How this list changes

A roadmap nobody can hold you to isn't one.

ORDER IS A COMMITMENT
Phases ship in sequence. If something jumps the queue, this page says so and why.
TIMING IS NOT
We publish status, not dates. A phase moves from PLANNED to IN BUILD when it is genuinely being written.
SCOPE CAN NARROW
A listed deliverable can be cut if it would compromise a design law. That is a feature of the process, not a failure of it.
STAKERS GOVERN THE UNIVERSE
Which assets become electable is decided on-chain, so the pace of that widening is not ours alone to set.

Anything on this page beyond T1 describes intent rather than deployed code, and none of it is an offer, a solicitation, or investment advice.

T1 is live. Start there.

TENDER is settlement infrastructure - not payroll, tax, or investment software.