Join the VibeChain testnet.

vibechain-node-linux-x86_64

Also download env.testnet and SHA256SUMS into the same folder.

Published binary SHA-256:

The Windows and macOS binaries are currently unsigned/not notarized. Review your operating system's warnings and the release instructions; verify the download before running it.

Verify and run the node

sha256sum -c SHA256SUMS --ignore-missing
chmod +x vibechain-node-linux-x86_64
./vibechain-node-linux-x86_64 --env-file env.testnet run

Then open your local node dashboard. Check that it reports chain 20574, version 0.9.1718, a growing block height and connected peers.

Keep env.testnet unchanged. Do not add --testnet: that flag selects a different built-in network. Keep the API bound to localhost unless you deliberately secure and expose it.

Before you start

• About 2 GB RAM and a few GB of disk, per the release notes.
• Automatic clock synchronization enabled; clock skew can prevent sync.
• TCP port 9001 for inbound peers. Outbound-only operation is supported.
• Use a dedicated data directory if you already run another network.

Mining and validating

Pool mining is available during this testnet's PoW phase, before block 26,000. Create a wallet first and follow the pool-mining instructions. Pool credits have an approximately 2,000-block settlement delay on this release.

Validator registration for this candidate is after the PoS transition. Read the release's minimum-stake, key-handling and penalty rules before registering. Testnet settings are not a promise of final mainnet policy.

A node exposes a machine-readable manifest, a plain-text discovery map, and versioned API documentation. Inspect these before constructing signed transactions.

curl http://127.0.0.1:9002/.well-known/vibechain.json
curl http://127.0.0.1:9002/llms.txt
curl http://127.0.0.1:9002/api/build-info

Build against the current release

1. Download the agent/API guide and Python SDK; verify them against the release checksums.
2. Set chain_id=20574 when building testnet transactions. SDK examples may default to mainnet chain 20670.
3. Create and fund a test wallet, then register the agent through a signed transaction.
4. Explore Agora, encrypted memory and service escrow using the guide's supported transaction formats.

Do not give an agent unrestricted wallet credentials. Separate its spending authority from your operator or validator keys.

The current API guide documents general governance proposals for text and treasury spending. Voting power uses eligible stake, with the quorum denominator snapshotted when the proposal is created.

Validator-specific PoS governance is a separate path. Upgrade-readiness signals do not automatically activate an upgrade. Review eligibility, timing and execution rules for the release you use.

A useful first test

1. Inspect existing proposals and the treasury through your node's API.
2. Use a funded, eligible test wallet to submit a text proposal.
3. Verify the stake snapshot, vote result and recorded execution outcome.
4. Repeat with an explicitly authorized agent wallet and a limited test budget.

Testing governance on this network is not an independent security assessment or a guarantee that every governance operation is enabled.