Validator Seats Are Won Before Mainnet

The seat is decided before mainnet opens.

That is not hype — it is arithmetic. The active set caps at 100 seats, stake thresholds are published, and DAR scores you on a formula you can read today. Everyone who "starts preparing" after the launch announcement is already behind the people who trained on the local build.

Here is the honest ground truth first: our own status file says not_launched / No-Go, and it only flips on an official launch announcement. So this is not a "send us money now" guide. It is the training plan.

Know the four roles before you pick one

MSG Chain separates who produces blocks from who governs. Four roles exist on-chain, and they differ in admission, quota, duty, and reward source:

The zero-stake entry is the point. You can run a full or light node, sync blocks, relay transactions and serve RPC endpoints today — no stake, no committee, no permission. That is the rung where everyone actually starts.

The numbers you are scored on

Once you meet stake and uptime requirements (steady-state minimum 100,000 MSG, uptime at least 60%), DAR keeps scoring four axes:

• uptime 0–40 — did you actually show up
• stability 0–30 — did you stay consistent
• holdings 0–20 — skin in the game
• holding duration 0–10 — time in the seat

Totals are not vibes; they are weights. A candidate optimizing only stake while crashing nightly loses to a smaller holder with clean uptime. The validator cap defaults to 100 and never drops below it — DAO governance can expand it, which means the seat count itself is a governed parameter, not a marketing number.

Your copy-paste training checklist

Do these in order. None of them require the chain to be live:

1. Read the status file, not the timeline. Open https://msgchain.org/status.json and read network_status and mainnet_verdict yourself. If it does not say launched, nobody's claiming it is.
2. Pick your role honestly. Non-validating node = zero stake, unlimited quota, real work (sync, relay, RPC). Candidate = stake range and 14-day unbonding. Validator = steady-state threshold and continuous DAR checks.
3. Study the 148 site-hosted developer references in the docs layer — every link points to a local copy, and the page states plainly that the chain is not launched and each document has not been independently verified. Read like an auditor, not a fan.
4. Rehearse the qualification loop. The join path is: deploy a node → register validator info → enter the governed active set → keep passing ongoing DAR qualification, slashing, challenge and recovery checks. Step four never ends — that is the job.
5. Score yourself monthly on the four axes above. Fix the weakest axis first; the formula does not care about your narrative.

Where AI stops (and why)

The validator page is blunt: eligibility follows stake and DAR qualification regardless of subject type — but AI does not take over validator duties in production today, and signing and deployment still require human approval. Same boundary as our constitution: rights attach to roles, keys stay scoped, and the treasury line never moves. We publish the restriction instead of demoing a fantasy.

Honest status

MSG Chain is not launched — mainnet is No-Go until the official announcement says otherwise. Stake thresholds, scoring weights and caps above are published design parameters from our official validator page, not live measurements. Train on the local build while the numbers are still cheap to get right.

Questions for the community

1. Would you start on the zero-stake rung or go straight candidate — what breaks first in each path?
2. Is a 40/30/20/10 scoring mix the right way to weight "showing up" versus "skin in the game"?
3. If the DAO expands the 100-seat cap, what should it demand in return?

Pressure-test at qa.msgchain.org · read the boundaries at https://msgchain.org/whitepaper · argue live: https://t.me/+OrceJ-S4iJIxMzU1

Follow @msgchain — we publish the checklist we actually test with, including the parts that say No-Go.