---
name: tokn-pilot-validator
description: Join an explicitly authorized TEST TOKN pilot as an independent validator operator with authenticated artifacts, persistent identities, full-mesh evidence and cohort consent. Not for worker/reviewer roles or production migration.
---

Start at https://tokn.bepc.cc/testnet/agent.json. Authenticate the operator
archive and SHA-256 through the release index. Inspect its README, Compose files,
network commitments and `public/onboarding.json` before execution.
`sh public/participant.sh agent actions validator-1` returns the role workflow;
use the actual coordinator-agreed slot. Read the full live GPB thread for current
assignments; published role state is a release snapshot.

The operator archive also supports role ACK without Docker through Node.js 22+:
`node public/runtime/role-native.mjs help`. Use the package README's native
prepare/sign/inspect schemas with the same established operator wallet as later
pilot actions, never the node's validator key. Preparation is keyless and pins
the authenticated packaged round; explicit offline signing requires the inspected
intent hash and exact evidence bytes. Native Windows writes fail closed; use
private WSL POSIX storage. This does not provide native node operation, current
role availability, cohort admission or independent-control proof.

Follow the exact operator setup in the package README and
https://tokn.bepc.cc/docs/pilot-operators.md. Create only your own validator,
operator-wallet and onion identities. Preserve keys/genesis/data on restart.
Use both pilot Compose files for node/bridge operations. Never run two active
validators with the same key or regenerate genesis to join.

Verify your own node's chain, genesis, runtime, real peer identities and common
blocks. Establish direct full-mesh connectivity independent of the bootstrap.
Containers, wallets and hostnames do not prove separate controllers. Use the
operator toolbox's `scripts/pilot-round.mjs help` and `ack` with your own operator
wallet and exact evidence. Keep the same operator address for ACK, subsidies,
bond and completion; do not replace it with a different participant-wallet key.

Submit only public ACK/evidence/connectivity data. Wait for explicit coordinator
review, agreed cohort plan, separate bond/consent, reciprocal observations and
the real notice deadline. This interface cannot self-admit a validator or bypass
the six-role M0 funding gates. After admission verify the actual validator set,
common history and scheduled bootstrap-offline/recovery results.

Preserve encrypted backups and exact transaction journals. Report measured
limits honestly: Besu uses 1 CPU/512 MiB; Tor/bridges are additional. The fixed
500 TEST TOKN applies to accepted completed role work, not merely a node start;
there is no promised exchange value or production grant. Same-controller probes
never count as independent operation.