Built in public.
t3rn is small and ships every week. The conversation happens in a few specific places — this page tells you which channel is right for what.
1 · Where to be
2 · How updates ship
Big changes (new contracts, surface retires, incident responses) are announced on Twitter and Discord first, with a full write-up at /announcement and a per-track summary at /docs/tracks.
Small changes ship continuously to portal.t3rn.io via the self-hosted runner on every push to main. There's no weekly release cycle — the deployed build always matches main.
3 · How to contribute
- Found a bug? Open an issue on github.com/t3rn or post in Discord. Include the route, your wallet address if relevant, and what you expected.
- Want to run a solver? Start at /docs/solver. The reference solver is open source.
- Integrating another protocol? /docs/deploy covers the deploy wizard. For the solver-registry consumer path, see
taifoon-solver/docs/B2B_SOLVER_REGISTRATION.md. - Holding govTRN that didn't migrate? Ping support in Discord with your address + a tx hash from the legacy stake. We have a Merkle claim + drop path ready.
4 · Governance
The DAO surface is temporarily offline while we redesign it post-incident. Proposals, treasury views, and on-chain votes will return as part of the next governance cycle. Until then, decisions are made publicly in Discord with summaries posted to Twitter.
When DAO returns, it will be at /dao (today those routes redirect to home).
5 · Incident transparency
The 2026-05-11 incident drained genesis-allocated TRN held in EOAs. We responded by retiring the buggy legacy GovAdapter stack, deploying clean replacements, and migrating 263 holders without action required from them. Full write-up when the dust settles legally; until then, see /announcement for the public statement.