bcoin VS tokei

You can just submit your changes to the Bitcoin core repo https://github.com/bitcoin/bitcoin or you can fork it and create your own version. You can even just use/change one of the alternative implementations: https://github.com/bcoin-org/bcoin

I'm not sure what you mean by "truly separate", but our hot wallets are indeed separate wallets, both running on top on bcoin.io

bcoin

My first bitcoin reimplementation was written in node.js and called bcoin[1]. So this is my second time reimplementing the bitcoin protocol, albeit in a very different language.

Bcoin was frequently used as a reference along with bitcoin core v0.8.0-v0.11.0 when I felt like double checking consensus functions (among other things).

As an aside, I personally think bitcoin core v0.8.0 is the best version of core if you want to learn bitcoin from it. It's a lot more straightforward than later versions. I personally don't enjoy reading any version beyond v0.11.0.

This is also the reason mako doesn't support taproot yet. That code is very new and isn't present in upstream bcoin. I could try to implement it from the BIPs alone, but I won't know what intricacies are present in the actual bitcoin core code until I actually read it.

[1] https://github.com/bcoin-org/bcoin

Hey guys, Is there a way to run a bitcoin-core program (like https://github.com/bcoin-org/bcoin) without downloading the blockchain?

So If we would only count code and not comments, it is only 9489 LoC Rust. Which would be about 0.03% and if we take all lines and not only LoC it would be around 0.05%

[0] https://github.com/XAMPPRocky/tokei

[1] https://github.com/torvalds/linux/commit/b401b621758e46812da...

thirdly: found this (https://github.com/XAMPPRocky/tokei) and wanted to analyze languages used on my system, didn't see a package manager (apt) for it that I had. So i installed cargo via apt-get rustup. Added the bin folder to $PATH via PATH=$PATH:~/.cargo/bin. But did not make it permanent. And stupidly rand tokei on "/", realizing how long and unhelpful that would be killed it. Then ran it in a dump folder with some very nested repo dumps, and tons of wolfram.nb files. After killing that too, and attempting to kill via system monitor. Still have two of those as zombie processes.

tokei

For what it's worth, tokei seems to be named after tokei.

BTW, for more info on how it is done, you can check out tokei which is the library use by onefetch for code statistics.

With pytokei you can count code quickly using all the power from tokei, but from python.

Tokei is a nice utility to count lines and stats of code. It is very fast, accurate, and has a nice output. It supports over 150 languages and can output in JSON, YAML, CBOR, and human-readable tables.