Skip to content

Conversation

@luke-jr
Copy link
Member

@luke-jr luke-jr commented Dec 30, 2018

The idea being to save this information in a usable format before we remove BIP70 entirely...

Thoughts?

}
return {};
}
bool writeWalletTxValues(const uint256& txid, std::map<std::string, std::string> new_map)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be marked override?

@DrahtBot
Copy link
Contributor

DrahtBot commented Jan 3, 2019

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, this pull request conflicts with the following ones:

  • #13756 (wallet: "avoid_reuse" wallet flag for improved privacy by kallewoof)
  • #9381 (Remove CWalletTx merging logic from AddToWallet by ryanofsky)

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.

@jonasschnelli
Copy link
Contributor

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?

@luke-jr
Copy link
Member Author

luke-jr commented Jan 3, 2019

The BIP70 stuff is currently stored in a protobuf-encoded format IIRC, so accessing it post-removal or even from RPC would be invasive.

@laanwj
Copy link
Member

laanwj commented Jan 8, 2019

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.

@DrahtBot
Copy link
Contributor

Needs rebase

@laanwj
Copy link
Member

laanwj commented Sep 12, 2019

closing in favor of #16852 (if it works)

@laanwj laanwj closed this Sep 12, 2019
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants