Proof where it counts.Choice everywhere else.
WetDrool separates durable protocol facts from fast, replaceable services. That makes the network independently verifiable without asking every screen to feel like a block explorer.
This page describes the intended protocol. Live writes remain disabled until the SDK, programs, and real-validator tests pass.
Four layers
Canonical is a narrow word on purpose.
The less a protocol must own, the more operators can improve the experience without capturing it.
- 01
Compact and verifiable
DroolNet proof
Identity roots, delegations, selected public relationships, hashes, references, governance state, payments, and tombstones belong in compact protocol state—not raw media or private information.
- 02
Content-addressed
Signed content
Versioned manifests carry body and media references, language, warnings, accessibility fields, audience, hashes, and signatures. Deletion-compatible storage remains the default.
- 03
Rebuildable
Open projection
Indexers validate events and manifests into fast search and feed views. Their databases are disposable projections, never the canonical social network.
- 04
Replaceable and humane
Human experience
Clients, relays, gateways, media workers, and recommendation providers make the network pleasant. People can replace them without replacing who they are.
Replaceability test
If it goes away, what survives?
RPC unavailable
Reading degrades, identity survives.
The client tries configured alternatives and explains freshness. Cached public reading should not become a blank screen.
Indexer unavailable
Convenience pauses, proof remains.
Another operator can replay protocol events and verified manifests. The flagship projection is not the source of truth.
Client disappears
Your identity opens elsewhere.
Public specifications and portable provider settings let a compatible client continue without a proprietary interpretation service.
Permanence deserves consent
A content hash is not a promise of erasure.
Ordinary publishing is designed to prefer deletion-compatible storage. Permanent providers require item-specific consent. Tombstones tell compliant clients to stop serving content, while receipts must explain which independent or immutable copies may remain.
Inspect the boundary