Slesarew

Is it still present? #1014 seems to be related to this (possibly duplicate)

As far as I understand, you are correct. This is improper payload formatting, for some reason they did not scale-encode the message properly and/or used an external signer raw payload...

Right, but maybe without `toU8a` conversion. On Signer side it was meant to just follow "sign message" protocol, just sign a string.

On contrary, this was removed for fixing as far as I know. It was not supposed to be possible there in current state. I'm pretty sure support will come back...

Either way, this is just something that should be fixed outside of Signer. I'll keep this issue open to help building pressure on that front.

Ok, looks like we can adopt 2 formats of signing freeform messages in Signer simultaneously. 1. Messages enveloped in `...`. These are used in pjs extension and Stylo. These are...

I think we just should add a `no-std` feature for `generate_message` eventually. However, be careful here - fetching metadata in CI without checking might be dangerous, and if you are...

As mentioned in #1048 we can also add decreased framerate option for hardware-compatibility updates, unless this is fixed by upcoming qr decoding refactoring aiming at moving decoder away from native...

#898 as usual will make this transition simple. Then we can let user build metadata locally using some settings switches - we'll have to occupy space that will be freed...

Yes, I knew someone needs it! I think this will be slightly more complicated though; this - Signer - repo will move towards more and more embedded-friendly format, I hope...