Skip to main content

Submit a gentx for the Stateset Commerce Network Testnet

Network: stateset-1-testnet Denom: ustst (micro‑STST) Plan: This testnet simulates stateset v0.0.8.

Quick Start (Copy/Paste)

Replace <moniker-name> and <key-name> with your own values. Default home in this doc is ~/.stateset. If your build uses ~/.statesetd, adjust paths or pass --home ~/.statesetd.

“First!” — If you’re resetting from a previous run

  1. Stop your node
  2. Unsafe reset
  3. Remove old genesis & gentxs
  4. Proceed with the gentx flow below.
Heads‑up: Some older builds default to ~/.statesetd instead of ~/.stateset. If your setup uses ~/.statesetd, swap the home path (or pass --home ~/.statesetd on each command).

Prerequisites

  • Golang ≥ 1.17 installed and on your PATH
  • git, curl, and basic build tools
  • (Recommended) A configured GOPATH/GOBIN
Example environment setup (Linux/macOS):
If in doubt:

Build the statesetd Binary

This installs statesetd into $GOBIN (commonly ~/go/bin). Ensure it’s on your PATH. Verify:

Option B — Starport/Ignite (alternative)

If you prefer Starport:
Note: Version parity matters for the testnet. If you use Starport, confirm statesetd version aligns with the testnet commit/tag.

Minimum Hardware

  • RAM: 8–16 GB
  • Disk: 100 GB (SSD recommended)
  • CPU: 2 cores

Generate Your gentx

  1. Init your node
  2. Pull the testnet genesis
    (Alternate earlier path used in some guides: .../main/stateset-1-testnet/pregenesis.json)
  3. Create a key
  4. Add a funded genesis account
  5. Create the gentx Minimal form:
    Advanced (with metadata & commission):
    Success looks like:
  6. Validate

Submit Your gentx

  1. Fork the networks repo: https://github.com/stateset/networks
  2. Clone your fork:
  3. Copy your gentx into the testnet folder:
  4. Commit & push, then open a PR back to stateset/networks.
Acceptance note: Only PRs from individuals/groups with a history of successfully running nodes may be accepted to ensure the network launches on time.

Tips & Troubleshooting

  • Home directory differences Some environments use ~/.statesetd as the default. Either:
    • pass --home ~/.statesetd to every command, or
    • symlink: ln -s ~/.statesetd ~/.stateset (pick one path and stay consistent).
  • Keyring backend Use --keyring-backend os for persistence with your OS keystore. Alternatives:
    • file (plaintext on disk), test (ephemeral/in‑memory).
  • Denom & amounts
    • Denom is ustate (micro‑units).
    • 1 STATE = 1,000,000 ustate
    • Examples:
      • 10,000 STATE = 10000000000ustate
      • 9,000 STATE = 9000000000ustate
  • Commission fields If you include commission params in your gentx, typical values for testnets:
    • --commission-rate "0.01" (1%)
    • --commission-max-rate "0.20" (20%)
    • --commission-max-change-rate "0.05" (5% per day)
  • Build issues (Go/GOPATH) Ensure:
  • Sanity checks

Security Notes

  • Back up your mnemonic offline. Anyone with it controls your validator funds.
  • Never commit ~/.stateset* contents to any repository.
  • Double‑check addresses before submitting on‑chain transactions.

What Happens After PR Merge?

  • The Stateset team publishes the final testnet genesis (with accepted gentxs) and launch time.
  • You’ll be instructed to download the final genesis and start your node/validator for network launch.