Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
We’re excited to publically announce that Matic Network is partnering with Gitcoin to launch the Build-n-Earn Program – assisting dApps t…
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
I figure this one will probably be a lot of work and I don't know what other discussions already exists but maybe I can trigger some brainstorming.
My (limited) understanding is that we can't use multiple devices with a single id (key) because the log could get out of sync between devices. Eg: if I make a post on my phone, then another post on my laptop but the two don't sync between then I've got a divergent log. (Ignore the fact that there's no mobile support)
My first (naiive) solution is to give each user an ID on her first device, and each other device gets a child ID. Now each device owns it's own log. The user needs to just assert once in the device log that this ID also represents her. This assertion also being signed by the root ID; sort of like an https certificate. Maybe we can even do this using the existing certificate standards.