Slesarew

As far as I can tell, the payload used to use "sign message" protocol that implies scale encoding. By just scale-encoding raw payload we can keep things working without introducing...

One way or another, Signer was getting 2 different formats of "sign message" payload and treated them similarly. I understand that scale-encoding raw payload makes no sense in general; but...

Actually, there is no sense to send "raw payload" as utf-formatted thing. Thus, why don't we indeed add another uos payload type (04 or 05, whichever is free) and not...

So if raw payload will be just a message with `` in it, I'm pretty sure I don't have to do anything on my side. Will you check it (or...

https://github.com/paritytech/parity-signer/issues/1049

Yes, now that we have green light from security we can do that. Be sure to eventually mark weird UTF symbols like non-renderable and technical ones when you re-implement this...

This is likely caused by improper clearing of frame collector upon transaction parse. Should get fixed once it submerges into rust as well.

I think it got temporary fix in #986

key name does not exist anymore though; probably need to figure out something here. Maybe this feature will just be more comfortable in individual key screens?

Might go well with other options #871 This is a bit too many choices for the user though... but super-secret and moderately-secret seeds could co-exist nicely in fact. We just...