NODENODEENCRYPTED
Public-Benefit Oriented & Open Source Concept Phase – Looking for Contributors

450M verified identities.
No open directory.
// TODO: build it Protocol & operations: Zero Trust · Zero Cloud · Federated · EUDI-native

The EUDI Wallet answers “is this really this person?” – but only when they actively present it. What is missing is the other direction: looking up keys and reachability for a verified identity, without that person being online. ROND is a public-benefit oriented project building that directory as an open protocol – and it is looking for people to shape it.

We Need You →
Vision

Why ROND?

By late 2026, every EU citizen will gain access to an EUDI Wallet — Germany plans to go live in early 2027. For the first time, this creates a pan-European identity layer for 450 million people.

What's missing is the open directory on top. Today, "Sign in with Google" and "Sign in with Apple" solve the password problem – but the price is handing your entire digital identity graph to a corporation.

ROND aims to build the open, federated, public-interest alternative — the earlier an open standard exists, the better its chance against proprietary solutions. The protocol should belong to people, not its inventors, not investors, not a corporation.

Your identity belongs to you – not a corporation, not a cloud, not an algorithm. At ROND, digital sovereignty should follow from the architecture, not from a promise.

Project Status

  • Problem analysis & concept paper v0.6
  • Legal framework analyzed (BGH, eIDAS 2.0, TDDDG)
  • Website & infrastructure built
  • Community building & expert feedback
  • Prototype Fund application (window 1 Oct – 30 Nov 2026)
  • External architecture validation
  • Formal protocol specification
  • Nonprofit organizational structure (when needed)

Governance

Prospectively: Nonprofit organization (gUG → foundation). Non-saleable, purpose-bound. Formation when concrete triggers occur (co-founders, grants, donations). Model: Signal Foundation, Let's Encrypt (ISRG).

This project can't be built alone.

What exists is a problem analysis, a conceptual architecture, and a favorable window of opportunity. The architecture is a draft — it needs to be validated and refined by domain experts. What's missing are the people with the expertise:

Want to understand which design questions are still open first? See the open design questions →

🔬

Cryptography

Formal protocol specification, zero-knowledge architecture, Shamir's Secret Sharing, cryptographic security proofs.

ZKP · SSS · Formal Verification
⚖️

Legal

Inheritance law, data protection (GDPR), eIDAS 2.0, digital sovereignty, foundation law. Legal opinions on protocol compliance.

GDPR · eIDAS · Inheritance Law

Integrity Anchor & Distributed Systems

Assessing the mechanisms that could serve as a tamper-evident integrity anchor for the Registry: security analysis, operating cost, formal verification. The decision is open.

Architecture decision open
🖥️

Infrastructure

Operating Tier-1 nodes on owned hardware. Federated systems, network architecture, high availability.

Self-Hosted · Federated
🎨

UX & Design

Infrastructure accessible to everyone – not just the technically savvy. Hide complexity, build trust.

Accessibility · Trust UX
🏛️

Civil Society & Funding

Organizations and foundations that fund and support critical digital infrastructure as a public good.

NGO · Public Interest Tech
Digital Sovereignty

Three principles. Non-negotiable.

Digital sovereignty is not a feature. It's a foundational architectural decision that permeates every aspect of the protocol.

DIGITAL SOVEREIGNTY 01

No secrets leave your device

All sensitive data is encrypted on your device before it leaves. Keys are to be fragmented via Shamir's Secret Sharing. At no point does a complete key exist on a foreign system.

Operator promises not to read
→ Operator cannot read
DIGITAL SOVEREIGNTY 02

No central cloud dependency

This applies to the protocol and to the project's operating infrastructure — node software, Registry, hosting, CI, and forge. No single provider controls the infrastructure; encrypted shards sit with identifiable node operators in known jurisdictions. Individual nodes can use cloud hardware, since all data is encrypted client-side.

Dependent on one cloud provider
→ Federated architecture, cloud-independent
DIGITAL SOVEREIGNTY 03

No trust required

Wherever possible, ROND replaces trust with cryptography and central authorities with federated networks. You only need to trust mathematics – and it's publicly auditable.

Trust in operators, ToS, regulation
→ Trust in mathematics & open code

Integrity anchor: an open architecture decision

The Registry needs an anchor that keeps it provable over decades that rules, public keys, and hashes have not been altered after the fact. Which technology provides that anchor is not decided – the architecture decision is in progress (ADR-003, status: Proposed). Independently of it: your content leaves your device encrypted and is stored as shards across federated nodes – never in plaintext, never complete in one place.

Status of the architecture decision →

Starting Point

The missing directory.

The EUDI Wallet answers “is this really this person?” – but only when that person actively presents it. What is missing is the other direction: looking up keys and reachability for a verified identity, without that person being online.

For practitioners: the key discovery problem

For decades, S/MIME and PGP have failed not because of the cryptography, but because there is no reliable directory in which the key of a verified person can be looked up. That directory is what is missing.

Identity Registry

Sovereign Authentication

An EUDI-based, federated opt-in key directory. The EUDI Wallet is a wallet, not a phonebook – the Registry connects verified identity with cryptographic reachability. "Sign in with EUDI" follows from that: no password, no corporation, no tracking.

What can build on top

Authorization Protocol

Authorized Communication

Who can contact me, under what conditions, verified by EUDI attestations. You set the rules. Spam isn't filtered – spam becomes structurally impossible. Existing messengers like Signal or Matrix can integrate the API.

Legacy Protocol

Digital Legacy

Encrypted data released to verified recipients after death or incapacitation. Dead Man's Switch and Guardian verification – the trigger logic is deterministic, transparent, and cannot be manipulated by any single person.

