Skip to content

BEYUL · PRIVATE SETTLEMENT INFRASTRUCTURE

Private settlement infrastructure with user-controlled disclosure.

Beyul is a pre-testnet research prototype exploring private payments, scoped disclosure, and permissioned audit access.

Read Technical Draft View Current Status

Download Research Build ↓

Prototype only · not for real funds · v0.1.0-w0

SHA-256 234a36d223ca7ddac4262aef96c2efe7a2665308d049f3db89b3377e4121e23b

Open Wallet Prototype → See the demo → Explore architecture →

Research prototype · no testnet · no mainnet · unaudited · not production-private · not safe for funds →

IN ONE MINUTE

First, plainly: what it is — and what it isn’t.

What is Beyul?

A settlement-network design that puts privacy and accountability together: transactions are private by default, and when needed you disclose only specific information to specific parties.

Can I move real money today?

No. It is a research prototype — no testnet, no mainnet, unaudited, and not for real funds.

So what can I try right now?

An interactive demo, a wallet prototype on a simulated network, and a block explorer with demo data — all for research.

What it is not

Not absolute anonymity, and not a tool to evade regulation or audit. Privacy and accountability, together, is the design goal.

WHO IT IS FOR

Who it’s built for — and who it’s not.

Built for

  • Privacy-preserving settlement research
  • Scoped transaction disclosure
  • Audit and reconciliation workflows
  • Cosmos / ZK protocol researchers

Not built for

  • Hiding illicit funds
  • Evading sanctions
  • Anonymous high-risk transfers
  • Production financial use
  • Token speculation

01WHAT IS A BEYUL

སྦས་ཡུལ

Privacy has a home.

Beyul (སྦས་ཡུལ) — Tibetan: a hidden sanctuary valley.

Protected. Invisible. Open only to those permitted.

A sanctuary does not hide — it simply does not open to those it does not concern. We named this network after it: your financial life resides in the valley, sheltered by the protocol. When the gate opens, for whom, and how far — you decide.

Privacy by default. Disclosure by choice.

02THE PROBLEM

Public ledgers were never designed for privacy.

  • Salaries
  • Treasury operations
  • Donations
  • Supply chains
  • Institutional settlements

None of these should be permanent public records. On transparent ledgers, they are.

03DISCLOSURE

One transaction. Four perspectives.

Amount

2,450,000.00

Sender

Meridian Capital

Recipient

Atlas Holdings

Memo

Q2 settlement

Reconciliation

Reconciled

Validity proof

Target: on-chain validity proof

As the owner, you see everything.

Demo shows the target design. Current prototype boundary: deposit and withdrawal amounts are still public on-chain. Threat model →

04DISCLOSURE IS NOT BINARY

Between fully public and fully hidden, there is a third model.

01

Personal privacy

Your history belongs to you. No observers — including the network itself.

02

Transaction disclosure

Prove a chosen transaction to a chosen party. That one, and only that one.

03

Asset disclosure

Prove what you hold without surrendering where it came from.

At the protocol layer: viewing keys · TDC · ADC Technical detail →

05ACCOUNTABILITY

Built for accountability.

Privacy and accountability are not opposites — lose either, and the other cannot stand.

Auditing

Verification within granted scope — not an open ledger.

Verification

Every transaction provably valid, on-chain.

Institutional reporting

Produced on demand. Purpose-bound, scope-bound.

Financial integrity

The network verifies. It does not watch.

Auditability in full →

06RESEARCH BEFORE PROMISES

Research before promises.

Beyul ships when ready — not when scheduled.

  1. Research

    Complete

    Disclosure model and protocol design

  2. Prototype

    In progress

    Client implementation, continuous testing

  3. Testnet

    Planned

    Shielded pool end-to-end

  4. Ecosystem

    Planned

    Audits, operators and partners

07BUILD WITH BEYUL

Build with Beyul.

Everyday users

Open and try it — web wallet, desktop install, block explorer.

Wallet prototype

Browser prototype on a simulated network. Not for real funds.

Open wallet → Prototype
Download offline build ↓

Desktop app (PWA)

Install to desktop (PWA prototype): open in Chrome / Edge, then “Install to desktop” to run as a standalone window. It still runs in a browser environment and does not use native secure storage (Keychain / Credential Manager); native packaged builds are still planned. Not for real funds.

Install to desktop → Prototype

Block explorer

Privacy-first explorer: on a private-by-default chain it shows only public data and what users disclose. Demo data for now.

Open explorer → Prototype

Builders & validators

Run and read deeper — validator path, protocol draft, developer entry.

Validator program

Opens with the testnet stage.

Register interest → Planned

Research papers

Pre-testnet technical draft.

Read → Published

Developers

What you can build today, what is not yet possible, and the contribution path — stated honestly.

Enter → In preparation

Institutions & auditors

Evaluate and do diligence — disclosure framework and the current fact anchor.

Institutional disclosure

Framework, threat model, briefing.

Enter → Channel in preparation

Current status

What exists, what does not, what is planned — item by item.

View → Published

08POSITIONING

How we’re positioned — said with restraint.

Beyul does not compete on maximum anonymity. It focuses on private settlement with scoped, user-authorized disclosure.

Default privacy
Transactions are private by default.
User-controlled disclosure
The holder decides what is revealed, to whom, and for how long.
Audit access
Scoped, authorizable audit channels.
Production status
Research prototype — no testnet / no mainnet.
Compliance posture
Provides a capability; does not claim compliance.
Developer maturity
Internal prototype; public gates on the Developers page.
See full positioning →