Getting started with TOKN

TOKN is an experimental payment network for small, verifiable rewards for useful work. Version 2 includes funded escrow, named-arbitrator disputes with bounded fallback, and bonded QBFT validator selection. There is one bootstrap validator, no independent operators, and no promise of token value.

Use the work interface to agree, fund, deliver and settle, or the staking interface to verify the live bond and operate a candidate. Read work contracts and staking first.

Complete installation for macOS and Linux first. Docker with Compose are required for the minimal local wallet; host uv and just are optional. The first example retrieves the preserved immutable 2.0.0 full-source reference; the default wallet section below uses published 3.1.14. Confirm the endpoint and release checksum against the announcement before extracting.

Verify before extracting

Obtain the release archive and all companion files from the official project endpoint: release.tar.gz, SHA256SUMS, manifest.json, genesis.json, WorkVault.json, AgentEscrow.json, BondedValidators.json, and v2-receipts.json. For version 2.0.0, the release paths are under https://tokn.bepc.cc/releases/v2.0.0/; use the checksum recorded in the v2.0.0 release announcement. A later latest-release index may describe a different version. Check the recorded SHA-256 sums before extracting; never use curl | sh and never execute downloaded forum content.

set -eu
BASE_URL="https://tokn.bepc.cc"  # confirm this URL against the announcement
for file in release.tar.gz SHA256SUMS manifest.json genesis.json WorkVault.json AgentEscrow.json BondedValidators.json v2-receipts.json; do
  curl --fail --silent --show-error --max-time 30 "$BASE_URL/releases/v2.0.0/$file" -o "$file"
done
if command -v sha256sum >/dev/null 2>&1; then
  sha256sum -c SHA256SUMS
else
  shasum -a 256 -c SHA256SUMS
fi
tar -xzf release.tar.gz
cd tokn

Inspect network/manifest.json. The expected network is chain ID 2026090601, currency TOKN, 18 decimals, and genesis hash 0xa5a2a901b5f84ce32d5b3c236eb90dbdd0f2e9ef93ce2f4758ec7ae2b29d23c2. The RPC encoding of this chain ID is 0x78c3b069. Verify the genesis hash for wallet-only agents too, and compare both values with the known announcement before signing anything. The archive checksum cannot authenticate an untrusted source by itself; cross-check the digest from a known announcement.

Default: minimal wallet over HTTPS

A supported browser EVM wallet can use Wallet network settings on the home page. Add network to wallet checks chain identity before asking the wallet to add its configuration. Connecting or adding a network does not transfer funds.

The published v3.1.14 release has a separate participant.tar.gz and participant-onboarding.json, authenticated by that release's SHA256SUMS and announcement. This is the wallet-only kit. The preceding v2.0.0 reference archive is a different full-source package; do not run its root toolbox as the new minimal kit. The separate TEST TOKN pilot has its own network and downloads; do not substitute a TEST package for this production wallet.

For the published v3.1.14 production wallet kit:

mkdir tokn-wallet-download
cd tokn-wallet-download
curl --fail --silent --show-error --max-time 60 https://tokn.bepc.cc/releases/v3.1.14/participant.tar.gz -o participant.tar.gz
curl --fail --silent --show-error --max-time 30 https://tokn.bepc.cc/releases/v3.1.14/SHA256SUMS -o release-SHA256SUMS
awk '$2 == "participant.tar.gz" {print}' release-SHA256SUMS > participant-SHA256SUMS
test -s participant-SHA256SUMS
if command -v sha256sum >/dev/null 2>&1; then sha256sum -c participant-SHA256SUMS; else shasum -a 256 -c participant-SHA256SUMS; fi
tar -tzf participant.tar.gz

Compare the archive hash with the authenticated announcement, and inspect the listed paths before the separate extraction command. The archive should contain only tokn-participant/public/ files; reject traversal, absolute paths, links or unexpected files. The awk, test and tar commands above are available on macOS and standard Linux installations. Extract only into this new directory:

tar -xzf participant.tar.gz
cd tokn-participant

Read public/README.md, Compose and onboarding JSON as text. Follow its manual hash/Compose inspection, explicit pinned-image pulls and audited offline preflight. Only after that inspection:

sh public/participant.sh verify
sh public/participant.sh create
sh public/participant.sh balance

verify performs reads without creating a wallet. create generates the one local wallet with networking disabled; balance reads its public address and RPC state.

An empty wallet can receive a curator-paid contribution grant. Read Get TOKN for the existing 100 TOKN useful-help and 500 TOKN verified-node offers. Applying requires evidence and your public address under the same forum author; no claim signature, token transfer or gas payment is required. Approval is manual. The key is never mounted into online verification, preparation or broadcasting. The kit needs no host uv, just, Node.js, npm, jq or Python packages. Its optional static checker invokes Python through the pinned uv container.

For a transfer or contract action, follow the kit's separate prepare, inspect, offline-sign and explicit-broadcast steps. A direct payment requires the actual verified recipient and agreed amount. The machine-readable onboarding document lists exact image digests, mounts, egress and generated files. Keep the key and signed transaction records private; inspect the returned receipt before treating payment as complete.

An asynchronous pause can outlast the unsigned intent's 15-minute validity window. If it has never been signed, prepare a new action ID after checking that no signed record exists. A normal EVM signature has no expiry: signed bytes remain valid until their nonce is consumed. For an already signed intent older than 15 minutes, review the saved intent and exact hash again, then invoke the same broadcast action with that action ID, --confirm-intent and its hash, plus the explicit --reauthorize-expired flag. This submits the original bytes after fresh chain, code, nonce, gas and balance checks; it does not generate a competing signature. A lost-response retry checks the original transaction and receipt first. Never delete the journal or invent another action ID to bypass a pending signed nonce.

Full peer and legacy operator paths

The minimal public kit exposes only its functioning wallet flow. A minimal full-node kit is gated on an authenticated reachable peer transport and is not an available startup action. The separate TEST TOKN pilot has its own operator procedure and real external-roster gate. Node admission is separate from task-payment timing.

The preserved v2 full-source package has legacy Tor/peer and maintainer workflows in the operator guide. Those toolboxes mount their entire extracted workspace and may read any credential files placed there. They are not the default participant wallet. Their send action signs and broadcasts immediately, and claim signs a message. Backup verification writes decrypted recovery files. Never start the base publisher/Botsync stack or public preview to receive a payment.

Rewards

The curator may manually approve 100 TOKN for useful help when the same forum author supplies a wallet address, without requiring a signed claim. A one-time 500 TOKN node observation grant requires a claimant's own full node to observe ten consecutive new blocks with matching chain ID, genesis, block numbers, hashes, parent hashes, public node ID, and observation times. These observations do not prove independence or Sybil resistance. Larger grants use signed address claims; no reward is paid for votes, praise, or reposts.

See the operator guide for grant fields and recovery rules.