Kaspa Explained is an independent guide to Kaspa with interactive explanations and experimental Testnet-10 applications. The public build includes 18 canonical pages and 87 compatibility routes.
Enter the town. Buy greenhouse parts, pool three backers’ investment, pay Pip for a checked work schedule, sell the harvest, and carry the purchased food to the store.
Pip earns 0.1 tKAS and spends 0.03 tKAS from that exact wage output on three crop vouchers. The rest returns to Pip after the network fee. Sprout’s three accepted moves complete the delivery. The first order uses 21 Testnet transactions and one local rejected request; an additional order earns a fresh wage without rebuilding the greenhouse.
Signatures, spending limits, voucher ownership, payments, pledge conditions, the schedule check and movement rules are enforced on Testnet-10. Parts, greenhouse production, cargo and food delivery are game interpretations. The browser controls all demonstration accounts. These are unaudited experiments with free test coins, not mainnet applications.
A complete economic order and its reload were verified on Testnet-10 on 7 September 2026. Inspect the accepted transaction record, browser checks, and economic route and evidence boundaries. These are dated observations, not a security audit or unconditional finality.
The bridge example shows a recorded round trip: lock 100 pUSD on Ethereum Sepolia, issue its representation on Kaspa, transfer the claim to Pip, then burn it and release the source tokens to Pip. The verification record includes the source receipts and four accepted Kaspa transactions, including initialization.
The public page displays dated demonstration balances and explorer links. It cannot sign or send bridge transactions. A trusted test oracle authorizes issuance and release; Kaspa does not independently verify Ethereum consensus here. wTestUSD cannot buy the town’s crops. See bridge architecture.
Wrap lab also supports native test-KAS receipts: lock backing, transfer its claim and redeem it. Other experiments include payments, escrow, threshold treasury, prediction payouts, fixed-proof checks and capped tokens.
Use Node.js 22 or later:
npm ci
npm run setup:testnet
npm run build
node scripts/static-preview.mjs distOpen the local preview. SDK/compiler setup verifies pinned checksums. Contract VM checks additionally require Rust/native build tools, Git, unzip and tar; macOS and Linux arm64/x64 are supported by the setup workflow. Windows setup is unverified.
The public application is static. It creates disposable accounts, encrypts browser recovery and connects directly to Testnet-10. It needs no public signing server or compiler endpoint. The optional fixed-amount faucet is described in faucet operations.
For the standalone education build, use npm run build:v1 and preview dist-v1. Maintained source is in src/; generated output belongs in dist/ or dist-v1/.
npm run check
npm run check:v4
npm run check:contracts:vm
npm run check:v4:vm
npm run check:economy
npx playwright install chromium firefox webkit
npm run check:v4:flows
node scripts/check-wrap-recorded-browser.mjs
npm run check:copy
npm run check:postsThe economy browser regression uses the real SDK with synthetic RPC; it is separate from the recorded live Testnet run. npm run check:public:browser checks public wallet loading and recovery across three browser engines using real RPC without funding accounts or submitting transactions. Node unavailability fails that gate. Run bash scripts/check-site.sh before publishing, following the release checklist.
Contract sources are in contracts/public/; tests and verification tools in tests/ and scripts/; social posts in content/. Public architecture describes transaction construction, signing and recovery. Historical release reports remain in docs/ and design/ as dated evidence.
npm run serve starts the separate local workshop at 127.0.0.1:8898. npm run setup:wrap and npm run serve:wrap prepare and run the local bridge experiment; see its setup instructions. These services control local demonstration identities and are excluded from the public static build. Private state under ignored .local/ must never be published. Uncertain submissions must be reconciled before another spend.
New project-controlled code is offered under PolyForm Noncommercial 1.0.0, and educational content under CC BY-NC 4.0. Commercial reuse is not granted under these new terms; see their permitted purposes and scope in LICENSE.md.
Earlier MIT and CC BY 4.0 grants remain valid for previously released material. Third-party code, independent contributions and Moose’s books retain their own terms. Preserve the notices in THIRD_PARTY.md.
Corrections should identify the exact claim or behavior and a supporting primary source.