Add TMYG 17

2026-02-26_tmyg-17.README.md

@@ -0,0 +1,38 @@
+---
+publication_date: 2026-02-26T00:00:00Z
+slug: monthly-dev-17
+tags: [gnoland, ecosystem, updates, TMYG, community]
+authors: [michelleellen]
+---
+
+# The More You Gno
+
+Recently, the team launched [Test11](https://test11.testnets.gno.land/), which we expect to be the final testnet before the Beta Mainnet release, barring any major issues. The goal is not simply to deploy new features, but to verify that governance, validator coordination, and network operations function under conditions as close to Beta Mainnet as possible.
+
+Test11 introduces multi-signature functionality, updates to the GovDAO, and critical fixes to the GnoVM. It launched with an internal validator set and is now actively exercising governance by voting in additional validators to stress test the system. Currently, three additional core contributor validators have been voted in and the proposal executed.
+
+The deployment also demonstrated increased operational maturity across the release workflow and on-chain governance processes. Upgrades, proposal flows, and validator coordination were executed with significantly fewer manual interventions than in prior testnets.
+
+## What Test11 Is Proving
+
+The primary purpose of Test11 is final validation. Stability, performance characteristics, governance execution, and validator onboarding are all being tested in parallel.
+
+Validator onboarding requires a valoper [profile](https://test11.testnets.gno.land/r/gnops/valopers) setup, a proposal submission by a GovDAO test [member](https://test11.testnets.gno.land/r/gov/dao/v3/memberstore) (for now), and formal [on-chain voting](https://test11.testnets.gno.land/r/gov/dao). The selected group of external validators still need to be voted in by the GovDAO, and their Test11 performance will serve as an important indicator of readiness.
+
+In parallel, development continues on the Beta Mainnet launch [milestone](https://github.com/gnolang/gno/milestone/7). The core team will determine which pending fixes are merged before the launch. The two remaining priorities are finalizing the initial GovDAO member composition and completing the genesis token distribution plan.
+
+## Validator Composition and GovDAO
+
+For the initial pre-Beta validator set,  we selected a group of interested validators from AtomOne. Selection criteria included alignment with AtomOne, voting participation history, an internal scoring framework, and geographic diversity across multiple countries.
+
+Ultimately, Gno.land’s Beta Mainnet GovDAO is responsible for approving the full Gno.land validator set. The initial target for the Beta launch is approximately 15 to 20 validators. Over time, additional validators may be voted in by the GovDAO, with preference given to those who avoid reliance on cloud infrastructure, make meaningful contributions to the community, and strengthen the geographic distribution of the validator set.
+
+Gno.land doesn’t operate in the same way as traditional Proof-of-Stake, so being voted in after Beta Mainnet genesis does not carry the same implications as in conventional PoS networks.
+
+## Building Before Beta
+
+As Beta approaches, contribution pathways are becoming clearer. After launch, applications, tools, and ecosystem proposals will move through the GovDAO review processes, making this current timeline between Beta and the full Mainnet important. Builders who begin now position themselves ahead of those waiting for finality.
+
+## When Beta Mainnet?
+
+The answer has not changed. Mainnet follows readiness. Stability, GnoVM fixes, governance reliability, and validator coordination must meet the required standard set forth by the core engineering team. The work now underway is focused on this. If Test11 proves what it is designed to prove, Beta will follow.