Bumblefudge

Results 367 comments of Bumblefudge

the latter -- just add a section to the [polkadot/caip10.md](https://namespaces.chainagnostic.org/polkadot/caip10#syntax) between syntax and test cases with a `###` header instead of a `##` header! this is exciting, i was hoping...

Hey @tlodderstedt -- we discussed this on today's call and realized that the LD-Frame object (section 7.5 of today's spec) could be used to specify more explicitly for selectively-disclosed properties...

Came back to this today on today's call, and had a clarifying question: does the Verifier really trust the Wallet/Holder to do this selection? Is it somehow enforced on the...

all the matching VCs in your wallet, not oneOf them, you mean?

NB @decentralgabe @andorsk -- "overask detection/notification" sounds like potential use-case for the TOIP spec, particularly if the TRAIN paper is listed as prior art and feature parity with other architectures/implementations...

I'd recommend we keep the issue open cuz PEv3 is on low-key hiatus while gathering implementation feedback (of which this is a good example) and focusing on related specs (like...

@brentzundel brought up the good point that even if a NEW FEATURE gets put off til v3, vNow could include a little non-normative guidance or explanation of how to do...

@Sakurann -- We discussed on today's call, and debated a bit whether this use-case could be supported by a feature or by core functionality. Reluctant to make such a consequential...

Discussed on today's call: 1. might help to get precise on $ref limitations in common libraries, etc to minimize DDoS surface of huge JSON Schemas 2. will in upcoming meetings...

Okeydoke, just turn on Discussions here and I'll redirect the current link pointing to multiformats/multiformats/discussions 😵‍💫