Ticketh

Ticketh is a mobile ticketing platform with a mission to create tangible utility for NFT-based tickets by providing cross-chain access on Web3 account models. It serves as an attestation-based, cross-chain ticketing reputation platform, where users can accumulate reputation through active participation.

The use of NFTs as tickets frequently requires interaction with different platforms, managing additional information, and maintaining an unsustainable ticket generation mechanism. Challenges such as multi-usage of tickets, their transfer to others, and the constant need for external verifications are unavoidable.

Ticketh addresses these issues by aggregating NFT tickets on identity platforms, notably ENS, using resolvers on various chains. In collaboration with the Ethereum Attestation Service (EAS), it allows event organizers to create unique attestations for their events across multiple chains, thereby forming a reputation system around these attestations.

As users attend more events and accumulate attestations, they enhance their reputation score on the Ticketh platform. Event organizers can then utilize this reputation score, along with the user's Web3 ID via Next.ID, to offer customized perks, such as discounts, early bird access, or exclusive tickets. This system not only incentivizes user engagement but also promotes a more active and robust event community.

The platform runs in multiple chains by allowing event registrations and refunds on those chains while storing the critical attestation data that they receive from the organizers for their involvement in the events to improve their reputation points in the master chain.

A mobile app has been developed to create an environment that the users can reach the events and the event owners can manage the events. The app connects to blockchain networks by WalletConnect and sends transactions.

Ticketh runs with the master chain where the critical data is stored and the side chains which present a seamless use-case for the users. The master chain is a stack with app layers which are for identities, attestations, tickets, and impact. It matches the social identities of the users with the accounts, stores or generates attestation based reputations, holds ticket assets, and provides an environment for impactful applications. The side chains allow users to register/attend events, hold assets, and communicate with the master chain to ensure system integrity.

Identification with NextID: Ticketh makes it possible to prove a Web2 account on-chain which unlocks unlimited options for developers to authenticate and reward users. Using NextID and Ticketh’s SocialManager, one can easily create applications where only users who follow an account on Twitter or create unique assets for a specific user. Under the hood, we use CCIP-Read and NextID verification mechanisms to create an on-chain approach to prove account ownership.

Ticket Assets: Each event ticket is created as an ERC-1155 token asset. Then, these tokens are bought, can be refunded, and can also be stored in the “Apple Wallet” to create easy verifications.

Attestations: Event owner attests that users bought their ticket and attended the event using Ethereum Attestation Service (EAS). It is also possible to attest for different achievements made at the event. Aside from the regular benefits of using Attestation Service, we introduce Multi-Chain Attestations (MCAs), which are attestations that can be read/written to different chains. This makes such scenarios possible where a user buys a ticket on one chain and receives its perk on another. We are also using power of offchain attestation, instead of onchain tickets, that are provided by EAS, allowing users to more tailored approach to ticket information sharing, reducing the fraud risks.

Chainlink CCIP: Chainlink CCIP is providing a multi-chain structure for our application where the users can interact with the protocol from many chains, then its attestations can be written to the master chain.

CCIP-read: CCIP-read solution allows side chains to read the reputation data (attestations) from the master chain and utilize this score. This results with seamless user combined with seamless developer experience as read operations can be made in a single call instead of asynchronous callback mechanisms.