arf-rp-verification

Verify digital identity attestations for authenticity, revocation, and device binding.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill arf-rp-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arf-rp-verification
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/arf-rp-verification
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill arf-rp-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for Relying Parties (RPs) to securely and reliably verify the authenticity, validity, and integrity of digital identity attestations presented by users via Wallet Units. It ensures that the presented credentials are trustworthy and belong to the rightful holder.

Core Features & Use Cases

  • Authenticity Verification: Confirms the digital signature of the presented PID or attestation using trust anchors.
  • Revocation Checking: Verifies if the attestation has been revoked by the issuer.
  • Device & User Binding: Ensures the attestation is tied to a secure device and that the presenter is the legitimate user.
  • Combined Presentation Handling: Manages scenarios where multiple attestations are presented together, ensuring their combined validity and user ownership.
  • Use Case: An online service needs to verify a user's age and residency. The user presents a digital PID. This Skill verifies the PID's authenticity, checks if it's revoked, confirms it's from a trusted device, and ensures the person presenting it is indeed the user.

Quick Start

Use the arf-rp-verification skill to verify the authenticity and revocation status of a presented PID.

Frequently Asked Questions about arf-rp-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify the authenticity of a digital identity attestation presented to a Relying Party?

Verify digital identity attestations by validating the digital signature of the presented PID or attestation against established trust anchors. This confirms the credential's authenticity and ensures it was issued by a trusted source.

How does revocation checking work for PIDs and QEAAs in the EUDI Wallet ecosystem?

Revocation checking works by querying the issuer's status service to verify if a presented PID or QEAA has been revoked. This ensures the attestation remains valid and has not been cancelled before accepting it.

What is device and user binding for combined digital identity presentations?

Device and user binding ensures attestations are cryptographically tied to a secure device and the legitimate user. For combined presentations, it verifies that multiple credentials belong to the same presenter.

Can I use this to check multiple attestations presented together from an EUDI Wallet?

Yes, you can check combined presentations of multiple attestations from an EUDI Wallet. The process manages scenarios where several credentials are presented together, ensuring their combined validity and user ownership.

Does eIDAS2 require specific security checks for digital identity verification by Relying Parties?

eIDAS2 requires Relying Parties to perform security checks including authenticity verification, revocation status checking, and device binding. These ensure presented attestations are trustworthy and securely bound to the user.

Why does my Relying Party need to validate cryptographic binding for digital identity presentations?

Your Relying Party needs to validate cryptographic binding to prevent identity fraud and ensure the person presenting the credential is the rightful holder. This secure binding confirms the attestation is tied to the user's device.