pull down to refresh

BTCD already powers most of the Lightning Network and test vectors are no different than one version of Core upgrading to another...

Every new version of Core or fork of core incurs the same risk.

Case in point, Core's database backends (Berkeley DB and LevelDB) in 2013 caused a temporary chain split.

Diversity of implementations keep whoopsies small when they do happen, rather than most of the network downloading a default

It's a tradeoff, I'm not trying to bash BTCD, and yes you're right, different versions of the same implementation can cause splits too.

reply