Content pfp
Content
@
0 reply
0 recast
0 reaction

Dan | Icebreaker pfp
Dan | Icebreaker
@web3pm
Just got my google attestation from my former Eng director too!! Gotta collect em all
1 reply
2 recasts
6 reactions

Roberto Bayardo 🎩 pfp
Roberto Bayardo 🎩
@bayardo.eth
How does that work exactly?
1 reply
0 recast
1 reaction

Dan | Icebreaker pfp
Dan | Icebreaker
@web3pm
Anyone who verifies email domain using Icebreaker automatically gets a Verified: domain EAS credential Once you have a verified credential, you can attest to anyone else having worked there using the UI. It will then generate another verified attestation and equip it to their profile, with a note in the context field tracing the origin back to you (as opposed to email verification). There will be a "Dispute Company" flow in the future that will allow for downvoting untruthful attestations. Sort of like a very very slow version of blockchain consensus
2 replies
0 recast
2 reactions

πŸ”΅  kate.base.eth pfp
πŸ”΅ kate.base.eth
@kate
@web3pm I think this is a good start. Let's assume I attest with my Coinbase email and then I start attesting people to Coinbase. How useful is that data? When somebody has Coinbase attestation, does it mean they worked there? do they still work there? are they a full-time employee? were they a contractor? were they an intern, a partner vendor? Does it simply represent affiliation with the company? What are the use cases that this attestation would be helpful when it is this broad by definition?
1 reply
0 recast
1 reaction

Dan | Icebreaker pfp
Dan | Icebreaker
@web3pm
Yup, great questions! Since attestations support refUIDs, we can let you add context to prior attestations through additional attestations. So in the future, after you attest "worked directly with" someone, imagine we will prompt you to indicate the company where you worked with them. And when you verify someone's company, there will be an option to select "they currently work here". Maybe in the future you could attest to their role or other things directly from Icebreaker. Technically, there's nothing that prevents you from doing this now using EAS, since you can sign arbitrary statements referencing the attestations you've made thru Icebreaker. The usefulness is to then expose this data so it's easy to ask things like: - Who previously worked at Coinbase from 2015-2020 and where do they work now? or - Who did Dan work with while he was at Coinbase? If you have any ideas for initial use cases you'd like to be solved, let me know!
1 reply
0 recast
1 reaction

πŸ”΅  kate.base.eth pfp
πŸ”΅ kate.base.eth
@kate
This is great, thank you for the details Dan! I really like you are building it in an extendable way. One thing to flag based on past mistakes and learnings on my end: I think going vertical in the beginning and solving a narrow problem helps build better products than casting a wide net. Since I am interested in onchain employment verifications - I'd first try attestations to answer a more concrete question. I personally am interested in where people work right now. If there was an attestation system that'd give me that data with rough accuracy, there'd be a lot to build on it. I assume that'd require some sort of regular attestation refresh. Your plans and use cases might be completely different, so please take it or leave it as a suggestion. To me it is a much more interesting onchain verifiable data point that Dan currently works at Icebreaker or Tom currently contributes to OnchainKit, than Tim was affiliated with Google at one point (how/when/why to come later).
1 reply
0 recast
1 reaction