Keep the alpha available
Cover one small server, Tor control paths, monitoring, backups, and the founder’s real-world field canary.
Community Funding
Fund the infrastructure. See what it unlocks.
Daemonet can accept voluntary Bitcoin support directly into the operator’s self-custody wallet, publish aggregate progress, and connect funding thresholds to specific operating capacity and evidence gates.
Payments are disabled in private alpha. This page does not create an invoice.
Why community funding
Turn interest into visible operating choices—not hidden pressure.
Early infrastructure costs are concrete: a small always-available server, independent Daemongates, relay capacity, storage, release signing, security review, and continuity. Aggregate support can show which pieces the community values without requiring an advertising profile.
Funding a threshold can make work possible. It does not make an untested feature complete. Every release still has to cross its technical, security, and operating evidence gate.
Add independent Daemongates
Move from one development gate toward the three independently keyed domain-control witnesses required by the verified-name product.
Improve reachability
Add independently operated entry locations and health evidence without claiming global availability before it exists.
Fund explicit bandwidth
Introduce separately metered relay only after direct-only behavior, routing policy, abuse controls, and cost accounting are proven.
Test storage and recovery
Pay for independent encrypted capacity and destructive restore drills—not a premature promise of infinite storage.
Buy external scrutiny
Fund protocol review, penetration testing, release integrity, legal work, incident readiness, and continuity evidence.
Funding contract
Show the runway, the dependency, and the stop condition.
A useful transparency page should distinguish wallet settlement from spend, recurring operating cost from one-time work, repository completion from live proof, and a planned unlock from a generally available service.
Publish settled totals and optional name attribution. Do not turn donor behavior into a marketing profile or public transaction graph.
Label work as research, repository-built, field verification, private alpha, public beta, or release. Money cannot skip the state.
Separate recurring servers, bandwidth, storage, security, and support from feature-development targets.
If capacity cannot be sustained, publish the risk and export path before ending a managed service whenever safety and law allow.
Support pays an operator-controlled wallet. The watcher only observes; the operator manually signs and sweeps treasury transactions.
A donation is not a product purchase. Any beta grant or service right is a separate, explicit, signed authorization.
Attribution
Support may remain completely anonymous. A key-controlled DaemonChat name may opt in to a public settled total, but no donation is attributed from a payment address, invoice, or guessed identity.
How support will work
Direct payment, narrow observation, signed receipt.
The support console requests an amount and receives a Lightning invoice. Settlement goes directly to the self-custody wallet. A return handle can check status without revealing a name, and a signed receipt records the contribution.
Choose an amount
Use a suggested or custom satoshi value. No identity claim is required.
Pay the invoice
The wallet watcher sees settlement but has no key capable of moving the funds.
Keep the receipt
An unguessable handle and signed receipt let the supporter verify exactly what was observed.
Attribute only by choice
An authenticated name holder may explicitly bind the settled cumulative total to that public name.
Private alpha comes first