From my point of view this library origins from the DataIntegrityProof ecosystem. I myself found it quite a inconvenient to provide the proof of possession upon issuance as a JWT.
Therefore we contributed the DI proof of possession as a DI proof presentation openid/OpenID4VCI#66 to the OpenID4VCI spec.
It is almost finished/merged. The only point remaining is the naming (ldp_vp vs. ldp_vp_2.0). Maybe you, as an OID4VC library provider, could contribute an opinion and help to push the PR into spec.
From my point of view this library origins from the DataIntegrityProof ecosystem. I myself found it quite a inconvenient to provide the proof of possession upon issuance as a JWT.
Therefore we contributed the DI proof of possession as a DI proof presentation openid/OpenID4VCI#66 to the OpenID4VCI spec.
It is almost finished/merged. The only point remaining is the naming (
ldp_vpvs.ldp_vp_2.0). Maybe you, as an OID4VC library provider, could contribute an opinion and help to push the PR into spec.