What we are building
Four phases from terminal to public gallery. The labels mean exactly what they say and nothing more.
Read the labels literally
RELICLAUNCHER is pre-launch. Built means the surface exists in the product and works. Building means it is in the code and not finished. Next means it is scheduled. Planned means it is intended and not scheduled. None of it is open to the public yet, and nothing here is a delivery date.
This page changes as the work does. If something moves backwards, it moves backwards here too rather than quietly staying where it was.
IBuilt
The Terminal
Foundation
- Launch builder: token, supply, decimals, metadataBuilt
- Wallet vault with roles and randomised amountsBuilt
- Browser-side keypair generation and storageBuilt
- One-click sweep of unspent balancesBuilt
- Bundle composer with tip tuningBuilt
- Console: dashboard, wallets, bundles, activity, settingsBuilt
- Execution feed, written from receipts rather than from submissionBuilt
- Documentation, thirteen chaptersBuilt
- Pre-flight simulation against live chain stateBuilding
IIBuilding
Protection
Hardening
- Protection settings surface, defaults and per-launch overridesBuilt
- Spend ceilings and confirm-before-signingBuilt
- Private bundle routing through a block engineBuilding
- Transaction gating and allowlist modeBuilding
- MEV protection on the buy pathBuilding
- Retry policy and all-or-nothing guaranteesNext
- Independent review of the signing and bundle pathNext
IIIBuilding
The Gallery
Public launch
- Token gallery surface in the consoleBuilt
- Public token gallery with live market dataBuilding
- Launch records and shareable artifactsNext
- Creator profiles and launch historyPlanned
- Published platform pricingNext
IVPlanned
Scale
Beyond
- Team accounts and granular access controlPlanned
- Scheduled and conditional launchesPlanned
- Public API and webhooksPlanned
- Audit trail export and reportingPlanned
Follow along
Join the registerBe first when it opens
The register is notified before any public announcement.