CellScript Artifact Registry: Publish

Publish from your project

cellc reads the artifact from Cell.toml or Artifact.toml, checks it locally, and opens this page only when wallet approval is needed.

Run in the artifact directory $cellc publish --authorise

Source files, build outputs and the private publishing key remain on your machine.

Advanced publishing path

External signing and access recovery

Use this cellc-assisted workspace only for an external wallet, CI handoff, manifest scaffolding, or a publishing key already held by cellc. It does not upload an artifact from the browser.

Artifact identity

Describe what the Registry will name.

The artifact kind controls whether consumers may resolve it as a dependency, declare it as a TCB input, deploy it, or only copy it as local starter material.

Artifact kind Resolver-safe CellScript source with package, build and metadata identity. Source language This is the artifact's source language, independent of CKB-VM target and wire ABI.

Namespace Artifact name

Choose a stable artifact coordinate, for example dob/evolving-dob-profile-v1.

Artifact preflight

Install cellc, then run this once in the local package or artifact directory before authorising a wallet.

cellc package verify --json && cellc publish --dry-run

Local command options

Local package or artifact directory (optional)

Authorise this artifact for publishing.

Grant new publishing access with a CKB wallet, or ask the Registry to check access already held by cellc. Publishing continues only after the server confirms the artifact, expiry and namespace owner.

CKB mainnet Define an artifact, then choose an authorisation path

Move a checked artifact into the Registry.

Approve publishing for —

External signing and access recovery

Describe what the Registry will name.

Artifact preflight

Authorise this artifact for publishing.

Confirm saved access before publishing

Publish

Choose a wallet