The problem ZKTPS-V2 solves

High Costs: Traditional ticketing platforms impose substantial fees, including service and processing fees, making it expensive for smaller organizers to host events.

Centralization: Existing ticketing systems rely heavily on third-party platforms, leading to single points of failure, biased policies, and data breaches, reducing transparency and control for users.

Black Marketing: Tickets often enter a secondary market where they are sold at inflated prices, disadvantaging genuine fans and enabling unfair profits for scalpers.

Replay Attacks: Traditional ticketing systems are vulnerable to replay attacks, allowing malicious actors to reuse valid ticket transaction data for unauthorized access, compromising event security.

Challenges we ran into

While implementing garaga , as it is new in the community we faces several syntax issues due to improper and outdated docs and version problems.

Additional Features

Earlier the project was having L1-L2 messaging as a mode for verifying zk snarks proofs as they was unavailable on starknet, now we added zk snarks using garaga( a library to use zk snarks on starknet itself) by this invalidators don't have to carry eth in order to invalidate tickets.