Enhance Attestation View to Display Token Registration Details

Description

Currently, the explorer is displaying the attestation view based on parameters and data crucial for token transfer transactions. However, the most common use case for attestations is when a token is registered on the destination chain. Examples: Tx-With Destination Data API-CALL Tx-without Destination Data

Request

As a user of the blockchain explorer,

I want the attestation view to show relevant information about token registration transactions,

So that I can understand the details of a token being registered on the destination chain, including the symbol, name, token address, originating, and destination chain.

Acceptance Criteria

Display Token Registration Information: The attestation view must be enhanced to include detailed information about the token being registered. This includes: Source Chain Raw -> Source chain(Logo) Token Name, Token Address -> Source Address Signed VAA Raw -> as current Relaying Rwa -> ass current Target Chain -> Target chain(logo) Token Name, Token Address (ideally) -> Destination Address
Data Extraction from Payload: The application must extract token information from the transaction payload to accurately display the details mentioned above. Example: API

Frontend Enhancement (Nice to Have): Ideally, the frontend should also display similar token information for the registered token on the destination chain. This feature depends on the availability of such data in the API and may require API enhancement to support it.

Resources

Mockups

XLabs / wormscan-ui