these resolve protocol-level scalars from the standardized schemas. a single account's position — your Aave health factor — is not in that query shape, so a condition naming one evaluates to false rather than firing. README, “not in scope”.
Published names
reading the registryreading
The set of names comes from GET /api/registry/published, which enumerates MiniAppRegistry on 0G; each one is then read live from GET /api/resolve/<name> on mount. Nothing here is stored, and a record that is absent from the name renders as absent. The CID and the wallet are shown rather than linked: GET /api/publish reports the IPFS mode but no public gateway base, and an addr record carries no chain id, so either link would have to be guessed.
Registry
What this browser knows about — the seed set plus anything you published here. There is no shared index; the board is localStorage. Fork one and you get a local copy: no name, no wallet, no inherited spending authority.
Apps
16
this browser
Can spend
5
autonomous tier
Spent of caps
$0.00
metered at the signer
Forks, runs and thumbs are seeded texture — there is no network yet, and the README says so. Sources live, cost per run and spend against a cap are measured, each with a writer that went over the wire. Notional volume and creator earnings appear nowhere: nothing measures the first and no facilitator settles the second, so there is no figure to print.
Watch how hard the Aave market I am exposed to on Arbitrum is being borrowed against. When it runs hot, swap out of ETH to de-risk. Show me what you're doing.
Tell me when cumulative swap volume on the Arbitrum venues I watch crosses the next big round number. I want to hear that flow is picking up, not go looking for it.
Monitordex-amm@1.3.2dex-aggregator@1.0.2 — no live deployment
reading the registry…