Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #4575

Z

Zeppelin Blog

Company blog · blog.zeppelin.solutionsprogrammingstartups

Zeppelin Blog is the company blog at blog.zeppelin.solutions, writing about programming and startups. Since 2017, 16 different Hacker News readers have linked it 36 times, most often “Why I’m Building Zeppelin”. The last post was in 2018, but the archive is still widely read.

Visit the blog
36mentions?
16HN people?
2017–2019first – last linked?
Links on Hacker News per year · peak 16 in 2018

Too few sampled comments (7) to say how often HN recommends it.?

Why HN links it

Zeppelin's blog hosts a technical analysis of the Parity multi-sig wallet vulnerability. HN readers link it as the explanation of how the bug worked, including how delegatecall exposed the library's public functions.

Summarised by Claude from a sample of 7 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Growing and protecting the core infrastructure of an open, global economy, powered by blockchain technologies.

Most-linked posts?

  1. /on-the-parity-wallet-multisig-hack-405a8c12e8f7
    5 people · 5 mentions · first linked 2017-07-20
  2. Why I’m Building Zeppelin
    2 people · 2 mentions · first linked 2018-12-28
  3. Deconstructing a Solidity Contract (series)
    2 people · 2 mentions · first linked 2018-08-14
  4. Thin Protocols
    2 people · 2 mentions · first linked 2017-10-05
  5. The Global Coordination Machine
    2 people · 2 mentions · first linked 2018-10-12
  6. Technical Details of zeppelinOS
    2 people · 2 mentions · first linked 2017-08-02
  7. Deconstructing a Solidity Contract – Part II: Creation vs. Runtime
    2 people · 2 mentions · first linked 2018-08-21

What Hacker News says?

  1. This is the most useful explanation I've found about the vulnerability so far: https://blog.zeppelin.solutions/on-the-parity-wallet-multisi... 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…

    Comment linking /on-the-parity-wallet-multisig-hack-405a8c12e8f7

    on “153k Ether Stolen in Parity Multi-Sig Attack”
  2. Submitted ZeppelinOS: tools for smart contract applications as a story · 93 points

    HN discussion
  3. That's correct. Here is a more detailed explanation: https://blog.zeppelin.solutions/on-the-parity-wallet-multisi...

    Comment linking /on-the-parity-wallet-multisig-hack-405a8c12e8f7

    on “153k Ether Stolen in Parity Multi-Sig Attack”
  4. Submitted Augur REP Token Critical Vulnerability Disclosure as a story · 84 points

    HN discussion
  5. 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... See also CoinFund's Jake Brukhman: https://blog.coinfund.io/fat-protocols-are-not-an-investment... 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…

    Comment linking /thin-protocols-cc872258379f

    on “Building for the Blockchain”
  6. Submitted Announcing OpenZeppelin 2.0 as a story · 16 points

    HN discussion
  7. This is a retelling of the Parity Multi-Sig Wallet hack, from the hackers perspective: https://blog.zeppelin.solutions/on-the-parity-wallet-multisi... We're talking about 40mn USD here so I doubt that this account was written by the original hacker.

    Comment linking /on-the-parity-wallet-multisig-hack-405a8c12e8f7

    on “How I snatched 153k Ether after a bad Tinder date”
  8. Submitted Getting started with OpenZeppelin-eth: a new stable and upgradeable EVM package as a story · 5 points

    HN discussion
  9. They've also shown an unwillingness to fork other hacks, such as the Parity one: https://blog.zeppelin.solutions/on-the-parity-wallet-multisi... 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…

    Comment linking /on-the-parity-wallet-multisig-hack-405a8c12e8f7

    on “Cloudflare's Ethereum Gateway”
  10. Submitted The Global Coordination Machine as a story · 4 points

    HN discussion
  11. 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-par…

    Comment linking /on-the-parity-wallet-multisig-hack-405a8c12e8f7

    on “Tor Browser disabled NoScript, but can't update”
  12. Submitted A Gentle Introduction to Ethereum Programming as a story · 3 points

    HN discussion
  13. 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-... Via. https://blo…

    Comment linking /the-hitchhikers-guide-to-smart-contracts-in-ethereum-848f08001f05

    on “How does the Blockchain Work explained simply (2016)”
  14. Submitted MakerDAO Critical Vulnerability Notice as a story · 2 points

    HN discussion
  15. Submitted Bootstrapping a Developer Ecosystem with Zeppelin as a story · 2 points

    HN discussion
  16. Submitted Why I’m Building Zeppelin as a story · 2 points

    HN discussion
  17. Submitted Compliant Decentralization?: Exploring an Approach to Utility Token Distribution as a story · 2 points

    HN discussion
  18. Submitted Deconstructing a Solidity Contract (series) as a story · 2 points

    HN discussion
  19. Submitted New crowdsale contracts in OpenZeppelin as a story · 2 points

    HN discussion
  20. Submitted A Path Toward Better Token Sales as a story · 2 points

    HN discussion
  21. Submitted ZeppelinOS: tools for smart contract applications – Whitepaper as a story · 2 points

    HN discussion
  22. Submitted Technical Details of zeppelinOS as a story · 2 points

    HN discussion
  23. Submitted Introducing Coral: A Secure Platform for Token Sales as a story · 2 points

    HN discussion
  24. Submitted Technical Description of Critical Vulnerability in MakerDAO Governance as a story · 1 points

    HN discussion
  25. Submitted Follow This Quality Checklist Before an Audit as a story · 1 points

    HN discussion
  26. Submitted Why I’m Building Zeppelin as a story · 1 points

    HN discussion
  27. Submitted Solidity Compiler Audit as a story · 1 points

    HN discussion
  28. Submitted The Global Coordination Machine as a story · 1 points

    HN discussion
  29. Submitted Deconstructing a Solidity Contract – Part IV: Function Wrappers as a story · 1 points

    HN discussion
  30. Submitted Deconstructing a Solidity Contract – Part II: Creation vs. Runtime as a story · 1 points

    HN discussion

Search all of HN for blog.zeppelin.solutions