
Building on NEAR, Flare Networks // Founder @linkedup_app
Earth
Joined April 2019
- Tweets2K
- Following488
- Followers841
- Likes5.5K
Pinned Tweet
Bug bounties are broken and AI is about to make it obvious
So I built BounTEE for the NEAR hackathon. An AI agent found a bug, got paid in USDC and paused the affected contracts on Base and Arbitrum
No triage, no committee, no waiting
live on ⋈ @NEARProtocol mainnet
Feels like there’s a new hack every week right now, and AI agents are only getting better at finding bugs
If a whitehat finds one first they still have to write a report and wait for someone at the protocol to read it.
So I built BounTEE. You prove the exploit instead, a TEE replays it, and if it actually drains funds a contract on @NEARProtocol pays you and pauses the protocol on every chain the bounty covers #NEARHackathon
25
If a bug is on one chain, it’s probably on every chain that protocol deployed to
BounTEE ⋈ pauses all of them with one proof
When BounTEE proves an exploit, the contract asks NEAR’s MPC network to sign the pause for every chain the bounty covers.
Base and Arbitrum are the first two. It'd be cool to see contracts on @FlareNetworks next
Banknotez ☀️ retweeted
BREAKING: Uphold is authorized under the EU's MiCA Regulation 🚀
Uphold has been authorized by the Bank of Portugal as a Crypto-Asset Service Provider, through our subsidiary, Uphold Digital Assets Europe Unipessoal, Lda.
The license allows Uphold to fully operate its enterprise, @TopperbyUphold and retail businesses across Europe.
More to come 👀
Anyone can say they found a bug. So what stops someone from lying their way to getting paid?
BounTEE ⋈ skips the report and replays the attack instead
Left is a fake claim we sent BounTEE
Right is the real exploit from the same run
Both get the exact same treatment. A trusted execution environment runs each attack on a recent copy of the chain, and the only thing that counts is whether funds actually come out of the covered contract
Real one: the AI agent got paid USDC and the contract got paused on Base and Arbitrum
Fake one: no exploit proven, no payout, no pause
1
7
146
Check the run yourself, every transaction is linked: bountee.dev
Live on ⋈ @NEARProtocol mainnet, built for the #NEARhackathon
1
1
36
Great question let me dive into the answer a bit:
Everything in engineering is a tradeoff. A false positive that briefly freezes withdrawals sucks, but it sucks a lot less than the alternative (the contracts getting drained while someone assesses the bug report)
With BounTEE the thing that triggers the pause isn’t the agent’s report. It’s the exploit being replayed inside the TEE against the latest state of the chain
If that replay shows real theft past the threshold amount the protocol set on the bounty, it pays out to the white hat and pauses the affected contracts
Replying to @itzbanknotez @NEARProtocol
An agent that can pause contracts with no committee cuts both ways. What proves the bug before the pause fires: an exploit replayed inside the TEE, or the agent's report?
A false positive that freezes withdrawals costs users too.
1
4
236
5️⃣ 𝙒𝙝𝙖𝙩 𝙮𝙤𝙪 𝙨𝙩𝙞𝙡𝙡 𝙩𝙧𝙪𝙨𝙩
OutLayer, to run the judge inside a secure enclave and keep exploits sealed until payout
NEAR's MPC network, to sign pauses only for the bounty contract
1
43
6️⃣ 𝘾𝙝𝙚𝙘𝙠 𝙞𝙩 𝙮𝙤𝙪𝙧𝙨𝙚𝙡𝙛
Every step is a mainnet transaction, linked on the site
github.com/Vasqq/BounTEE
bountee.dev
Built for the NEAR hackathon
@NEARProtocol @NearBuilders #NEARHackathon
46
Been building on @NEARProtocol for the hackathon this week, and coming from Flare the overlap is kind of wild
@FlareNetworks is fleshing out protocol managed wallets and NEAR has chain signatures
Both basically let a smart contract on one chain act on another chain without a bridge and without a single entity holding the keys
For my build, that means when someone proves an exploit, my contract on NEAR pauses the vulnerable contracts on Base and Arbitrum automatically
I’d never built anything cross-chain like this before so it’s eye opening. It’s already given me a bunch of ideas for what I want to build with protocol managed wallets once they go live on Flare
A bounty on NEAR pausing a contract on another chain is a small example, but it’s the bigger picture that gets me
Blockchains have mostly been isolated islands, each doing their own thing. Once chains can act on each other directly, my bet is transaction volume goes somewhere we’ve never seen before, and imo that’s good for all of crypto
AI agents are getting insanely good
Good enough that every protocol should assume its bugs will get found
No protocol gets to opt out of that, but you do control what happens when one finds your bug
I spent the @NearBuilders hackathon building for that on @NEARProtocol mainnet
My agent proved an exploit, a NEAR contract paid it 10 USDC, and NEAR's MPC network signed pauses that landed on Base and Arbitrum One and nobody had to approve a thing
███████▒▒▒ 70%
An afternoon of finishing touches
tbh, especially with AI, spending an exorbitant amount of time on the requirements before the first line of code is the only reason a few dedicated days got me this far
Site drops tomorrow
#NEARHackathon @NEARProtocol @NearBuilders
3
7
290
Coming from safety-critical work, the first question I ask about any system is what happens when it’s wrong
For my project on @NEARProtocol, the answer is one column on the landing page:
the worst a wrong verdict can do is pause the contracts covered by the protocol im building
It can’t move anyone’s funds and it can’t unpause anything.
4
133







