HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
libbitcoin
libbitcoin-system
C++2018–2023
libbitcoin / libbitcoin-system

libbitcoin-system

Bitcoin Cross-Platform C++ Development Toolkit

11Distinct people
12Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Bitcoin Cross-Platform C++ Development Toolkit

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2018-03-08 22:24:56 UTC to 2023-08-09 04:17:16 UTC.

02462018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC707
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

What Hacker News says

12 sources
Some extra relevant links: https://github.com/libbitcoin/libbitcoin-system/pull/559 The pull request adding the vulnerability, the lack of review or collaboration is worth noticing. The prior code was already dubious in that AFAIK std::random_device library doesn't promise that the randomness is suitable for cryptography. I believe on common systems where this code was run the old code was not likely to be exploitable, but I wouldn't bet my money on it. https://twitter.com/evoskuil/status/1688657656620167169 Developer commentary on this issue. I can't figure out what "long-documented intended usage" a seed command that mandates 128-bits of output but never has more than 32-bits of entropy would have. https://archive.is/A7Jn6 The documentation the tweet references. I don't know how the 'Pseudorandom seeding' warning there would be dist
Read the rest
inguishable from warnings against CSPRNGs in favor of dice rolls or whatever, perhaps this is an example of the harm that chicken-little crying about CSPRNGS causes. Nor can I figure out for whose convenience this function would serve except attackers. In any case, this is the only place I found any kind of warning and the warning postdates the mastering bitcoin usage (as well as the change that made the command unconditionally unsafe). https://archive.is/HDe8h Current libbitcoin-explorer instructions telling users to use the seed command to generate private keys. https://archive.is/fhm5J#selection-12915.2-12915.10 Current libbitcoin-explorer instructions telling users to use the seed command to generate BIP39 seeds (also private keys). https://archive.is/PWLKJ Current libbitcoin-explorer documentation on randomness noting that bx seed is the ONLY source of randomness available to users in the package, and that all other commands that need randomness require the user to provide it. It also notes that 'bx seed' will not function if less than 128-bits are requested. The private key and bip39 seed usage (above) sure appears to be the "intended usage" in their documentation, but the "bx seed" function as currently implemented (since 2016) is unambiguously not fit for those purpose.
In Milk Sad Disclosure
Cryptocurrency uses the blockchain as a fundamental building block. For good faith proponents of cryptocurrencies, the appeal is that they provide the potential to do low friction digital payments (e.g. "micropayments"), reduce the barrier to entry to participate in financial transactions and allow for a single, global unifying currency. You may disagree that Bitcoin, or any other cryptocurrency, has the potential to do this or whether it can actually do this, but that's the appeal. Proof of Work (PoW) is probably necessary for a decentralized currency [0]. Proof of Stake (PoS) can be a valid cryptocurrency but fails in it's centralization criteria [1]. The Lightning network provides a layer-2 solution to payments, increasing transaction throughput and, thus, reducing PoW energy usage [2]. This might get into centralization territory but
Read the rest
maybe this is a happy compromise between energy usage, throughput and centralization. In some sense, we have many "layer-2" like structures on the internet, with DNS caching, replication and load balancing etc. > Most importantly, non regulation doesn't always mean good. Otherwise why we need law and government? Why not live in the wild west and let strong people kill weak people? Why not let big company play the monopoly? As a counterpoint, regulation isn't always a good thing when it's been captured by hedge funds, oil companies, pharmaceutical companies or other special interests. I'm having a hard time understanding if the line "Why not let big company play the monopoly?" was meant to be rhetorical in the affirmative or the negative. Are you suggesting that company monopolies are a good thing? Or are you suggesting that a decentralized currency unseating what is essentially the current banking monopoly is a bad thing? [0] https://www.youtube.com/watch?v=ZDGliHwstM8&t=490s [1] https://github.com/libbitcoin/libbitcoin-system/wiki/Proof-o... [2] https://en.wikipedia.org/wiki/Lightning_Network
In EU Funding for Developer Tools for the Decentralized Web
> Unlike Proof of Work based blockchains which require seizable factory infrastructure to break even, Proof of Stake doesn't need one. This isn’t inherent to PoW consensus. In 2010, Bitcoin was CPU mineable on any ordinary Windows PC. It wasn’t until Bitcoin commanded a significant market value — which wasn’t guaranteed in the slightest — that industrial scale mining operations came into the foray. > Most Proof of Stake supporters see this as a good thing because it means there's no electricity waste and higher degree of "censorship resistance". Your understanding of censorship resistance is gravely mistaken [1]: Overcoming censorship is not possible in a PoS system, as the censor has acquired majority stake and cannot be unseated. As such PoS systems are not censorship-resistant and the theory is therefore invalid. If 51
Read the rest
% of the stake — even if owned by separate entities — were to deliberately engage in censorship, the general public would have absolutely no recourse. Conversely, in Proof of Work systems, new miners could join the network at any time to challenge the majority miner censor. That is simply impossible under a Proof of Stake model with network censors. In addition to being vulnerable to total censorship, Proof of Stake consensus suffers from the misfeature of not even having a quantitative fork ranking protocol — i.e. it lacks a way to objectively compare the truthfulness of divergent blockchains. Under adversarial conditions, the PoS chains pos1, pos2, and pos3 cannot be quantitatively ranked by hashing power the way the PoW chains pow1, pow2 and po3 could be, as there is no hashing power in PoS. Instead, there is only “phone-a-friend” consensus, which Vitalik Buterin has euphemistically referred to as “weak subjectivity”. Jude C. Nelson, who has a PhD in distributed systems from Princeston, critiques PoS better than anyone [2]: PoW requires less proactive trust and coordination between community members than PoS -- and thus is better able to recover from both liveness and safety failures -- precisely because it both (1) provides a computational method for ranking fork quality, and (2) allows anyone to participate in producing a fork at any time. If the canonical chain is 51%-attacked, and the attack eventually subsides, then the canonical chain can eventually be re-established in-band by honest miners simply continuing to work on the non-attacker chain. In PoS, block-producers have no such protocol -- such a protocol cannot exist because to the rest of the network, it looks like the honest nodes have been slashed for being dishonest. Any recovery procedure necessarily includes block-producers having to go around and convince people out-of-band that they were totally not dishonest, and were slashed due to a "hack" (and, since there's lots of money on the line, who knows if they're being honest about this?). > Proof of Work blockchains, while wasting a lot of energy, can be regulated easily because the government can simply regulate the large miners in their countries. Because Proof of Stake blockchains can’t even come to consensus under adversarial conditions without human intervention (per JCN), these “blockchains” can actually be understood as distributed append-only ledgers managed by trusted central organizations the membership to which is gated by wealth. It’s highly misleading — even outright deceptive — to promote such systems as being more permissionless than PoW-powered systems like Bitcoin. “Green-friendliness” was never a design goal of cryptocurrency: creating a lasting store of value sans institutions, exchangeable pseudonymously over the internet, was. [1]: https://github.com/libbitcoin/libbitcoin-system/wiki/Proof-o... [2]: https://news.ycombinator.com/item?id=26810619
In Unstoppable Code?
Eric Voskuil writes about the "energy" argument. All moneys can be compared on energy level, and it is important to note not to look at energy solely, but also labor, land, services, energy, hardware, and other resources needed to keep a system running. If you are comparing the coin to fiat, take into account the military industrial complex, the cost of physical bank branches, physical issue, the cost of seignorage on the money holder (i.e. gain of energy for those close to the printing press vs. loss of energy for existing holders). If you rationally examine, the money holder will select the money with the least energy waste. All moneys not held imply a higher amount of energy inefficiency. This is why one may hold the USD, as opposed to the Turkish Lira. This is why one may hold btc, as opposed to the USD. If you want to investigate a b
Read the rest
it more in depth, cryptoeconomics Proof of Work fallacy is a great resource by Eric Voskuil. Link: https://github.com/libbitcoin/libbitcoin-system/wiki/Proof-o....
In Tesla buys $1.5B in Bitcoin, may accept it as payment in the future

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.