When formatting the public key, status desktop chooses to use what looks like base64 (zQ...) - the accepted standard for formatting Ethereum keys using standard derivation however is hex (0x04...) - this breaks interoperability with virtually all tooling out there and introduces unnecessary friction between Status and the community around it.
Steps to reproduce
View a key
Expected behavior
Use hex when displaying keys - since the keys are "mostly hidden" anyway, it doesn't really matter what gibberish is displayed as long as the gibberish matches across different tools in the wider ecosystem.
Bug Report
Description
When formatting the public key, status desktop chooses to use what looks like base64 (
zQ...
) - the accepted standard for formatting Ethereum keys using standard derivation however is hex (0x04...
) - this breaks interoperability with virtually all tooling out there and introduces unnecessary friction between Status and the community around it.Steps to reproduce
View a key
Expected behavior
Use hex when displaying keys - since the keys are "mostly hidden" anyway, it doesn't really matter what gibberish is displayed as long as the gibberish matches across different tools in the wider ecosystem.
Actual behavior
Additional Information