Live data from Hacker News

Viewing profile — 5chdn

5chdn

HN member
Joined
Sat, Jul 22, 2017, 11:55 AM UTC
HN karma
6
Public activity
13 items

About 5chdn

[ my public key: https://keybase.io/5chdn; my proof: https://keybase.io/5chdn/sigs/FholL7IHYje1-KvaYX0Ds_ij7qYaLAONbdII8pvUAdQ ]

Recent public activity

  1. comment
    Comment #16845087

    Curious why people think so w.r.t. (2). Anyone can submit a proposal.

  2. comment
    Comment #16845082

    EIP 867 which you are referring to is in limbo, this is not conforming with the ERP.

  3. comment
    Comment #16845028

    Exactly. It is the library used by hundreds of wallets. The library itself does not hold any balance.

  4. comment
    Comment #15947839

    Thanks for not reading the linked article, I'm explaining this very same example in the first paragraph :)

  5. comment
  6. comment
    Comment #15947828

    But that's precisely my point. Pruned Ethereum nodes hold _all_ blocks and therefore are full nodes. In Ethereum, unlike pruning Bitcoin nodes, old blocks are not deleted.

  7. comment
    Comment #15947811

    But a pruned bitcoin node does not hold the full blockchain for other nodes to download. A pruned Ethereum node, however, does.

  8. comment
    Comment #15947803

    Miners are already incentivized not to mess with the state.

  9. comment
    Comment #14826888

    Confirming this always was and still is the case. (Working for Parity.) However, this does not guarantee that such mistakes happen.

  10. comment
    Comment #14826874

    Parity does not run on the EVM, it's a local node processing a local copy of the blockchain. You can create normal accounts which are just private/public keypairs you have full con…

  11. comment
    Comment #14826853

    Not directly, but Parity multi-signagure wallets on Ethereum Classic, Expanse, Musicoin, and other public chains are affected as well.

  12. comment
    Comment #14826808

    Not at all. Solidity is just the most widely used language for the EVM. There are also Mutan (dead), Serpent (dying), LLL (recently revived), and Viper (being drafted).

  13. comment
    Comment #14826756

    The code was reviewed by two other developers and this is the standard procedure for any pull request touching any of our code-base. The mistake that happened here, that security-r…