bcoin-* about bcoin

[czzarr]

I'm totally up for it. I split bcoin into separate modules for my own needs, chief among them being testnet support.

[ryanxcharles]

I think there's great value in having all the little elements of the bitcoin protocol in their own module. This makes it easy to use only the piece you need.

However, I also think there's value in having a large repo that has all the elements in the same repo. This makes it easier to work on the system as a whole, keep track of issues, and make sure all the pieces continue working together correctly.

The way this will probably play out is for the components of the bitcoin protocol that can be easily extracted will end up in their own highly optimized modules, like bn.js, elliptic, and base 58 ( https://github.com/cryptocoinjs/bs58 ), and then things that can't be easily extracted will stay a part of the larger repos.

As for what's right for bcoin, that's up to @chjj & @indutny.

Also cc @jprichardson.

[chjj]

I don't like this idea. It's just messy. Coined was the opposite, a wrapper just to make bcoin more digestable for most people. I don't see the benefit of splitting everything up. Coined does have testnet support. It might be missing something though (the core seeds don't work anymore of course).

[indutny]

idk, it seems that the components are quite dependent on each other. What is the value of providing them in a separate packages? I think it will cause only a dependency and maintenance hell, without giving that much pros.

[czzarr]

@indutny you're right, I've been experiencing the kind of hell you're talking about in the past few days. Learning as I go. I'll keep maintaining a fork though with testnet support, and other stuff I need.

[indutny]

Oh, this saddens me a lot. I'd rather keep you here, but since neither me nor @chjj has enough time to figure it out - probably this is the best way to go.