Roles
Necter has three main roles. One person can hold all three, and a single server can be both a miner and a validator, but each role has its own keys and rules.
| Role | Who | Runs | Trust and weight | Paid by |
|---|---|---|---|---|
| Developer | Anyone who builds a module or a project | HiveKit + hivec, a backend that submits tasks or reads results |
An enrolled developer account (Sign-In with Ethereum); projects are operator-reviewed before listing on the testnet | The developer share of each epoch’s fees (fee_split_bp.developer) |
| Miner | Anyone, on a phone, laptop, desktop or server | The Necter Miner (macOS app, Android app, or the necter-miner CLI/daemon) |
NECTA collateral bonded per device and project, plus a reputation score | The miner share, per verified compute unit, claimed from the project vault |
| Validator | Always-on servers | ndsr serve in committee mode |
Approved by the network operator on the testnet (stake-elected validators are coming soon) | Project epochs pay miners, the developer and the treasury, not validators. Validator economics are coming soon with stake-elected validators |
Developers
Section titled “Developers”You write modules, deploy them, and either call them directly through validator consensus or publish a project: a worker module plus a signed manifest that sets the economics, committee size and device requirements. You fund the project’s vault with its reward token and earn the developer share of every settled epoch. Start with the quickstart.
Miners
Section titled “Miners”A miner device has an ed25519 node key (its identity) and is bound to an owner wallet that bonds collateral and receives payouts. Miners connect outbound to the Hub relay (no open ports), accept task offers when their policies allow it, execute in NDSR and sign votes. Correct votes earn compute units; provably wrong or conflicting votes can be slashed. Start at Mine.
Validators
Section titled “Validators”Validators finalize committee rounds (signing a finality record of who was right), re-execute a random
share of rounds plus every contested one, attest the miner-set snapshots that committees are drawn from,
attest per-project reward receipts, execute direct /v1/execute calls, and keep module state in sync.
On the testnet the four validators run in the US, EU, Asia and Africa; see
Run a validator.
Also on the roadmap
Section titled “Also on the roadmap”The store design includes operators (miners with fleets of devices: device groups and batch subscriptions exist in the API today) and governance (NECTA stakers reviewing listings, voting on proposals and resolving disputes). Governance is coming soon; on the testnet the network operator reviews listings and arbitrates slash disputes.