Deploy & publish overview

There are two levels of “deployed” on Necter:

1. A deployed module. Upload the .hbc; anyone can call it through validator consensus with POST /v1/execute. This is enough for stateful app logic. Upload and call a module
2. A published project. A stateless worker module plus a signed project manifest, registered on-chain, funded through a vault and reviewed for listing. Miners subscribe to it, execute its tasks in committees and get paid. This page is about that path.

The publish flow

flowchart TD
  A[Build a stateless worker .hbc] --> B[Sign in with Ethereum]
  B --> C[Enroll as a developer<br/>auto-verified on the testnet]
  C --> D[Upload the worker<br/>POST /v1/modules]
  D --> E[Write the project manifest<br/>consensus, scheduling, listing]
  E --> F[Validate: POST /v1/developers/projects/prepare<br/>→ canonical bytes, project_id, vault address]
  F --> G[Sign the canonical bytes<br/>personal_sign, EIP-191]
  G --> H[Submit: POST /v1/developers/projects]
  H --> I[Register on-chain, gasless<br/>sign EIP-712 Register → POST …/register]
  I --> J[pending_review]
  J --> K[Create the vault: createVault<br/>needs a little Sepolia ETH]
  K --> L[Fund the vault with the reward token]
  J --> M[Operator review → listed]
  L --> N[Miners subscribe; tasks run in committees]
  M --> N

1. Build and test the worker. It must import no storage.* and no hive.call (Rust, Go or AssemblyScript). hivec inspect shows the imports. Choosing a language
2. Sign in and enroll. Sign in and enroll
3. Upload the worker. Upload and call a module
4. Write and validate the manifest. The project manifest
5. Sign, submit and register. Register a project
6. Create and fund the vault. Vault, reward token, funding
7. Wait for listing review. On the testnet the network operator reviews new projects (pending_review → listed). Governance review is coming soon.
8. Send tasks from your backend, or let the schedule run. Submitting tasks
9. Monitor health, miners, proofs and revenue. Monitoring

In the store or through the API

The store’s Develop → Create wizard does steps 3–6 for you in six screens (Details, Work, Economics, Requirements, Branding, Review): it uploads the .hbc and listing images, validates every field with the Hub as you go, asks your wallet to sign the manifest and the gasless registration, and shows the predicted vault address. Creating and funding the vault are wallet transactions. Everything is also available through the API, which these pages show with curl and a short Python helper.

A complete live example

The testnet’s reference project, Hash Chain Lab (hashchain-lab, project id 0x84588f60bd2190a6c7929d655010de448e15d22d61ec8021b29ef2c56a553743), was published exactly this way. Its worker and manifest are walked through in Verifiable computation.

Project lifecycle

stateDiagram-v2
  [*] --> submitted: signed manifest submitted
  submitted --> pending_review: ProjectRegistered indexed
  pending_review --> listed: approved
  pending_review --> rejected: rejected
  listed --> paused: pause
  paused --> listed: resume
  listed --> delisted
  paused --> delisted

Only listed projects get scheduled work and appear in Discover. paused projects stop new rounds at once and keep paying for finished epochs. There is no ownership transfer: the developer address is part of the project id.