@eth_skillz | Independent Ethereum coverage & commentary
Ethereum
Joined May 2021
- Tweets30.9K
- Following216
- Followers7.3K
- Likes82.9K
This is a very cool product that can actually help real world people save better, while slowly building wealth using stable assets.
Bullish on real-world use cases for crypto.
liam retweeted
Introducing Earn+: 12% rewards on your dollars in a single tap.
Available now for Pro and VIP users and rolling out to all Ethena Pay users in the coming days.
liam retweeted
New EIP!
EIP-8450: Post-Quantum Validator Key Registry (leanXMSS + VRF root)
🔗 github.com/ethereum/EIPs/pul…
Highlights:
- Each validator registers two post-quantum commitments in beacon state: a leanXMSS public key for future signing and a 32-byte VRF-tree root to commit to non-grindable random outputs.
- Registration is a new consensus-layer operation (no execution-layer request path): it includes a proof-of-possession signed with leanXMSS at leaf index 0 and is authorized by a BLS signature from the validator’s current pubkey.
- To prevent replay and throttle changes, each validator has a stored last-change epoch; the registration includes the previous_change_epoch and key changes are rate-limited by MIN_PQ_KEY_CHANGE_DELAY (default 256 epochs; smaller in minimal preset).
- Uniqueness is enforced for the leanXMSS key across validators (so validators can’t share/copy signing keys), but VRF roots are allowed to collide (two validators may commit to identical VRF trees).
- The registry is ‘dormant’ in this fork (duties still use BLS); its purpose is readiness measurement and early verification/testing of post-quantum primitives defined externally in EIP-CRYPTO.
ELI5:
Ethereum validators currently use BLS signatures, which quantum computers could break. This EIP adds a new “phonebook” in the beacon chain state where each validator can pre-register post-quantum cryptographic material ahead of a later upgrade. Each validator stores (1) a hash-based leanXMSS public key for future signatures, and (2) a Merkle-root commitment to a huge VRF tree that pre-fixes one random-looking output per index so validators can’t ‘game’ randomness-based selections later. Validators prove they really control the leanXMSS key (proof of possession) and authorize updates with their existing BLS key; the new keys are recorded now but not used for duties until a future fork.
liam retweeted
Today, more people are backing Ethlabs.
Ethereum co-founder @MihaiAlisie joins as an anchor funder, @payward and @gattacahq join as contributors, and 19 new supporters from the Ethereum community are now backing our mission.
Thousands of people across the world have spent years building Ethereum and holding $ETH, we aim to honor their commitment by becoming an open, accessible, and user-focused organization that supports the development of both this unstoppable network and its immutable asset.
We care deeply about what makes Ethereum special: its credible neutrality, security, censorship resistance and openness. We also believe that Ethereum's potential is only realized when people use it at scale and when it remains the natural place to innovate, issue assets, hold + settle value, and be the home to a digital future its users can own.
A big thank you to our initial anchor funders @BitMNR, @Sharplink, and @ethereumJoseph; to everyone joining us today, to the countless people and organizations that make Ethereum possible, and to all who have supported our work so far.
There is an enormous amount left to do, and we are fortunate to have so many people who believe that it is worth doing.
Now back to work.
Funders: ethlabs.org/funding
Weekly updates: ethlabs.org/writings
The @polarisfnd protocol uses an Adaptive Peg Defence mechanism to protect the value of USDp.
When USDp is trading above $1, anyone can buy at its $1 target and sell on the open market.
When trading below $1, redeem USDp at peg for the underlying collateral (pETH).
Stables usually have a strong defense on one side of the peg but also a weaker one on the other.
And it’s often minters who pay for this problem.
But with polaris assets, this will actually become a new source of yield for them.
USDp defends both sides directly because above $1 anyone can buy newly minted USDp at peg with pETH and sell it right away.
And below $1 anyone can redeem it at peg for pETH.
Arbitrageurs never even need to open or close a position, so no debt to manage and no liquidation risk.
For the people backing USDp with their pETH, nobody gets singled out anymore. Actually, keeping the peg will now become a new yield source.
Why is it, that in 2026, there are still so many people that don't understand "why" the Ethereum Foundation needs to sell ETH?
The EF's runway (the funds needed to continue developing the Ethereum protocol) is made of its ETH treasury, in which portions of the asset must be sold on various occasions in order to continue funding the Ethereum roadmap.
It is not frustrating that the EF sells ETH - it would be more frustrating if they didn't, and instead gave up on important (and desperately needed) initiatives such as Lean Ethereum and Quantum Resistance.
Not everything is about "making as much money as humanly possible." For some ecosystems, it's about building a technology platform that can improve peoples lives.
In all honesty, seeing the Ethereum Foundation sell $ETH again is incredibly frustrating.
I love Ethereum. I love the chain. But why are we constantly selling the asset instead of doing more to increase its value?
Start thinking seriously about buybacks. Create stronger incentives for L2s to accumulate and buy back $ETH. Improve ETH value capture.
The ecosystem is incredible. Now we need the economics of the token to reflect that.
While institutions may find themselves falling behind by not integrating some sort of onchain strategy, they will fall even further behind by not adopting ZK-based systems.
Ethereum and its L2s are leading the charge in the development of zero-knowledge technology.
Major financial institutions are taking a "crawl, walk, run" approach to digital assets.
Leaders like the NYSE and DTCC are starting small, but organizations that don’t embrace digital assets will be left far behind.
@gluk64, CEO of @the_matter_labs, tells @RemyBlaireNews.
liam retweeted
Last week, core devs had to delay forking the Hoodi testnet to Glamsterdam to study a report by @chain_security which revealed some problems with how EIP-8037 interacts with a few contracts.
Over the weekend, ppl tried to get a better picture of the impact and by now it's quite well understood. So here's what you need to know:
What's been known is that contracts which hardcode forwarded gas are affected by repricings, e.g. making state writes (SSTORE) more expensive.
What's new is that some coding patterns rely on specific invariant which were broken with EIP-8037.
Gas already spent can come back mid-tx, so gasleft() can go up. This causes two problems:
(1) a before / after gas counter underflows and reverts
(2) a failed sub-call hands gas back, so a path that should've been unreachable runs, and the tx looks like it succeeded
Related but different: (3) measuring the gas usage of a call using GAS - before and after the call - might undercount because the state gas reservoir is not visible during execution (e.g. gas_left).
It's now about deciding how to proceed. Delaying hoodi bought time but won't resolve the issue. This week, we have to dig deep into contracts and make sure nothing is missed. Eventually, this might just need some coordination among the involved parties (dapps, core devs, auditors, people running nodes, etc.), or worst-case, spec changes.
If you're an app dev or auditor, check your contracts for issues with EIP-8037/EIP-8038, and report them.
Also, share this with your favorite app dev to spread awareness.
⚠️ It has just been decided to delay the Glamsterdam hard fork on the Hoodi testnet because of security impacts we identified in this blog post: chainsecurity.com/blog/glams…
We already found 13 real-world examples and are in responsible disclosure with the affected projects.
Please check your contracts as soon as possible, as the EF is determining how many contracts are impacted in which way.
Feel free to reach out to us with questions via [email protected].
liam retweeted
What if @ethereum could verify ZK proofs itself, so rollups and apps wouldn't need to run their own verifiers?
This could be achieved through native proof verification.
And we've made some progress there over the past month: the draft for EIP-8357 was merged, and a native rollup is now running on a devnet 👇
liam retweeted
Proud that @polarisfnd will launch formally verified and immutable
In the age of AI having the math proven and without the ability to upgrade and break this is a huge safety feature
DeFi done right
liam retweeted
Glad to see core devs and researchers take any time that's needed to get glamsterdam ready. The next few years are going to be incredible for ethereum. We'll go postquantum, add native privacy for ETH, and massively increase L1 TPS and the blob target. All while L1+L2 hypergrow.
liam retweeted
This weekend we launched EthLib, a Lean4 library for Ethereum!
The goal is to bring Ethereum's primitives, specifications and theorems into one place, building a shared foundation for formally specifying and proving things about Ethereum.
github.com/ethereum/EthLib
liam retweeted
It’s best to think about these positions as pETH/pAsset LP positions in a way
The ratio of collateral and debt will continue to change due to peg buys and redemptions but you will continuously slurp fees and pETH incentives
Become a decentralised asset backer with Polaris
Negative debt will finally be a thing (yes you read that right).
Collateral-only positions will let you deposit pETH into any pAsset market with zero debt at the start.
From there, debt moves with the health of the whole market, fed by peg arbitrage fees and higher-leverage positions.
If it ends up below zero, the difference is minted straight to your wallet in the pAsset you chose.
You never borrow a thing, and you can still walk away with pAssets on top of your pETH.
liam retweeted
Polaris works a lot like an MMO (Massively Multiplayer Online for the non-nerds).
Everyone plays in the same world but everybody can play a different game.
If you prefer PvE, you swap ETH into pETH and hold it, and the floor grows while you get on with your day.
If you like to min-max, you loop fpETH without liquidation risks, so you push the build without the risk of losing it.
If you want PvP, you trade vpETH against people who read the pETH premium differently from you, long or short.
And if you want hardcore full loot, you deposit USDp in the Earn Pool and wait for the next liquidation to be collected.
Whatever you pick will grow back fees that flow into pETH in any case.
liam retweeted
Another day, another bridge 🫨
From my perspective these developments are mostly good, the market is pushing latency and costs down, and this is the result of clear demand for crosschain operations. The multi-chain world is undeniable.
On us to ensure that Ethereum's security and liquidity are the easiest, cheapest and fastest to export, so Ethereum users and assets reap the benefits of broader use cases and distribution.
Introducing the fastest crosschain swaps on the market. Crosschain transactions on @fomo now land in <1s.
A week ago, we rolled out our own internal bridge to a small % of users.
Public rollout of fomo bridge begins now.
liam retweeted
Core developers decided to delay the upcoming Hoodi hard fork on today's ACDE call.
Refer to this blog post for further details and be sure to watch for any client releases pertaining to your infrastructure on Hoodi.
blog.ethereum.org/2026/10/22…
