eIDAS 2.0 readiness — ERF protocol alignment
ERF is designed for the
EU digital identity transition.
eIDAS 2.0 entered into force in May 2024. Every EU member state must provide a digital identity wallet by end of 2026. From 2027, regulated private sectors must accept the EUDI Wallet for authentication. Vraimony's ERF protocol is designed to be compatible with this transition — through W3C Verifiable Credentials export, qualified electronic timestamping, and open backward-compatibility contracts.
W3C VC export (optional layer)
Qualified timestamp compatible
GDPR-aligned (no tracking)
Open backward-compat contract
eIDAS 2.0 timeline — what matters for ERF users
Key dates and what they mean for evidence exchange.
May 2024
eIDAS 2.0 entered into force. W3C Verifiable Credentials 2.0 became W3C Recommendation.
End of 2026
Every EU member state must provide at least one European Digital Identity Wallet (EUDI Wallet) to citizens and businesses.
From 2027
Regulated private sectors (banking, telecoms, healthcare, education, large online platforms) must accept EUDI Wallet for authentication.
ERF now
ERF already implements ed25519 signing, SHA-256 content hashing, independent timestamp anchoring, and optional W3C VC export — the technical foundation for eIDAS 2.0 alignment.
Technical alignment — ERF vs eIDAS 2.0 requirements
What ERF already implements. What is on the roadmap.
eIDAS 2.0 / W3C VC REQUIREMENT
ERF STATUS
NOTES
Cryptographic signing (asymmetric key)
✓ Live
ed25519 — every sealed record
Content integrity (hash)
✓ Live
SHA-256 — in every receipt payload
Independent timestamp anchoring
✓ Live
SHA-256 commitment + OTS anchor — verifiable offline
Tamper-evident record
✓ Live
ed25519 + timestamp_anchor — any modification detectable
No tracking / privacy-first
✓ Live
No receiver accounts. No personal data stored outside the record.
Backward compatibility contract
✓ Live
Additive-only. erf/1.x records remain valid indefinitely.
W3C Verifiable Credentials export
⟳ Roadmap
Seal receipt + ACK as VC — optional export layer Q3 2026
RFC 3161 Qualified Timestamp (eIDAS Article 41)
⟳ Roadmap
For EU enterprise compliance tier — contact for timeline
EUDI Wallet compatible presentation
2027
Follows W3C VC export completion — aligned with mandate timeline
What this means for EU businesses using ERF now
Early adoption creates forward compatibility.
◼ What you get today
- ed25519-signed records (legally admissible in many jurisdictions)
- Independent timestamp — verifiable without Vraimony servers
- PASS / Declared / Unverified with evidence_degree
- Portable exports (PDF) — no vendor dependency
- Open backward-compat contract — records valid indefinitely
▶ What this means for 2027
- Records sealed today will be compatible with EUDI Wallet infrastructure
- W3C VC export adds another presentation layer — does not invalidate existing records
- Qualified timestamp upgrade available as add-on for enterprise tier
- ERF Foundation backward-compat contract enforces no breaking changes
► Recommended action now
- Start sealing dispute, handover, and qualification records now
- erf/1.x records sealed today remain valid post-2027
- Contact for EU enterprise compliance tier (RFC 3161 + qualified TS)
- Register interest in ERF Foundation certified membership
Honest boundary: ERF is designed for eIDAS 2.0 alignment — not certified compliance. For regulated EU sectors requiring formal qualified electronic timestamps (QES) under eIDAS Article 41, contact us about the enterprise compliance tier with TSA integration.
EU compliance enquiry
Building on ERF for EU markets?
Whether you're building a compliance layer, integrating ERF into an existing platform, or preparing for eIDAS 2.0 obligations — we're happy to discuss the technical and governance path.