robbsbro retweeted
BLEEEP Social Activation is Live ✨
Meet @bleeep_xyz, the verifiable trading ecosystem built around Proof of Provenance.
→ Follow BLEEEP on X
→ Complete the activation
→ Enter the $500 USDC raffle
Bleep it → superboard.xyz/campaigns/ble…
robbsbro retweeted
RNT Protocol Social Quest is live! ✨
@rntprotocol, the onchain stack that turns tokenized real estate into liquid capital.
🔓 Hold 500 SUPR Points to unlock
🔔 Follow RNT Protocol on X
✅ Complete social tasks
🎁 Enter the $200 USDC raffle
Join → superboard.xyz/quests/rnt-pr…
robbsbro retweeted
Vex Social Activation Is Live ⚡
Vex, a self-custodial desktop crypto agent that researches markets, quotes swaps, and executes onchain actions.
🔗 Follow @ProjectVEXai on X
🕊️ Complete the social tasks
💰 Enter the $500 USDC raffle
Join → superboard.xyz/campaigns/vex…
DEAR CRYPTO, LETS SHOW THE WORLD WHAT WE ARE MADE OF. DONATE NOW.
The Nepal floods have been devastating, 5,083 people are still missing but the search is still on, and it needs your help. This morning, two workers were pulled out of a hydropower tunnel after nine days underground.
Imagine being their family yesterday, and now imagine being one of the thousands of families tonight who are still waiting.
Every drop counts, and you can help directly.
Nepalrelief.org
Now let me get a bit more personal, I wrote this in my journal last week:
“My country was ravaged by what can only be described as an apocalyptic flood meets earthquake meets tsunami. It feels very strange being so far from home. It’s hard to think of anything that can even compare in the slightest to what those who perished or witnessed the floods felt; because for that, there is NO precedent, there are no previous videos of such things happening, there are almost no warning signs. It just happened, on a quiet morning, suddenly gargantuan waves filled with tons of debris moving at 200mph overtook entire villages, toppled entire buildings..and, well you’ve seen the footage.
And all I can think of is WTF are we doing? My industry speaks of millions and billions in revenue and hundreds of thousands in paper profits; but the beauty of all of that is that it is powered by a global financial network; one that literally just works and can genuinely help the world.
I’m also sat here thinking who the FUCK cares about all the bullshit we argue about everyday?
Solana donated 160k through a channel made by Polygon, and it just worked. Chains battling pseudo religious battles while thousands have been entirely displaced feels so inconsequential.
We ask which chain will win, but we never ask what will the world win if one does? We conveniently say we are boosting economic freedom but what about when it matters most? Why not reframe progress from real world outcomes instead of charts? Why not become the #1 vessel for relief on any calamity in the world? Why are we simply optimizing to please tech narratives? What about impact we can give to the world TODAY?
We have everything it takes, we just need to do it.”
Well, this is an attempted answer to most of those questions:
Nepalrelief.org
Special thanks to @sandeepnailwal, @Mudit__Gupta, @Ronak0010, @DianaChimes, @vibhu, and countless others who have spent nights and weekends to help Nepal.
And a major h/t to @0xPolygon
robbsbro retweeted
Today we're launching a crypto campaign to support the people of Nepal and contribute to the Government of Nepal's Prime Minister Disaster Relief Fund.
To help, donate at NepalRelief.org.
Stablecoins work best when money has to move fast to people who need it. While many others collected donations for Nepal in a more traditional sense, we built a path that leverages blockchain technology that lands as local currency in the government's relief fund.
The campaign is powered by Polygon's Open Money Stack, Coinme, and @CrossRiverBank. Blockchain for Impact has already pledged $100,000.
No one's pain matters more because of geography. But some tragedies just hit differently when they touch a place that's part of your own story, and Nepal has always felt close to home for me.
I was born in the Kumaon belt of Uttarakhand, India, right alongside Nepal, and my maternal family comes from that same region. Communities on both sides of the border have been connected for generations, through family, culture, faith, food, trade and everyday life. India and Nepal have what we often call "Roti-Beti ka rishta," ties of family and shared life that run far deeper than a line on a map, and Prime Minister Modi, speaking recently about Nepal, called its people our brothers and sisters.
I want to do my small part to stand with them, and I hope you'll join me. This campaign lets people around the world contribute in stablecoins to support relief and rebuilding efforts in Nepal.
robbsbro retweeted
Introducing LI.FI Intents.
Infrastructure for apps, wallets, and neobanks to:
• Enable stablecoin payments
• Access real-world assets
• Tap into compliant onchain liquidity
Built for enterprises bringing financial products onchain.
robbsbro retweeted
$2,500 rewards on offer
LI.FI Intents is live on Jumper, and you can win a share of $2,500 in @USDC + guaranteed 25 Jumper XP.
To enter the raffle
1. Move $250 in USDC from Base to @arbitrum
2. Use @lifiprotocol Intents route
3. Complete mission tasks
Participate here: jumper.xyz/missions/lifi-int…
robbsbro retweeted
Tether froze 3.29M USDT to the hackers.
Tether cares.
#CertiKInsight 🚨
We have seen an incident affecting @rhea_finance
The attacker created fake token contracts and added liquidity in fresh pools, likely misleading the oracle and validation layer.
In total, at least ~$7.6M was extracted
nearblocks.io/address/31ac7a…
robbsbro retweeted
me watching a woman who joined web3 a month ago promoting scams and act like she runs CT
robbsbro retweeted
Now, the quantum resistance roadmap.
Today, four things in Ethereum are quantum-vulnerable:
* consensus-layer BLS signatures
* data availability (KZG commitments+proofs)
* EOA signatures (ECDSA)
* Application-layer ZK proofs (KZG or groth16)
We can tackle these step by step:
## Consensus-layer signatures
Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation.
Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation.
One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are:
* Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in
* Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower)
* BLAKE3 or similar (take the most efficient conventional hash we know)
## Data availability
Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems:
1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world.
2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection.
Summary: it's manageable, but there's a lot of engineering work to do.
## EOA signatures
Here, the answer is clear: we add native AA (see eips.ethereum.org/EIPS/eip-8… ), so that we get first-class accounts that can use any signature algorithm.
However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify.
We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify.
We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower.
The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero.
## Proofs
Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs.
The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is.
In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block).
This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct.
Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this:
ethresear.ch/t/recursive-sta…
firefly.social/post/farcaste…
1/ Meet @WheresBroox (Broox Bauer), one of the multiple @AxiomExchange employees allegedly abusing the lack of access controls for internal tools to lookup sensitive user details to insider trade by tracking private wallet activity since early 2025.
Woof woof 🐾🐶 I'm Woofulisted for @woofulove Free Mint on Abstract Chain!
Tiny paws leave permanent prints 🐾🐶🐾
#Woofu #AbstractChain
1
29
robbsbro retweeted
Woof woof 🐾
Cutest puppies about to woof woof on @AbstractChain
Fully FREE Mint on @opensea
Get your Woofulist → woofu.xyz
Only for 48hrs (WoofLuck) 🐶






























