two days at @Ledger op3n: a run club, the offices, and a look inside the donjon, the lab where they try to break their own devices.

the line of the week: agents propose, humans decide, hardware enforces.

thank you @AntoineM_eth for a truly amazing experience
4
1
13
710
badge took 3rd at @Ledger op3n, out of 13 student teams. 1k$ prize 🥉
5
1
16
480
Replying to @frytegg
@Ledger code: github.com/ebenbaruk/badge
3-min demo: youtu.be/OVdxuhtCuYE

and a fix it surfaced in ledger's ethereum test client (filtered eip-712 crashed above chain id 255): github.com/LedgerHQ/app-e…
0
0
1
16
Replying to @frytegg
@Ledger next time it's a gate at idea stage: can a juror do the demo themselves, on stock hardware, on stage?

if you've demoed a hardware consent flow to a room that couldn't touch the device, what worked?
0
0
0
11
Replying to @frytegg
@Ledger badge, built with @elibenbaruk : company memory for ai agents. a colleague's notes reach your own agent only once they sign for it on their own ledger.

ledger sells agent security on payments. we put the same rule on context: the only podium project that moves no money.
0
0
2
32
token2049's own faq: 60%+ of its 25,000 attendees are c-level or founders.

i went as a student. four things got me further than the badge did 🧵
7
0
2
102
Replying to @frytegg
brume, code + 7-page paper: github.com/BuzzBallz/Brume
the long version: lnkd.in/p/ehmXNqKt
0
0
1
13
Replying to @frytegg
what the week was about: tokenization and agents.

x402 has settled ~$42m across 192m payments. 22 cents each on average, tests included.

the rails are ahead of the demand. so who's building the return counter?
0
0
1
9
Replying to @frytegg
4. keep iterating.

twice that week, the project that made a stranger lean in was orma, from september. not the one i'd just built.
0
0
1
8
Replying to @frytegg
3. go to the rooms where you feel out of place.

best advice of the week, on a rooftop full of suits: quantify the risk on the protocol. for an institution, every operation is a risk.

best conversation: a check-in queue at changi, on the way home.
0
0
1
11
Replying to @frytegg
2. believe the judges and sponsors.

day one, in writing: the use case isn't clear. we spent two days building a better answer. two hours finding a better question would have done more.
0
0
1
7
Replying to @frytegg
1. do the hackathon.

130 of 200 builders at origins went to the cardano track: ai agents that pay. masumi said it in august: everyone built the checkout, nobody built the return counter.

@0XAndrea_ and i built the return counter. we didn't place. x.com/frytegg/status…
built brume at @token2049 origins last week, cardano track.

the escrow that pays ai agents has a dispute branch. it works fine. it just needs an arbitrator, and that arbitrator hasn't signed anything since november 2025.

61 escrows are still sitting in it. ⬇️
0
0
2
47
so happy to have shipped this project alongside @elibenbaruk, whose work was impeccable

anyone who understands that context is the real currency in the agentic ai era will thrive in any project they build

Badge makes context sharing inside companies safe
🧑‍💻 Our @Ledger N3XT hackathon build is in !!

@elibenbaruk and @frytegg shipped Badge: each employee's Ledger becomes their company badge for AI agents.

No context leaves without its owner's signature.

#LedgerN3XTCollab
by @DeVinciBC
1
0
2
50
Replying to @frytegg
who owns your context in your company ?
0
0
0
10
built brume at @token2049 origins last week, cardano track.

the escrow that pays ai agents has a dispute branch. it works fine. it just needs an arbitrator, and that arbitrator hasn't signed anything since november 2025.

61 escrows are still sitting in it. ⬇️
4
0
0
68
Replying to @frytegg
@token2049 code, every transaction hash and a 7-page annex with the proofs:
github.com/BuzzBallz/Brume

built on @MasumiNetwork's vested_pay contract. mainnet numbers pinned to a census block in the repo. we didn't place.

if you know how to measure a front-run cleanly, i'm listening.
0
0
2
6
Replying to @frytegg
@token2049 what it doesn't do: pre-signing kills the refusal, not the race. once leg 1 lands the buyer can still broadcast a competing exit. we never got a clean window to measure that, so the solver prices it at worst case.
0
0
0
Replying to @frytegg
@token2049 so brume builds the exit that doesn't need one.

two transactions, signed before either is sent. the seller concedes, the buyer has already signed the split, so there is nothing left to refuse.

12 settlements on preprod, 24 legs, no admin key in any of them.
0
0
0
1
Replying to @frytegg
@token2049 the number that stopped me: across all 120 arbitrations that contract has ever seen, the seller side was paid in 0 of them.

not rarely. zero.
0
0
0
5
went to the @Ledger n3xt student gathering and conference, at SMU in Singapore.

always nice to see many student’s community thriving

can’t wait for this week Op3n here in paris, in the Ledger HQ

see you there 👀
1
1
6
73