-
Notifications
You must be signed in to change notification settings - Fork 75
RegTest support #588
Comments
First two steps seems pretty straightforward however am wondering how the checkpoint strings are encoded..? |
Hey @cuhte3 , For RegTest you better use this class. You don't have to implement |
Hey @esen, initially I've tried to use the default RegTest implementation (replaced only dnsSeed and port)
however BitcoinCoreBuilder
|
Seems like a bug, this network type was not used for a long time. Let's mark this ticket a This API is not actually needed if |
Yeah I've implemented the syncer, the only thing is still not clear is how to encode a block as checkpoint string? Could please provide an example? @esen Thanks! |
I was able create checkpoint string using the android tool, however am having an issue while decoding it. Here is how I encoded the block:
the output checkpoint string looks like this
I assume its way too long (compared to those in framework) and it's decode into wrong block (wrong height, timestamp, bits etc). This resulting me having having if I do not include previous block header hash info the output string looks like this
the block data decoded correctly however am getting @esen could you please provide en example how to encode a block? Should the bip44 checkpoint pointing to genesis block? |
Thanks for the awesome library!
I'd like to extend the kit to support regTest in my app. It seems like there are at least 3 steps involved:
Would that be enough or I miss something?
The text was updated successfully, but these errors were encountered: