Skip to content

Use Bike NFT ​

Bike NFT is a digital registry for bicycles and bicycle components, such as frames, motors, batteries and suspension parts.

An authorized registrar creates a record for a component using its serial number. Registration creates a unique digital token (NFT) on-chain, associated with that component.

The blockchain records the component's serial number, token ownership, service status and missing-report status. Owners can transfer their tokens when selling components, with each transfer recorded on-chain.

Additional component information, such as descriptions, photographs, specifications and supporting documents, is stored off-chain. The on-chain registry links to this information, allowing it to be maintained without storing entire documents on the blockchain.

Owners can also authorize workshops to update specific component information. These permissions are managed on-chain, can be limited in scope and duration, and can be revoked by the owner.

Find the component before acting

Open the intended chain and CAM host. Enter the exact serial, including case and spaces, and choose Look up component. Check its owner, collection, token ID, service state and missing-report state.

Editing the search input does not change the displayed loaded component or the target of its actions. Look up the new serial first. Connect the intended wallet and let the view refresh before preparing a write.

Register an unused serial

  1. Connect a wallet with the manager's registrar role. Choose Check registration for the unused serial.
  2. Enter the initial owner's address. It can differ from the registrar. Prepare the token document using the metadata guide, including its collection-base check.
  3. Choose Register component, review and send. After a successful receipt, check the loaded record and NFT owner.

The serial determines the token ID from its hash; it is not a short human identifier or a metadata digest. Losing registrar authority removes permission to create records, not ownership of existing NFTs.

Choose the right authority

TaskWho can authorize it?
RegisterA manager-authorized registrar.
Change metadata or manage a missing reportThe owner or a workshop with that specific live capability.
Take out of service, reactivate or manage grantsThe current token owner.
Handover through the appThe current owner, through a direct NFT transfer.

Hand over ownership or authorize a workshop explains expiry, replacement presets and transfer invalidation. These grants are not NFT transfer approvals. Account profile information is separately self-managed by its account and grants no registry authority.

Missing reports and service state

Use Report component missing with a nonempty published report URI. Resolve it with Resolve missing report and a resolution URI. These are public references, not encrypted private messages or proof of an investigation.

Take out of service and Reactivate change a separate owner-controlled lifecycle flag. Neither opens, resolves nor erases a missing report. Current contracts still allow metadata corrections and ordinary token transfers in either service state; older irreversible retirement contracts retain their old behavior.

Try locally

After source setup, start:

make bike-nft/local/demo/gui/up \
  DOCKER_CONTEXT=your-local-context COMPOSE_PROJECT_NAME=cam-demo

Keep it running and open the complete printed URL, normally on loopback port 5173. Read DEMO-FRAME-001, DEMO-BATTERY-001, DEMO-MOTOR-001 or DEMO-BIKE-001 without a wallet. Choose Load preview to inspect its metadata.

Follow Attach a local test wallet using FIXTURE_WALLET_APP=bike-nft and the same context/project. Its seller, mechanic and buyer are public fixture identities; the latter two need local gas before sending. Practice registration with a new serial, not an already seeded one.

Detach the wallet, stop the launcher and let cleanup finish. The explicit matching cleanup is:

make bike-nft/local/demo/gui/down \
  DOCKER_CONTEXT=your-local-context COMPOSE_PROJECT_NAME=cam-demo

The current fixture pins SHA-256 of the exact CAM manifest bytes. That local result does not qualify a public deployment. Closing a browser tab alone does not stop the fixture or erase its state.

Know which contract owns the action

BicycleComponents owns the ERC-721 tokens. BicycleComponentManager owns registry actions and workshop grants. The read-only projection returns screen data; CamRoot publishes resources and contract bindings. The viewer submits calls to those actual destinations.

Manager pause and collection pause are separate. A paused manager blocks its registry writes, not direct token transfers; a paused collection blocks transfers. A manifest label, preview or enabled control is not authorization: inspect the actual call and wait for its receipt.

Deploy or accept administration

Use Bike deployment settings with the shared release procedure. For a pending nominee, open Deployment handovers, connect the nominated wallet and check the specific contract and acceptance time. CAM ownership and the two delayed administrator handovers are independent.

Source baseline: 04a18763. This page changes no older deployment's permissions, metadata-prefix policy or retirement semantics.

CAM route reference

The table is checked against the committed manifest. Read routes supply screens; write routes prepare calls and continue after successful execution.

Show route calls and continuations
RouteKindContract functionContinuationUser-facing purpose
deploymentHandoversreadviewDeploymentHandovers(camHost, account)ui.app(view={'screen': 'deploymentHandovers', 'task': {'paused': '$outputs.0.paused', 'componentTokenPaused': '$outputs.0.componentTokenPaused', 'cam': '$outputs.0.cam', 'components': '$outputs.0.components', 'manager': '$outputs.0.manager', 'actions': '$outputs.0.actions', 'navigationSerial': ''}, 'navigationSerial': '', 'navigation': 'navigation'})Inspect independent CAM ownership and Components/Manager administrator handovers.
acceptCamOwnershipwriteacceptOwnership()routes.deploymentHandoversWithContext(serialNumber=$inputs.serialNumber)The nominated owner accepts ownership directly on the selected CAM host.
acceptComponentsAdminwriteacceptDefaultAdminTransfer()routes.deploymentHandoversWithContext(serialNumber=$inputs.serialNumber)The nominated Components administrator accepts after its chain-time delay.
acceptManagerAdminwriteacceptDefaultAdminTransfer()routes.deploymentHandoversWithContext(serialNumber=$inputs.serialNumber)The nominated Manager administrator accepts after its chain-time delay.
findComponentFormreadviewEntry(account)ui.app(view={'screen': 'entry', 'task': {'serialNumber': '$inputs.serialNumber', 'actions': '$outputs.0.actions', 'paused': '$outputs.0.paused', 'componentTokenPaused': '$outputs.0.componentTokenPaused', 'account': '$outputs.0.account', 'canRegister': '$outputs.0.canRegister', 'accountInfo': '$outputs.0.accountInfo'}, 'navigationSerial': '$inputs.serialNumber', 'navigation': 'navigation.find'})Return to component search with the selected serial.
deploymentHandoversWithContextreadviewDeploymentHandovers(camHost, account)ui.app(view={'screen': 'deploymentHandovers', 'task': {'paused': '$outputs.0.paused', 'componentTokenPaused': '$outputs.0.componentTokenPaused', 'cam': '$outputs.0.cam', 'components': '$outputs.0.components', 'manager': '$outputs.0.manager', 'actions': '$outputs.0.actions', 'navigationSerial': '$inputs.serialNumber'}, 'navigationSerial': '$inputs.serialNumber', 'navigation': 'navigation'})Inspect deployment handovers while retaining the selected serial.
entryreadviewEntry(account)ui.app(view={'screen': '$outputs.0.viewId', 'task': '$outputs.0', 'navigationSerial': '', 'navigation': 'navigation.find'})Look up a component or edit the viewed account’s profile.
componentreadviewComponent(serialNumber, account)ui.app(view={'screen': '$outputs.0.viewId', 'task': '$outputs.0', 'navigationSerial': '$inputs.serialNumber', 'navigation': 'navigation'})Read one component and its available actions.
registerreadviewRegister(serialNumber, account)ui.app(view={'screen': '$outputs.0.viewId', 'task': '$outputs.0', 'navigationSerial': '$inputs.serialNumber', 'navigation': 'navigation'})Check whether a serial can be registered.
registerComponentwriteregisterComponent(owner, serialNumber, tokenURI_)routes.component(serialNumber=$inputs.serialNumber)Mint the component NFT and register its serial.
setAccountInfowritesetAccountInfo(infoURI)routes.findComponentForm(serialNumber=$inputs.serialNumber)Set the sending account’s public information URI.
updateComponentMetadatawritesetComponentMetadata(serialNumber, tokenURI_)routes.component(serialNumber=$inputs.serialNumber)Update the component NFT’s metadata URI.
markComponentMissingwritemarkComponentMissing(serialNumber, reportURI)routes.component(serialNumber=$inputs.serialNumber)Open a missing report with its published URI.
clearComponentMissingwriteclearComponentMissing(serialNumber, resolutionURI)routes.component(serialNumber=$inputs.serialNumber)Resolve the missing report with a resolution URI.
decommissionComponentwritedecommissionComponent(serialNumber)routes.component(serialNumber=$inputs.serialNumber)Owner takes the component out of service without erasing missing reports.
reactivateComponentwritereactivateComponent(serialNumber)routes.component(serialNumber=$inputs.serialNumber)Owner returns an out-of-service component to service.
delegationreadviewDelegation(serialNumber, delegate, account, duration)ui.app(view={'screen': '$outputs.0.viewId', 'task': '$outputs.0', 'navigationSerial': '$inputs.serialNumber', 'navigation': 'navigation'})Inspect a workshop grant and preview its expiry.
setComponentDelegatewritesetComponentDelegate(serialNumber, delegate, capabilities, validUntil)routes.component(serialNumber=$inputs.serialNumber)Owner grants expiring, scoped workshop permissions.
revokeComponentDelegatewriterevokeComponentDelegate(serialNumber, delegate)routes.component(serialNumber=$inputs.serialNumber)Owner revokes workshop permissions.
transferComponentwritesafeTransferFrom(address,address,uint256)(from, to, tokenId)routes.component(serialNumber=$inputs.serialNumber)Owner transfers the NFT directly to its recipient.