Sens. Susan Collins, Lisa Murkowski, Thom Tillis, and Mitch McConnell voted against Sen. John Kennedy's amendment to add SAVE America Act provisions—requiring proof of U.S. citizenship for federal voter registration and photo ID for ballots—to a budget reconciliation package. The measure failed 48-50, stalling the House-passed bill amid filibuster hurdles and concerns over Senate rules like the Byrd rule. Trump allies expressed outrage, accusing leadership of betrayal, while moderates worried about unlimited Democratic amendments; Democrats called it unnecessary voter suppression. It's funny they want to blame Republicans and point out the 4 when in all this here, what I am posting is what your DEMORATS are about. Yes, nearly every Democrat in Congress has consistently voted against the SAVE America Act (and the similar SAVE Act) in its various forms.
I published a premium subscription write-up.✍
It includes a 27-minute voiceover I recorded.🎙️
Bottom Formation Signals Flashing
- Technical Indicators and On-Chain Historical Signals, Coins that Have Institutional & Value Demand.
blockchainbacker.substack.com/p/bottom-forma…
🚨 WOW! President Trump reads 2 Chronicles 7:11–22 as part of the America Reads the Bible event
Incredible 🙏🏻
"And as for you, if you will walk before me as David your father walked, and do according to all that I have commanded you, and shall observe my statutes and my judgments, then will I establish the throne of my kingdom according to as I have covenanted with David your father, saying there shall not fail you as a man to be ruler in Israel."
"But if you turn away and forsake my statutes and my commandments which I have set before you and shall go and serve other gods and worship them, then will I pluck them up from the roots out of my land which I have given them, and this house which I have sanctified for my name will I cast out of my sight and will make it to be a proverb and a byword among nations."
"And this house which is high shall be an astonishment to every one that passes by it, so that he shall say, why has the Lord done thus to this land and to this house?"
"And it shall be answered, because they forsook the Lord God of their fathers which brought them forth out of the land of Egypt and laid hold on other gods and worshiped them and served them, therefore has he brought all this evil upon them."
As with all the scaremongering in defense of financial surveillance, the root of this problem goes deeper.
Why make this about KYC and privacy instead of addressing broader systemic problems with campaign finance?
The UK is planning to ban crypto donations to politicians, due to no sender KYC.
They understand that payments are political, and they want to limit the markets ability to make decisions.
Encrypted private payments are a must for the free world.
assets.publishing.service.gov.uk/media/69c29f84…
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…
🚨 @SecRollins is launching the National Proving Grounds Network for AgTech — a bold new initiative that puts American farmers and ranchers FIRST!
Together with Chairman @SenJohnHoeven, @USDAScience Under Secretary Scott Hutchins, and our partners at @TheGrandFarm in North Dakota, we’re rigorously testing precision ag tools under real farming conditions.
This means cutting input costs, reducing risk, boosting productivity, and giving producers trusted data they can actually use.
Innovation + American farmers = the future of agriculture. Farmers come first!
🔗 usda.gov/agtech
An insider is claiming that GTA 6's user-generated content will "produce millionaires"
"When it does come, especially on PC, if you thought GTA 5 was crazy, especially with the RP servers, you haven’t seen nothing yet"
9 Followers 39 FollowingExploring the world of crypto, one blockchain at a time. Passionate about decentralization, innovation, and the future of finance. #defi #crypto #web3
1.1M Followers 2K FollowingLeadership on #food, #agriculture, natural resources, #rural development, #nutrition, & related issues based on public policy, science, & effective management.
6.2M Followers 2K FollowingBest-Selling Author | Clinical Psychologist | #1 Education Podcast | Co-founder of @petersonacademy | Order my new book "We Who Wrestle With God" here:
153K Followers 18 FollowingA first-of-its-kind effort to rapidly advance human spaceflight capabilities while continuing to raise funds & awareness for important causes on Earth
5.0M Followers 4 FollowingOpenAI’s mission is to ensure that artificial general intelligence benefits all of humanity. We’re hiring: https://t.co/dJGr6LgzPA
1.2M Followers 558 FollowingTrump-Endorsed Republican for Governor of Florida, Congressman, Husband, Father, and Follower of Christ Proudly Serving SWFL. Official Account: @RepDonaldsPress
90K Followers 55 FollowingOfficial account of the Modern War Institute at West Point, a research center dedicated to the study of war and warfare.
Gov't Org
Follow & Likes ≠ Endorsement
83K Followers 1K Following#Bitcoin since 2016. Holding world record for buying 10,000 pizza with 1 #Bitcoin on 22 May 2023. YouTuber. Trader. link👇 https://t.co/oMZJsGiyUz