POSITIONING
Different design goals, different networks.
How BEYUL differs from Monero, Zcash and ordinary transparent L1s. This is a positioning note, not a ranking — each of these projects made serious, deliberate trade-offs for its own goals.
Research prototype · no testnet · no mainnet · unaudited · not production-private · not safe for funds
BEYUL builds on the engineering and research lineage these projects created. What follows describes a difference in emphasis — not in merit.
Monero
Always-on privacy for everyone. Strong hiding of sender, receiver and amount as the default and only mode.
Monero provides view keys, but purpose-bound, user-scoped disclosure workflows for institutional review are not its product emphasis. BEYUL’s target model treats the disclosure experience itself — who sees what, for which purpose, for how long — as the protocol’s first-class concern.
Zcash
Shielded pools with zero-knowledge proofs, plus viewing keys and payment-disclosure concepts. BEYUL’s shielded-pool design stands in this lineage.
BEYUL concentrates its entire surface on user-controlled disclosure: a disclosure center, transaction and asset disclosure credentials (TDC / ADC), and selective audit workflows as the core product — not an auxiliary capability.
Ordinary L1s
Transparent by default. Every balance and transaction is a permanent public record; privacy arrives, if at all, through external add-ons.
Neither privacy nor scoped disclosure is protocol-native. BEYUL’s target model makes privacy the base state and disclosure a granted, scoped, read-only capability.
BEYUL — the target model
Research prototype
Privacy by default, disclosure by choice, selective audit, and accountability — together, at the protocol layer. This is a target model under research: a client disclosure core and a chain prototype exist; production privacy does not yet.
Like every privacy network, BEYUL does not claim absolute anonymity. Privacy limitations →