Really interesting interview with @eastdakota on @Bankless.
Cloudflare accounts for over 20% of internet traffic. That's 500M transactions per second. It can monetize 1–10% of that traffic (with x402), so it needs 5–50M transactions per second from a blockchain.
I'm a researcher at an L1 blockchain startup that can reach these levels.
Let's change the internet!
1/6
“It’s not about money moving faster. It’s about money moving all the time.”
That line, and the stablecoin sandwich, stay with me at yesterday’s @EBlockchainCon in Barcelona.
(Lovely, quiet pond at the venue.)
1
1
35
Thanks to @jevgenijs (@tempo), @0xceaneCodjia (@coinbase), Angel Gomez (@utila_io), and @MarkZalan_ (@GoMining) for the discussion.
And to Sascha Dobratz (@DanskeBank_DK) for being a great moderator.
1
50
5/5
Respect to the Hugging Face team, and thanks to the whole ZipNN team!
𝗥𝗲𝗽𝗼: github.com/zipnn/zipnn
𝗣𝗮𝗽𝗲𝗿: arxiv.org/abs/2411.05239
HF post: huggingface.co/blog/from-chu…
Expand the replies at the bottom to see the discussion.
23
Data will be queried for agents, not for humans.
SQL was created 50 years ago and it’s still great for human use.
I wonder if this will still be the case in 10 years for agent-native databases (agentDB).
I’m not talking about similarity search. I’m talking about direct data retrieval. SQL works great today.
Right now agents access data through SQL or through apps that use SQL under the hood.
I believe that in a few years a new paradigm built for agents will start replacing SQL.
Why?
Because AI agents are not humans. Their requirements are different. They can work directly on raw data without the SQL layer in between, which means faster queries and lower latency.
This makes me wonder: What kind of metadata will these systems need, and what will they actually look like?
I’ve seen some startups working on this, but I haven’t seen a real killer solution yet.
What do you think? Should we build a new data paradigm for agents?
#AIAgents #AI #Databases #SQL #AgenticAI
2
106
The "Where" Matters: TEE Deployment Environments:
Even with top hardware (SGX/TDX), security depends on where that box lives.
For privacy-focused TEEs: Breach leaks data, but protocol integrity holds (no double-spends).
The "Hostility Levels" define your risk. 👇
1/ Bank Vault (Safest) 🏦
- Env: Trusted clouds (AWS/GCP/Azure) or foundations.
- Pro monitoring & compliance.
- Risk: Side-channels minimized by layers of physical security.
2/ Train Station (Less Safe) 🚉
- Env: Decentralized validators.
- Accessible, mixed motives.
- Risk: Software probes likely (timing/cache via OS exploits). Assume side-channel threats.
3/ Gargamel’s Castle (Hostile) 🏰🧪
- Env: Malicious nodes or state hackers (e.g., Lazarus).
- Attacker owns the hardware.
- Risk: Physical/supply-chain tampering, TEE breach inevitable.
- Avoid or Pivot to MPC or ZK-proofs. If you are building for this scenario, hardware is just the first line of defense.
Bottom Line: A TEE is a "safe." But one in a bank vault >> one in a villain's dungeon.
#Web3 #Privacy #ConfidentialComputing #TEE #Blockchain
1
3
375
Moshik retweeted
The world is changing, FAST.
Software is going to be fast and cheap to create.
Agent are going to be prevalent.
Value will accrue at the platforms that capture the network effect where interactions happen.
Blockchains are perfect platforms for this new world. Even critical.
But dramatic improvement are still needed for blockchain to play that roll.
Privacy, compliance, scale, scale, scale….
Ben Horowitz explains why AI killed the 'Mythical Man Month':
"For my whole life in technology, there was this thing called the Mythical Man Month: nine women cannot have a baby in a month."
"If you're Google, you can't just put a thousand software engineers on a product and wipe out a startup because you can only... build that product with seven or eight people. Once they've figured it out, they've got that lead."
"That's not true with AI. If you have data and you have enough GPUs, you can solve almost any problem. It is magic."
"You can throw money at the problem. We've never had that in tech."
@bhorowitz with @DavidSolomon and @dhaber
Amazing!
NeurIPS 2025 accepted papers with over 100 AI-hallucinated citations across at least 53 of them!
We must change the review process: too many hallucinations and too many papers.
NeurIPS had more than 21K submissions!
A quick must-have: Add an AI reviewer to catch this and handle the burden.
fortune.com/2026/01/21/neuri…
#NeurIPS #Academia #MachineLearning
83
Interesting podcast of @YuvalRooz at Bankless
One takeaway: Privacy Vs. Anonymity
Privacy: Your data stays private; you control who sees it via contracts. But in extreme cases (e.g., court subpoena), it can be shared.
Anonymity: No data revealed, ever.
This setup lets regulated finance run on-chain.
I lean toward the privacy side. balances freedom with accountability.
What do you think?
[Podcast link: bankless.com/podcast/is-cant…]
#Crypto #privacy #Bankless #RWA
1
10
478






