II / the net · dreggnet
the host
cannot lie.
Every cloud asks for your trust. This one hands you a proof instead. On DreggNet, the bytes you're served and the price you're charged are each a cell you re-witness against a committed root. No ID, no card — the chain is your account. A five-year-old clicks deploy; an adept checks the proof.
what you can check yourself
Not a promise — a proof you re-run.
the bytes
Served byte-for-byte from a published site cell (hello.dregg.works is live), the publish sealed in a signed receipt chain. Named open, one lane: moving that commitment onto the public ledger itself, and the visitor-side re-hash — independent of the host, so it cannot be stripped (the extension).
the bill
Value moves Σδ = 0, in-band, per request — the meter is the ledger. Metering and conservation are the same theorem; there is no mystery invoice to dispute.
the account
A capability you attenuate, not a password you surrender. granted ⊆ held — and you can revoke.
And underneath: the runtime is durable, crash-resumable, exactly-once-metered, receipted. You pay for what ran — and can prove what ran is what you paid for.
the workload that transacts
A function, grown a voice.
Your code, mid-request, reaches back through the cap-gated bridge: invoke a service, move value, read and write its own cell — each call weighed against its lease, charged, and signed into the ledger. Not a function that just returns — an agent that can pay, call, and answer for what it spent.
- run a verified node and drive it — real committed turns through the Lean kernel; nothing is a mock
- federations finalize — a re-runnable 3-node BFT federation; a real external client's attested transfer stream-finalized cross-node on n=4
- publish a trust commitment — a cap-gated turn commits your site's hash on-ledger (live example); visitor-side re-hash = the named open half
- billing that can't surprise you — invoices are views over settled receipts; an over-cap charge is a real in-band refusal
- metered-but-unpaid is unrepresentable — the meter advance and the reserve draw are one atomic write; drift isn't forbidden, it's inexpressible
- pay() is one kernel move — every charge desugars to exactly one conserving, signature-gated transfer; settlement is exactly-once per period
- a lapsed lease is a 402 — in-band, from the executor, with the lease named
the service catalog
What the cloud is made of — each entry grounded in the tree, with its seam named. The repo labels its own remainders in the source; this table keeps that discipline.
*.dregg.works names is the opening half.commit real; serving openingdreggnet cloud
The hosted offering being assembled on this substrate — opening soon.
The shape: git push → built in a sandbox → published as a cell → live at your domain, with a real cert, paid in $DREGG. Durable agent execution, hosting, domains, compute — metered per-turn, receipted. Services, not features: the code stays open source either way. What the coin is and isn't →
Where it stands, plainly: the rails are in the tree with end-to-end tests — the site-commitment turn, the jailed-grain rental spine, the metering and spend-cap refusals. What's not yet operated as a public service: the byte-serving gateway for everyone's *.dregg.works names, public grain rental, and the durable-compute tier. Built ≠ operated, and we say which is which.