Privacy you can verify. For any chain, any application, any builder.
Joined July 2019
- Tweets 9,271
- Following 667
- Followers 284,928
- Likes 6,924
2,248 Photos and videos
Privacy isn't a feature. It's an absence. The thing you don't see. The leak that didn't happen. The data that didn't move. Nothing to look at. Working as designed.
4
14
74
1,838
Jun 12
The pull request you didn't get to today will still be there Monday. Go outside.
7
9
68
2,256
Jun 11
1/ Public mempools were always a tradeoff. The argument was 'anyone can audit, anyone can build, transparency is the feature.' That's true for the network. It's not true for the user. Every order, every liquidation, every rebalance sits in the open before it executes. Predators know what you're going to do before you do it.
4
12
103
2,294
Jun 11
2/ The cost shows up in price. MEV is the visible number, well over a billion dollars extracted per year and rising. The invisible number is bigger: every institutional desk that looked at onchain execution, saw the mempool, and decided to keep size offchain. Public mempool is the single biggest reason serious capital hasn't moved.
2
1
41
1,565
Jun 11
3/ Confidential mempools, intent privacy, and end-to-end encrypted execution paths are the fix. Sapphire and ROFL together give you flow where the intent never broadcasts, the routing happens in confidential compute, and the settlement is the only public step. DeFi catches up with TradFi execution quality the moment that stack ships at scale. We're at that moment.
3
35
1,301
Jun 10
1/ Most people's AI context is a mess. Notes in one tool. Highlights in another. Conversations across three chat interfaces that don't talk to each other. Every new session starts over. @PluralityWeb3 built AI Context Flow to fix this: one place to hold your context, carried into any tool, any agent, any website.
5
23
123
2,721
Jun 10
2/ The harder problem isn't portability. It's where that context lives in motion. AI infrastructure runs on Model Context Protocol (MCP), and the operator running the MCP server sees everything flowing through it. Plurality runs theirs on ROFL, inside a TEE. The operator can't read the context in memory. Remote attestation proves what code is running.
1
4
41
1,609
Jun 10
3/ Next up: a context marketplace. Domain experts package years of curated knowledge into context packs that anyone can inject into any AI tool. A broker that brokers without seeing what's being brokered. The kind of product that doesn't exist without confidential infrastructure underneath. @PluralityWeb3
1
5
45
1,394
Jun 9
1/ "IP" | Intent Privacy
Every transaction on a public chain leaks two things before it executes: what you want to do, and how much you want it. An intent (a swap, a borrow, a trade) sits in the public mempool from the moment you sign. Searchers, MEV bots, and competing traders all see it. The price you get is shaped by the fact that they saw it first.
2
22
122
3,086
Jun 9
2/ Intent privacy routes the intent through an encrypted path instead. The user signs. The intent enters a confidential environment, gets matched, routed, or executed. Only the final state lands onchain. Nobody sees the order in flight.
1
3
44
1,589
Jun 9
3/ Private trading depends on this. Smart yield depends on this. Any DeFi product serious enough that an institution would route flow through it depends on this. Sapphire and ROFL give you confidential intent flow end to end. It's the gating primitive for the next generation of onchain finance.
5
44
1,494
Jun 8
This week: a Decoded on intent privacy, a surprise ecosystem thread, a Thursday read on what public mempools have cost DeFi, and the Critรฉrium du Dauphinรฉ final weekend.
10
16
112
4,273
Jun 8
Monday๐ฅฑ
Imagine if every Venmo you sent was broadcast to your coworkers.
That's most of DeFi today. We're working on it.
8
9
78
2,591
Jun 7
Sunday on Oasis๐น
Quietly building.
Mainnet up and running for almost six years.
Same job tomorrow.
4
17
131
3,772
Jun 5
"Friday.
Five days of pretending we have life-work balance.
Two days of pretending the laptop doesn't exist.
Both work. See you Monday."
17
12
102
3,864
Jun 4
"Three years ago: ""we promise we won't train on your data.""
Today: ""we cannot train on your data because the cryptography prevents it.""
The first is a policy. The second is infrastructure.
Guess which one will be standard in 2030."
21
24
148
6,411
Jun 3
1/ A tokenized T-Bill is a great product. A tokenized T-Bill on a public ledger is a broadcast of who holds what, how much, and when they moved it. That's not how institutions buy treasuries today, and it's not how they'll buy them onchain either.
9
19
111
4,559
Jun 3
2/ The fix isn't fewer onchain RWAs. It's confidential settlement underneath them. Verifiable that the asset exists, verifiable that you own it, private about the position itself. That's the bridge.
1
6
42
2,786
Jun 3
3/ @MidasRWA is building exactly that bridge. Tokenized institutional yield, with the privacy posture the buyer-side actually requires. $50M Series A in March, proud to be backing the team.
5
41
2,562