Announcements:
- Get dat POAP
- Will be sent via DEGEN to all the participants.
- Dev Guild Newsletter
- If you don’t have guild tags, get them here:
- Focused Discussion meeting on TUESDAY at 11:30am EST!
- Knowledge Sessions
- Governance updates
- Dev Guild Coordinator
- Talent Coordinator
- Check with HashedMae, cross guild coordinator.
- Dev Guild First quests Admin Elections
- Check with jordaniza, everyone in dev-guild is welcome.
- voting in #dev-first-quest
- Dev Available tag
- Dev guild intake form:
- Tally Form
- New devs please fill out this form
- Allows the talent coordinator to better pair people to projects!
- DAO announcement
Intros:
Discussion Topics:
- Burger talk - paying in Bankless lol
- Pinging of @developers guild
- Preferences?
- most people on the call - pings have not a problem
- Digital Identity
- https://discord.com/channels/834499078434979890/914916952881905694/914918487313514546
- 0xNSHuman - Content Gateway
- Data from different projects are stored in flat collections with no relation to each other
- user that completed a course cannot be tied with the user that claimed a bounty
- hope that there is a discord ID / ethereum address to try and establish relationship between them in order to show on mobile app homescreen.
- Realization - need some kind of standard between these different types of data
- if you want your data to be resolved and assigned to particular user in content gateway, then you should add eth address + discord ID (for example). Then content gateway will create relationship and allow querying user
- ERC20 - standard created to allow users to query balances very easily
- Multi-tenant approach in bountyboard API
- question - how to manage rules of the game that different daos establish
- for example bankless only L2 can create bounties, other daos might have different rules
- need different mechanisms for authorized users to create bounties for other bounty boards
- this problem would benefit from identity standard - this particular user can be authorized across DAOs
- identity is simple standard at beginning but further on different usecases will use identity to tie relationships across different DAOs and projects
- what data fields are needed on Content Gateway to create a strong tie between identity on all different projects
- simple mechanism with no third party dependencies and just an internal agreement between API developers
- BrightID = peer to peer KYC
- ID - discord ID in the future might not be a future part of identity. Most people agree we are staying on Ethereum.
- even if DAO is not on mainnet, as long as EVM compatible machine then the addresses will map
- ENS - set text record Discord = montgomery
- Chainlink - create separate nodes as validators
- could we encapsulate ID logic into nodes and have several people running them across the DAO for proving identity for contribution?
- have nodes run by DAOs for identity validation?
- projects need to include a small amount of information (ethereum address) in order to establish an anchor to provide a query/grouping of all of the interactions with that address
- need identity standard for bounty-board API and also mobile app use case, also DEGEN for tipping
- By default can dev guild sites be deployed on ENS?
Action Items: