Supply compute to Murakumo

Anyone can run a Community node. Registration alone is not capacity: a node earns only for work it actually serves.

From node to payout

1. Run a node. Install the Murakumo node runtime on your hardware.
2. Enroll. The node registers with its own did:key. Open enrollment always creates a Community node in pending state.
3. Qualify. The node answers a challenge derived from a fresh nonce. Passing makes it schedulable; it is an admission gate, not an attestation.
4. Serve. Each served job is settled on the ledger: a protocol treasury cut, and the rest to the serving node's DID as earned credits.
5. Withdraw. Earned credits — and only earned credits — can be requested as a payout. Every payout is approved by the protocol operator before settlement.

Payout terms in force

Source: https://api.murakumo.cloud/infer/payout · read 2026-10-09T11:57:30.212Z

What Community means

A Community provider can inspect its own host, so Community nodes receive only public or non-sensitive work. Confidential customer workloads run only on AWAI Secure capacity; there is no fallback between the two.

Running many nodes

Grouping several nodes under one node operator account — one balance, one payout, one counterparty — is proposed and not yet live. Until it ships, each node is its own account.

What is not promised

• No yield, APY or mining reward.
• No guaranteed utilization or minimum earnings.
• No token sale, revenue share or claim on the protocol treasury.