web3log.in-nearvatar

web3log.in

Inspiration

Nowadays our web3 experience is just scattered, users and developers are overwhelmed by tons of public chains surging in. We know that "decentralize" is the idea, but it doesn't mean we should do the same thing over and over again. developers and content providers are facing difficulties in choosing which chain they are gonna support, really a waste of time they should focus on the content they are creating. and the users deserve an elegant way of login into the website using web3, they deserve an avatar and a profile page others can see. there should be someplace to reflect the real "you", not the piece of "you" or part of "you" in a single chain. we got our inspiration from gravatar, GitHub login(OAuth), and cyber connect-eth.

What it does

Therefore web3log.in does 2 things Nearvatar and WEB3log.in service

Nearvatar for users

It's just like the gravatar but in the blockchain. you can mint your nearvatar from your NFT collections, and also fork the nearvatar you like from other people. you can also get your profile page and store your info into the contract so other people can see it. Minted Nearvatar will store his father and ancestor into the NFT metadata. when getting the nearvatar user will be able to login into any website that supports the web3log.in with just one click.

WEB3log.in service for developers

an easy to deploy SDK for developers who wants to support web3login, but don't want to add too many buttons on the login page one button, we will handle the OAuth and multichain support. also, developers can show users avatars (nearvatar) on their website. Click the nearvatar photo will redirect you straight to his nearvatar profile page. starting with Near and Eth, more public chains coming soon.

How we built it

Starting with the sample idea above we form a team with frontend backend and contract. the frontend will do the backend will do the contract will do

Challenges we ran into

fork mechanism

The first challenge is the fork mechanism, nearvatar can only be minted in 2 ways, mint from the NFT collection or fork from others. how can we tell the difference between the people who own the NFT and people who fork from others？ we solve this problem by adding 1 px of the frame to the picture, if you mint the nearvatar from your NFT collection red frame will be added to the picture and mint a new nearvatar NFT. if you fork from others, we will remove the red frame and add a yellow frame to the picture. people will tell the difference by looking at the frame of the picture. also, we store the Nearvatar's father and ancestor and other information in the metadata, it will be fun to play with the "fork family tree"

team building

it's pretty difficult when working remotely, especially when your teammates are from all over the world. it's a little bit difficult to communicate the first time, and teammates come and go. we finally manage to form a stable team to deliver the product before DDL.

Accomplishments that we're proud of

Forking mechanism

Universal did and login solution for users and developers

NFT as nearvatar

SDK for developers

Nearavatar API for developers

What we learned

Form a team and be productive with other people you have never seen before in a short time.

Combine OAuth and multi-chain login

Building a product in Near

What's next for web3log.in-nearvatar

Multi-chain support starting with Near and Eth. The vision of web3log.in-nearvatar is to support most of the public chains and provide a secure login service for all the web3 users and developers. we will add more public chain support soon. There are a lot more fun to play with the fork mechanism and "fork family tree" development around them are on the way Test flight for some chosen users. lobbying team will start to lobby some web2 webmasters to deploy our service to their website we will see the list of their names soon.