Skip to content

INSTITUTIONS

Designed for diligence and compliance review.

Beyul is built on the premise that confidentiality and accountability must coexist. This page describes the disclosure framework, the trust posture, and exactly which diligence material exists today — and which does not yet.

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

Project identity

Privacychain is the protocol and repository development name; BEYUL is the public brand and network name for users, institutions, and network participants. The project remains a research prototype. Repository and gate status disclosures will be published when the public-release conditions are met.

The disclosure framework

Every transaction is private by default. Visibility is then granted — not assumed — along three constraints:

Purpose-bound

A disclosure exists to prove a specific fact to a specific reviewer — a transaction, a screening result, a funds threshold — not to open the books.

Scope-bound

The reviewer sees the disclosed fields and nothing adjacent: no full history, no unrelated counterparties, no spending authority.

Holder-controlled

Disclosure rights live in user-held keys. No network operator — and not the Beyul team — can grant access on a holder’s behalf.

The homepage carries an interactive demonstration: one transaction viewed as owner, counterparty, auditor and public network. Open the disclosure demo →

The trust posture

No one — including us — holds a master viewing key to user transactions.

A continuously tested design property — not yet an audited guarantee.

Reviewable

Design notes and prototype boundaries are documented without overstating readiness.

Explainable

The disclosure mechanism can be explained to regulators and auditors in their own terms.

Restrained

No mainnet-ready claims, no implied institutional adoption, no token-sale language.

Open research

Design notes, test results and known limitations are published as the protocol matures.

Diligence material — what exists today

Threat model

Published

Target security posture, selective-disclosure risks, prototype boundaries and operational assumptions.

→ Threat model

Technology overview

Published

Architecture components and the three disclosure primitives, with per-claim implementation status.

→ Technology overview

Security status

Published

Audit status, known limitations and responsible-disclosure posture, stated plainly.

→ Security status

Privacy limitations

Published

What privacy depends on, and what may still occur. No absolute-anonymity claim.

→ Privacy limitations

Auditability

Published

What can be disclosed — with real implementation status — and what a disclosure can never do.

→ Auditability

Disclosure Center

Concept page

The future wallet module for granting, scoping and tracking disclosures. Concept only.

→ Disclosure Center

Test evidence

Client tests 40/40

Disclosure-code client core: 40/40 tests passing (2026-06-10). Reproducible-build instructions ship with public release.

Legal entity & jurisdiction

Disclosed before testnet

Currently operated as an independent research effort; no legal entity has been established yet. Entity and jurisdiction will be disclosed before any public testnet.

External audit plan

Planned · not started

Independent audits of the protocol, cryptography and implementation are sequenced before any mainnet claim. No audit has been engaged or started.

Capability boundary

Beyul provides a selective-disclosure capability. It is not a compliance product, and it does not provide:

  • KYC / identity verification
  • AML screening or transaction monitoring
  • Account freezing or fund seizure
  • Regulatory approval or endorsement
  • Legal or compliance opinions

Disclosure is a tool the asset holder controls. How it is used to meet any obligation is the responsibility of the user and their advisors.

Briefing

A 30-minute briefing covers the disclosure framework, prototype boundaries and the research roadmap. The dedicated briefing channel is being prepared; until it opens, this page is the canonical statement of what can be claimed.

This page makes no claim of institutional adoption, regulatory approval, or commenced audit.

In preparation · not yet open Back to homepage