PRIVACY LIMITATIONS
Beyul does not claim absolute anonymity.
Privacy here is an engineering property with stated dependencies and stated failure modes — not a magic guarantee. This page lists both.
Research prototype · no testnet · no mainnet · unaudited · not production-private · not safe for funds
Privacy depends on
Protocol design
The shielded pool and disclosure model define what can be hidden at all.
Wallet implementation
A flawed or compromised wallet can leak what the protocol protects.
Operational security
Key handling, device security and recovery material remain the user’s responsibility.
Network conditions
Transport and timing characteristics of the network affect what observers can infer.
User behavior
Reuse patterns, disclosure habits and off-chain context all shape real-world privacy.
What may still occur
- Metadata leakage may occur — timing, fees and mempool activity are observable.
- Timing correlation may occur.
- Wallet compromise may reveal activity.
- A disclosure you grant reveals information — intentionally, and irreversibly to its recipient.
No global administrator view key exists.
No one — including the Beyul team — holds a master viewing key to user transactions. A continuously tested design property, not yet an audited guarantee.