btcd VS parity-ethereum

Following the instructions on their official repo, first, install go and check the version with go version, root path, and path with go env GOROOT GOPATH.

This dude caused all LND nodes to stop syncing recently with a single transaction costing less than $5 - https://twitter.com/brqgoo. Issues been patched recently. Theres others, will need to dig in order to find again.

the main one i know of btcd is written in Go and sees a lot of use from what I understand: https://github.com/btcsuite/btcd

For the Go code, I modified the code I found online to be able to generate P2PKH address, I believe. I am having a tough time navigating the plethora of functions defined here. I've also looked at the address_test.go to understand if I could get some clue, but I'm having trouble figuring out the intermediate conversions done to the Private Key hex like btcutil.NewAddressPubKeyHash(pkHash, &chaincfg.MainNetParams).

Salary: Competitive salary. Reach out to discuss. Port Bitcoin Tech to Peercoin, the World's First Green Blockchain (Opportunity for Ongoing Role) The Peercoin Foundation is looking to hire a developer experienced in both Go and Bitcoin. Peercoin is a cryptocurrency forked from Bitcoin that was launched ten years ago in 2012. It is responsible for inventing Proof of Stake consensus, the world's first green blockchain technology. The Peercoin Foundation is looking for an experienced developer to port Btcd to Peercoin. Btcd is an alternative full node bitcoin implementation written in Go. (https://github.com/btcsuite/btcd)

The Peercoin Foundation is looking to hire a developer to port btcd to Peercoin. Btcd is an alternative full node bitcoin implementation written in Go (golang).

Anyone. Also, there isn't just one implementation of Bitcoin. There are several implementations of the protocol in different programming languages, but they all stick to the same rules. btcd for example is written in Go, while Haskoin is written in Haskell.

The library killer's confession contains the bugged contract address, and some post-mortem links.

Not really. If one of the clients interpreted a part of the spec in a different way, event if they are right, they would have change it to follow an officially approved code because that's the consensus.

There are examples like https://github.com/openethereum/parity-ethereum/blob/55c90d4...

$150 Million of ETH gets locked up in Parity multisig contracts after a user "accidentally" kills a referenced library.

Case in point. Here's the line of code that introduced a bug in a contract that was ultimately worth $32M:

https://github.com/openethereum/parity-ethereum/blame/4c3217...

https://blog.openzeppelin.com/on-the-parity-wallet-multisig-...

If you look at the associated pull request, it added over 2K lines of code, and removed almost 1K, spread across 20 different files. 5 files have changed so much, GitHub doesn't even show their diff by default.

It was reviewed by one person in a single day.

for those that don't know, Gavin Wood was responsible for writing the Parity Multi-Sig wallet contract on Ethereum, which was famously killed by mistake due to a bug that was discovered by a developer who was playing around with the contract. This caused 513,743 ETH to be permanently frozen ($1,842,796,141 USD as of today).