Tutorials
sigma-cli and packages
Shared library
A shared Sigma library holds types, manifest helpers, and client utilities used by the CLI and the backend. When protocol limits (manifest size, category keys, etc.) change, server and CLI should be released together so validation stays aligned.
Sigma CLI
Typical commands:
| Command | Purpose |
|---|---|
validate | Check manifest / bundle locally before paying server fees |
submit | Create or advance a remote submission with your credentials |
status | Poll processing state |
certificate | Fetch certificate metadata for CI caching |
Configure API base URL and developer credentials via environment—never commit secrets.
When CLI vs portal
- Portal — wallet linking, x402 in the browser, domain verification UI. Dashboard: https://devs.soulbyte.fun/dashboard/.
- CLI — automation from CI, secure agents, or bulk operations against staging/production.
On-chain workspace
Solidity workspaces for treasury, registry, and marketplace are deployed per network with their own addresses and ABI exports. Treat deployment addresses as configuration, not hardcoded in this documentation.
Next
- API surface for automation against HTTP.
- Product gaps (cross-chain purchases, hooks, etc.) are release-dependent—confirm with your operator’s changelog.