Current release status
Public document hashing and exact integer aggregation are live with signed results. Native consensus, mining, issuance, COMPUTE payments and rewards are inactive. Independent operation is not yet demonstrated.
Current status
No general smart-contract or programmable financial-contract service is active. Native customer-funded work-order and receipt-bound settlement logic is an isolated implementation, not an authorisation to spend production funds.
Consent and economics
Any future payment requires a consenting payer, explicit recipients, customer-authorized quotes and separately signed debit authorization under ratified rules. Existing balances and the 21-million cap cannot be overridden by a receipt or administrator.
Historical accounting and the original schedule
Historical facts are preserved separately from future incentive policy. A public Compute Receipt is not an issuance authorization.
| Boundary | Implementation / evidence | Meaning |
|---|---|---|
| Historical records | 8 blocks / height 7 | Original genesis and transfers preserved |
| Historical test issuance | 350 COMPUTE | Seven 50-COMPUTE issuance events; no new issuance here |
| Reconciled migrated balance | 342 COMPUTE | Historical transfers of 5, 2 and 1 remain accounted for |
| Declared schedule | 21-million cap; 50 initial subsidy / 210,000 halving interval | Future issuance eligibility/cadence needs explicit ratification |
Practical procedure
- 1Separate issuance ordinals from a future zero-issuance ordering record.
- 2Check authorized customer funding and exact quoted recipients/fees.
- 3Reject duplicate obligations, replay and unauthorized debits.
- 4Independently reconcile balances and supply; production payments remain disabled.
Original subsidy research (not an activation instruction): issuance ordinal 0 … 209,999: 50 COMPUTE issuance ordinal 210,000 … 419,999: 25 COMPUTE Subsequent halvings remain subject to the declared cap. Current mining / issuance / rewards / payments: INACTIVE.
Limits and failure cases
- Initial zero-issuance qualification does not permanently abolish the original schedule.
- No customer payment, stake transfer or return is offered by the qualification installer.
- No automated retry/refund or rollback of real balances is authorized by a reorganisation example.