SIP describing Stacks message signing about sips

[MarvinJanssen]

Is there a reason this method is preferred over using SIP018 with a string-ascii type? The SIP018 document describes some potential issues with "non-structured messages". For example, potential replayability issues depending on how the app dev formats the message, as well as the ability for wallet software to display sign in (and future) message types more nicely. Since some apps are broken right now due to the recent change, I would suggest them to simply move to SIP018 since it is implemented and shows the app name and version.

Nonetheless, at Ryder have not implemented non-structured signing due to there not being a standard yet. If it were adopted as a SIP it be safer for devs to rely on the functionality.

[Hero-Gamer]

From my understanding from the last SIP call when this item was discussed Friedger and Jude were present, the conclusion on the I believe was to just for this to be part of SIP-018. Will let the others confirm this.

[Hero-Gamer]

Hi @kyranjamie @MarvinJanssen since SIP-018 will activate with SIP-015 (provided Stacks 2.1 vote will be a pass), do you guys need to make any amends to SIP-018 based on this above conversation?

[kyranjamie]

I made this issue to note that there's no SIP covering this functionality, that's currently supported by the Hiro Wallet and Ledger Stacks app.

I'm no advocate for it, though. @MarvinJanssen's right that developers should favour SIP-018 going forward. Perhaps this functionality is better considered non-standard, not covered by a SIP, and eventually deprecated—that's up to Stacks app developers/community.

I don't believe any action is necessary relating to upcoming SIP activations.

[Hero-Gamer]

Understood. Thank you Kyran for bringing this to people's awareness!

[MarvinJanssen]

@Hero-Gamer it also does not make sense to me to include it in SIP018 as the message signing described in the OP is quite different.