Built at NEAR HACKATHON

Buyer protection for payments from any chain

Lummy is a resale marketplace for concert tickets with escrow: the money waits until the show is over. A crypto payment cannot be taken back, which is a real risk when the seller is a stranger. So NEAR Intents brings the money from any chain into the escrow, and a model in NEAR AI's Trusted Execution Environment reads the ticket first.

1. Pay from any chain

A live quote from NEAR Intents for one ticket at 9.50 USDC. This holds nothing and costs nothing to try.

Pay with

Asking for a live quote...

Each order has its own receiver address, derived from its terms: listing, seller, price, show end, refund address and deadline. Paying that address is agreeing to those terms.
Until the money is locked in the escrow, it can only go into the escrow on those terms, or back to the refund address. No key controls it, Lummy's included. Once it is locked, Lummy's operator key rules on claims and can only split the money between this buyer and this seller.
Real payments here are open to the Lummy team only: the contract is unaudited and capped at a small amount.

2. A ticket check you can verify

Ticket PDFs carry names and booking codes. Lummy takes those out first, then a model running in NEAR AI's hardware-isolated environment reads the rest and pre-fills the listing. It decides nothing: a person rules on claims. Try it on a made-up ticket.

In the product: a listing on Binance Blockchain Week 2026 shows "Read by AI in NEAR AI's TEE: check the receipt" beside its price, the receipt of its own read.

3. On chain

Escrow on Arbitrum One: 0x68d5…3cb3 Receiver factory: 0x3dFc…b75C

The first real payment, 9 Nov 2026, with the team's own money

1. Paid 1.0156 USDC on Base 2. The swap on NEAR Intents (the unused 0.0078 USDC went back on Base) 3. 1 USDC arrives at the order's receiver on Arbitrum One 4. Locked in the escrow 5. Refunded by the escrow 6. Back at the buyer's refund address

Then the whole flow on lummy.id, 10 Nov 2026: a team account sold a sample ticket, another bought it from Ethereum, claimed it was never handed over, and got the money back

1. The ticket read in NEAR AI's TEE: its receipt on NEAR's Verification Center 2. Paid 9.603158 USDC on Ethereum 3. The swap on NEAR Intents 4. 9.5 USDC at the order's receiver on Arbitrum One 5. Locked in the escrow 6. Refunded on staff's ruling, after the buyer's claim 7. Back at the refund address locked before paying 8. The whole order on Lummy's public proof page, read from the contract

And from a connected wallet, 12 Nov 2026: Lummy read the wallet, picked USDC on Base, and the buyer confirmed one transfer. Locked in the escrow 37 seconds later; on 13 Nov we filed a claim on it, a person ruled, and the money went back

1. One transfer of 9.603158 USDC on Base, confirmed once in the wallet 2. The swap on NEAR Intents: 9.507126 used, 0.093632 sent back to the wallet 3. 9.5 USDC at the order's receiver on Arbitrum One, 27 seconds after the transfer 4. Locked in the escrow, 37 seconds after the transfer 5. Its public proof page: locked on 12 Nov, claimed and refunded on 13 Nov Every order paid into the escrow, read from the contract

Check the terms yourself: the receiver of the first payment, 0x903C…8f6A, shows its listing, seller, price, show end, refund address and deadline under Read Contract. Give them to the factory's receiverOf and it returns that same address. Change any one of them, the refund address included, and the address changes: the money could only go where those terms say.

Lummy existed before this hackathon: QRIS in Xendit's test mode for shows in Indonesia, and test USDC on Arbitrum Sepolia for shows abroad. It has no users or revenue yet. What is new is what this page shows.

Loading…