Tizzle
Website: tizzle.app
Network: Devnet

Whitepaper

Tizzle is a refundable staking-based event ticketing protocol built on Solana. Instead of purchasing tickets traditionally, users stake tokens to reserve attendance. If they attend the event, their stake is refunded, reducing no-shows while removing payment friction.

01

Executive Summary

Tizzle is a Solana-based event ticketing protocol that replaces traditional ticket purchases with a refundable staking mechanism. Users lock tokens when registering for events and receive refunds after verified attendance, creating a commitment-based system that dramatically reduces no-show rates while eliminating payment friction.

The protocol introduces a Pay-per-Slot business model where organizers pay a flat platform fee for every attendee slot created, while attendees stake tokens that are held in escrow and returned after attendance verification. This creates aligned incentives for both organizers and attendees without charging attendees directly.

02

Vision & Mission

Vision

To become the standard infrastructure for on-chain event management, enabling a future where attendance verification, reputation systems, and token utility are seamlessly integrated into everyday event experiences.

Mission

03

Problem Statement

Traditional event ticketing systems face several critical challenges:

High No-Show Rates

Free events often experience 30–50% no-show rates, wasting organizer resources.

Payment Friction

Traditional payment methods create barriers, especially for international attendees.

Limited Token Utility

Most crypto tokens lack real-world use cases beyond speculation.

No Verification

Lack of transparent, on-chain attendance verification.

Tizzle addresses these issues by building entirely on Solana, using stake-based commitment mechanics, deterministic smart contracts, and a fee-backed sustainable model.

04

Core Mechanism Overview

Stake-to-Attend Flow

Tizzle introduces a five-step process that ensures commitment without upfront payment:

Key Innovation

Tizzle never charges attendees directly. Platform revenue comes exclusively from organizer fees, while attendee stakes are held in escrow and returned after attendance verification.

05

Economic Model

5.1 Platform Fee Structure

Tizzle implements a Pay-per-Slot model that charges event organizers a flat fee for every attendee slot created, regardless of whether the slot is filled.

Total Platform Fee = Event Capacity × Fee Per Slot

Example:
capacity     = 100 attendees
fee_per_slot = 0.0005 SOL
Total Fee    = 100 × 0.0005 SOL = 0.05 SOL
Property Description
Fee Model Linear Pay-per-Slot
Charged To Event Organizer
Payment Time During event creation
Destination Platform Treasury PDA
Attendee Cost Zero platform fee

5.2 Revenue Streams

Platform Revenue (Protocol)

Source:      Organizer platform fees (paid in SOL)
Formula:     platform_fee = capacity × fee_per_slot
Destination: Platform Treasury PDA
Use:         Protocol development and maintenance

Organizer Revenue

Sources:
1. Host Fee (optional)
   - Percentage deducted from attendee refunds
   - In same token as stake
   - Example: 5% of 10 SOL = 0.5 SOL

2. No-Show Penalty
   - Full stake from non-attending users
   - In same token as stake
   - Compensates for lost event capacity

5.3 Token Flow

Flow Type From To Token
Platform Fee Organizer Wallet Platform Treasury SOL (always)
Stake Deposit Attendee Wallet Escrow Vault Any supported token
Refund (Attended) Escrow Vault Attendee Wallet Same as stake
Host Fee Escrow Vault Org Treasury Same as stake
No-Show Penalty Escrow Vault Org Treasury Same as stake
06

Technical Architecture

Tizzle consists of three integrated layers:

6.1 On-Chain Program (Anchor/Rust)

6.2 Backend Services (NestJS)

6.3 Frontend Application

07

Smart Contract Design

7.1 Account Structure

The protocol uses Program Derived Addresses (PDAs) for deterministic account management:

Account Purpose Seeds
Protocol Config Global protocol settings ["config"]
Organization Organizer profile and treasury ["organization", organizer]
Event Event configuration and metrics ["event", org, event_id]
Registration Attendee ticket record ["registration", event, user]
Escrow Vault Holds staked tokens ["escrow", event]
Platform Treasury Collects platform fees ["treasury"]

7.2 Multi-Token Support

Native SOL

Direct lamport transfers via System Program. Most gas-efficient option.

SPL Token

Standard fungible tokens using Token Program. Backward compatible.

Token-2022

Next-gen tokens with transfer fees, hooks, and metadata support.

Important

Platform fees are always paid in native SOL, regardless of the stake token type. This ensures consistent protocol revenue while allowing flexibility in stake token selection.

08

Event Lifecycle

Events progress through deterministic states based on timestamps, ensuring predictable behavior without requiring manual updates.

Status States

Status Condition Actions Allowed
Available now < start_time Registration open
Ongoing start_time ≤ now < end_time Check-in active
Ended end_time ≤ now < unlock_time No actions
Settlement now ≥ unlock_time Refunds claimable
Closed All refunds processed Event finalized
Immutability Rules

Once created, events cannot be deleted. This ensures historical transparency, prevents organizer manipulation, and maintains reliable on-chain attendance records. Critical fields like stake_amount, capacity, and organizer cannot be modified after creation.

09

Security Model

9.1 On-Chain Security

🔐
PDA Authority

All accounts use Program Derived Addresses, ensuring only the program can authorize critical operations.

Double Refund Prevention

Registration accounts track refund status, preventing users from claiming refunds multiple times.

🛡️
Token Verification

All token transfers use transfer_checked with mint and decimal validation.

Timestamp Validation

Strict time-based checks prevent premature refunds and ensure proper event progression.

9.2 Backend Security

Wallet-Based Authentication

1. Client requests nonce from server
2. Client signs message with wallet private key
3. Server verifies signature using Ed25519
4. JWT token issued for authenticated sessions
5. All protected endpoints require valid JWT

On-Chain Verification

All POST and PUT operations verify on-chain state before database updates. The blockchain is the source of truth. The backend database serves as a cache and metadata store, but all critical operations are verified against on-chain state.

10

Why Solana?

Ultra-Low Fees

Transaction costs average $0.00025, making micro-transactions economically viable for event ticketing.

🚀
High Throughput

65,000 TPS capacity enables simultaneous registrations during high-demand events without congestion.

📱
Mobile Wallet Support

Native mobile wallet adapters provide seamless on-site check-in experiences via QR codes.

⏱️
Fast Finality

400ms block times enable real-time attendance verification and instant refund processing.

11

Roadmap

Phase 1: Foundation (Q1 2026) ✅

Phase 2: Enhancement (Q2 2026)

Phase 3: Expansion (Q3 2026)

Phase 4: Ecosystem (Q4 2026)

12

Risks & Mitigations

Smart Contract Risk

Risk: Bugs or vulnerabilities in smart contract code could lead to loss of funds.

Mitigation:

Adoption Risk

Risk: Users may be unfamiliar with crypto wallets and staking mechanisms.

Mitigation:

Network Risk

Risk: Solana network congestion or downtime could affect event operations.

Mitigation:

13

Conclusion

Tizzle represents a paradigm shift in event ticketing, replacing traditional payment models with a commitment-based staking mechanism that aligns incentives for all participants. By leveraging Solana's high-performance blockchain, Tizzle delivers zero platform fees for attendees, instant refunds, and transparent on-chain attendance records.

The protocol's design prioritizes security, transparency, and user experience while maintaining the flexibility to evolve through community governance. As blockchain technology continues to mature, Tizzle demonstrates how decentralized systems can solve real-world problems more effectively than traditional alternatives.

Vision

Tizzle aims to become the standard infrastructure for on-chain event management, enabling a future where attendance verification, reputation systems, and token utility are seamlessly integrated into everyday event experiences.