Sequenced by dependency,
not by calendar.
Each phase unlocks the next. We publish the order we will work in and the state of every item, rather than dates we cannot hold.
Foundations
CompleteEverything the rest of the project stands on: the contracts, the tests that prove what they cannot do, and a full rehearsal on a public testnet.
- Token contract — fixed supply, no fee, no freeze, no pause, no owner minting
- Vesting contract — 5% monthly, sealed, non-revocable, permissionless release
- Liquidity lock contract — no owner, no override, no early exit
- Paymaster contract — gas paid in STTR, the user never holds the native token
- Intent escrow — cross-chain buying on any EVM chain with all liquidity kept on Base
- Swap router — the second route: sell STTR on the Base pool, bridge the proceeds out
- Bridge mint caps and a guardian halt — a compromised bridge costs one window's cap, not the supply
- 323 automated tests, including tests asserting the absence of dangerous functions
- All six contracts deployed and exercised on Base Sepolia — 136 live checks across four suites, zero failures, source verified on Blockscout
- Public testnet app — a pool of real testnet ETH anyone can provide liquidity to, swaps into six assets with thirteen testnet destinations, 1 free test STTR per wallet per day from an on-chain faucet, and more sold for testnet ETH
- Real SOL from STTR — sell on Base, receive SOL on Solana devnet at market price, refunded automatically if not delivered; SUI on Sui testnet built alongside
- Selling with no ETH — a relayer pays the gas and is paid in STTR, then sells those fees back for its own gas; verified live from a wallet holding zero ETH
- Six multisigs at 2-of-3, one per allocation, addresses published
Hardening
In progressNothing reaches mainnet until this phase closes. An audit's findings decide whether phase three begins or phase one repeats, which is precisely why no date is attached to it.
- Independent third-party security audit — not started, and the gating item for everything below
- Static analysis across all six contracts — four real issues found and fixed; every remaining finding triaged in writing
- Source verification on a public block explorer
- Production multisigs on hardware wallets, signers distributed
- Vesting start date fixed — immutable once deployed
Mainnet and liquidity
PlannedDeployment is deliberately unremarkable: the same architecture already rehearsed on testnet, with the admin role held by a multisig from the first block.
- Base mainnet deployment, admin held by multisig from block one
- Vesting contract funded and sealed — sealing is refused unless it already holds every promised token
- A Uniswap pool opened with part of the liquidity allocation, LP locked for a minimum of 365 days
- Centralised exchange listings, from the liquidity multisig's reserve
- Token list and block explorer submissions
The utility goes live
PlannedThe point at which STTR stops being a token with a thesis and starts paying for gas. Bridges are authorised one at a time, each an explicit decision, because bridge rights are the sharpest edge in the design.
- Paymaster deployment — the contract is written and tested; this is the first chain where it actually settles gas, with a funded deposit and a live rate feed
- Bridge authorisation via ERC-7802, one bridge at a time — each with a mint cap sized to real volume, and a guardian key that can halt it
- Community airdrop — 20% of supply, criteria and weightings published before the snapshot
- Solver network — the intent escrow is only useful once someone is filling orders; onboarding solvers is the work
- Social-finance application, first release
Handing over control
PlannedThe end state is that we cannot unilaterally change anything. The token is already built for it — voting is checkpointed and the admin surface is deliberately tiny — so this phase is governance catching up with the contract.
- DAO Governor and Timelock contracts
- Admin role transferred from the multisig to the Timelock
- Grants programme operating under DAO control
- Additional chains as paymaster coverage expands
Why there are no dates
An audit takes as long as it takes, and its findings determine whether phase three starts or phase two repeats. Publishing a mainnet date before the audit is even booked would be a marketing decision dressed as a plan. The sequence above is fixed; the calendar follows it, and we would rather be late than ship on a date we announced.