stacks-core icon indicating copy to clipboard operation
stacks-core copied to clipboard

Published 20 hours ago • verified publisher icon stacks-network

[Nakamoto] Add signer key authorizations to negate requirement of signatures

Open hstove opened this issue 1 year ago • 1 comments

We recently added a signer-sig parameter to pox-4 transactions that include a signer-key as an argument. The purpose of that signature is to ensure that the signer has authorized the use of their signer key.

This new parameter is problematic to use in burn ops, because the total OP_RETURN payload is too long if the signer signature is included.

Instead, we should add the ability for signer key authorizations to happen out of band. If enabled, the signer-sig can be omitted from Stacking transactions.

hstove avatar Feb 14 '24 20:02 hstove

Will there be a burn op tx for authorisation registration ?

friedger avatar Feb 15 '24 06:02 friedger