status-im / feature-specs

repo for feature specs & feature requests
2 stars 4 forks source link

Difficult-to-work-with key formatting #93

Open arnetheduck opened 1 year ago

arnetheduck commented 1 year ago

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

caybro commented 1 year ago

CC @John-44

osmaczko commented 1 year ago

@arnetheduck the rationale: https://github.com/status-im/status-go/issues/1937