A single list of every asset in the active project — EVM contracts, Solana
programs and PDAs, EVM EOAs, Solana accounts, and ZK circuits — rendered
as a grid of asset cards that link to each item’s runtime-specific page.
Why it exists
When analysis is spread across runtimes, it is easy to lose track of what
has been analyzed, what is stale, and which assets carry the highest risk.
The Assets page provides one filter/sort/search surface over the combined
inventory so these questions can be answered without switching pages.
Who uses it
Auditor — scans the whole engagement inventory in one place before
drilling into a specific finding.
Researcher — locates a previously analyzed target to compare runs
or re-open it in Studio.
Operator — checks which assets have gone stale and need a fresh run.
How to open it
Sidebar → Assets.
Top bar → Assets chip (if visible for the active project).
Direct URL — /assets.
Using the page
Add asset — opens the asset picker so a new contract, program,
wallet, or circuit can be added to the project.
Search — filters the grid by label, address, or network.
Asset type — radio group of kinds (All / Contracts / EOAs /
Programs / Wallets / PDAs / Circuits); selecting one scopes the
grid to that kind.
Sort — selects the ordering of the grid: Risk ↓,
Findings ↓, Stale first, or Recent.
Asset card — clicking a card opens /w/<id>/<tab> for that
asset at the last-viewed tab.
Inputs and outputs
Input
Source
Required
Active project ID
workspace-changed event / localStorage
yes
Access token
Sign-in session
yes
Output
Format
Destination
Asset card grid
HTML list
In-page render
Controls reference
Add asset — opens the asset picker modal.
Search — text filter over label, address, and network.
Asset type — radio group scoping the grid to one kind.
Sort — dropdown with Risk ↓, Findings ↓, Stale first,
Recent.
Asset card — link to the asset’s runtime-specific detail page.
Summary tiles — four top tiles populated from the server
inventory: severity bar, highest-risk asset, analysis health, last
analysis run.
Limits
Requires a signed-in account and an active project.
The grid merges /api/v1/workspaces/{projectId}/code-assets and
/account-assets with a browser-local recents cache; items only
appear after at least one of those sources returns them.
Pinned and recent state is stored in localStorage and does not
sync across browsers.
Troubleshooting
Symptom or error
Cause
Action
“No assets in this project yet” empty state
Server returned zero assets and recents cache is empty
Use Add asset to add a target.
Asset visible in one browser but not another
Recents cache is local-only
Re-open the asset in the second browser or wait for the server inventory to catch up.