Skip to content

DEVELOPERS

What you can build on today — and what you cannot yet.

An honest developer entry point. Beyul is a research prototype: there is no public testnet, no production integration target, and no SDK/API stability promise. This page lists the real entrances and the real boundaries.

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

Available today

Threat model

Protection goals, prototype boundaries, operational assumptions.

→ Threat model

Not possible yet

  • Run a public node — no public testnet or devnet exists. Node software is not yet publicly available.
  • Integrate against a production target — none exists.
  • Rely on SDK or API stability — no stability promise has been made at this stage.
  • Clone the public repository — the repository has not been opened yet.

Prototype & future devnet

A single-node chain prototype with tested shielded-pool operations exists in internal research.

Internal prototype

Public node software and a joinable devnet/testnet are sequenced on the roadmap — after the prototype stage completes.

Planned

Contribution path

Opens with public release

The contribution path — public repository, issues, discussions and contribution guidelines — opens together with the public release of the repositories. Until then, there is deliberately no way to contribute code: an unreviewable contribution channel would be worse than none.

Reserved entrances

Documentation portal

Planned

Public repository link

After public release

RPC / API reference

Planned

Run-a-node guide

With devnet

These entrances are reserved, not hidden — each will carry a real link the day its target actually exists, and not before.

Related

Architecture → Technology → Security → Validators → Disclosure Center → Institutions → Glossary → Back to homepage