Nearchos

icebreaker

Minor detail in this week's launch, but big implications for giving more control over linked data on Icebreaker.

We've begun splitting login methods from account verifications and data integrations.

To date, we've used /privy for most account verifications*

(*plus integrating with other verified sources like farcaster, talent, ens, etc because we believe in the principle of "verify once, use across web3")

Moving forward, we will begin splitting out:

linked accounts / login methods (e.g., using privy)
-> used both for login and for verifications

verified accounts (e.g., using oauth, magic links, txt records, attestations)
-> not necessarily login methods. lets us expand the universe of verifiable accounts dramatically without compromising on account security

data integrations (e.g., reclaim, oauth, opacity, verifiable ai agents)
-> optionally lets you integrate more deeply, e.g., pulling your full linkedin, twitter, or google calendar networks so you can see your strongest connections in one place

"The beauty of building a modern networking solution on web3 rails is that we can architect so that even if we want to rug / gatekeep / lock you in, we don't have the technical ability."

- @web3pm 

There's no single thing that will indicate we've achieved the web3 dream, but there will be signs.

Identity and math

Co-founder at @icebreaker

icbk.me/web3pm.fc

When the system protects users even from its creators that’s when trust becomes native.