Old Dip Tracker

fixed with #3222

> is their a dedicated place where i can send some UI designs as a piece of giving some inspiration or idea's? I've seen your design in #2948 and it...

> May I ask if the synchronization issue in 1.21 is one which is resulting in error: "prev block not found" in function AcceptBlockHeader()? It won't sync fully until auxpow...

@victorsk2019: you are correct, there is still #2355 to merge for that. I will rework that PR. We do need to make sure that wallets created with 1.14.0-1.14.3 (which have...

@victorsk2019 feel free to submit PR. Note that we need to support both `3'` and `0'` as BIP44 coin field value for this, because wallets created with 1.14.0-1.14.4 have `0'`...

I mean with that that we (a) have merged auxpow functionality (2 PRs) and (b) have made absolutely sure that segwit and wtxid-based relay are disabled. **Re: to segwit or...

It's not just lightning that is affected by it. Anyone's ability to change an announced transaction's hash is risky because that hash is recorded as input for a followup transaction....

> It's kind of too bad that GetConsensus() in 1.21 is not recursive like in 1.14 and chain parameters are not represented in BST so as to retrieve chain parameter...

> 1.21 seems to be slightly more time/memory efficient as it picks chain parameter with O(1) efficiency. This is at the cost of parametrized activation as a boolean and instead...

_Re: regtest parametrization in 1.21 comment by @victorsk2019 in https://github.com/dogecoin/dogecoin/pull/2977#issuecomment-1264730855_ Regtest needs to be fully re-engineered to be compatible with 1.14 and I am working on it - for weeks...