Not a mixer.
Beyul does not pool, tumble, or obfuscate funds to break their trail. Privacy here is a property of the protocol, not a laundering service.
COMPLIANCE POSITION
A clear position — not a compliance claim.
Beyul does not market itself as compliant. It is a research prototype exploring one specific capability — user-controlled disclosure — and it is precise about what that is and is not.
Research prototype · no testnet · no mainnet · unaudited · not production-private · not safe for funds
What Beyul is not
Not AML / KYC software.
Beyul does not screen, identify, score, or sanction-check users or transactions. It is not a compliance product and does not replace one.
No regulatory approval.
Beyul does not provide licensing, regulatory approval, or a legal opinion, and does not claim endorsement by any authority.
No “compliance by design.”
Beyul does not claim that privacy plus disclosure equals compliance. That phrasing overstates what any protocol can deliver.
What Beyul explores
User-controlled disclosure
The holder — not the network — decides what is revealed, to whom, and for how long.
Scoped, auditable access
Reconciliation, audit, and institutional review without making everything public by default.
Accountability without default surveillance
A design where verification is possible on the holder’s terms, rather than exposure being the baseline.
Whose responsibility
Disclosure is a tool the holder controls. Meeting legal, tax, and regulatory obligations remains the responsibility of the user and their advisors. Beyul provides a capability, not a compliance service — and at this stage, a research prototype of that capability.