mxaddict
mxaddict
@aguycalled is this still an issue? might be related to the key dumping scenario that I talked about on discord.
> the reason why i did not change it for navcoin 5.0.0 was that it would require users to sync from scratch or go through a chain/wallet migration process We...
Is this still applicable to latest version?
@sakdeniz I think we already have blockheight and blocks synced, which you can add to get the current block height of the peer (so no need to get bestblockhash?) About...
I'll be adding more PRs from upstream to the list once I find them, still looking at what required PRs we need to have bitcoin/bitcoin#9289 and bitcoin/bitcoin#9441 work (Since we...
These changes will also require changes from #566, #554, #525 and #509
Once these changes are ported over, issue #568 and #569 should be resolved
@aguycalled should I just create an index for the dotNav names like I did for nftindex?
Should I maybe add the name to the `namerecords` index?
Alright, makes sense. On Sun, Feb 27, 2022, 01:03 alex v. ***@***.***> wrote: > I'd say modifying the current index would make current clients crash when > they try to...