Verifiable Presentation

If a Verifiable Credential is the passport, a Verifiable Presentation is the act of handing it over at the border, wrapped with proof that you, specifically, are the person it belongs to, and that you're presenting it right now, to this checkpoint, not replaying a copy captured somewhere else.

A Verifiable Presentation (VP) wraps one or more credentials with the holder's own signature, bound to a specific request, a challenge, often also a domain, so it can't be captured and reused against a different party:

{
  "@context": ["https://www.w3.org/2018/credentials/v1"],
  "type": ["VerifiablePresentation"],
  "holder": "did:solidus:testnet:7Hk3mRtQZv...",
  "verifiableCredential": [
    { "...the full credential being presented..." }
  ],
  "proof": {
    "type": "Ed25519Signature2020",
    "challenge": "challenge-id-from-relying-party",
    "domain": "relying-party.com",
    "verificationMethod": "did:solidus:testnet:7Hk3...#key-1",
    "proofPurpose": "authentication"
  }
}

The challenge and domain fields are what stop a captured presentation from being replayed elsewhere: the signature only checks out for the request it was made for.

Where it comes from

Same source as Verifiable Credential: the W3C Verifiable Credentials Working Group defines the VP shape. Solidus implements it in two forms: a lightweight DID-authentication version (login, no credential attached) and a full credential-presentation version (a verifiableCredential array, used to reuse a real KYC credential with a new relying party).

Solidus status

Shipped, testnet-live. The SDK builds and verifies both presentation shapes; an OID4VP-style flow is also live on auth.solidus.network for EUDI-style presentation exchange. What's genuinely missing: a real, unaffiliated relying party in production actually accepting a reused Solidus credential. The mechanics work; the trust network that would make them matter doesn't exist yet.

Proof you can run yourself: the full challenge → sign → verify loop is documented with runnable code in Solidus's credential-flow developer guide, against the live testnet endpoint.