No SIP exists describing how arbitrary messages are signed.
Specifics such as what the prefix is, and what encoding is used should be described. EIP-712, for example, has an arbitrary message section.
The current prefix follows the same format as EIP-712, with Stacks in place of Ethereum.
"\x17Stacks Signed Message:\n" ‖ len(message) ‖ message
The need for this SIP comes from issues that've arisen migrating to a single prefix: See stx-labs/stacks.js#1328.
In migrating to a new prefix, some apps have seen breaking changes. Were this described in a SIP, a more structured, community-driven approach to changes would've been required.
cc/ @friedger @markmhx @MarvinJanssen @pradel @Hero-Gamer
No SIP exists describing how arbitrary messages are signed.
Specifics such as what the prefix is, and what encoding is used should be described.
EIP-712, for example, has an arbitrary message section.The current prefix follows the same format as
EIP-712, with Stacks in place of Ethereum.The need for this SIP comes from issues that've arisen migrating to a single prefix: See stx-labs/stacks.js#1328.
In migrating to a new prefix, some apps have seen breaking changes. Were this described in a SIP, a more structured, community-driven approach to changes would've been required.
cc/ @friedger @markmhx @MarvinJanssen @pradel @Hero-Gamer