👨‍🚀 StarkPass

StarkPass brings Starknet IRL by letting you buy tickets for your favourite events on-chain, using Starknet L2, Argent and Sismo.

For users

Starknet makes buying event tickets cheap, convenient and verifiable.

• ✅ Pay for the ticket that you want, not the high gas fees
• ✅ Register for global events without worrying about incompatible international banking systems
• ✅ On-chain and privacy-preserving evidence of your ticket via Sismo
• ✅ Support event organizers by leaving tips

For organizers

Create an on-chain ticketing system for your events.

• ⭐ Deploy a "ticket contract" for your new event
• ⭐ Withdraw revenue from ticket sales to your wallet
• ⭐ Define "ticket logic" to receive donations, ask users to lock up a stake, redistribute stake after the event

🔨 How was it made?

The project revolves around Starknet and the new Cairo 1.0 contracts. This creates and manages the "ticket contracts" that are defined by the event organizer and let customers buy event tickets.

The dApp interface was built with Next.js and integrates Argent X. We also use Sismo Connect's Zero-Knowledge Proofs to provide provable purchase confirmations that preserve user privacy. This setup lets us offer a secure, private, and efficient ticketing system.

⚙️ Technologies

The combination of Cairo contracts deployed on Starknet, Argent X, and Sismo's ZK proofs resulted in a system that is cost-effective, secure, and flexible.

To tie this together, we use JavaScript (Node.js) for the backend and the Web3.js library for interacting with Starknet (starknet.js and @argent/get-starknet) and Sismo (@sismo-core libraries).

👷 Build

To build the front-end part of the project, please follow the instructions described here.

The back-end part is basically all on-chain, represented as cairo contracts for Starknet. To build the main contract you should have starkli and scarb CLI tools. After the setup you can follow these instructions:

scarb build

starkli declare ./target/dev/contracts_StarkPassEvent.sierra.json --network=goerli-1 --compiler-version=2.0.1

starkli deploy <CLASS_HASH> <EVENT_ORGANIZER> <TICKET_PRICE_PART1_u128> <TICKET_PRICE_PART2_u128> <EVENT_NAME> --network=goerli-1

🧑‍💻 Todos

• Add events
• Remove the mock_buy function
• Approve spending for ERC20 from the FE
• Add staking logic
  • Requirements:
    • Organizer can require users to stake a token to receive a ticket. “Staking” means “locking the token and receiving it back after a user attended the event”
    • Organizer can redistribute the staked tokens to users who attended the event
    • Organizer can specify that users receive their stake back after “checking in” (to be defined what checking in actually entails) or when the organizer decides to (i.e., organizer triggers a “stake reimbursement”)
    • Users can stake tokens and receive a ticket
    • Users can be checked in or checked out
    • Users can receive their stake back immediately after checking in
• Add an event when sending a tip
• Add tests inside of the Cairo contracts
• Research whether Foundry for Cairo can be useful
• Add a factory contract
• Make tickets into ERC721 or Soulbound tokens that can be “checked in”

LICENSE

MIT