Window

Why now? Two developments converge.

These two prerequisites never existed at the same time. The window opens in late 2026 and will close once closed platforms occupy the space.

🪪

EUDI Wallet (late 2026)

EU Regulation 2024/1183 mandates every member state to provide an EUDI Wallet. By late 2027, banks, telecoms, healthcare, and Very Large Online Platforms must accept it. 450 million verified digital identities – with qualified electronic signatures and selective disclosure.

Person Identification Data · QES · Selective Disclosure
⚖️

Mature Legal Framework

German Federal Court 2018: digital inheritance equals physical inheritance. § 4 TDDDG (2024): providers must cooperate with heirs. eIDAS 2.0: legal framework for EUDI Wallet and qualified attestations. The laws exist – what's missing is the technical infrastructure to implement them.

§ 1922 BGB · GDPR · eIDAS 2.0 · TDDDG

From infrastructure to everyday life.

ROND doesn't build apps – ROND provides the open protocol layer on which businesses, governments, and civil society can build their own services.

USE CASE 01

No more passwords

"Sign in with EUDI" via the ROND Identity Registry. Verified identity, authenticated once, cryptographically secured – without a corporation sitting in between. No password. No SMS. No code.

For services: Standardized API any provider can integrate. The Registry stores no login history and no usage profiles.
Example

A physiotherapy practice offers patients an online portal for appointment booking and medical reports. Instead of building its own login infrastructure, it integrates the ROND API – patients authenticate via their EUDI Wallet. No password, no "forgot password" flow, no user database that can be hacked.

Learn more →
USE CASE 02

Verified Communication

Companies identify themselves via EUDI Business Wallet. Phishing emails pretending to be from Deutsche Bank become impossible – the sender can't fake EUDI verification.

Sender verification: The Registry only releases a key tied to an EUDI-verified identity – forged senders get none.
Example

A family doctor defines in ROND: "Contact only from my patients, the lab, and the health insurance association." Everything else never arrives – no spam filter needed because unauthorized messages are structurally undeliverable. A pharma rep would need a government-verified identity AND individual authorization from the doctor.

Learn more →
USE CASE 03

Digital Legacy

Encrypted letters to children, released only after death. Structured overview of all online accounts for authorized persons. Crypto asset inheritance, planned via Shamir's Secret Sharing. Powers of attorney with digital activation.

Recipient side solved: Recipients are identified via EUDI attributes – no crypto knowledge needed, no upfront onboarding.
Example

A freelancer has 47 online accounts, three crypto wallets, and a life insurance policy. They store an encrypted overview in ROND and designate their partner as the recipient. Three of their five guardians confirm the death via EUDI – the partner gains access. No notary needed, no password note in a drawer, no "I can't get into their laptop."

Learn more →
USE CASE 04

Institutional Integration

Notaries complement traditional estate planning digitally. Insurers verifiably confirm trigger events. Banks operate their own storage nodes. Government agencies communicate with citizens through authorized channels.

Open Ecosystem: Managed node operators, integrators, app providers – anyone can build on the protocol.
Example

A sports club uses ROND across all three layers – members log in via EUDI (no password-reset chaos), the board is only reachable by verified members (no spam on the club email), and the bank account credentials are secured via Legacy Protocol in case something happens to the treasurer.

Learn more →
Strategy

From everyday problem to infrastructure.

People don't switch for security. They switch for utility – and get security as a bonus. That's why ROND doesn't start with legacy, but with passwords.

1

The Daily Hook

"Sign in with EUDI"

Users sign up because they never want to type a password again. The Identity Registry becomes the sovereign identity provider – without Google or Apple watching every login.

2

The Aha Moment

Authorized Communication

Users who already have their identity in the Registry next control who can send them messages. No separate service – an organic extension of an existing account.

3

The Legacy Moment

Digital Legacy

The user is already in the system, understands the mechanics, trusts the infrastructure. The barrier for the legacy question drops dramatically – the Legacy Protocol becomes a logical conclusion, not a morbid entry point.

Roadmap

Four phases. From specification to ecosystem.

Phase 1

Foundation

Q3 2026 – Q1 2027
  • Protocol specification Identity Registry (open – originally planned for 2026)
  • Architecture decision on the integrity anchor
  • Prototype Fund application (window 1 Oct – 30 Nov 2026)
  • Prototype Fund response (March 2027)
  • Prepare nonprofit organizational structure
  • EUDI integration via SPRIND Sandbox
  • Open-source repository & community
Phase 2

Everyday Utility

Q2–Q4 2027

Conditional on funding being granted. Without approval, this phase shifts.

  • Prototype Fund funding period (June–November 2027, if granted)
  • "Sign in with EUDI" API production-ready
  • First federated nodes & public API
  • First service integrations (Matrix ecosystem)
  • Independent security audit
  • Tier-1 operators & community node software
  • Enterprise API specification
Phase 3

Expansion

Q1–Q4 2028
  • Registry in production operation
  • Authorization Protocol & messenger integration
  • Legacy Protocol: Dead Man's Switch MVP
  • Guardian system & multi-party verification
  • Enterprise API for notaries & insurers
  • Mobile apps (iOS / Android)
Phase 4

Ecosystem

from Q1 2029
  • Evaluate Shamir's Secret Sharing for crypto assets
  • Open governance process for protocol evolution
  • Event confirmation by death registries
  • Expansion: Signal, Threema, XMPP, email
  • Transition to independent foundation
  • Internationalization beyond the EU
Next Step

A concept looking for contributors.

The EUDI Wallet arrives late 2026 / early 2027. The infrastructure layer on top will be built — the question is whether it will be open and federated, or closed and commercial.

We Need You →