ocubes π retweeted
INTRODUCING HOLECARD; My build for the #NEARHackathon.
I built Holecard because i wanted to explore something beyond the usual AI agents making decisions and asking everyone to trust the outcome.
What if an AI agent could have its own on-chain account, make decisions privately and have everything independently verified before any settlement happens? Thatβs what Iβve been building with HOLECARD on @NEARProtocol.
Holecard is an AI-powered Texas Hold'em tournament arena built around verifiable agent execution, on-chain escrow and independent result verification. But the interesting part isn't really the poker; It's the infrastructure behind it.
Here's how everything works.
β
Every AI agent has its own NEAR account:
Agents aren't just profiles sitting in a database. Each one gets a dedicated NEAR sub-account created through the smart contract, with carefully restricted permissions.
The owner controls the full-access key, while the server only receives a limited function-call key. It can enter tournaments and initiate withdrawals, but it cannot redirect the agent's funds.
β
AI decisions happen privately inside a TEE:
Before a match begins, the operator commits to a deck seed on-chain. OutLayer VRF supplies verifiable randomness, with its Ed25519 proof checked on-chain before cards are dealt.
The agents run open AI models, including Qwen 3.6 and GLM-5.3, inside NEAR AI Cloud Trusted Execution Environments.
Prompts aren't stored, instead request and response hashes are signed by the enclave and checked against fresh attestations.
The goal is simple: private decisions with verifiable execution.
β
The operator cannot just declare a winner and release funds:
The operator can submit a match result, but that alone isn't enough for settlement. A separate OutLayer TEE independently replays the match, validates the actions, and confirms the final rankings.
Only matching verified results can trigger settlement. Their is no payout if their is no Verifiable result.
β
I also built the complete player experience:
Beyond the contracts, Holecard includes:
β Free practice matches with explained decisions and odds
β NEAR Connect authentication through NEP-413 signatures
β Dedicated on-chain agent accounts
β Gas-sponsored onboarding through a NEP-366 relayer
β NEAR Intents integration for cross-chain asset quoting
β Automated agent participation
β Public leaderboards tracking performance and Elo ratings
β Soulbound NEP-245 achievement trophies
β Escrow accounting, fixed prize allocations, and refund handling
The idea was to make the interface simple while keeping the underlying system verifiable.
β
And yes, I tested the verification flow on-chain:
In a NEAR testnet match:
β 15 hands were independently replayed by OutLayer
β All 62 AI decisions carried TEE signatures
β Settlement completed with testnet payouts of 1.4 and 0.6 NEAR
The contract only proceeded after the verification checks passed. That's the part I'm most excited about.
Holecard brings together 12 NEAR technologies and integrations in one project, but the bigger idea goes beyond a card game. If AI agents are going to control assets and make financial decisions, we need systems where execution can be checked instead of simply trusted.
I've attached the demo video showing the experience and the verification architecture. π
Play here π holecard.fun
GitHub π github.com/Somtiee/holecard
Contract π agent-arena-ad7b13.testnet
Built on @NEARProtocol for the #NEARHackathon.
@NearBuilders
Still building. Still learning.
ocubes π retweeted
Introducing SETTLE, a decentralized escrow, work verification, and payment protocol built on NEAR Protocol for humans and autonomous AI agents.
As AI agents become capable of executing tasks, interacting with APIs, and working independently, one major challenge remains: How do we verify their work and ensure payments are settled fairly without relying on trust?
That's what we're building with SETTLE.
SETTLE combines on-chain escrow, programmable verification, and automated settlement into a system where payments are tied to predefined conditions rather than promises.
Here's what we've built so far:
β’ Smart Contract Escrow: Funds are locked on NEAR, with milestone-based releases governed by agreed conditions.
β’ Programmable Verification: Supports API checks, GitHub CI, deterministic text validation, and human review for subjective deliverables.
β’ Automated Settlement: Cryptographically signed verification results enable payouts after a challenge window. Failed verification cannot trigger automatic payment.
β’ Bounty Marketplace: Clients can publish escrow-funded tasks that humans or eligible AI agents can claim and complete.
β’ Autonomous Agent Swarm: AI agents can discover bounties, execute supported tasks using NEAR AI, submit deliverables, undergo verification, and earn on-chain payments.
β’ Agent Integration: Developers can connect their own agents through our MCP server, TypeScript SDK, or HTTP API, using agent-controlled NEAR accounts.
β’ Payment Security: Immutable agreement terms, exact integer accounting, dispute handling, bounded revisions, partial settlements, and duplicate-payout protection.
And this isn't just theoretical.
We've successfully executed a complete workflow on NEAR testnet where an AI agent claimed a funded bounty, completed the task, received a cryptographically signed PASS verification, and was paid automatically by the escrow contract.
The entire process, from bounty creation to settlement, took just over three minutes, including the challenge window.
Every transaction is publicly verifiable on-chain.
Our long-term vision is to create an open coordination and payment layer where humans can hire AI agents, agents can hire other agents, and work can be verified and compensated through transparent, enforceable agreements.
We're expanding verification capabilities to support more complex code execution, data processing, and multi-stage workflows.
SETTLE is currently live on NEAR testnet, with mainnet deployment planned after a comprehensive security audit.
Explore the product, test the protocol or contribute to development.
π settlenear.xyz
π» github.com/folarihn/settle
Verifiable work. Programmable trust. Onchain settlement.
Built for #NEARHackathon, @NEARProtocol.
ocubes π retweeted
Lionel Messi.
The undisputed GOAT.
A record-breaking eighth Ballon d'Orπ
#BallonDor
ocubes π retweeted
Unai Simon wasnβt in laliga team of the year
Not in UCL team of the year
Not even in the World Cup team of the year
How come heβs the best goal keeper in the world?
π£οΈ Petr Δech on the Ballon dβOr organisers naming Unai SimΓ³n Goalkeeper of the Year over David Raya:
βI honestly can't believe what the Ballon d'Or has become. Is this a football awards ceremony or a FIFA World Cup winners' celebration? Are we really judging an entire season by a seven-game tournament?
It's embarrassing. David Raya has won THREE consecutive Premier League Golden Gloves, kept 19 clean sheets in the league and nine more in the Champions League. Yet somehow, that's not enough to make him the best goalkeeper of the year?
Unai SimΓ³n deserves credit for his World Cup performances, but individual awards should recognise consistency across an entire season, not just international tournament success.
Raya has proved himself week after week at the highest level. If we're going to ignore that kind of consistency because another goalkeeper won the World Cup, then what exactly are these awards meant to recognise?
The Ballon d'Or organisers need to explain their criteria because decisions like this make a mockery of the entire process.
#BallonDor
ocubes π retweeted
Arsenal were UCL and Carabao Cup finalists and Premier League winners without a top 14 player, without the best GK in the world, and without the best coach in the world.
Interesting π
My Tiny Legends whitelist application is in (spot #1886)! Pixel idle RPG, coming soon to mobile and browser. Join with my link: @Tinylegends_io tinylegendsgame.io/#ref-1iwkβ¦
66
ocubes π retweeted
me texting you in the middle of a football match is a bigger sign that i want to marry you than me introducing you to my mum
ocubes π retweeted
When I first started exploring @torpornet , I didnβt know exactly what to expect.
I just wanted to see what the project was about and how the MACHINE worked.
Now, Iβve got a few things to share from my journey so far:
- At first, my application was still pending, and my top card showed a C status.
I had two cards at the time, and I was curious about what would happen next.
Of course, I wanted to see some progress.
- I kept showing up and posting about Torpor.
- Eventually, I checked again and noticed that my top status had moved from C to B.
- That was a nice little moment because I could actually see a change in my progress.
One thing I have learnt is that you canβt always expect everything to happen immediately.
Iβm taking my time, checking the updates, exploring the features, and sharing what I find along the way.
If youβre also exploring @torpornet ,where are you currently in your journey? How many cards do you hold? Mine is currently 10
Iβm tired and about to call it a night, but knowing me, Iβll still check @torpornet before I sleep.
Let me see what The Machine has for me this time.
For now, let me get some rest. Expect more insights from me later today. πΈπ
Gn Torpor fam
Gn @torpornet
Secured my Whitelist spot for @SpacInk1 on @inkonchain! β‘
β’ 1,111 Supply | 100% FREE MINT
β’ Unlock 100% Gasless Utility
π 1-Time Use Invite Code for the next voyager:
SPACINK-MZNJ-6679
Claim the next spot fast (1,000 Max):
spacink.wtf/wl
67
I just drew my Smart Case and got on the whitelist π₯
808 drawn incubators. One egg each. Nobody knows what hatches.
Get yours before they hatch: smartcase.lol/r/ocubesx2
@smartcase4frens #SmartCases
32
ocubes π retweeted
Replying to @torpornet
@torpornet is taking a different approach to mints. Itβs a hand curated early access system built around patience and deliberate participation.
Apply with link below, create around them and get a GTD spot.
Apply here: torpor.net nitter.cf/torpornet/status/21051β¦

























