You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The public keys generated by generate-stacking-signature and check-config don't match. I've used the public key generated by stacking signature command in stack-aggregation-commit contract calls and the signer is not registered for cycle 84. The private/public keys are generated directly off secp256k1 package in node:
Using stx get_address <privKey>, @stacks/transactions package and check-config all point to the address SPYQ2Q584Y5059SEVN695YREBZ3RPJ68GJBQTPV8, while the public key generated from generate-stacking-signature matches the address SP2H1N2V9S7PEBC0120S3WMEAT32B9N7CGMPSGF16 (checked by @hstove).
On another note, the public key generated by generate-stacking-signature is the same one that is being generated in the node script (process.stdout.write([publicKey, ":", privateKey].join(""));).
I haven't seen other signers run into this issue, so that makes me think if it's because of the way the private key is being generated.
The text was updated successfully, but these errors were encountered:
Update:
After trying with Hank's implementation of compressed key in the check-config function (#4762), the public keys match, but the signer is still unregistered:
The public keys generated by
generate-stacking-signature
andcheck-config
don't match. I've used the public key generated by stacking signature command instack-aggregation-commit
contract calls and the signer is not registered for cycle 84. The private/public keys are generated directly off secp256k1 package in node:generate-stacking-signature
response:check-config
response:Using
stx get_address <privKey>
,@stacks/transactions
package andcheck-config
all point to the addressSPYQ2Q584Y5059SEVN695YREBZ3RPJ68GJBQTPV8
, while the public key generated fromgenerate-stacking-signature
matches the addressSP2H1N2V9S7PEBC0120S3WMEAT32B9N7CGMPSGF16
(checked by @hstove).On another note, the public key generated by
generate-stacking-signature
is the same one that is being generated in the node script (process.stdout.write([publicKey, ":", privateKey].join(""));
).I haven't seen other signers run into this issue, so that makes me think if it's because of the way the private key is being generated.
The text was updated successfully, but these errors were encountered: