Sources & limits

QUID reads real onchain positions and never touches anyone’s funds. This page is the whole method, in plain terms.

What QUID reads

Position sizes come from Morpho Blue’s per-market position view on Arc (chain 5042), pinned against Morpho’s own public address book, and from Aave v4, which tracks balances per Spoke rather than per market — the two venues are read differently because they are not the same unit. Both reads use Arc’s public JSON-RPC endpoint, which needs no key.

What QUID never does

The preparer can read a counterparty’s balances and can never initiate anything on their behalf. A prepared sequence is handed over as a batch that the recipient approves in their own wallet — Arc’s Osaka baseline includes EIP-7702, so a plain externally-owned account can press the whole batch in one go, with no smart account to deploy and no custody at any point.

How a report is confirmed

Once a sequence is pressed, “what was left” is confirmed by reading the transaction receipt back from the Arc JSON-RPC. explorer.arc.io answers an interstitial challenge page rather than JSON from this reader, so it is never the programmatic source for reconciliation — only the RPC is.

Coverage today

Two lending venues are live on Arc: Morpho Blue and Aave v4 (its Arc market activated 2026-09-16). Coverage grows as more venues integrate; a chore for a market QUID cannot yet read is shown as unsupported, not silently guessed.

A known limit of this build

Wallet identity in this build is self-asserted (no personal_sign verification yet) — every write is still checked server-side against the chore’s actual poster/claimer address before it is accepted, but a visitor could type any address into the “acting as” field. Signature verification on claim and attest is the fast-follow.

Contact

Questions about a specific match or a data discrepancy: reach the team via the links in the footer of every page.