MRT 💹🧲

@ClavicularNews bro mixed up peptides with pepsi

Clavicular meets his biggest supporter who donated him over 2000 subs ($10,000) on Kick 😳

loooooooool I am trying to picture how ridiculous this guy's average day must be Goes out, nobody wears masks, society functions perfectly, nothing particular going on in hospitals or anything, bro is like: "they all live in a lie without knowing the full dangers of covid "

He had the gift clairvoyance

you are trading against people shocked at a hand having 5 fingers and wondering if markets are efficient

@RobKPF @varrock Shoplifters, muggers, rapists and vandals belong in prison or back to their shithole country where that’s normal

@varrock This is king mentality, telling people where they should be. Nobody should have this authority.

Third world immigrants are fundamentally incompatible with a trust-based society, and will never assimilate

@disclosetv Is everyone on this app becoming retarded?

NOW - Israel's Netanyahu: "I'm dying for coffee... here, you wanna count my fingers?"

@Rasterblath @SpeechUncut

@SpeechUncut “What if we made gameplay feel like you were on an ice rink. Yes” “What if we stole ideas from PC shooters but pretended shooters didn’t exist before us. Yes.” “What if we spent the next two decades living off the rep of the most overrated game in history. Yes.”

This is true.

@Gamafram @Radikal828 Preveč estrogena pri tranziciji?

@Radikal828 Indijci dobrodosli, vsi Naziji pa lahko spizdite.

Ljubljana New Delhi

@JesseSisson2 @EYakoby bro is a flying carpet denier

@EYakoby Your video is fake; it even says it was made with AI

BREAKING: Iran shoots down an F-15 with a man on a flying carpet.

@RealJessica can guarantee you these people have no idea how short of a life they will live

Woman shows her “coffee of the day”. That “coffee” alone exceeds the amount of calories that should be consumed in an entire day. This same lady used to make her “water of the way” and it was just straight packets of flavoring powder and sweet syrups. 🤮🤮 At a certain point, it is no longer coffee. You can’t claim to be a coffee lover while drinking terrible instant coffee and covering up the taste with sugar. Follow: @RealJessica

@GoodAmericanMan was already unfuckable before the haircut

Foids are committing stolen Norwood valor now

Oi bruv, you got a non-terrorism loicense for that meme or what?

@B1TuckerCarlson @EndWokeness n

Iryna murals keep getting vandalized Her crime? Being white

So all crypto needed was just total Israeli dominance over the middle east?

BREAKING sources saying Samir Heidari AKA "The Ghost of Tehran" has shot down over 73 American Pig F-22s and sunk the USS Gerald Ford

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-8141 ), 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-st… firefly.social/post/farcaster…

@yo_jaydee LMFAO

ready for #worldofwarcraft #Midnight

@zoecabina When the narrative doesn't fit and they have to transform you into a fictional female that never existed

Hating Jews