Skip to content
LATTICE

Roadmap · 2026

Two quarters, and no dates we cannot keep.

Everything marked shipped is something you can read in the repository today. Everything else is written as a thing to do, not a thing that exists.

Shipped
6
Building
1
Planned
7

Q3 2026

July → September

Build the thing, and say plainly what it is.

  1. 01

    The ve(3,3) core

    Shipped

    Escrow, three-day ballot, gauges with a 1x–2.5x boost, per-round fee and incentive books, a fixed emission pot paying 0.64% of its remainder. 48 checks.

  2. 02

    The range vault

    Shipped

    One shared Uniswap v3 position per pool, one-sided deposits, a permissionless keeper, fees split by how much of the vault is staked. 31 checks against the real v3 factory bytecode.

  3. 03

    Hardening

    Shipped

    A five-minute price guard on every path that moves money, swaps bounded to 1% from spot, a mutex everywhere, and books that credit what actually arrived.

  4. 04

    One-call claiming

    Shipped

    claimAll walks the gauges a lock voted for, both books of each, and every asset either was paid in.

  5. 05

    $LATTICE

    Shipped

    The token is live on Robinhood Chain. The emission pot is bought at launch, not minted.

  6. 06

    The site and the docs

    Shipped

    The mechanism explained in full, with the numbers the contracts use and a plain statement of what is not deployed.

  7. 07

    Deploy the protocol

    Building

    Core and the first vaults to chain 4663, from a script that dry-runs against the live chain before it spends anything. The last thing left this quarter.

Q4 2026

October → December

Run rounds, hand the levers over, and prove it in the open.

  1. 01

    The first rounds

    Planned

    Gauges on the pools that graduated from Pons, emissions following the vote every three days, and the incentive market open to anyone who wants a pool funded.

  2. 02

    The app on live data

    Planned

    Dashboard, vaults, ballot and lock reading the chain instead of fixtures — positions, weights, what a round owes you, and what a vault is quoting right now.

  3. 03

    A keeper anyone can run

    Planned

    The bot that settles a closed round and re-centres a drifted vault, published with what it costs and what it pays, so it is not one machine holding the system up.

  4. 04

    Auto-vote, enrolled from the app

    Planned

    One approval, revocable without a transaction, and a strategist whose only power is to waste your round.

  5. 05

    Round history, in public

    Planned

    Every round: what was voted, what was emitted, what the fees came to, and what each vault paid its voters. The argument for a gauge should be its record.

  6. 06

    External review

    Planned

    A read of the contracts by someone who did not write them, published whatever it says. No date, because it is not ours to promise.

  7. 07

    Gauges without an operator

    Planned

    Gauge creation moving off the single address it starts on, so a pool does not need us to be worth voting for.

What would change this

Only two things move the second column much: whether the first rounds show real depth arriving where the votes went, and what an outside read of the contracts turns up. Both are findings, not decisions, and this page will say so when they land.