*https://github.com/snowblossomcoin/snowblossom/compare/b17f71b69513...eaa43613032f* https://github.com/snowblossomcoin/snowblossom/commit/eaa43613032f709df0e573a3a911c946f1f892e6 - Update duck32 exceptions

*https://github.com/snowblossomcoin/snowblossom/compare/eaa43613032f...74dd160dd7bb* https://github.com/snowblossomcoin/snowblossom/commit/74dd160dd7bb379925eea4754f94242fbd38099a - Lower history limit

if git repositories can dig themselves out of the sha-1 pit, can a blockchain?

in this case, where the sha1 is always fed by another hash, absolutely :wink:

we want to provide hooks to channel managers such that we can integrate orphans meaning take orphan blocks and do something with the transactions within them. this additionally means that nodes that have orphans chains will try to advertise them and we want other nodes to be able to pick up the orphan chains it gets weird I'm not really sure.