I had a second v9.60 node that was off for a while. Turned it on, and for some reason it was not able to continue where it left off and did an automatic “reparse”. Waited for this to finish…

I’m not sure if it downloaded a bootstrap or not, but when comparing the hashes to my other v9.60 node these don’t match. Something is broken here

Hope this matches your hash
https://twitter.com/wasthatawolf/status/1621277483642265600?s=20&t=QSYvY3bjlRF3DeWoEuHVcQ

I thought there were actual hashes! 😆 But is just the code

I’m now running a node from code 100% in my repo which I have modified to remove all instances of bootstrap functionality. I need to be sure that it does the full parsing. This should finally provide nodes with consistent hashes.

I read somewhere that Counterparty and Bitcoin have different multisig. Anyone know more about this, are they not compatible?

This doesn’t sound right, they need to be compatible

Counterparty is compatible with standard multisig. The kind that starts with 3.

Not compatible with segwit multisig. Address starts with bc1q but much longer than normal bech32 address.

The issue is that counterparty uses 21 bytes to encode addresses. Bech32 msig requires more bytes, so updating would be a headache

Had to restart the node because I found even more bootstrap code in the cli.

I solved it by first fully integrating the cli into the lib. Then removed the bootstrap functionality.

So, in github/CNTRPRTY there are only 3 components required to run your node: fednode, addrindexrs and counterparty-lib.

🐸