During the last 3 days I built TixPact for the NEAR HACKATHON
📆When an event is cancelled, your refund depends on the seller still having your money. Often they don't.
🎟️TixPact: event tickets whose price stays reserved in a NEAR smart contract until an agreed verifier confirms the event happened.
📽️In the video, on NEAR testnet with a real wallet:
• Ana buys a ticket. Her 0.5 NEAR goes to the contract, not to the organizer.
• The same ticket opens the door: her wallet signs a five-minute pass, with no transaction.
• She gives the ticket to Luis. It is an NFT, so the right to the refund travels with it.
• The organizer disappears. Nobody confirms the event and the deadline passes.
• Luis claims the 0.5 NEAR himself. No organizer, no support desk, no us.
✅What NEAR makes possible here:
• The contract holds the money and its only key was deleted: no owner, no admin, no upgrades.
• The verifier is a named account you can read O where 2 of 3 must agree.
• An AI agent can hold tickets with its own account and spending caps, and claim its refund on its own.
💡It works for any event: sports, concerts, AI summits.
Try it: https://t.co/RcuCtA8MmL
Code: https://t.co/cdB9Ql1hLR
One limit we state plainly: a verifier who liesrust to confirm that a concert really happened:the venue, a DAO of ticket holders, someone else?
Built at NEAR HACKATHON @NEARProtocol #NEARHackathon
Not every workflow requires an immediate response.
For single- or multi-turn workflows that can wait, save up to 40% per token than Standard on GPT-6.2 Astra or GPT-6.2 Sol.
In Responses API background mode, choose a 2h or 8h target for the first response. These discounted windows are now in public beta.
Hey @X algorithm, connect me with real human beings that are developing businesses as founders in AI
Developers
Engineers
Designers
All are welcome 🚀
Let's connect 🤝