Nick Addison
@naddison
Followers
2K
Following
7K
Media
489
Statuses
2K
Ethereum, Solidity | Developer at @OriginProtocol | Author of sol2uml and tx2uml
Sydney
Joined March 2009
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.
2
0
6
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,
28
46
322
Over the past 6 Weeks, I’ve been building bera-reth, a Reth SDK execution-client with enshrined proof of liquidity without forking Reth. 10+ PRs contributed to Reth/Revm to support our use case. Now live on the Berachain Bepolia Testnet. 🧵
13
11
105
Testing merkle proofs of beacon chain data to verify OETH validator balances is coming along nicely
2
1
17
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.
3
1
54
sol2uml now supports @etherscan's V2 API The one API key can now be used across all Etherscan's supported testnet and mainnet blockchains. https://t.co/7Nwx0Lp7sW
github.com
Upgraded to use Etherscan V2 API As the Etherscan V2 API is being used, the same API key can be used for any chain supported by Etherscan. The -n, --network option can now take a ch...
1
0
7
tx2uml has been upgraded to support @etherscan's V2 API. This means the same API key can be used for any chain supported by Etherscan. https://t.co/kdv0w68LxV
github.com
Upgraded to use Etherscan V2 API Removed the Etherscan API keys so the -k, --etherscanKey option is now mandatory. The Etherscan API key can also be set with the EXPLORER_API_KEY environment variab...
0
0
7
Ethereum partial withdrawals delivered with the Pectra upgrade have been disappointing. 4.5 days to process 4 requests. Can anyone explain why these are so slow?
1
0
7
Was just looking at Origin Protocol's stats in our Grafana. Over the last two years we've grown our TVL 4.7x, and we've 6x'd our yield sent to users.
6
9
51
The Lido ARM hit a 48.0% APY today📈 Seizing the opportunity with low $stETH prices the ARM recovered 73% of liquidity (2,512 $WETH) at a massive 17-20 basis point discount! Now hitting an impressive 11.3% 30-day APY. Deposit $ETH into the ARM on our dApp to live the
4
5
44
Ethereum L2s are about to hit a brick wall. 55% of all blob space is already consumed by just 2 chains. And at current growth rates, we're only months away from everything breaking. Here's what's happening 🧵
226
342
2K
I've been using call graphs more and more in internal audits. They are a fantastic way to spot things that are missing, clean up architecture, and view the big picture. I threw together a diagram of the Morpho Blue lending code. What can we learn from this view of the code? 1/n
11
21
177
Yesterday's sophisticated 50 million Radiant Capital hack happened after attacker's trojaned the computers of multiple team members. Team members saw and verified good multisig data on screens, but their hardware wallets signed evil data. 1/7
100
301
1K
Update: Crowdstrike came out and released a technical report confirming my analysis. They were reading in a bad data file and attempting to access invalid memory. This global crash was a two-part bomb. The detonator apparently, was NOT new.. it was PRE-INSTALLED. /1
Crowdstrike Analysis: It was a NULL pointer from the memory unsafe C++ language. Since I am a professional C++ programmer, let me decode this stack trace dump for you.
296
4K
15K
The ongoing squarespace DNS hacks are *even* *worse* than phishing attacks on major sites. If an attacker controls a project's DNS, they control a project's email. Using that, they can reset passwords and takeover team members accounts on other services. 1/3
SEAL and other researchers have been hard at work assisting teams affected by the @squarespace domain hijacking incident. We are publishing an official security advisory to clear up any confusion. Summary: - Likely related to Google migration - Remove extra users and enable 2FA
1
11
54