-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ibc: transparent address support #1950
Conversation
🦋 Changeset detectedLatest commit: 8712343 The changes in this PR will be included in the next version bump. This PR includes changesets to release 15 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
after the chain upgrade lands, I’d like to do some round-tripping testing around transparent addresses to complement the manual testing and provide greater assurance. prax mainnet round-trip transactions
|
// in the UI component library. For example, when handling IBC withdrawals with transparent | ||
// addresses, this component transforms ephemeral addresses into their bech32-encoded | ||
// transparent form to ensure the proper data is being displayed. | ||
export const txvTranslator = async (view: TransactionView): Promise<TransactionView> => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remediates https://forum.penumbra.zone/t/usdc-transfers-temporarily-affected-by-noble-chain-upgrade/129 by detecting whether inbound / outbound IBC transfers involve Noble USDC and uses a transparent address (t-addr) to bypass the
bech32
encoding compatibility issues that have previously blocked transfers. For all other assets sent to Noble, we use thepenumbra1
encoding format.references penumbra-zone/penumbra#4950
pairs with prax-wallet/prax#254