Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #7745

C

Conformal Systems, LLC.

Company blog · blog.conformal.comprogrammingsystems

Conformal Systems, LLC. is the company blog at blog.conformal.com, writing about programming and systems. Since 2013, 10 different Hacker News readers have linked it 22 times, most often “The Bitcoin Consensus Red Herring”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
22mentions?
10HN people?
2013–2016first – last linked?
Links on Hacker News per year · peak 9 in 2013

Too few sampled comments (6) to say how often HN recommends it.?

Why HN links it

HN commenters link Conformal posts about Bitcoin block size limits, scaling simulations, the btcd Go full node, and Ethereum and hard-fork risks, usually as sources or see-also references.

Summarised by Claude from a sample of 6 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Most-linked posts?

  1. The Bitcoin Consensus Red Herring
    3 people · 3 mentions · first linked 2015-01-05
  2. Btcd: a bitcoind alternative written in Go
    3 people · 3 mentions · first linked 2013-05-02
  3. Btcsim: Simulating the rise of Bitcoin
    2 people · 4 mentions · first linked 2014-10-25

What Hacker News says?

  1. Block size isn't a free parameter. The team behind btcd, a Bitcoin full node written in Go, made the following observations about block size [1]: 1. a 32 MB block, when filled with simple P2PKH transactions, can hold approximately 167,000 transactions, which, assuming a block is mined every 10 minutes, translates to approximately 270 tps 2. a single machine acting as a full node takes approximately 10 minutes to ver…

    Comment linking /btcsim-simulating-the-rise-of-bitcoin/

    on “Bitcoin Is Dead, Long Live Bitcoin”
  2. Submitted Btcd: Not your mom's Bitcoin daemon as a story · 111 points

    HN discussion
  3. Also see: https://blog.conformal.com/btcd-a-bitcoind-alternative-writt... Btw, this original link was posted here full week ago.

    Comment linking /btcd-a-bitcoind-alternative-written-in-go/

    on “Btcd: A Full Alternative Bitcoin Implementation, Written In Go”
  4. Submitted Gotk3: GTK3 the Go way as a story · 111 points

    HN discussion
  5. The original announcement page lists some of what they claim to be the advantages of the port to Go: https://blog.conformal.com/btcd-a-bitcoind-alternative-writt... * integrated test infrastructure * no active memory management * standard formatting * platform independent code * simpler parallelism * virtually crash-proof * built-in profiling and documentation facilities From a development standpoint, I appreciate i…

    Comment linking /btcd-a-bitcoind-alternative-written-in-go/

    on “Btcd: Not your mom's Bitcoin daemon”
  6. Submitted Btcd Beta Announcement as a story · 29 points

    HN discussion
  7. > In any case, fixing the blocksize limit will be good This presumes the blocksize limit is being fixed, which is an incorrect assumption. Originally, the proponents of Classic wanted to boost block size limits to 20MB effective January 2016 [1], and used bombastic and divisive language, inventing their own crisis even, to get people to take them seriously. Interestingly, those same people are now contending for jus…

    Comment linking /btcsim-simulating-the-rise-of-bitcoin/

    on “Is Bitcoin breaking up?”
  8. Submitted Btcsim: Simulating the rise of Bitcoin as a story · 11 points

    HN discussion
  9. Bitcoin can scale a lot, though: https://blog.conformal.com/btcsim-simulating-the-rise-of-bit...

    Comment linking /btcsim-simulating-the-rise-of-bitcoin/

    on “The Myth of the Megabyte Bitcoin Block”
  10. Submitted The Bitcoin Consensus Red Herring as a story · 9 points

    HN discussion
  11. The essential points underlying the overall argument are: 1) A more powerful programming language in the blockchain carries greater risk of bugs which could take down all nodes in the network, 2) multiple implementations are a bad idea, and 3) hard forks are a bad idea. Problem #1 has the most merit. Ethereum's implementation may not be the winner, but _someday_ there will be a block chain which has a powerful progr…

    Comment linking /the-bitcoin-consensus-red-herring/

    on “Why I’m short Ethereum (and long Bitcoin)”
  12. Submitted Redecentralization: building a robust cryptocurrency developer network as a story · 8 points

    HN discussion
  13. Submitted Btcd: a bitcoind alternative written in Go as a story · 6 points

    HN discussion
  14. Submitted HTTPS safe? Maybe not as a story · 4 points

    HN discussion
  15. Submitted Summer Internships: hacking Bitcoin with Go as a story · 3 points

    HN discussion
  16. Submitted Coinvoice begins processing payments from BTC to USD as a story · 3 points

    HN discussion
  17. Submitted The Bitcoin Consensus Red Herring as a story · 2 points

    HN discussion
  18. Submitted Transaction Malleability: No Shortcuts Allowed as a story · 2 points

    HN discussion
  19. Submitted Btcscript – the script package from btcd as a story · 2 points

    HN discussion
  20. Submitted BIP0064 – Not yet as a story · 1 points

    HN discussion
  21. Submitted Deslugging in Go with pprof: btcd as a story · 1 points

    HN discussion
  22. Submitted Btcwallet and btcgui: Wallet handling for btcd as a story · 1 points

    HN discussion

Search all of HN for blog.conformal.com

Linked by the same people?