Bumblefudge

icon indicating a website link http://learningproof.xyz

icon company @ChainAgnostic icon location Berlin, Deutschland icon location Identity nerd, tech writer, data sovereignty maxi, he/him. standards @ChainAgnostic , @protocol , etc ; steercomm @decentralized-identity fdtn; ex @spruceid

Results 365 comments of Bumblefudge

eth_call signature combined with block number is a unique identifier

4 weeks from tomorrow at the same time! Please smash the calendar-subscribe button here: https://github.com/ChainAgnostic/CASA/issues/14

eth_call signature combined with block number is a unique identifier

Reminder-- meeting next week, would love to discuss!

eth_call signature combined with block number is a unique identifier

Discussed on today's call: - start with a PR defining just blockheight URN (CAIP 2 + 10 + ___) - future spec PR about callSignatures should - include a reference...

Create automation to update the index of CAIPs

there's gotta be a way to automate this from the jekyll-style yaml frontmatter... any gitpages/jekyll wizards out there?

Add extension mechanism to allow different methods for VP-to-VC / holder binding to next version of standard to allow verification of rightfulness of presentation

Over the years, I have actually heard about many different solutions (variously elegant) to what I have come to call the "VP Containing VCs With Different `credentialSubject`s Problem". I think...

Add extension mechanism to allow different methods for VP-to-VC / holder binding to next version of standard to allow verification of rightfulness of presentation

This also seems relevant to #879 (even if that's backwards-looking and this is forward-looking, whoever works on that section of the Imp Guide should know about this!)

Add extension mechanism to allow different methods for VP-to-VC / holder binding to next version of standard to allow verification of rightfulness of presentation

> I really dislike having OR types in a specification Just spitballing here, but what about this upgrade path: V1: `holder` = string V2: `holder` = string OR object, but...

Question: Using Refresh Service Property to update a credential when Credential Subject has a new field

NB @solidnerd -- this might help! https://github.com/w3c-ccg/vc-api/issues/245

Question: Using Refresh Service Property to update a credential when Credential Subject has a new field

> The holder or verifier can request the refresh service to start to get a new credential Issuer-initiated refreshes are... unpopular proposals within the CCG community (slippery slope!) but holder-initiated...

Standardize recording a pre-issuance DID Auth VP as evidence property

I am a huge fan of the `evidence` property, and I always wished there was some way of registering, harmonizing, open sourcing, or even just documenting usages of it. Doesn't...