Slesarew

Same thing should go into https://github.com/paritytech/metadata-portal; all of this is really part of polkadot's releasing flow and should be triggered there.

#914 allows .wasm signing and https://github.com/paritytech/ci_cd/issues/309 maybe should fix this at least partially. The only difference with the flow of the latter is that here we should only be updating...

Consider this a draft if you landed here. From @kirushik : In PolkadotJS UI there's an "Add Proxy" item in the triple dot menu on your account Or you can...

> in case of major reshuffles Well, yes, *just* throwing screenshots blindly would be silly; this should be some part of automatic tests CI flow, somewhat similar to in-docs assert!...

> Well, I guess there's https://openqa.opensuse.org/, huh, that's a huge overkill. Normal mobile testing suites can detect screen elements and print screenshots - so we can just look at the...

The UI from these screenshots is outdated desperately. What exactly are you trying to do?

Fair enough; not sure how useful or safe it is, but let's think about it! The upcoming version does not have this feature yet.

Oh, no, you are not supposed to do that, and certainly not copy-paste the address within the phone! The usage of Signer is based on it being airgapped, it should...

> Then it will be nice if parity releases an android wallet app for more day-to-day usage. Can't agree more; there are some mobile wallets for the ecosystem not created...

wait, #951 is for android.