Daemonet/Ecosystem/DaemonCoin

Closed-loop resource credit · protocol verification

Useful service earns credit.
Claimed capacity does not.

DaemonCoin is the proposed accounting layer for contributed DaemonCloud infrastructure. A provider can offer spare capacity to one exact regional resource pool, but credit is earned only after bounded service evidence is accepted by the consumer and a separately certified verifier.

Current truth: the repository defines a closed-loop, holder-bound test-credit protocol, an offline DaemonSeed policy ceremony, and a bounded Gate-local durability reference. Storage is the first active reference class. No public blockchain, transferable coin, exchange listing, fixed conversion, investment return, production issuance, authenticated settlement service, or live provider marketplace is claimed. Compute and bandwidth settlement remain planned.

REPOSITORY FOUNDATIONPool measurement, accepted-head schedules, staged storage evidence, offline policy delegation, and a bounded local settlement journal are implemented under verification. NOT A TOKEN SALENo purchase solicitation, appreciation promise, dividend, governance right, or redemption guarantee appears here.

One causal chain

Measure the work before settling the credit.

A storage provider first quotes exact bytes, interval, pool, and a settlement-accepted schedule. The customer accepts that exact service. After delivery, the provider, customer, and a distinct verifier bind their signatures to the same evidence before a settlement signer may advance a holder's balance.

Announcing a large drive changes neither a balance nor a reward. Capacity evidence may influence the next market schedule, but only verified delivery can enter the reward path.

Measure a pool

A certified measurement key reports verified usable and committed capacity for one resource class and region.

Accept a schedule

A measurement key publishes integer rates within cold-policy bounds. A separate settlement key accepts one exact successor head, with at most one bounded adjustment per 24-hour rate anchor.

Prove service

Provider, consumer, and separately certified verifier attest to the exact aggregate byte-time service—not a self-reported disk total.

Advance a balance

A separate settlement key applies one reward or holder-authorized spend to a hash-chained state. The local reference commits its account head and one-use quote and receipt causes atomically.

Scarcity has a bounded job

Lower spare capacity can raise credits quoted per resource unit and the reward offered for verified service. It does not create a protocol guarantee that DaemonCoin/USD, DaemonCoin/BTC, or any speculative market must rise.

Separate resource markets

Storage is not compute wearing a different label.

Each class and region needs its own evidence, utilization, and schedule. A storage shortage in one region must not silently price a GPU job elsewhere. Balances can remain usable across activated services while every cause of a debit or reward stays bound to its exact pool.

01

Storage GiB-hour

The first active reference unit. Each provider quote rounds its aggregate upward; verified rewards apply attested availability and round downward. A future customer-order layer must aggregate billing across a multi-provider shard set.

02

Compute vCPU-second

Reserved vocabulary only. Sandboxing, result verification, memory accounting, egress, and workload trust classes remain release gates.

03

Bandwidth GiB

Reserved vocabulary only. Direction, relay role, abuse handling, duplicate traffic, and independently verifiable delivery remain unspecified product work.

04

Global holder balance

Credits are not trapped in the pool that caused them. Every quote, receipt, reward, and spend still names the exact pool and schedule that caused the transition.

Separated authority

No one online key defines the market and pays itself.

The cold DaemonSeed policy key defines bounds and certifies narrowly scoped online keys. Measurement cannot settle balances. Settlement cannot rewrite utilization. A provider cannot verify its own service, and a consumer cannot mint a reward merely by signing with the provider.

COLD

Policy authority

The offline DaemonSeed ceremony inspects and pins one genesis policy, then journals narrowly scoped signer certificates before export. It does not perform routine online measurement or settlement, and no policy-successor ceremony exists yet.

OFFLINE BOUNDARY
HOT · SCOPED

Measurement signer

Signs short-lived capacity snapshots and schedules for certified pools. It cannot create credits or debit a holder.

NO BALANCE AUTHORITY
HOT · SCOPED

Settlement signer

Advances an exact holder chain only after validating the causal artifact. It cannot set a price or attest that service occurred.

NO MARKET AUTHORITY
SERVICE

Provider

Commits capacity and signs exact delivered-service evidence. Its own signature is necessary but never sufficient for reward.

NO SELF-PAYMENT
CUSTODY

Consumer

Accepts service and signs spends with holder-controlled authority. A network operator cannot transfer the holder's test credits on its own.

NO IMPLIED TRANSFER
SEPARATELY CERTIFIED

Verifier

Checks the same bounded service evidence and must be cryptographically distinct from provider, consumer, measurement, settlement, and cold-policy roles. Distinct keys do not prove independent operators or prevent collusion.

DISTINCT KEY REQUIRED

Honest limits

A signed test-credit protocol is not yet an economy.

Real operation still needs an authenticated and externally anchored settlement service, provider admission, anti-collusion and Sybil controls, audited measurement, incident handling, tax and accounting treatment, and evidence that rewards actually sustain reliable capacity.

01

Local durability is not consensus

The Gate package can atomically select one configured cold-policy, market, and account history in a bounded private journal. It has no listener, cross-Gate consensus, or external anti-rollback anchor and is not a live settlement operator.

02

Collusion remains possible

Signatures prove which keys approved evidence, not that nominally different people or machines are economically independent. Admission and audits remain necessary.

03

Credits are not dollars

There is no fiat peg, cash redemption, exchange value, liquidity, appreciation promise, or protection from later testnet reset.

04

Capacity is finite

Higher rates cannot conjure disks or CPUs instantly. Admission control, reserves, repair priority, and dependable commercial capacity remain operational safeguards.

05

No escrow or refund yet

The current test spend is an irreversible pre-service debit. Failed service blocks provider reward but does not restore customer credits; hold, finalize, dispute, and refund transitions remain release gates.

06

Shard billing is not aggregated yet

A provider quote aggregates only that provider's service. The customer-level order needed to round one multi-provider placement once is not implemented.

Release evidence

Launch only after the feedback loop survives reality.

A production decision needs multi-provider aggregate orders, reserve/finalize/refund behavior, storage over long intervals, forced outages and repairs, receipt and quote replay attacks, market and policy forks, dishonest capacity reports, split-service rounding attacks, signer compromise and rotation, settlement recovery, price-oscillation simulations, privacy review, and independent economic and legal analysis.

Strongest accurate statement

DaemonCoin currently provides signed closed-loop test-credit primitives, an offline policy/delegation ceremony, and a bounded local durability reference for pool-specific verified storage service. Measured scarcity can adjust resource prices and rewards within signed bounds; no external value, public token, or live production marketplace is promised.

Measured capacity · bounded settlement

Contribute useful infrastructure.
Prove the service, then earn the credit.

This page does not offer, sell, list, or promise appreciation of a crypto asset. Product naming remains subject to clearance.