@OriginProtocol I spent most of last year working on merkle proofs of beacon chain data for Origin's OETH LST.
It's so pleasing to see that the different proofs are now working on mainnet. 🚀
English
Nick Addison
2.1K posts
Nick Addison
@naddison
Ethereum, Solidity | Developer at @OriginProtocol | Author of sol2uml and tx2uml
Sydney Katılım Mart 2009
1.4K Takip Edilen2.4K Takipçiler
OETH is the among first LSTs to use Merkle proofs to verify staked ETH balances.
This upgrade introduces new compounding validators, front-run protection, and partial withdrawals for quicker beacon chain exits.
Here's what to expect ↓
English
@metrokatz @zxstim @KyberNetwork @PocketUniverseZ You don't disclose that the "small" fee is 80 basis points (0.8%). Why?
English
We’ve received reports that the @PocketUniverseZ browser extension has added an extra fee to swaps made through KyberSwap.com. If you see an unexpected platform or swap fee, please note that it is not charged by KyberSwap. KYBERSWAP DOES NOT CHARGE ANY FLAT FEE FOR SWAPPING ON OUR UI.
Please double-check your browser extensions and only use trusted tools when trading. We are also working on preventing extensions from modifying our API parameters and adding warnings in our UI to help users identify this situation.
English
English
@naddison @zxstim @KyberNetwork @PocketUniverseZ Wrong. The fee is shown in every PU pop-up before the transaction is sent to the wallet. It funds up to $30k in coverage per transaction for the user. Disclosed on X, in Discord, inside the extension, and in our ToS before it ever went live nearly 2 years ago.
English
@zxstim @KyberNetwork @PocketUniverseZ The don't disclose what the fee actually is. 80 basis points on all swaps is a not a "small" fee.
English
Uninstall the Pocket Universe browser extension.
The "small" fee is 80 basis points on swaps :-(
English
It's been a good week for the Origin ARMs. They tend to do well when crypto prices are falling.
Origin Protocol@OriginProtocol
Origin’s ARM helps support LST stability during market volatility. ➡️ $stETH ARM: 7.6% APY ➡️ $eETH ARM: 7.4% APY When markets get choppy, the ARM captures price dislocations through arbitrage, generating elevated ETH yield while reinforcing LST pegs across secondary markets.
English
sol2uml now shows what functions are called on contract dependencies.
The latest release also contains bug fixes and performance improvements.
@claudeai did all the code changes and testing
English
Nick Addison retweetledi
The $OETH staking upgrade has passed governance and is now deployed.
This marks the start of OETH’s transition to Merkle Proof–based validation: a major step toward fully trustless Ethereum staking.
Validator migration begins this month 🧵 (1/2)
English
This makes me happy as a smart contract developer.
Thanks @NethermindSec, @sigp_io and @OpenZeppelin for their security audits.
The new staking strategy that uses merkle proofs of beacon chain data is now in the governance pipes.
English
Nick Addison retweetledi
Hardhat 3 is now in beta, and ready for production use!
Hardhat 3 is a complete overhaul. We introduced Solidity tests, rewrote the performance critical components in Rust, added multichain support across the board, implemented OP Stack simulation, revamped the build system, modernized our TS CLI and plugin system, and a lot more.
🧵
English
English
@naddison @danrobinson @rolfyone @ralexstokes I assume this is a bad AI that wrote that contract? That restriction comes from Bellatrix, not Electra.
English
While I think ePBS is the wrong direction for the protocol, in the interest of technical accuracy I have to defend it on one thing
While ePBS has an “optionality” problem, it doesn’t have a “free option” problem, because the builder’s payment is unconditional. The optionality makes the slot more valuable, so the builder should bid more in the auction
This still means there will be skipped blocks, and means more MEV is being extracted from users, but the value of the option accrues to the proposer, not the builder (if building is competitive)
Dan Robinson@danrobinson
Was surprised to hear that ePBS (EIP 7732) is considered likely to be scheduled for Glamsterdam on tomorrow’s ACD call, and particularly that it’s seen as a substitute for delayed execution (such as EIP 7886) Have never heard a very good reason to do delayed execution at the consensus layer rather than the execution layer. Unlike EIP 7886, ePBS doesn’t help simplify builders—they still have to execute the full block to generate the state root As many have pointed out, the optionality problem seems bad (8 seconds for a builder to cancel their block!). Even when the option isn’t exercised, this could add a lot of latency before users can see if their transaction was included But it also just seems like yet another complex change that doesn’t do anything to help users, which I thought Ethereum was moving past
English
English
@rolfyone @ralexstokes What if we took all the “seconds” numbers in the consensus client and divided them by 2
English
Nick Addison retweetledi
Testing merkle proofs of beacon chain data to verify OETH validator balances is coming along nicely
English
Nick Addison retweetledi
@kaanuzdogan @samczsun @blockscout @routescan_io @verifalliance Something 4bytes doesn't have but would be useful is to include error codes. 4bytes only includes function sigs and events.
For example
error InvalidDecimals(); // 0xd25598a0
English
@naddison @samczsun @blockscout @routescan_io @verifalliance Not yet but we'll be building our own 4-bytes from the verified contracts this quarter. We heard and observed a need for this recently.
If you have features, current issues in mind or how the API/data should look like, happy to hear that!
github.com/ethereum/sourc…
English
huge news for the contract verification ecosystem. please consider using sourcify so that your contract source code can automatically be picked up by tooling (wallets, debuggers, etc) and other explorers (@blockscout, @routescan_io) via @verifalliance
sourcify.eth@SourcifyEth
We just launched a brand new Verification UI! With Sourcify APIv2, it makes verification smoother than ever: ✅ Clear error messages ✅ Onchain vs recompiled diffs ✅ One-click GitHub issue reporting when it fails ✅ Etherscan import ✅ Solidity & Vyper Let’s break it down 👇
English
@dimsomedim Proof of validator balances for Origin ETH (OETH)
Although it's more complicated than that, as it also needs to handle validator deposits.
English
I'm learning how to construct merkle proofs of beacon chain data.
The generalized index is powerful, allowing any beacon chain data to be proved against the beacon chain root.
English