btcd VS libtorsion

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.

Most of the crypto is from my more general crypto library libtorsion: https://github.com/bcoin-org/libtorsion

I originally wanted to vendor my libtorsion code and link to it, but it felt clunky since libtorsion pulls in a ton of crypto that bitcoin doesn't need. Also, since I was focusing on just a few algorithms, it gave me the opportunity to optimize a lot of them (in particular, the ECC backend was optimized for secp256k1 whereas in libtorsion it supports all kinds of curves).

Because of all of this, there's probably some leftover comments. That comment isn't true anymore. rand.c is definitely used internally for libmako, just not libtorsion.

edit: fixed link.

The 2-by-1 and 3-by-2 division functions described in the paper result in a very measurable speedup in my code. I think you're confusing those with the reciprocal calculation itself (which can be computed with a lookup table). I agree that part doesn't really lend itself to any significant performance benefit and is probably better calculated with a single hardware division instead.

I feel it necessary to point out that the 3-by-2 division actually has multiple benefits which are easy to miss:

1. The quotient loop can be skipped as I mentioned.

2. The "Add back" step is less likely to be triggered.

3. Since a 2-word remainder is computed with the division, you can skip 2 iterations on the multiply+subtract step.

My reimplementation of GMP documents both the 2-by-1 and 3-by-2 divisions pretty thoroughly[1][2].

[1] https://github.com/bcoin-org/libtorsion/blob/master/src/mpi....

[2] https://github.com/bcoin-org/libtorsion/blob/master/src/mpi....