Start with a public project when you want to understand a token's observable liquidity. A project bookmark keeps evidence for your workspace; operational vault setup follows a separate qualification process.
Analyze a public project#
Open Analyze a project at /app/analyze and enter a supported Virtuals project URL or a nonzero Base token address. The public lookup does not require a session or payment. It resolves supported token and pool identities and shows the public evidence it can verify.
Review the token identity, pool identity, reserves, source provider, block number, block hash, source timestamps and coverage gaps before drawing a conclusion. Reserves are shown using verified token precision, with exact atomic amounts available. The resolver pins its reads to a finalized block and rechecks the block hash; its finality claim relies on a single RPC provider.
Pool presence alone does not prove launch graduation, issuer control, safe transfer behavior or trading suitability. Reserve amounts do not establish executable depth, USD valuation or a slippage quote.
Investigate liquidity opens the included public reserve-scale investigation. You can compare a positive VIRTUAL amount with the verified reserve or review coverage without entering an amount. The investigation fetches a new public observation and reports a bounded finding. Its browser-session result is separate from a saved workspace agent report.
Save a project to your workspace#
- Choose Save to workspace from the public result.
- Sign in and select the intended organization. If you need membership, complete workspace setup.
- Check the organization named on
/app/projectsand review the canonical identifier. - Choose Save to this workspace. Wait for the validated server receipt.
Arriving on the page, signing in, reading history and reloading do not perform a save. Organization owners, treasury admins, analysts and Klineo operators can save and refresh; other permitted members can inspect recorded evidence.
The first accepted save creates a public bookmark and its initial immutable observation. Saving an identifier already present in the organization opens the existing bookmark. It does not add another observation.
Review and refresh evidence#
Open a saved project and inspect its latest observation. Record fresh observation creates a new immutable observation after the server accepts the reviewed project version. History lets you reopen earlier observations; project and history lists paginate in groups of twenty.
Keep three times distinct:
| Time | Meaning |
|---|---|
| Source read time | When the resolver read the provider. |
| Block time | The timestamp of the source block. |
| Recorded time | When the workspace stored the observation. |
A saved snapshot is historical evidence. It is not continuous live monitoring. A failed refresh leaves the previous observation visible with stale or unconfirmed status. Review that status before using it in further analysis.
If a save or refresh times out, use the offered retry for that exact action. The app retains the action identity and reviewed version so it can recover a recorded result without silently creating another write. Reload recovery depends on browser session storage; signatures and private market snapshots are not retained by this saved-project recovery mechanism. Access rejection clears the project view, and switching organization clears the prior workspace context.
From a current saved observation, an authorized writer can review and deliberately start a public Health investigation, optionally comparing an earlier baseline. Accepted runs appear in AI Agent → Agent tasks. This requires server enablement and a compatible live provider. Partial and abstained reports retain their coverage limits.
Project read access and issuer control#
A bookmark does not associate the project with a private treasury account, teammates, a Safe or a vault. Where configured, Treasury → Project read access provides a separate attestation and signature workflow:
- An organization owner or treasury admin imports a signed project identity supplied by an approved identity publisher and specifies the custody account.
- Request and review the server challenge, including its exact identity, organization, custody and expiry bindings.
- Download the signing request and obtain the required controller and custody signatures externally.
- Import the exact signed proof, submit it and inspect the matching server read-access receipt.
An expired challenge cannot authorize fresh signing. An uncertain request must be recovered with its original artifact and request identity. Reauthentication returns you to review; it does not submit the proof automatically.
Accepted project read access still requires separate custody-evidence admission. It does not establish spendable cash, approve a transaction or grant vault operating authority. Continue to vault qualification for the operational path.