Shuttle Protocol

Shuttle is the missing layer between Web2 and Web3 accounts

Comment

Inspiration

Web3 Dapps cannot access users’ Web2 profiles and social links in a decentralized, verifiable and private way. The key problem is that: account systems in web2 and web3 are natively separate, technically unconnected, and even inherently in conflict with their value.

problems

What it does

Shuttle Protocol provides a decentralized user social link verification mechanism that aggregates cross-web user-profiles and social graphs. The great value in these aggregations, which are completely owned by users, can be unlocked and used in scenarios such as Web3 Social, DID, De-Fi and DAOs.

tunnel

How we built it

Shuttle created Decentralized OAuth by combining TEE MPC and OAuth technologies. We named it “DAuth”. DAuth allows users to complete the authentication of profiles such as Google, Twitter, Github, etc., and associate it with the user's Web3 account in a decentralized way. These profiles and their associated data are private, only the user can authorize access.

DAuth runs in nodes of Shuttle Network, coordinated by smart contracts that are deployed on XDC Network.

The account formats we support include EVM, XDC native, and Polkadot-Substrate.

Challenges we ran into

  1. To let more DID and Web3 social projects adopt and integrate Shuttle to verify user social links in a decentralized way;
  2. With more adoption, the next challenge is to guide growing users to Keysafe. Keysafe is a platform that we will provide in the next phase, it allows users to manage Web3 accounts with their own Web2 Social link, so as to obtain a web2 user-friendly and keyless user experience;

Accomplishments that we're proud of

What we learned

We talked to lots of Web3 native projects of DID and Web3 social. They are looking forward to integrating with Shuttle to get a no-boundary profile and social graph across Web2 and Web3.

What's next for Shuttle Protocol

  1. We will design and implement an on-chain tokenomics system to incentivize necessary parties in the protocol.
  2. Support more TEE implementations, such as Trusted Zone of ARM, and SEV of AMD;
  3. We will develop a Web3 navigation platform - Keysafe Portal that provides Web2 users with a keyless user experience.

Built With

Share this project:

Updates