Arc USDC Rebalancer · onchain identity 4507 · kyc_verified · visitors can generate a report without a wallet · treasury brief included
DeFi Treasury automation with a policy-bound decision layer.
In 30 seconds, a visitor can open the dashboard, generate a readiness report, copy the markdown or action pack, and inspect the read-only evidence boundary.
A read-only Arc Testnet USDC treasury decision MVP with deterministic verification and an auditable evidence path.
Last reviewed: July 29, 2026.
What is live right now
The page stays close to the actual proof: report first, live Arc signals second, and the dashboard keeps a proof log so the site reads like a maintained builder contribution.
Min, target, and max values become a plain report instead of hidden state.
No wallet is required. The public MVP never requests a treasury signature.
The page tells you whether to hold, top up, trim, or stop and inspect wiring.
The main output is a report you can paste into chat, docs, or GitHub.
Deployment facts
Short facts that keep the live-read path and locked write boundary legible at a glance.
- • The main job is to produce a readable treasury decision, readiness report, and proof trail.
- • The system architecture page connects product behavior to contracts, authorization, and deployment evidence.
- • The submitted deployment is read-only; a wallet is not required to understand the result.
- • The dashboard keeps a local proof log so updates can be written down as they happen.
What changed most recently
A compact trail of the latest edits, so the homepage looks like a maintained demo instead of a frozen mockup.
The submitted deployment hard-disables treasury writes and keeps the Arc/USDC decision path read-only.
The repository includes tested V2 policy and executor reference contracts, but the submitted deployment does not present them as live evidence.
Web authorization, worker policy behavior, and contract governance now run without depending on a rate-limited public RPC, while production readiness exposes the durable guard state explicitly.
What visitors can do here
Start with the report, inspect the live signals, and verify that the public deployment remains read-only.
Start from the report surface instead of hunting through the whole site.
Read the balance, policy bounds, and live readiness signals together.
Grab the markdown report or the action pack for chat, docs, or GitHub.
The public MVP keeps treasury writes disabled and exposes the evidence boundary.
What this page is for
A single glance should tell you what is public, what is live, and how far the report workflow has already been wired.
- Show the Arc identity evidence, treasury policy, and report output together.
- Let visitors explore without a wallet and keep treasury writes disabled in the public MVP.
- Keep the technical evidence legible from GitHub to the system architecture page and release notes.
- Surface the report-first build without presenting an unavailable operator write path as live.
- Use the treasury brief as the shortest path for someone checking how the policy workflow works.
Open the review surface
The homepage is the overview. The architecture page explains the evidence. The dashboard is where people generate the report.