Example apps

These apps demonstrate how a contract-defined workflow uses dapp32. Each app owns its business rules and publishes its own CAM bundle. The generic viewer interprets those bundles; it has no Bike NFT, Escrow or Pay-to-Play business logic.

The app guides explain behavior and local demos. The deployment guides explain how an operator creates and verifies an instance. No deployed addresses are implied by these documentation pages.

What the demo launchers are for

Use a demo to explore an app’s workflow or manually test changes to its contracts, CAM bundle and viewer together. Each launcher starts its own disposable Anvil blockchain (chain ID 31337), deploys fresh app contracts, serves the CAM resources, and starts the generic viewer. Open the URL it prints.

• make bike-nft/local/demo/gui/up — Bike NFT demo guide
• make escrow/local/demo/gui/up — Escrow demo guide
• make pay-to-play/local/demo/gui/up — Pay-to-Play demo guide

Run from a source checkout with Docker, Compose and Make, after installing the locked dependencies. Keep the command running while using the demo. Exiting attempts cleanup; closing the browser tab does not stop it. Treat all chain state as temporary. The app guides explain wallet setup and each demo’s matching down command if cleanup fails. A demo does not attach a signing wallet automatically.

To view contracts already deployed on a public chain, use make viewer/release/up with their saved deployment.json; it asks for the artifact path and a browser-public RPC, and deploys nothing. To practice the actual deployment and approval process, follow the local release workflow on chain 31338.