Native-KAS hash-chain Testnet-10 proof

Commands below run from the protocol/ workspace.

Current release: 1.0.1. The funded browser payment and retry are recorded in the gateway guide. Historical runs below retain their original covenant versions and source scope.

The 2026-10-07 development verification records a fresh head-v2 run: two accepted paid HTTP requests and successful owner recovery after an abandoned grant. Historical head-v1 records remain below.

RC2 — Historical Published Evidence

The published v1.0.0-rc.2 prerelease includes the optional native-KAS hash-chain-additive profile and hosted browser demo. Release checks on 2026-10-01 passed three funded browser payments and identical retries across owner rotation, including a retry after Worker redeployment. The gateway uses PNN/WSS evidence throughout. See the RC2 release reference and its attached transaction evidence and checksums.

Historical Candidate Evidence

The runs below record earlier Testnet-10 candidate validation and retain their original evidence-source boundaries. They do not describe the current hosted deployment. The latest historical run below used committed runtime code 6d02163 on 2026-09-26. Its detailed report is ignored by Git at .kaspa-x402-live/hash-chain-security-6d02163-20260926-run1/report.json; signing keys and the encrypted grant database remain in that private directory.

Reproduce

Build the workspaces, then run the proof script with a funded Testnet-10 private-key file and a synced Testnet-10 PNN node with a UTXO index:

npm run build
export KASPA_X402_KASPA_WASM_MODULE=/path/to/kaspa-wasm/kaspa.js
node scripts/proof-hash-chain-testnet.mjs --live \
  --wallet-file /path/to/private-testnet-wallet.json \
  --rpc-url wss://your-testnet-10-node/kaspa/testnet-10/wrpc/borsh \
  --output-dir .kaspa-x402-live/hash-chain-new-run

The SDK module must provide the same RpcClient API as the exact/batch proof; its Node installation must resolve websocket. There is no implicit SDK path inside this repository. Optional KASPA_X402_PROOF_FEE_SOMPI sets the genesis/rotation/funding-shard fee (default 1,000,000, maximum 100,000,000). KASPA_X402_HASH_CHAIN_PAYER_FEE_SOMPI sets the payment fee (default 1,000,000, maximum 10,000,000, preserving the public signer's cap). The report records both.

The script creates a private funding shard if needed, generates a new owner and hash chain, broadcasts genesis, serves two loopback x402 resources, claims and broadcasts both payer-signed spends, deliberately abandons a third grant, and broadcasts an owner rotation. It requires both payment responses to be HTTP 200 with PAYMENT-RESPONSE.success = true and each transaction to be selected on chain before reporting success. It records the full response and head lineage locally. It does not reuse an output directory.

Selected-chain PNN run on 6d02163

The run completed on 2026-09-26. One configured PNN supplied the pre-spend UTXO snapshots and coherent selected-chain checkpoint evidence. Genesis reached 30 confirmations; both exact HTTP requests returned 200; an abandoned grant was recovered by owner rotation, leaving the issuer ready at head version 3.

This proves the candidate's funded Testnet-10 flow against that configured PNN. It is not independent multi-node corroboration, a hosted browser demo proof, or mainnet evidence. The browser/host wiring added later must be checked separately after deployment.

Post-review run on bd62fee

The run started at 13:08:11 UTC and completed at 13:08:58 UTC. Its KIP-20 covenant ID was d1d1550880711277ec26d8a30fba9d4de2ad61aedcdc298784bf6726d746dec3 through genesis, both payer borrows and owner rotation.

Both payments increased the same head by the quoted 20,000,000 sompi. The private report records selected-chain readback, the accepting blocks, both x402 settlement responses and hashes of seven built modules and the proof script. Those hashes match the rebuilt files from bd62fee. A fresh readback after the run still found all four transactions selected. Genesis had 30 selected-chain confirmations; the payment and rotation evidence establishes accepted finality, not 30 confirmations. The proof used one public Testnet-10 RPC node and one REST API, with no independent full-node corroboration or hosted-gateway deployment.

The first attempt against a different RPC endpoint timed out with a funding shard still unspent. The successful retry used that shard and a new private output directory. The first attempt is not counted as a payment proof.

Earlier run (before the grant-readback fix)

The earlier run started at 09:12:40 UTC and completed at 09:13:28 UTC. Its KIP-20 covenant ID was 435c3dbe5ae699e42ceb1dfcef4a572f855801bf43d5ce378112cdc11ca32aee from genesis through both borrows and owner rotation.

Both payments increased the same head by the quoted 20,000,000 sompi. The server returned a resource only after its selected-chain verifier accepted the respective fully payer-signed transaction. The abandoned grant was delivered for version 2 and never used; its local expiry put issuance into needsRotation. The owner then spent that head into a new guard under the same covenant ID. The predecessor of each row is the prior row's output 0; the private report also records the accepting blocks, grant assignments and full x402 settlement responses.

The private report records SHA-256 fingerprints for the exact built core, covenant, server, encrypted issuer, client, facilitator and CLI modules and the proof script. The client bundle fingerprint is 109a27133dad29d2b6e59b9a641c10aa1e72617ebfe461b7f5a32e53e8e87ed0; the server bundle fingerprint is cdd85b814479a53022a312a8923546a1ac682c3fc197fc3a210518557da66fe5.

The genesis was observed with 30 selected-chain confirmations. The payment and rotation checks used the Testnet-10 REST transaction and selected accepting-block status (accepted finality); they did not establish 30 confirmations for those transactions. One public RPC source and one REST API were used, without independent node corroboration. The loopback HTTP server used the candidate SDK and server code; the hosted gateway was not deployed for this proof.

Earlier exploratory runs left separate Testnet covenant heads after a relay fee rejection and an overly strict extra RPC confirmation scan. Those runs are not counted above; their private reports are retained locally for reconciliation.

Source: /docs/hash-chain-live-proof.md