Web2 to Web3 Proof of Concept

Inspiration

Social media likes, gaming achievements, and online activities often exist only in centralized Web2 platforms. While these metrics are important, they cannot be independently verified outside the original platform.

We were inspired to create a system that transforms Web2 activity data into verifiable, trustless proofs stored on-chain. In addition, we realized that real-world identity confirmation and event participation could also benefit from the same model of verifiable proofs — enabling communities to build trust without relying solely on centralized authorities.


What it does

Web2 to Web3 Proof of Concept connects Web2 APIs to the blockchain.

  1. A user logs in via Auth0 to access our Web2 API.

  2. The API returns a simple example activity (e.g., “completed 5 lessons” or “watched 3 videos”).

  3. The user signs this activity with their Web3Auth wallet.

  4. The signed proof is submitted to XION testnet, where anyone can verify it.

This proves that Web2 data can be anchored to Web3 in a secure and trustless way.

On top of that, we extend the idea into two additional proof types:

Identity Confirmation: Users can confirm each other as “Public” or “Anonymous” identities. Proof of confirmation is recorded on-chain, so trust relationships can be traced without exposing sensitive data.

Event Confirmation: Events (e.g., workshops, demonstrations, hackathons) can be created by coordinators. Attendees receive event tickets (pre-event confirmations) and attendance proofs (post-event confirmations). These confirmations are traceable and can include hierarchy rules (e.g., only Level 1 or Level 2 coordinators can validate attendance).


How we built it

Frontend: Capacitor + Vanilla JS, with early experiments in React Native (Expo Go).

Authentication: Auth0 for Web2 login, Web3Auth for wallet connection.

Backend: Node.js + Express API (simulating Web2 activity and confirmation flow).

Blockchain: XION SDK + zkTLS (to create verifiable proofs and store them on-chain).


Challenges we ran into

Integrating Web2 authentication (Auth0) with Web3 wallet connection (Web3Auth).

Designing confirmation flows (identity and event) that are both flexible and socially meaningful.

Limited time and resources to connect real external APIs (e.g., YouTube, Instagram).


Accomplishments that we're proud of

Demonstrated that Web2 API data can be converted into on-chain verifiable proofs.

Extended the idea into identity and event confirmations, making the system relevant to real-world community coordination.

Built a modular design where any Web2 API or social confirmation flow can be plugged in.

Built a working prototype that runs fully on XION testnet.


What we learned

How zkTLS can provide verifiable connections between Web2 and Web3.

The importance of bridging user identity between Web2 login systems and Web3 wallets.

That social trust (identity confirmation and event participation) can also be expressed as on-chain proofs.

That simplicity (starting with our own API and dummy confirmations) is often the best way to prove a concept.


What's next for Web2 to Web3 Proof of Concept

Integrating real-world APIs like YouTube views, fitness trackers, or gaming platforms.

Expanding confirmation models for community identity graphs and event verification.

Improving the UX by streamlining dual-login (Auth0 + Web3Auth).

Exploring marketplace opportunities where verified activity, identity, or event participation can be exchanged or rewarded.

Built With

Share this project:

Updates