Skip to main content
Spoke’s evidence is intended to be inspectable. The recorded transactions are scripted demonstrations using non-redeemable SDUSD, not customer revenue, adoption metrics, or financial performance.

​
Open the deployed system

​
Frontend-to-backend journey

The checked production journey artifact records 15 confirmed transactions. It covers campaign 3, a settled sale, a refunded sale, reward claims, authenticated delivery, and refund-driven delivery revocation.
  • Campaign 3 shows the public testnet offer.
  • Its network exposes attribution and sale outcomes.
  • Sale 4 is finalized with claimed allocations.
  • Sale 5 records the refund outcome.
Spoke sale receipt with claimed reward allocations, settlement timeline, policy hash, order key, and explorer link

The settled testnet receipt connects reward allocations to the purchase and settlement evidence.

This journey proves the recorded client/API/contract flow. It is not a claim that every hardware passkey, wallet, device, or future route has been tested.

​
Contract settlement fixture

The Monad Testnet proof artifact records campaigns 1 and 2, finalized sales 1 and 2, and refunded sale 3. Its 58 confirmed transactions include gas funding. The fixture exercises a four-level path, a branch, multiple merchants, exact allocations, refund timing, finalization, claims, and unused-budget withdrawals while liabilities remain protected. Recorded reward and buyer-payment conservation checks reconcile to the contract balance.

​
Source verification

The deployment manifest identifies network, addresses, and verification evidence. Matching deployed bytecode to published source improves inspectability; it does not demonstrate the absence of vulnerabilities.

​
Reproduce the result

Follow local setup, then the repository’s settlement fixture instructions. Use fresh test wallets and keep signing material private. Never present a replayed fixture as independent user activity.