EUDI Wallet and relying parties – eIDAS 2.0 in practice

Miłosz Mach

13 Nov 2025
EUDI Wallet and relying parties – eIDAS 2.0 in practice

In post #2 of our eIDAS/EUDI series we move from “what and why” to “how”. If you own onboarding, KYC, e-signatures or any other relying parties with access to digital services, EUDI Wallet acceptance becomes a concrete delivery item bound to eIDAS 2.0 and the implementing acts.

Need broader context first? Start with our intro article: eIDAS 2.0 and the EUDI Wallet – the essentials

What the implementing acts actually change?

They specify:

  • the minimum wallet capabilities and attribute verification process;
  • exchange standards (OpenID4VP/CI, VC/DID);
  • audit requirements and cross-border interoperability;
  • roles and trust registries.

In practice, service providers (fintech, telco, education, healthcare, QTSP) must adopt the EUDI Wallet acceptance model and adjust identity flows.

Two integration models: Direct RP vs Broker

Direct RP (relying party)

  • You implement the protocols (OpenID4VP/CI) and your own attribute validation backend.
  • More control, more responsibility for conformance and maintenance.

Broker / gateway

  • An intermediary layer that unifies multiple national wallets behind one API.
  • Faster time-to-market, with vendor dependency.

How to choose?

  • Strong in-house IAM and signature flows? - Direct.
  • Need to launch quickly across countries? - Broker.

The standards you’ll meet on day one

  • OpenID for Verifiable Presentations (OpenID4VP) - how to request and receive attribute presentations from the wallet;
  • OpenID for Credential Issuance (OpenID4CI) - how to issue credentials (if that’s your role);
  • Verifiable Credentials (W3C VC) and DID - the data and identifier layer;
  • Qualified signatures and seals (e.g., XAdES) - required for documents and qualified registries.

Reference architecture (relying party)

Layer 1 - Front (signup/KYC/signature):

  • “Sign up with EUDI” / “Verify with EUDI” buttons;
  • clear consent UX.

Layer 2 - RP Backend:

  • OpenID4VP/CI clients, presentation validation, session handling,
  • data minimization: store the result or a proof hash, not a full document.

Layer 3 - Audit and compliance:

  • event logs, reproducible consent trail,
  • optional on-chain anchoring of hashes (keep personal data off-chain).

Layer 4 - Integrations:

  • QTSP (QES/QSeal);
  • CRM/CDP;
  • antifraud.

A 4-week PoC that actually ships

Week 1 - Discovery and wireframes: map identity touchpoints, choose Direct vs Broker, consent UX mockups.
Week 2 - Technical integration: OpenID4VP requests, attribute validation, minimal disclosure logic.
Week 3 - Audit and metrics: logs, alerts, dashboard (p50/p95 verify time, acceptance, errors).
Week 4 - Tests and demo: edge cases, compliance package, go/no-go for rollout.

The metrics that matter

  • Verification time (p50/p95) - typical cases vs long tails;
  • Completion rate - does EUDI reduce friction versus legacy KYC?;
  • Stability and errors - where the chain breaks and how often.

Common pitfalls to avoid

  • Treating EUDI like a document upload - it’s not. Aim for fact confirmation, not document copies;
  • Skipping retention and minimization - keep personal data off-chain, anchor hashes, and consent;
  • Neglecting consent UX - poor consent screens can kill adoption.

Short implementation checklist

  • Pick a model: Direct RP or Broker.
  • Design consent UX and error handling.
  • Implement OpenID4VP and VC validation.
  • Define retention, audit and anchoring strategy.
  • Set metrics and SLOs.
  • Ship PoC, then scale.

Need help with a PoC? Get in touch, we’ll help you cut p95 and shorten the signup path without risking compliance.

Most viewed


Never miss a story

Stay updated about Nextrope news as it happens.

You are subscribed

Blockchain for Creators: Secure and Sustainable Infrastructure

Miłosz Mach

07 Nov 2025
Blockchain for Creators: Secure and Sustainable Infrastructure

In today’s digital creative space, where the lines between art and technology are constantly blurring, projects like MARMALADE mark the beginning of a new era - one where creators can protect their work and maintain ownership through blockchain technology.

For Nextrope, being part of MARMALADE goes far beyond implementing features like screenshot blocking or digital watermarking. It’s about building trust infrastructure - systems that empower creators to thrive in the digital world safely and sustainably.

A new kind of blockchain challenge

Cultural and educational projects come with a completely different set of challenges than typical DeFi systems. Here, the focus isn’t on returns or complex smart contracts - it’s on people: artists, illustrators, educators.

That’s why our biggest task was to design secure yet intuitive infrastructure - lightweight, energy-efficient, and accessible for non-technical users exploring Web3 for the first time.

