Don't Trust Us — Read the Code

Every ticketing company says they're fair. Every platform claims low fees. Every marketplace promises to fight scalping.

Here's the thing about promises: you can't audit them.

Today we're open-sourcing the smart contracts that power Celium Tickets. Not a sanitised excerpt. Not a whitepaper describing what the code does. The actual contracts — the logic that mints tickets, processes purchases, enforces resale caps, tracks attendance, and manages loyalty points.

We're doing this because the entire point of on-chain ticketing is that you don't have to trust the platform. And if you can't read the code, you're still trusting the platform.

What You'll Find in the Contracts

Celium's ticketing infrastructure runs on a set of interconnected smart contracts. Here's what each one does and why it matters for organisers and fans.

Ticket Minting and Sales

The core contract handles ticket creation as ERC-721 tokens. Every ticket — whether it's general admission or a specific seat — is a unique, verifiable asset. When an organiser creates an event, the contract defines the supply, pricing, and sale conditions. These parameters are immutable once deployed: no quiet price changes, no hidden inventory manipulation.

The Purchase Tracker

This contract records the relationship between buyers and events on-chain. It's not just a receipt — it's a verifiable history. An attendee who's been to five shows by the same artist has an on-chain record that proves it. This is the foundation for fan loyalty features that don't depend on any single platform's database.

Resale Controls

Seated tickets (ERC-721) can be transferred, but the contract enforces rules set by the organiser. That means price ceilings on resale — say, a maximum 20% markup — with royalties automatically routed back to the organiser and artist. Scalpers can't circumvent this because it's not a policy. It's code.

Burn and Proof of Attendance

When a ticket is scanned at the door, it's burned — consumed on-chain. But burning doesn't erase it. The burned ticket becomes a permanent, verifiable proof-of-attendance record. This opens the door to post-event utility: collectable tokens, artist airdrops to verified attendees, discount access for loyal fans.

Loyalty Points

A points contract lets organisers reward repeat attendees. Because it's on-chain, these points are portable and verifiable. An organiser doesn't need a partnership agreement to honour points earned at another venue — they can simply read the chain.

Why Open Source?

There are three reasons, and none of them are altruistic posturing.

It proves integrity. When your business model depends on trust — and ticketing absolutely does — the strongest thing you can say is "verify it yourself." Open-sourcing the contracts is the logical conclusion of building on a public ledger. If the chain is transparent but the code is proprietary, you've just moved the trust problem, not solved it.

It invites scrutiny. Security in smart contracts improves when more eyes are on the code. We'd rather have independent developers find an edge case than discover it in production. The contracts have been tested and audited, but open-sourcing them extends that review process to the entire community.

It raises the bar. If competitors want to match this level of transparency, they'll need to open their code too. That's good for the industry. The more platforms that prove their logic publicly, the harder it becomes for opaque incumbents to justify their black-box pricing.

What This Means for Organisers

If you're evaluating ticketing platforms, you now have something you've never had before: the ability to read exactly what happens to your money, your tickets, and your customer data. Not a terms-of-service document. Not a sales deck. The actual logic.

You can verify that resale caps work the way we say they do. You can confirm that royalties route correctly. You can see exactly how ticket supply and pricing are enforced.

That's not a feature. It's a standard that the rest of the industry should meet.

Where to Find the Code

The contracts are live on GitHub with full documentation. We've included inline comments explaining the business logic behind each function, a test suite you can run locally, and deployment guides if you want to inspect the contracts on a testnet.

Whether you're a developer evaluating the architecture, an organiser deciding which platform to trust, or a fan who wants to understand how your ticket actually works — the code is there. Read it.