> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usespoke.xyz/llms.txt
> Use this file to discover all available pages before exploring further.
# Proof and deployments
> Inspect public receipts, contract sources, and reproducible testnet evidence without confusing fixtures with traction.
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
| Surface | Link |
| - | - |
| Live application | [usespoke.xyz/explore](https://usespoke.xyz/explore) |
| Demo walkthrough | [usespoke.xyz/demo](https://usespoke.xyz/demo) |
| System status | [API system status](https://api.usespoke.xyz/v1/system/status) |
| Endpoint coverage | [API endpoint registry](https://api.usespoke.xyz/v1/system/endpoints) |
| Developer surface | [Spoke developers](https://usespoke.xyz/developers) |
| Source repository (access required) | [Enoch208/spoke](https://github.com/Enoch208/spoke) |
## Documentation and SDK distribution
The [hosted documentation](https://docs.usespoke.xyz) is published through Mintlify. The [npm package `@enochid/spoke-sdk@0.1.2`](https://www.npmjs.com/package/@enochid/spoke-sdk) and matching [SDK v0.1.2 release](https://github.com/Enoch208/docs-madonna/releases/tag/sdk-v0.1.2) provide a versioned package and SHA-256 checksum. Its release process checks clean installation, both JavaScript module formats, and TypeScript declarations. Read the [SDK guide](/developers/sdk) for the exact installation command and runtime requirements.
## Frontend-to-backend journey
The checked [production journey artifact](https://github.com/Enoch208/spoke/blob/main/packages/contracts/deployments/10143-production-journey.json) 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](https://usespoke.xyz/c/3) shows the public testnet offer.
* [Its network](https://usespoke.xyz/c/3/network) exposes attribution and sale outcomes.
* [Sale 4](https://usespoke.xyz/receipts/10143/4) is finalized with claimed allocations.
* [Sale 5](https://usespoke.xyz/receipts/10143/5) records the refund outcome.
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](https://github.com/Enoch208/spoke/blob/main/packages/contracts/deployments/10143-proof.json) 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](https://github.com/Enoch208/spoke/blob/main/packages/contracts/deployments/10143.json) 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](/developers/local-development), then the repository's [settlement fixture instructions](https://github.com/Enoch208/spoke/blob/main/packages/contracts/README.md). Use fresh test wallets and keep signing material private. Never present a replayed fixture as independent user activity.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.