robbsbro

Web3 Explorer | 🇳🇵

[LI.FI @lifiprotocol]

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.

[Jumper Pass @jumperpass]

$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: https://t.co/4YDvbFTi9h

[robbsbro @robbsbro369]

@Samir86201620 @JobFound5 hait hero tw eta po busy ho aajkal

[robbsbro @robbsbro369]

@Samir86201620 @_Auza_ @KyberNetwork @SafePal me too bro

[robbsbro @robbsbro369]

@Samir86201620 @JobFound5 eklai eklai

[robbsbro @robbsbro369]

@Samir86201620 @hrithikk @GracyBitget @_RichardTeng hait hero

[Paolo Ardoino 🤖 @paoloardoino]

Tether froze 3.29M USDT to the hackers.
Tether cares.

[robbsbro @robbsbro369]

@Rijan39413165 @SwarnimWagle hero remittance ma cut vako paisa government lai haina ra jani ??

[hrithik ( 히리틱 ) @hrithikk]

me watching a woman who joined web3 a month ago promoting scams and act like she runs CT

[Starknet (Privacy Arc) @Starknet]

1/ The STRK20s Technical Paper is now live.

It outlines the design, architecture, and core ideas behind STRK20s, a privacy capability for any ERC-20.

If you’re bullish on privacy as crypto’s next major unlock, this paper is for you 🧵

[Handout @Zeefire02]

😭😭

[naiive @naiivememe]

losing money in crypto : omg f*ck my life

losing money in crypto with bros :

[vitalik.eth @VitalikButerin]

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 https://t.co/YD9nIpsxcC ), 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:

https://t.co/rAUSJjW7WL
https://t.co/EtXpkaDll5

[ZachXBT @zachxbt]

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.

[sgp @stogolp]

i fucking knew my portfolio wasn't down 90% because I'm a bad trader, it was Jane Street stopping me from winning

[robbsbro @robbsbro369]

Woof woof 🐾🐶 I'm Woofulisted for @woofulove Free Mint on Abstract Chain!

Tiny paws leave permanent prints 🐾🐶🐾

#Woofu #AbstractChain

[Woofu @Woofulove]

Woof woof 🐾

Cutest puppies about to woof woof on @AbstractChain

Fully FREE Mint on @opensea

Get your Woofulist → https://t.co/hb929m8473

Only for 48hrs (WoofLuck) 🐶

[robbsbro @robbsbro369]

@Woofulove @AbstractChain @opensea woof woof
0xe88d2D7e13a71eA68A438b9FEdD6363bE48A0373

[ZachXBT @zachxbt]

NEW: Major investigation dropping February 26 on one of crypto’s most profitable businesses where multiple employees abused internal data to insider trade over a prolonged period of time.

[robbsbro @robbsbro369]

@roshan_546 k chaldae xa yaha ?