Orie Steele

I tried to make a typescript implementation, but ended with something which is neither 1.0 or 2.0... https://github.com/transmute-industries/did-peer.js Current plan is to sort out alignment with KERI than then revise...

I have found it, I was just not sure i should use it given the potential spec changes... I plan to help update the spec and then make the implementation...

I recommend using: https://github.com/pokusew/nfc-pcsc, its supports raw transmit, and can be configured to handle large responses... You will need to generate / parse the TLV yourself.

Came across this, not sure if its useful. https://bcoin.io/docs/net_bip151.js.html There is also the original RFC for ECDH-ES with x25519 https://tools.ietf.org/html/rfc8037 IMO, the signature suites, key exchanges, or other protocol stuff...

@lemoustachiste the context IRI should not matter, as long as it produces the same nquads. My opinion is that an error should be thrown when attempting to sign a document...

Let's close

Yes, go ahead a close, are there any tests for the instance API and authz that can be linked to for future readers?

You might also want to consider the following: verifying a single presentation or 5 credentials, 2 have holder binding to different keys, 3 have status lists, 2 have multiple statuses...

I suggest closing this issue, the APIs seem to have ossified beyond the value of a greenfield exercise.

I'm ok leaving the recommendation to make the API stateless to profiles, I recommend closing this issue.