Skip to content
Crypto.world

Research

Know Your Contract: eIDAS-Based Verifiable Legal Identities for Smart Contracts, Enabling Regulatory-Compliant On-Chain Operations

Public blockchains give no native way to check which legal person or organisation controls a deployed smart contract: addresses are pseudonymous, and nothing links them to a real-world entity.

Know Your Contract: eIDAS-Based Verifiable Legal Identities for Smart Contracts, Enabling Regulatory-Compliant On-Chain Operations
arXiv
2601.13903
Published
2026-01-20
Authors
Awid Vaziry, Sandro Rodriguez Garzon, Christoph Wronka, Axel Küpper

AI summary

Overview

Research area: Blockchain security and regulatory compliance — specifically on-chain digital identity, public key infrastructure (PKI), and the EU eIDAS trust framework applied to Ethereum smart contracts (arXiv category cs.CR, Cryptography and Security).

Technical level: Advanced. The paper assumes familiarity with X.509 certificates, ASN.1/DER encoding, ECDSA over P-256 (secp256r1), the Ethereum Virtual Machine, and the structure of EU trust lists.

Scope (one sentence): The paper specifies KYC Seal, a protocol design that cryptographically binds Ethereum smart contracts to eIDAS Qualified Electronic Seals by mirroring the EU trust-list hierarchy on-chain and verifying certificates inside the EVM, without oracles or runtime intermediaries.

What This Paper Is About

Public blockchains give no native way to check which legal person or organisation controls a deployed smart contract: addresses are pseudonymous, and nothing links them to a real-world entity. This creates an "attribution gap" that conflicts with EU rules such as MiCA, the AMLR, and PSD2/PSR, which require transactions to be traceable and attributable to accountable parties. The paper's goal is to carry the EU's existing, government-curated eIDAS trust chain — from the European Commission's List of Trusted Lists (LOTL) down through Member-State trusted lists and Qualified Trust Service Provider (QTSP) certificates — all the way to an individual contract address, and to prove the holder's legal identity on-chain at low recurring cost.

Key Contributions

  1. A protocol that extends eIDAS to the EVM. KYC Seal is described as the first protocol to extend the EU eIDAS trust infrastructure to EVM smart contracts, enabling trustless on-chain verification of legally recognised identities without oracles or runtime intermediaries.
  2. An on-chain ASN.1/DER parser for X.509 certificates. The paper presents what it describes as the first on-chain ASN.1/DER parser that extracts public keys, Legal Person Identifiers (LPIDs), and validity periods directly on the EVM, closing the semantic gap between "the QTSP signed a hash" and "the signed bytes contain the claimed identity fields."
  3. Registration-once, verify-always caching. Both cryptographic verifications — the QTSP issuance signature (V2) and the certificate holder's seal signature (V1) — are performed once during registration and cached as on-chain state, so per-interaction seal verification becomes a pure state check with no per-call signature operation.
  4. A system and trust model plus a positioning against prior work. The paper defines three contracts (TrustedList, SealCertificateRegistry, SealedContract), three cryptographic artifacts (the QTSP service digital identity SDI, the qualified seal certificate QSealC, and the seal itself), and five actors, and compares KYC Seal against blockchain-based PKI and on-chain identity schemes in a taxonomy table.

Main Findings

  • Zero P-256 operations on the steady-state path. Both signatures are verified exactly once — V2 at registerCertificate, V1 at registerSeal — and cached as unforgeable on-chain state, so the recurring verification path performs zero P-256 operations.
  • Permissionless, sender-independent registration. Seal registration is authorised cryptographically by the Certificate Holder's P-256 signature over the seal payload rather than by msg.sender; any Ethereum account may submit the transaction, which the authors say enables account abstraction and relayer submission.
  • Identity fields are bound to the signed bytes. The parser reads the public key, LPID (from organizationIdentifier, OID 2.5.4.97, checked against a LEIXG- prefix), validity window, and serial from the same TBSCertificate byte string whose SHA-256 digest is verified under the QTSP issuer signature, so no identity field is accepted as independent caller input.
  • Envelope substitution is reduced to signature forgery. Binding envelopeHash = keccak256(cadesBlob) into the V1 payload commits the holder to a specific CAdES envelope; substituting a different envelope later fails V1 verification and would require an ECDSA forgery against the certificate's public key.
  • The P-256 precompile is the enabling condition. The authors state that the Ethereum Fusaka upgrade (December 2025) introduced a P-256 precompile (EIP-7951), making cryptography on the eIDAS-mandated curve economical on the EVM for the first time. No gas figures are reported, because the gas evaluation is explicitly deferred to forthcoming work.
  • The trust root is governance-curated, not cryptographically verified at registration. registerTrustService mirrors the DER-encoded SDI from the LOTL without verifying an issuer signature, on the argument that trust is curated by governance, analogous to how browsers and operating systems ship pre-vetted CA certificates.
  • Three revocation paths are defined: the Contract Owner removes its own seal via removeSeal; the Certificate Holder signs a revocation payload submitted via revokeSealByIssuer; and any party submits a DER-encoded CRL signed by the SDI, which CRLParser searches to permanently set the certificate's active flag to false.
  • Positioning against related work. The paper contrasts KYC Seal with CA-rooted blockchain PKI (IKP, CertLedger, SCPKI, zk-X509), with organisational credential systems (GLEIF vLEI, Functional Credentials, Chainlink ACE, EBSI), and with the amended eIDAS qualified electronic ledger (Art. 45k, 45l); only KYC Seal is classified as both full public-chain verification and fully composable.
  • Limitations are stated openly: the DER parser is narrow by construction and not formally verified, so it is treated as part of the trusted computing base; the curated trust-root assumption reduces on-chain verification to trusting an honest LOTL mirror; and a seal binds a single CAdES envelope, so legitimate envelope rotation (for example, BES to LT) requires a fresh signature and a new registerSeal call.

