E20 | Devpost

E20 is a wordplay that works in italian, since 20 is "venti", and events is "eventi", so: "E-venti" ;)

Inspiration

With E20 ETHTurin wants to make crypto event technologies less self-referential. In order to achieve this goal we want to create meetups and gatherings that mix crypto technology education and usage with music, moving from a pure technical and crypto-enthusiast public to potentially everyone that just wants to vibe to open mics and dj sets (and probably just snag some free drinks). Since we have to onboard these non-crypto native people, the experience of creating a wallet, claiming POAPs and vote on polls has to be completely frictionless.

What it does

It's a system that enables different actors (event organizers, event attendees and event location staff) to interact with events.

Event organizers use an authenticated dashboard to:

create organizations which can host multiple events
create events (to be imagined more like long-lived tracks) inside those organizations which can be divided in instances
create event instances which have these infos attached:
- basic event infos (from-to datetime, position, various social links to share)
- A POAP (with minting functionalities) that can be used for event access and benefits (like free drinks)
- POAP-gated Polls which can be submitted to participants (for example to vote for the best performer at an open mic)

Event attendees have a couple of pages to:

automatically create a Burner Wallet and claim event instance's POAPs
vote on POAP-gated polls
show their wallet's QR code to event location managers

Event location staff have access to a page to scan and validate QR codes with POAPs to distribute benefits such as access or free drinks.

How we built it

We built E20 using:

Next.js for the frontend
ethers.js to create Burner Wallets and interact with the Gnosis Chain blockchain.
Ceramic Network to store events data and their relative datamodels.
Hardhat to setup the Poll smart contract development and testing.

Challenges we ran into

The only major roadblock we bumped into was the discovery that POAPs cannot be directly minted using their smart contract but you have to use poap.xyz APIs and pass their reviewing committee check. So right now we are at a crossroads with a decision to make:

Just use their API
Fork them, sacrificing composability to favor permissionlessness

Accomplishments that we're proud of

We glued together a lot of different technologies in such a short amount of time, making use of what we think are underrated technologies such as DIDs and DID documents for authentication and data storage and Burner Wallets for a fast and frictionless onboarding experience

What's next for E20

Stop using a centralized EOA to fund users' transactions and use a decentralized relaying network like GSN
Decide what to do with the token event attendance problem as stated in the challenges section above
give users the possibility to login with some web3 wallet if they're more crypto-savvy and/or a way to transfer their POAPs from the burner wallet to their already existing wallet