Brickken Developers
Build with Brickken Campaign
API

Tixken

AYAy· 11d ago

Most event tickets are disposable. They can be screenshotted, resold above face value, hard to verify, and worthless once the event ends. Tixken turns the ticket itself into an onchain asset. A host creates and tokenizes an event through Brickken. Attendees receive individually minted, whitelisted ticket tokens with QR codes. At the door, the ticket is checked onchain and burned after entry, preventing reuse. If an attendee can't make it, the ticket can be resold under a host-defined price cap, with the seller signing the transfer directly from their own wallet. Tixken also adds an agentic reclaim layer. Hosts decide what happens to unused tickets — burn them or convert them into credit. The reclaim agent is registered through Brickken's Agentic API, with RAMS actions configured around the host's chosen policy. Ticket lifecycle: Create → Mint → Verify → Enter → Resell → Reclaim. What makes it interesting: the same asset represents the attendee's right to enter, becomes unusable after entry, can move to another owner if plans change, and can retain value after the event through the reclaim policy — tokenization useful at every stage, not just at issuance. How Brickken is used: Tixken calls Brickken's sandbox REST APIs directly. Dapp API: newTokenization, whitelist, mintToken, burnToken, transferTo, approve, transaction status, whitelist status, token info. Agentic API: ERC-8004 agent registration, RAMS executor action configuration, ramsExecute. Runs on Ethereum Sepolia, Chain ID 11155111. Working features shown in the demo: event tokenization, ticket minting, QR generation, onchain door verification, burn-after-entry, resale with host price cap and wallet-signed transfer, and agentic reclaim architecture. Door Scan and Resale are confirmed end to end with real Sepolia transactions.

0 votes

One vote per person per contest — no account needed.

Comments (0)

Log in to join the conversation.

No comments yet.