Ecosystems · Arc

Arc: implemented offline, end to end.

The Arc track is a complete vertical slice built against injected transports and a fake execution port — decoding, structural discovery, decision, disposition and receipt — with every external boundary still unconnected.

What exists

A full path, with fabricated edges.

An Arc contract-execution intent is composed, decoded exactly, resolved against a structural graph, evaluated by a versioned policy and turned into an execution disposition — then either forwarded to the execution port or withheld.

Every transport in that path is injected and every external response is fabricated by a test fixture. That is what makes the logic testable today, and it is also precisely why none of it constitutes a live integration.

Chain id: eip155:5042002 (Arc testnet).
Native gas token: Documented as USDC. The raw tx.value unit remains unresolved upstream.
Endpoint trust: Chain identity verified before a response is used; mismatch yields no decision.

TodayA wrong-network endpoint is rejected rather than tolerated. Argus would rather return nothing than return a verdict derived from a chain it did not expect.

Arc capability status

Stated per capability, not as one badge.

Chain configurationProven offline
Arc testnet configured as eip155:5042002. Endpoint chain identity is verified before any response is trusted; a wrong-network endpoint produces no verdict at all rather than a cautious one.
Exact ERC-20 decodingProven offline
transfer, approve and transferFrom decoded field by field against USDC's documented ERC-20 interface. Unrecognised call shapes are reported as unrecognised.
EVM structural indexerProven offline
EIP-1967 and EIP-1167 discovery for proxy admins and implementations, run against injected transports in tests.
Circle Wallets pre-sign gateIntegration in progress
Intent composition, payload commitment, gate-created assessment provenance and disposition profile, all exercised against a fake implementation of the Circle API shape.
Native-value semanticsNot available
Arc documents USDC as the native gas token, but the unit for a raw tx.value is unresolved between Circle's own pages. Non-zero native-value transactions are deliberately gated rather than guessed.
Live Arc endpointNot available
No RPC endpoint is configured. The adapter has never been pointed at a real Arc node.
Circle Wallets executionNot available
No Circle API has been called from this codebase. The execution port has a fake implementation only.
Operational screening coverageNot available
No compliance or sanctions provider is connected, so no Arc subject can currently be cleared. Every evaluation reports the gap.
Live dependency indexing on ArcPlanned
The indexer exists and is tested offline; running it against real Arc state is milestone work.

Proven offlineImplemented and covered by automated tests against fixtures or injected transports. No live endpoint involved.

Integration in progressImplemented against a fake or injected boundary; the real external integration has not been exercised.

PlannedScoped and sequenced, not yet built.

Not availableDoes not exist. No partial implementation to point at.

Circle complementarity on Arc

Three distinct roles.

Circle Wallets executes the transaction and holds the wallet and key infrastructure. Circle Compliance Engine provides direct compliance and address screening where available. Argus contributes structural, controller, dependency and inherited-risk evaluation, and binds the decision to the execution-relevant payload and policy.

Argus does not duplicate either control and does not sign anything. No Circle integration is live, and nothing here represents an endorsement or a commercial relationship with Circle.

Milestone sequence

Live Arc testnet reads, read-only, with chain-id verification against a real endpoint.
One operational screening source connected, so a subject can be cleared rather than merely uncontradicted.
One real, gated testnet execution recorded against the exact policy version that permitted it.
Dependency indexing run against real Arc state instead of fixtures.
Production hardening: KMS/HSM-backed receipt signing and durable replay storage.

TodayScreening is sequenced before the first real execution deliberately. Executing a transaction that Argus allowed only because nothing was actually checked would be a worse outcome than executing none.

Assessing the Arc track?

The Arc vertical slice, its test evidence and its open questions are available for technical review on request.

Request access Sui track