Skip to main content

​
Asset types

There are two types of assets in Rover:
  • Token: ERC-20 or other fungible tokens
  • NFT: Non-fungible tokens (ERC-721, ERC-1155, etc.)
The Asset NFT Detail Page provides a complete view of a specific NFT, including its media, collection metadata, trait breakdown, and on‑chain activity. ​

​
Token Detail Page purpose

The Asset Token Detail Page is designed to answer “what is this token, who holds it, and what is it doing right now?” for any supported asset contract. It gives analysts and operators a single place to inspect token‑level properties while retaining drill‑down links into addresses and transactions.​ Asset Token Props

​
Header and primary metadata

The header surfaces the asset name (for example, “USD Coin (USDC)”), the asset type (Token vs. other asset classes), and a pinned tag for the network or collection if applicable. Core metadata includes:
  • Asset Address: the canonical contract address for the token on the current chain, with a quick‑copy control.​
  • Asset Symbol and Type: symbol (USDC) and high‑level asset type (Token, NFT collection, etc.) used across Rover tables and filters.
  • Price and Total Supply: latest tracked price in USD and the current total supply of the token on chain, when available from upstream indexers or oracles.
Sender, Receiver, and Views summarize aggregate usage for the asset: Sender and Receiver show the number of distinct addresses that have sent or received the token, and Views tracks how many times the asset detail page has been opened in Rover.

​
Properties and customization

Below the header, the page supports “Add Properties,” which lets teams attach custom metadata fields to the asset, similar to how additional properties can be configured for issues or projects in tools like Linear. Custom properties are scoped to the workspace and can be used in filters, search, and views anywhere the asset appears.

​
Addresses section

The Addresses section lists wallets and contracts that currently hold the token, giving quick answers to “who owns this asset?” It is organized into:​
  • View selector: a filter pill (for example, “Holds · USDC”) that constrains the table to addresses with a non‑zero balance of the selected asset.
  • Address table: a paginated list of addresses with columns for Address, Label, and Balance, plus an aggregate TOTAL row at the bottom representing the sum of balances in the current view.
Each row shows the checksummed address with a hover copy action, its workspace label (for example, “+ Custom” for user‑defined labels), and the current token balance formatted with thousands separators. The “Expand” control opens the full holder list with the same keyboard‑driven navigation and sort controls used elsewhere in Rover’s tables. Asset Token Addresses

​
Address labels and customization

Labels in the Addresses table work like tags on issues or projects: they can be created inline, edited, and reused across the workspace. Creating or editing a label here updates the label everywhere that address appears, allowing teams to maintain a single source of truth for counterparties such as exchanges, internal wallets, and contracts. Asset Token Label

​
Transactions section

The Transactions section shows the most recent on‑chain activity involving this asset, scoped to transfers and contract interactions where the token appears in logs. A filter pill (“Asset · USDC”) indicates the asset filter currently applied; changing or clearing this filter broadens the table to additional activity when supported. The table includes the following columns:
  • Transaction Hash: the canonical transaction identifier, truncated for readability with a link to the Transaction Detail Page.
  • Date: relative timestamp (for example, “3 minutes ago”) resolved against the user’s timezone.
  • Description: a short, human‑readable summary such as “0x… called function …” that is generated from decoded calldata and log events, similar to how other Rover detail pages summarize on‑chain calls.USInteractions with other detail pages
From the Asset Token Detail Page, users can navigate to related Rover entities to continue investigation flows. Clicking an address cell opens the Address Detail Page for that wallet or contract, while clicking a transaction hash opens the Transaction Detail Page, mirroring navigation patterns described in Rover’s transaction detail documentation.​

​
Keyboard shortcuts and behavior

The page follows the same interaction model as other Rover core detail pages: keyboard navigation for tables, consistent focus handling, and dark‑mode‑compatible styling based on the global theme. Any workspace‑level features such as saved views, search, or context sidebars that apply to other entities also apply to the Asset Token Detail Page to keep the experience consistent and predictable.

​
NFT Detail Page purpose

This page answers “what is this NFT, what collection is it from, and what has happened to it on chain?” for any supported token ID. It follows the same interaction patterns as other Rover detail pages, with consistent layout, navigation, and workspace customization options. ​ Nft Props

​
Header and core metadata

The header shows the NFT media on the left and a short collection description on the right so users can quickly recognize the asset and understand its context. Primary metadata includes:
  • NFT Collection: the parent collection name (for example, “LilPudgys”) with verification status when applicable.​
  • Floor Price and Total Supply: the current collection floor price in the native chain currency and the total number of tokens in the collection.
  • Address: the collection contract address, displayed in shortened form with a quick‑copy action and link to the collection or contract detail view.

​
Properties and custom fields

Below the main metadata, “Add Properties” lets workspaces attach additional structured data to the NFT, similar to custom fields for issues or projects in Linear. These properties are workspace‑scoped and can be reused in filters, views, and automations wherever the NFT appears in Rover.

​
Attributes section

The Attributes section surfaces the NFT’s trait data in a two‑column layout, grouping related traits. Each trait is rendered as a labeled pill (for example, BACKGROUND → Mint, HEAD → Beanie Gray), enabling fast visual scanning and comparison across tokens in the same collection. Trait labels and values are read directly from token metadata and normalized where possible so that filters and aggregations (for example, “HEAD: Beanie Gray”) behave consistently across Rover views. When traits are missing or null in the metadata, the UI displays a neutral value like “None” to make gaps explicit without breaking layout.​ Nft Attributes

​
Activity section

The Activity section lists the most recent on‑chain events involving this specific NFT, such as sales, transfers, or mints. The table includes:
  • Type: high‑level event type (for example, Sale, Transfer, Mint) derived from decoded logs.
  • Description: a human‑readable summary, such as “0x540…2f5 purchased from 0x0db…5af,” including links to buyer and seller address detail pages.
  • Date: a relative timestamp (for example, “3 months ago”) resolved to the user’s timezone, matching other Rover tables. Nft Activity
From the Asset NFT Detail Page, users can jump to related entities to continue investigations: clicking the NFT’s address opens the Contract Detail Page, and clicking an activity row’s address link opens the Addre Detail Page.