Practice the release workflow
These procedures use public fixture keys and local test coins. For a first browser interaction, use the shorter local-wallet tutorial; it is not a release rehearsal.
| Purpose | State and authority |
|---|---|
| Manual local release | Shared chain 31338 stays running across commands. You approve ordinary release transactions. |
| Automatic release rehearsal | An owned chain 31338 is created and removed for the run. Only fixture transactions are approved. |
| Approval rejection/success checks | An explicit reviewed approval image is tested in its own disposable chain; no public broadcast. |
Keep a local release between commands
Install the locked dependencies through source setup. In the source checkout, select one local context and project and use them for every command below:
CTX=your-local-context &&
PROJECT=cam-release-practice &&
INSTANCE=/absolute/private/pay-to-play-local &&
make network/local/up DOCKER_CONTEXT="$CTX" COMPOSE_PROJECT_NAME="$PROJECT" &&
make pay-to-play/release/setup DOCKER_CONTEXT="$CTX" COMPOSE_PROJECT_NAME="$PROJECT" INSTANCE="$INSTANCE" &&
make pay-to-play/release/deploy DOCKER_CONTEXT="$CTX" COMPOSE_PROJECT_NAME="$PROJECT" INSTANCE="$INSTANCE" &&
make pay-to-play/release/verify DOCKER_CONTEXT="$CTX" COMPOSE_PROJECT_NAME="$PROJECT" INSTANCE="$INSTANCE"Choose local in setup. It fixes chain 31338, the internal RPC http://release-anvil:8545 and its public fixture deployer. Setup still prepares protected instance files; each signed phase still requests transaction approval. Use separate instance directories for other apps.
For browser use, follow the hosting pause and host the prepared bundle at a browser-readable HTTPS or supported IPFS URI before CAM publication. The shared fixture's private resource server serves checked-in resources; it does not automatically host a newly prepared bundle.
After publication, use the final publication artifact printed by that operation:
make network/local/viewer/up \
DOCKER_CONTEXT="$CTX" COMPOSE_PROJECT_NAME="$PROJECT" \
APP=pay-to-play \
DEPLOYMENT_ARTIFACT_FILE=/absolute/private/operation/cam/artifact/cam-publication.json \
RESOURCE_ORIGIN=https://your-bundle-host.example/app/Replace the artifact path and resource prefix. The foreground viewer normally listens on loopback port 5174. It discovers the publication from the supplied coordinates, deploys nothing and attaches no wallet. Its local /rpc endpoint permits fixture writes; public test keys are unsuitable for any valuable account.
Stopping the viewer leaves the shared chain running. Run the final command only when you intend to remove that chain and its state:
make network/local/viewer/down DOCKER_CONTEXT="$CTX" COMPOSE_PROJECT_NAME="$PROJECT" &&
make network/local/down DOCKER_CONTEXT="$CTX" COMPOSE_PROJECT_NAME="$PROJECT"network/local/info prints running-service coordinates; network/local/status includes stopped-container state and health. No release command owns the separate lifetime of this shared network.
Rehearse automatically on a disposable chain
make pay-to-play/release/rehearsal/run DOCKER_CONTEXT=your-local-contextSubstitute the Bike NFT or Escrow prefix to test those apps. make dapps/release/rehearsal/check runs all three. These checks need locked Solidity/JavaScript dependencies, but no operator credentials or manually chosen approval image.
The rehearsal snapshots current source, including nonignored uncommitted files, into a private temporary Git candidate. It drives ordinary business and projection deployment, hosts the prepared bundle privately, approves CAM publication, tests keyless artifact reconstruction, accepts fixture handoffs, and loads the app. The candidate commit—not the original checkout's HEAD—identifies the tested bytes.
Owned containers, networks and copied dependency trees are removed on successful cleanup. Candidate source, ordinary phase records and logs remain at the printed path. RELEASE_APPROVAL_IMAGE_OUTPUT_DIR can select an existing external folder for dated rehearsal records. Reused operator images remain; a newly owned rehearsal image is removed only after its containers stop.
This exercises local release composition and handoffs, not a public RPC, public hosting/CORS, explorer verification or the integrating business service.
Test a particular approval image
Build or select the reviewed image, then use its exact ID and an existing external records directory:
make release/approval/image/build DOCKER_CONTEXT=your-local-contextmake escrow/release/approval/start/check \
DOCKER_CONTEXT=your-local-context \
RELEASE_APPROVAL_IMAGE=sha256:<reviewed-image-id> \
RELEASE_APPROVAL_IMAGE_OUTPUT_DIR=/absolute/existing/image-recordsThe startup check drives the first transaction review and rejects it automatically. It requires unchanged fixture nonce, no approval/transmission and owned cleanup. Do not intervene by approving during the test.
Replace approval/start/check with approval/success/check to exercise successful fixture approval. It checks ordered audits, mined receipts, complete artifacts and handoffs; it automatically approves only within its owned local chain. Both targets support all three apps. A fresh records subdirectory is allocated on every run.
Explicit approval rehearsals have a ten-minute execution deadline and allow up to seven additional minutes for nested cleanup. Let cancellation finish. See diagnostics for log limits and the separate simulation experiment.
Source: release and local-network targets, and rehearsal drivers.