You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for multi-chain asset display and Inter-Blockchain Communication (IBC) Protocol.
User Flow
Balance Aggregation
In the Wallet, tokens of the same kind across multiple chains are aggregated into a single balance for improved visibility.
In the Token Details Page, the distribution of the tokens by chain is displayed along with a composite transaction history that involves the token from all chains.
Multi-chain Addresses
The address popup displays all of the user's addresses in a single place.
The user may click on any of the addresses to copy it with ease.
Address Book
Each registered address is tagged with the corresponding chain.
When the user adds a new address, Adena detects the chain of the user's input and automatically tags it.
IBC Deposit
The Deposit menu displays all of the supported addresses. The user may copy the address or view details.
By clicking on the QR code icon, the user is taken to the Detailed Address, where a full QR code and a link to the respective explorer are available.
IBC Send
The user selects the token and the source chain.
Once the user enters an address from any of the supported chains, Adena automatically detects the destination network by analyzing the prefix. Adena also warns users to protect them from potential losses resulting from using IBC transfer to CEXs.
The user may review the amount and the destination network before approving the transaction.
Possibilities
Seamlessly connect Gno users to the broader interchain ecosystem by abstracting the complexities of multi-chain asset management.
Allow users to avoid manually searching and entering the channels during IBC transfers to streamline interchain experience.
Consideration
How (and whether) to allow users to search & add custom tokens from other IBC-connected smart contract platforms?
How to deal with edge cases in which a user sends a token through a "non-canonical" IBC path. (in terms of balance aggregation & display)
Any feedback is welcome!
The text was updated successfully, but these errors were encountered:
Overview
Support for multi-chain asset display and Inter-Blockchain Communication (IBC) Protocol.
User Flow
Balance Aggregation
Multi-chain Addresses
Address Book
IBC Deposit
IBC Send
Possibilities
Consideration
Any feedback is welcome!
The text was updated successfully, but these errors were encountered: