Zeppelin Blog
blog.zeppelin.solutions · Company blog · on HN since 2017
The Zeppelin team writes about Ethereum smart contracts, Solidity internals, and ZeppelinOS, a tool set for building smart contract applications.
What HN saysHN commenters cite its account of the Parity multisig wallet hack, in which one call froze many wallets, and its fat-protocols and Solidity posts.
16HN people shared it
7linked it in comments
29stories submitted
238story points
7 years agolast shared
2017people per year2026
Most-shared posts
- 1On the parity wallet multisig hack 405a8c12e8f75 people · first shared 2017
- 2The Global Coordination Machine2 people · 5 points · first shared 2018 · discussion on HN
- 3Why I’m Building Zeppelin2 people · 3 points · first shared 2018 · discussion on HN
- 4Technical Details of zeppelinOS2 people · 3 points · first shared 2017 · discussion on HN
- 5Deconstructing a Solidity Contract (series)2 people · 3 points · first shared 2018 · discussion on HN
- 6Deconstructing a Solidity Contract – Part II: Creation vs. Runtime2 people · 2 points · first shared 2018 · discussion on HN
- 7Thin Protocols2 people · 1 points · first shared 2017 · discussion on HN
- 8ZeppelinOS: tools for smart contract applications1 people · 93 points · first shared 2017 · 36 comments on HN
- 9Augur REP Token Critical Vulnerability Disclosure1 people · 84 points · first shared 2017 · 20 comments on HN
- 10Announcing OpenZeppelin 2.01 people · 16 points · first shared 2018 · 2 comments on HN
- 11Getting started with OpenZeppelin-eth: a new stable and upgradeable EVM package1 people · 5 points · first shared 2018 · discussion on HN
- 12A Gentle Introduction to Ethereum Programming1 people · 3 points · first shared 2017 · discussion on HN
- 13ZeppelinOS: tools for smart contract applications – Whitepaper1 people · 2 points · first shared 2017 · discussion on HN
- 14A Path Toward Better Token Sales1 people · 2 points · first shared 2017 · discussion on HN
- 15Compliant Decentralization?: Exploring an Approach to Utility Token Distribution1 people · 2 points · first shared 2018 · discussion on HN
What HN people wrote when they linked it
dsco · 2019-06-19
They've also shown an unwillingness to fork other hacks, such as the Parity one: https://blog.zeppelin.solutions/on-the-parity-wallet-multisig-hack-405…
I do understand that reverting is somewhat against fundamental blockchain ideals, but on the other hand – you could always just continue using Ethereum classic – if you're a more principled blockchain enthusiast.
Also the use of the word "embarassing" makes me wonder if you truly understand what massive efforts it takes to create something as ambitious as Ethereum without running into some critical bugs.
Legogris · 2019-05-05
Not exactly clients, but the Parity multisig "hack"[0] was pretty wild. All it took was one permissionless call to permanently wipe the shared library of a large bunch of multisig wallets, thereby freezing those wallets forever. Some of the impacted people, including Parity, are still pushing for overriding the wallets to be unlocked, despite no support from anyone else.
0: https://blog.zeppelin.solutions/on-the-parity-wallet-multisig-hack-405…
evanvanness · 2018-01-09
Lots of smart people in this space disagree with "fat protocols."
I'll immodestly list my own first: https://www.evanvanness.com/post/166666272011/theres-no-such-thing-as-…
See also CoinFund's Jake Brukhman: https://blog.coinfund.io/fat-protocols-are-not-an-investment-thesis-17…
And Zeppelin's Teemu Paivinen: https://blog.zeppelin.solutions/thin-protocols-cc872258379f
I hear that even Joel doesn't agree with how his piece has been interpreted.
albertgoeswoof · 2017-09-13
This is a retelling of the Parity Multi-Sig Wallet hack, from the hackers perspective:
https://blog.zeppelin.solutions/on-the-parity-wallet-multisig-hack-405…
We're talking about 40mn USD here so I doubt that this account was written by the original hacker.
pietrofmaggi · 2017-07-20
This is the most useful explanation I've found about the vulnerability so far: https://blog.zeppelin.solutions/on-the-parity-wallet-multisig-hack-405…
The explanation is a bit scary about what actually ended up in parity code:
The wallet contract forwards all unmatched function calls to the library using delegate call... This causes all public functions from the library to be callable by anyone, including initWallet, which can change the contract’s owners.
Edit: formatting
Z1515M8147 · 2017-07-20
Last night after reading about the Parity Multi Sig attack I decided to finally try and read up on this subject, but quickly got annoyed with all the 'how bitcoin/blockchain works' videos that repeat the same high level points without scratching any of my technical itches. That was until I found this very concise gem of an introduction:
http://www.imponderablethings.com/2013/07/how-bitcoin-works-under-hood…
Via. https://blog.zeppelin.solutions/the-hitchhikers-guide-to-smart-contrac…
mrb · 2017-07-20
That's correct. Here is a more detailed explanation: https://blog.zeppelin.solutions/on-the-parity-wallet-multisig-hack-405…