Skip to content

Conversation

@meshcollider
Copy link
Contributor

@meshcollider meshcollider commented Dec 6, 2018

Github-Pull: #14424
Rebased-From: 2f6b466

@laanwj
Copy link
Member

laanwj commented Dec 6, 2018

looks like your rebased-from header is not correct (should be 2f6b466aeb6d4c88ab2e0e8b2a402be0743608b5 instead of 2f6b466aeb6d4c88ab2e0e8b2a402be0743608b4)

Apart from that, utACK

Difference from cherry-picked commit is:

diff --git a/src/script/sign.cpp b/src/script/sign.cpp
index a95a8609b3cf8f51e48c81199a764a480dc34c73..86b42d874f4f68f837c277df3358a00cdd60e1c2 100644
--- a/src/script/sign.cpp
+++ b/src/script/sign.cpp
@@ -77,7 +77,10 @@ static bool CreateSig(const BaseSignatureCreator& creator, SignatureData& sigdat
         sig_out = it->second.second;
         return true;
     }
-    sigdata.misc_pubkeys.emplace(keyid, pubkey);
+    KeyOriginInfo info;
+    if (provider.GetKeyOrigin(keyid, info)) {
+        sigdata.misc_pubkeys.emplace(keyid, std::make_pair(pubkey, std::move(info)));
+    }
     if (creator.CreateSig(provider, sig_out, keyid, scriptcode, sigversion)) {
         auto i = sigdata.signatures.emplace(keyid, SigPair(pubkey, sig_out));
         assert(i.second);

This makes sense, as the key origin code is different from master to 0.17.

@meshcollider
Copy link
Contributor Author

Fixed the commit message, thanks @laanwj

@laanwj laanwj merged commit 89a9a9d into bitcoin:0.17 Dec 6, 2018
laanwj added a commit that referenced this pull request Dec 6, 2018
…to sign non-PKH schemes)

89a9a9d Stop requiring imported pubkey to sign non-PKH schemes (Pieter Wuille)

Pull request description:

  Github-Pull: #14424
  Rebased-From: 2f6b466

Tree-SHA512: 1ea10dee66626f04918f197cd7c4949a836fa49c8f676f276b2328f8d79389059db7b30fc04d4c4bf8209f6a8d21f3ea49a017ddc7623eca6b7e6efc2fe0d749
@gmaxwell
Copy link
Contributor

gmaxwell commented Dec 6, 2018

ACK (looks like it works to me)

@meshcollider meshcollider deleted the 201812_backport_14424 branch September 5, 2019 11:56
@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.

4 participants