← Back to home

KT Karen's Ticketing

Using web3 tech under the hood while offering an intuitive web2 experience: KT is an app that allows users to safely buy and resell event tickets as NFTs

Screenshots

KT Karen's Ticketing screenshot 1
KT Karen's Ticketing screenshot 2
KT Karen's Ticketing screenshot 3
KT Karen's Ticketing screenshot 4
KT Karen's Ticketing screenshot 5
KT Karen's Ticketing screenshot 6

Problem Statement

KT is a decentralized app that allows users to safely buy and resell event tickets.a straightforward user experience for both sellers and buyers: KT uses web3 tech while offering an intuitive web2 experience.buying safely: because event organizers' ENS data is added when they mint their tickets, a buyer will always be able to verify that their purchase is legiteffortless selling: you put up your ticket for sale and get a notification when it's sold

Solution

Demo: Prototype: https://www.figma.com/proto/8KPD1GzsM6PPAXTaNZfcs3/wireframes?t=hva80envolaOngHB-1Wallet infrastrucutre:Simple Onboarding for "Karen", a user without web3 experience/wallet.Authentication using dynamic for both web2 and web3 loginPossibility to use the coinbase smart wallet Secured by passkeyGasless experience utilizing the paymaster feature of the smart walletTicket infrastructure:Deployed to Base SepoliaTickets represented as ERC1155 NFTsEach event is represented by one NFT smart contract. ERC1155 allows us to have multiple types of tickets (the ID), each with an amount of available tickets.The event organizer creates the ticket contract and mints the initial supply of ticketsTickets become soul-bound tokens (meaning non-transferable) when the event opens its doorsTicket holders keep the NFTs as POAPs after the eventTicket holders enter the venue by signing a message while the back-end checks that the signer holds a ticket and has not entered yet. (Not implemented yet)Utilizing hardhat ignition for deployment and contract parameterizationUnit-test for fast development feedback and quality controlWeb development with expo to ensure compatibility across web, iOS and android from the beginningMarketing infrastructure:Holders of tickets can sell the ticketBuy offers and sell listings use the OpenSea infrastructure. We chose OpenSea because it is simple and fast to integrate (existing contracts, frontend, API). In the long run, it would be better to exchange with a less centralized solution utilizing on-chain data.Our front-end calls the OpenSea API to list and interact with sell offersFront-end infrastructure:Based on the Expo framework. Basically Next.js with the possibility to distribute the front-end as native Android/iOS app laterGeneral DevelopmentDesign and userflow created in FigmaGitHub as repositoryUsing monorepo structure to have all related code packages together.

Hackathon

ETHGlobal Brussels

2024

Contributors