Bike NFT deployment settings
Use these choices with Deploy a new instance, substituting the bike-nft prefix. The normal release creates an empty collection; only the disposable demo registers the sample components.
Choose the authorities before setup
| Authority | What it controls |
|---|---|
| CAM root owner | Manifest publication and contract bindings. |
| Components administrator | Roles on the ERC-721 collection, including its pauser and configurer. |
| Manager administrator | Registry roles, including pauser, configurer and registrars. |
| Registrars | Create serial records and mint components to their intended owners. |
Select explicit pauser/configurer addresses on both contracts and one or more unique registrars. The same account may hold several chosen roles; an unselected deployer role is not an intended standing permission. The release grants the manager the collection's mint/URI-setter roles and removes deployer operational roles unless explicitly selected.
COMPONENTS_ADMIN_DELAY and MANAGER_ADMIN_DELAY are positive transfer delays. Public setup proposes 259,200 seconds (three days) for each and preserves prior choices when revisited. They delay administrator transfers, not ordinary pausing, configuration or role grants.
Choose collection identity and metadata
Set the collection name and symbol. Use an empty base token URI for the generic viewer's complete URL/embedded-JSON workflow; setup's none choice means the empty string.
A nonempty base is an advanced suffix-client choice. The token contract concatenates it with every stored URI, including full URLs and data URIs. Changing that prefix affects existing tokens. Review the metadata boundary before selecting or changing it.
Collection-level contractURI() is separate from token metadata and CAM. Setup's inline choice generates collection JSON containing its name; alternatively provide your own collection URI. Hosting JSON or images does not register any NFT.
Deploy and publish through the shared procedure
Follow new-instance setup, approval and hosting. Keep the whole private instance; phase artifacts identify the created collection, manager, projection and root. Public files are only the prepared bundle's contents.
Preserve exact manifest/resource bytes and browser access before approving the root publication. CAM_HASH=auto commits the prepared SHA-256; a zero commitment is unverified, not a substitute for a correct served bundle.
A compatible projection or workflow update can reuse Components and Manager through the update procedure. Updating the browser alone does not change contracts or add missing deployment-handover routes to an old publication.
Accept three independent handovers
When a final authority differs from its creator, deployment submits a nomination, not acceptance. In Deployment handovers, connect the nominated wallet and inspect the exact target contract, current authority and acceptance time.
| Target | Nominee action |
|---|---|
CamRoot | acceptOwnership(); no CAM acceptance delay. |
BicycleComponents | acceptDefaultAdminTransfer() after its own delay. |
BicycleComponentManager | acceptDefaultAdminTransfer() after its own delay. |
Refresh handovers after chain time passes the deadline, review and send the relevant action, then inspect its successful receipt and updated authority. The old authority remains active until acceptance. No handover is needed when the creator is also the explicitly intended final authority.
For direct calls, Components/Manager addresses are in the business artifact; the root address is in the final CAM publication. Later administrator replacement uses that contract's beginDefaultAdminTransfer followed by nominee acceptance after its current delay. These transfers do not automatically change operational role holders.
Verify history, then inspect current state
bike-nft/release/verify checks retained original-source evidence without signing. Recorded pending nominations are valid historical facts, not proof that today's administration is accepted. Inspect current owners/admins, operational roles, pauses, metadata and publication separately.
Granting a role to a new account does not revoke the old holder. The relevant administrator must revoke it, or its holder can renounce it. Operational role changes have no administrator-transfer delay.
Qualify the intended workflow
Open the app through a compatible viewer; server hosting is separate from release deployment. Verify the selected chain/root/resources, then exercise registration, metadata, reports, reversible service state, temporary workshop access and owner handover using controlled test accounts.
Check that unauthorized accounts fail and that old workshop grants lose authority after transfer. Confirm collection and manager pause effects independently. Public source verification is a separate original-source publication task.
What the records do not establish
The administrator interface is not enumerable: current reads cannot discover every undisclosed role holder. Retained initialization/broadcast evidence and subsequent role-event coverage matter. Deployment records establish provenance, not physical component authenticity, future server availability or every later authority change.
Older irreversible-retirement or delegation designs retain their deployed meaning. Use compatible interfaces; a new CAM file is not a contract migration. Recover interrupted work through retained-operation recovery, not an automatic replacement.
Source: setup fields and business initialization. User guide.