The idea being to save this information in a usable format before we remove BIP70 entirely...
Thoughts?
The idea being to save this information in a usable format before we remove BIP70 entirely...
Thoughts?
353 | @@ -354,6 +354,13 @@ class WalletImpl : public Wallet 354 | } 355 | return {}; 356 | } 357 | + bool writeWalletTxValues(const uint256& txid, std::map<std::string, std::string> new_map)
Should be marked override?
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
Unsure about this... what is the long term use case for the stored data? Would it eventually be more straight forward to give steps how to keep the BIP70 data in a release notes (once completely removed)? Or would altering "dumpwallet" with an option to dump the BIP70 stuff make sense?
The BIP70 stuff is currently stored in a protobuf-encoded format IIRC, so accessing it post-removal or even from RPC would be invasive.
I think this makes some sense in context of deprecating BIP70. The data should remain in the wallet (for legal/historical purposes) but will effectively become inaccessible. Migrating it to another field makes sure that something of the historical metadata is visible even after BIP70 parsing is removed.
<!--cf906140f33d8803c4a75a2196329ecb-->Needs rebase