“Our mission wasn’t to build another financial protocol. It was to create a layer of trust for digital creators.”
— Nextrope Team

Security that stays invisible

The best security is the kind you don’t notice.
Within MARMALADE, we focused on making creators' protection seamless:

  • Screenshot blocking safeguards artworks viewed in browsers.
  • Dynamic watermarking helps identify unauthorized copies.
  • Blockchain registry ensures every proof of ownership remains transparent and immutable

“Creators shouldn’t have to think about encryption or private keys - our job is to make security invisible.”

Sustainability by design

MARMALADE also answers a bigger question - how to innovate responsibly.
Nextrope’s infrastructure relies on low-emission blockchain networks and modular architecture that can easily be adapted for other creative or cultural initiatives.

This means the technology built here can support not only artists but also institutions, universities, and educators seeking to integrate blockchain in meaningful ways.

Beyond technology

For Nextrope, MARMALADE is more than a project — it’s proof that blockchain can empower culture and creators, not just finance. By building tools for digital artists, we’re helping them protect their creativity and discover how technology can amplify human expression.

Plasma blockchain. Architecture, Key Features & Why It Matters

Miłosz Mach

21 Oct 2025
Plasma blockchain. Architecture, Key Features & Why It Matters

What is Plasma?

Plasma is a Layer-1 blockchain built specifically for stablecoin infrastructure combining Bitcoin-level security with EVM compatibility and ultra-low fees for stablecoin transfers.

Why Plasma Blockchain Was Created?

Existing blockchains (Ethereum, L2s, etc.) weren’t originally designed around stablecoin payments at scale. As stablecoins grow, issues like congestion, gas cost, latency, and interoperability become constraints. Plasma addresses these by being purpose-built for stablecoin transfers, offering features not found elsewhere.

  • Zero-fee transfers (especially for USDT)
  • Custom gas tokens (separate from XPL, to reduce friction)
  • Trust-minimized Bitcoin bridge (to allow BTC collateral use)
  • Full EVM compatibility smart contracts can work with minimal modifications

Plasma’s Architecture & Core Mechanisms

EVM Compatibility + Smart Contracts

Developers familiar with Ethereum tooling (Solidity, Hardhat, etc.) can deploy contracts on Plasma with limited changes making it easy to port existing dApps or DeFi, similar to other EVM-compatible infrastructures discussed in the article „The Ultimate Web3 Backend Guide: Supercharge dApps with APIs".

Gas Model & Token Mechanism

Instead of forcing users always to hold XPL for gas, Plasma supports custom gas tokens. For stablecoin-native flows (e.g. USDT transfers), there is often zero fee usage, lowering UX friction.

Bitcoin Bridge & Collateral

Plasma supports a Bitcoin bridge that lets BTC become collateral inside smart contracts (like pBTC). This bridges the security of Bitcoin with DeFi use cases within Plasma.
This makes Plasma a “Bitcoin-secured blockchain for stablecoins".

Security & Finality

Plasma emphasizes finality and security, tuned to payment workloads. Its consensus and architecture aim for strong protection against reorgs and double spends while maintaining high throughput.
The network launched mainnet beta holding over $2B in stablecoin liquidity shortly after opening.

Plasma Blockchain vs Alternatives: What Makes It Stand Out?

FeaturePlasma (XPL)Other L1 / L2
Stablecoin native designusually second-class
Zero fees for stablecoin transfersrare, or subsidized
BTC bridge (collateral)only some chains
EVM compatibilityyes in many, but with trade-offs
High liquidity early✅ (>$2B TVL)many chains struggle to bootstrap

These distinctions make Plasma especially compelling for institutions, stablecoin issuers, and DeFi innovators looking for scalable, low-cost, secure payments infrastructure.

Use Cases: What You Can Build with Plasma Blockchain

  • Stablecoin native vaults / money markets
  • Payment rails & cross-border settlement
  • Treasury and cash management flows
  • Bridged BTC-backed stablecoin services
  • DeFi primitives (DEX, staking, yield aggregation) optimized for stablecoins

If you’re building any product reliant on stablecoin transfers or needing strong collateral backing from BTC, Plasma offers a compelling infrastructure foundation.

Get Started with Plasma Blockchain: Key Steps & Considerations

  1. Smart contract migration: assess if existing contracts can port with minimal changes.
  2. Gas token planning: decide whether to use USDT, separate gas tokens, or hybrid models.
  3. Security & audit: focus on bridge logic, reentrancy, oracle risks.
  4. Liquidity onboarding & market making: bootstrap stablecoin liquidity, incentives.
  5. Regulation & compliance: stablecoin issuance may attract legal scrutiny.
  6. Deploy MVP & scale: iterate fast, measure gas, slippage, UX, security.