🚀

Voyager Identity #15

Last Edited Time
Jun 17, 2022
Created time
Jun 17, 2022
Participants
Created By
Type
Identity WG
Created
Jun 17, 2022
Property
Property 1
Attendees
  1. James Brennan, Cent Hosten, Mendes, Emily Furlong, Joshua Tan, Aaron
Resources
Meeting Primer
🚀
Voyager Identity #5 Meeting Summary
Meeting Minutes
Updates:
Primarily a working group session reviewing structure of the attestation spec paper.
Removing 'Key's
Josh: Originally we had things like contribution types. If you (Aaron) were publishing Metadata, what would you imagine being the minimum collection data.
type, contribution, description, engagement date, submission date
Expanding the contributions array to include contribution type and constribution reference (an arbitrary URI).
Might it be worth changing the Member JSON in the EIP from address to id or identifier, or does this need to be the same across both standards?
People will be able to write JSON blobs and the DAO*1 Transformers will turn things like "type" into "@type" to reeduce the amount of notational complexity and unfamiliarity a person writing the JSON file might exeperience.
Garbage collection: IF we hit an expiration then we can't provide that attestation any longer. Will have an internal system for refreshing attestations to see if they are still valid or not.
🚀

Voyager Identity #15

Last Edited Time
Jun 17, 2022
Created time
Jun 17, 2022
Participants
Created By
Type
Identity WG
Created
Jun 17, 2022
Property
Property 1
Attendees
  1. James Brennan, Cent Hosten, Mendes, Emily Furlong, Joshua Tan, Aaron
Resources
Meeting Primer
🚀
Voyager Identity #5 Meeting Summary
Meeting Minutes
Updates:
Primarily a working group session reviewing structure of the attestation spec paper.
Removing 'Key's
Josh: Originally we had things like contribution types. If you (Aaron) were publishing Metadata, what would you imagine being the minimum collection data.
type, contribution, description, engagement date, submission date
Expanding the contributions array to include contribution type and constribution reference (an arbitrary URI).
Might it be worth changing the Member JSON in the EIP from address to id or identifier, or does this need to be the same across both standards?
People will be able to write JSON blobs and the DAO*1 Transformers will turn things like "type" into "@type" to reeduce the amount of notational complexity and unfamiliarity a person writing the JSON file might exeperience.
Garbage collection: IF we hit an expiration then we can't provide that attestation any longer. Will have an internal system for refreshing attestations to see if they are still valid or not.