Methodology in Plain English

This is a design-and-specification paper, not an empirical one. The authors work from the existing eIDAS trust hierarchy: the European Commission aggregates Member-State trusted lists into the LOTL, Member States list their QTSPs, and QTSPs sign X.509 certificates for legal persons. Their approach is to mirror the top of that hierarchy into a smart contract (TrustedList), so a QTSP's public key is available on-chain.

From there, registration proceeds in five one-time steps: provisioning the trust anchor, registering an end-entity seal certificate (which requires verifying the QTSP's signature over the certificate using Ethereum's P-256 precompile), having the contract owner pre-approve a specific certificate for sealing, having the holder sign a CAdES envelope off-chain with their seal certificate's private key, and registering that seal on-chain after re-checking the approval and verifying the holder's signature.

Once both signatures have been checked and the certificate fields extracted, the results sit in contract storage. Any later interaction only reads that stored state and re-checks that the seal is active, that the certificate is still active, that the current time is inside the validity window, that the recorded chain ID matches, and that the issuing trust service is still valid. The paper presents the protocol as pseudocode (Algorithm 1 for registration, Algorithm 2 for verification) and reports that a reference implementation, a formal security analysis, and a gas evaluation are the subject of forthcoming work.

Why This Matters

Impact on research. The paper reframes on-chain identity as a trust-chain extension problem rather than a credential-issuance problem, and it contributes a reusable pattern the authors call "deferred verification": verify an expensive signature once at registration, persist the result as monotonic state, and reduce the hot path to storage reads. The authors argue this pattern generalises to any protocol whose trust artifact is signed by a slowly changing authority and consumed repeatedly, and it decouples steady-state cost from signature-scheme availability, which matters on platforms where new curves arrive only through protocol upgrades.

Real-world applications:

  • Crypto-asset service providers under MiCA, which must identify customers, ensure transaction traceability, and maintain auditability.
  • Tokenised real-world assets and TradFi participation, where transactions must be attributable to legally accountable entities before institutions can participate.
  • Payments and transfers under PSD2/PSR and the AMLR, where payment instructions must be unambiguously attributable to legally responsible persons and both initiating and intermediary parties must be traceable.
  • Audit and assurance workflows — the co-author affiliation with Baker Tilly's Financial Services Audit & Advisory points at attestation and audit use cases where a contract's controlling legal entity must be provable.
  • Regulated smart contracts that gate on identity: because the verified identity is on-chain state, another contract can query it atomically within the same transaction rather than calling an oracle.

Industry relevance. The protocol is designed to run inside normal contract execution with no oracle network, no wallet-to-relying-party exchange, and no permissioned ledger, which distinguishes it from Chainlink ACE (oracle-attested), GLEIF vLEI (wallet-held), and EBSI (permissioned). It also arrives alongside a concrete platform change — the P-256 precompile in the Fusaka upgrade — that turns an eIDAS-mandated curve from impractical to economical on the EVM, which is the kind of infrastructure dependency enterprises watch closely. The authors explicitly invite ERC-level standardisation of the on-chain trust-list semantics, certificate-record layout, and seal-verification interface.

Future Directions

  1. A reference implementation, formal security analysis, and empirical gas evaluation. All three are stated as the subject of forthcoming work; no implementation results, security proofs, or gas measurements appear in this paper.
  2. A formally verified DER parser. The authors propose a proof-carrying ASN.1 toolchain that would remove the parser from the trusted computing base; today the parser is narrow, accepts only the eIDAS QSeal profile, reverts on malformed encodings, and is explicitly not formally verified.
  3. Cross-chain seal portability. The current design binds a seal to a single chain ID. The authors propose generalising this into a signed portability statement so one legal entity can hold a consistent identity across L1 and L2 without independent re-sealing on each chain.
  4. Natural-person extensions with selective disclosure. Extending the same architecture to Qualified Electronic Signatures (QES) with selective disclosure or zero-knowledge proofs would bring GDPR-sensitive attribution into scope; the authors note the QES obstacle is regulatory rather than cryptographic, since QES and QWAC share the same profile family and TBS field positions as QSealC.
  5. Hardening and choosing a trust-root governance model. Four designs are laid out — admin-curated mirror (the current prototype), protocol-level trust anchor embedded in the client, individually curated trusted lists, and EU-operated on-chain publication — with the paper recommending transparency around root updates, append-only audit logs, delayed activation of new anchors, and multi-party threshold governance.

Target Audience

Readers who will get the most from this paper are blockchain protocol designers and identity-architecture researchers working on regulatory compliance; engineers building permissioned or identity-gated DeFi, tokenisation, and payment systems on Ethereum; compliance, legal, and audit professionals who need to understand how eIDAS seals could be represented on public chains; and standards contributors interested in ERC proposals for on-chain trust lists and certificate registries. It is also useful for readers comparing trust models across vLEI, EBSI, Chainlink ACE, and qualified electronic ledgers, since the positioning table makes those trade-offs explicit. Readers seeking measured gas costs, a working implementation, or a security proof will not find them here — those are deferred to forthcoming work.

Authors’ abstract

Public blockchains provide no native mechanism to verify the legal identity behind a deployed smart contract, which blocks institutional adoption and compliance with EU regulations such as MiCA and AMLR. We present KYC Seal, the first protocol that extends the EU eIDAS trust infrastructure to Ethereum smart contracts by cryptographically binding them to Qualified Electronic Seals issued by Qualified Trust Service Providers (QTSPs). The protocol realizes the full eIDAS trust…

The full abstract on arXiv
Read the original paper