Skip to content

Conversation

@uniyalabhishek
Copy link
Contributor

@uniyalabhishek uniyalabhishek commented Sep 19, 2025

This makes “known address” rendering consistent across CLI text output, and prefers Ethereum hex in parentheses when available (while still showing both addresses where required).

Dependency: This PR depends on oasis-sdk PR oasisprotocol/oasis-sdk#2335 being merged and a new github.com/oasisprotocol/oasis-sdk/client-sdk/go release being published, after that we’ll bump the SDK version.

@netlify
Copy link

netlify bot commented Sep 19, 2025

Deploy Preview for oasisprotocol-cli canceled.

Name Link
🔨 Latest commit f8d4456
🔍 Latest deploy log https://app.netlify.com/projects/oasisprotocol-cli/deploys/697a72736200f10008e823fb

@uniyalabhishek uniyalabhishek force-pushed the uniyalabhishek/feature/format-known-addresses-131 branch from 0068b35 to 95ace6e Compare November 5, 2025 10:59
@ptrus ptrus requested a review from matevz December 21, 2025 12:10
@ptrus
Copy link
Member

ptrus commented Dec 21, 2025

This would be nice addition. @uniyalabhishek can you rebase? @matevz can you review please?

@uniyalabhishek
Copy link
Contributor Author

This would be nice addition. @uniyalabhishek can you rebase? @matevz can you review please?

@ptrus sorry, this PR is not fully ready for review now (also oasisprotocol/oasis-sdk#2335). there have been higher-priority tasks and missed completing this. will prioritise it this week.

@uniyalabhishek uniyalabhishek removed the request for review from matevz December 21, 2025 15:10
@uniyalabhishek uniyalabhishek force-pushed the uniyalabhishek/feature/format-known-addresses-131 branch from 95ace6e to ee0dbb3 Compare January 19, 2026 18:12
@matevz
Copy link
Member

matevz commented Jan 20, 2026

FYI I'll be refactoring oasis account show to support JSON output in #677. It may cause some conflicts one way or another.

@uniyalabhishek uniyalabhishek force-pushed the uniyalabhishek/feature/format-known-addresses-131 branch 2 times, most recently from c451ac0 to a2b7ccc Compare January 22, 2026 15:47
@uniyalabhishek uniyalabhishek requested review from matevz, peternose and ptrus and removed request for matevz and peternose January 22, 2026 16:54
Copy link
Member

@matevz matevz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First pass. IMO we should simplify more.

func GenAddressFormatContextForNetwork(net *configSdk.Network) AddressFormatContext {
return AddressFormatContext{
Names: GenAccountNamesForNetwork(net),
Eth: GenAccountEthMapForNetwork(net),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to separate between the eth and non-eth accounts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, the ETH map is just optional metadata keyed by native address. If an ETH hex is known for that address we prefer it, otherwise we fall back to native bech32.

fix(account show): propagate derived eth address
@uniyalabhishek uniyalabhishek force-pushed the uniyalabhishek/feature/format-known-addresses-131 branch from a2b7ccc to f0e7240 Compare January 27, 2026 20:32
@uniyalabhishek uniyalabhishek requested a review from matevz January 28, 2026 09:23
@uniyalabhishek uniyalabhishek self-assigned this Jan 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Name addresses, if found in wallet/addressbook/test/paratime/rofl entries

4 participants