That KeyringJson, as injected, is much simpler. It basically has the name & address, no other info. Have not looked at your hack....

... looked at your hack. So teh SubjectInfo there, you are actually correct, it still contains the full info. So you can adjust the type there. Only on injection does it actually get whittled down to the bare minimum.

Scratch all that... yes, on the ui-keyring it is actually the full thing.

Nice, I'll PR that to ui-keyring now.

I think it's good to go for a first look @jacogr

The Address now accepts a new type prop. Based on this the address will be displayed with the ethereum encoding. If this is type is not supplied (in most cases) we'll check if we have this account in our Keyring.

The accounts aren't injected in apps, you may know why.

I have been ignoring this one, will get in after the update on Monday.

Not sure why not injected, not a bad thing atm - I believe it is a keyring issue with the re-encoding. ... possibly. With that not-working, it still is a good idea to get it in, the issue is that we will probably break apps (apps === any user, not just the apps UI) when we start injecting these addresses.

Not sure how to solve that, may need to deprecate the current accounts interface (or add a flag to it), to have some additional info coming along. Not sure.

Although the css for the image is a bit broad (img selector), it doesn't seem to break anything.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.