1E/ Unlocking Capabilities of Ethereum Keys / Sam G

From IIW

Session 1E

Unlocking Capabilities of Ethereum Keys


Session Convener: Sam G

Notes-taker(s): Zack


Tags / links to resources / technology discussed, related to this session:


Tree LDR - Spruce / https://blog.spruceid.com/introducing-treeldr-a-canopy-across-your-data-schemas/


Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:


Sam G from Spruce ID


EIP 191 - Signed Data Standard


SIWE - sign in with Ethereum

  • Standardized message format
  • Additional capability to detect something like a phishing request


Recaps Messages EIP 5573

  • “Read capability message” so users understand what they’re signing


Spruce is a part of “Chain agnostic standards alliance” - similar to EIPs but broader standards Kepler node treats your wallet as a source of authority where you can delegate Tracing that source of delegation, or the chain of delegation would require some amount of extension Spruce Rebase - Witnessing Verifiable Claims

  • Authenticating owners of social accounts and being able to provision access accordingly
Retrieved from "https://iiw.idcommons.net/index.php?title=1E/_Unlocking_Capabilities_of_Ethereum_Keys_/_Sam_G&oldid=24540"