Skip to content

Update an existing app ​

First identify what changed. A viewer image, workflow files and a contract are different components with different update procedures.

Changed componentProcedure and authority
Browser viewerThe server operator replaces its image. No CAM transaction.
Compatible labels, screens or navigationPrepare and host CAM files; the current root owner approves their publication.
Read-only Solidity projectionDeploy or select the projection, then publish compatible resources/bindings. Deployer and CAM owner may differ.
Business behavior or incompatible ABIPlan replacement and migration. This is not a UI refresh.

Publish compatible navigation or screen changes

Run on
The release operator's machine, in the reviewed source checkout, using its local Docker engine and private instance.
Requires
Retained evidence for compatible business/projection contracts and an existing CAM root; current publication-owner approval.
Changes
Prepared files and approved CAM reference/binding transactions, not an intended business-contract replacement.

These examples use Pay-to-Play; substitute the app prefix for another app. Verify its deployed ABI and policy before selecting today's authored files. A new operation must select the intended source revision; editing defaults does not rewrite an older operation's retained inputs.

CTX=your-local-context &&
INSTANCE=/absolute/private/pay-to-play-fuji &&
make pay-to-play/release/verify DOCKER_CONTEXT="$CTX" INSTANCE="$INSTANCE" &&
make pay-to-play/release/cam/bundle DOCKER_CONTEXT="$CTX" INSTANCE="$INSTANCE"

Select the compatible saved components and existing root. Preparation exports their original ABIs, combines authored files, refreshes pins and checks conformance. It sends no transaction. Inspect the selected identities and the printed bundle.

Host only that bundle's contents at a new versioned location, preserving paths and browser access. Compare the served bytes with the prepared files. Never upload private instance/configuration records.

make pay-to-play/release/cam/publish DOCKER_CONTEXT="$CTX" INSTANCE="$INSTANCE"

Select the prepared bundle and existing root, supply its manifest URI when prompted, and inspect every binding, hash and owner change before approval. This command does not upload files. A nominated future owner cannot publish before accepting.

Replace the read-only projection

Use this path when screen data requires a new Solidity read helper but the business contracts remain compatible. Run from the selected projection/authored source, retaining the original backing-contract evidence and its source.

make pay-to-play/release/ui/update DOCKER_CONTEXT="$CTX" INSTANCE="$INSTANCE"

The menu offers a new projection, a saved projection or a saved update to resume. Choose the existing root and compatible backing contracts. The operation prepares matching CAM files and updates that root only through approved transactions; it does not replace the business contracts.

For a new hosting location, omit settings.CAM_URI from the referenced CAM configuration before starting the new operation. At the hosting pause, host the printed files and repeat the same command, choosing Resume and entering their URI. A configured URI can skip the pause; ensure those bytes are hosted before approving publication.

To deploy a projection candidate without changing the app, use release/ui/deploy instead. Its saved artifact can be selected later; deployment alone changes no root reference. Separate projection-deployer and CAM-owner configurations are described in operation inputs.

Check the new publication

make pay-to-play/release/verify DOCKER_CONTEXT="$CTX" INSTANCE="$INSTANCE" &&
make viewer/release/up DOCKER_CONTEXT="$CTX" INSTANCE="$INSTANCE"

Select the completed publication and open a fresh session. Refreshing a screen's read does not reload publication resources. Inspect the chain, root, resource integrity, intended bindings and a known task. For the Pay-to-Play navigation update, check all six destinations and that the balances/keys belong to the same intended payment contract.

Historical record verification does not prove current ownership or every critical action. Test the intended authorities and app behavior before accepting the cutover. Stop this local viewer with viewer/release/down; permanent server hosting has its own lifecycle.

Business replacement needs a migration decision

A new business contract has a new address and state. Pay-to-Play vouchers bind the verifying-contract address; changing an ABI or manifest cannot move deposits, permanent keys or signatures. Specify the client/state transition and treatment of the old instance before deploying a replacement.

Recover or reverse deliberately

Keep failed attempts and resume the selected operation. Resolve uncertain submissions before approving another creation. Restoring an earlier CAM publication is itself an authorized on-chain update and may be incompatible with subsequent changes; rolling back a viewer image does not perform that reversal.