Skip to content

Examples and local demos ​

For a first run, follow Pay-to-Play with a local test wallet. It reaches a deposit and cleanup without real credentials. To open an existing public testnet instance, use the Gallery instead. The examples below run on your local Docker engine.

Workflow guides

Pay-to-Play

Fund a position, authorize voucher payments, withdraw and recover balances.

Deployment settings

Escrow

Create agreements, fund work, resolve disputes and withdraw settlement credit.

Deployment settings

Bike NFT

Register components and manage ownership, metadata and workshop access.

Deployment settings

Local demos

Each launcher creates its own disposable Anvil chain on ID 31337, deploys the app, serves its CAM files and prints a viewer URL. It does not attach a wallet automatically. Complete source setup first.

AppStartStop
Pay-to-Playmake pay-to-play/local/demo/gui/upmake pay-to-play/local/demo/gui/down
Escrowmake escrow/local/demo/gui/upmake escrow/local/demo/gui/down
Bike NFTmake bike-nft/local/demo/gui/upmake bike-nft/local/demo/gui/down

Add DOCKER_CONTEXT=your-local-context and use the same COMPOSE_PROJECT_NAME for startup, wallet attachment and shutdown. Keep the foreground launcher running and open its entire printed URL. Closing the browser tab does not stop the fixture.

The complete wallet tutorial shows the separate browser profile, attachment, actor selection and transaction approval. The other app guides retain their app-specific exercises. All fixture keys are public test identities; never use them with real funds.

To rehearse the actual operator approval/publication process rather than just explore an app, use the isolated release rehearsal. Its deployment process and chain are separate from these demos.