FACTA

audit.opinion

Version
0.1.0
Terms named on this page

Where one agent's income came from over a window, where its money went, how it handled its loans, and the opinion that follows from those figures by fixed thresholds.

Changelog

Changelog
VersionDateChange
0.1.0
2026-11-17
First version, with the spec's default thresholds. They are to be calibrated on the first 50 audits; a change of any threshold is a new version.

What it measures

An agent registered under ERC-8004 declares an agent wallet. This method takes every USDG transfer into and out of that wallet over a window, asks of each payer whether the agent's own side funded it, follows where the money went, and reads the agent's loans from its lender's own events. It reports what the transfers show, against which threshold.

It does not measure whether the agent's service is good, whether its income will last, or why anyone paid it. A low Third-party share says that much of the money came from wallets the owner or the agent funded, or from loans; it says nothing about intent. Priors' Score v2 already leaves out income from payers in an agent's own cluster, for the agents that borrow from Priors. This method is an independent recomputation, with its evidence attached, that covers agents whether or not they borrow.

Inputs

For one agent and one window of 90 whole UTC days, ending at the end of the last day that has ended:

  1. The identity: its owner and its agent wallet, as the ERC-8004 Identity Registry (0x8004a169fb4a3325136eb29fa0ceb6d2e539a432) answers ownerOf and getAgentWallet, and the agent wallets of the owner's other identities.
  2. Every USDG transfer of the agent wallet and of the owner from 30 days before the window to its end. USDG is 0x5fc5360d0400a0fd4f2af552add042d716f1d168, 6 decimals; a transfer is a Transfer(address,address,uint256) log of that contract.
  3. Every USDG transfer of each payer, from the chain's first block to the end of the window.
  4. The first funding of each payer, of the owner and of the agent wallet: the earliest of the address's first incoming ETH transaction, its first incoming ETH transfer made inside another transaction, and its first incoming USDG transfer. The sender is its first funder. An x402 payer can hold no ETH at all, because the facilitator pays the gas, so its first funding can be USDG.
  5. For a first funder that the payer shares with the owner or the wallet: how many distinct addresses it sent ETH or USDG to, counted until the count passes 500, and its public label, if the explorer gives it one.
  6. The lender's events of the agent: Borrowed, Repaid and Defaulted of Priors CreditPoolV2 (0x281210097f0de7a8fb6f87310af0f089c9c8de21), whose second topic is the agent's ID.
  7. For each contract that sent the wallet money: whether it is a Uniswap v2 or v3 pool, by its factory() read at the head.

About 3 million USDG transfers happen on this chain a day, and a plain ETH transfer leaves no log, so the address histories and first fundings are read through the explorer's API (Blockscout), with its free key, in the batch lane. Every transfer the report rests on is a log anyone can read again with eth_getLogs.

Gross income

Gross income counts as the draft income-statement standard, ERC-8458, counts: every USDG transfer into the agent wallet in the window, except

  • a transfer from the zero address (a mint),
  • a transfer of zero,
  • a transfer from the wallet itself,
  • a transfer from the owner: an owner putting money into its own agent is capital, not income.

This version leaves out one more: the output of a swap, a transfer from the Uniswap v4 PoolManager, from a Universal Router (0x8876789976decbfcbbbe364623c63652db8c0904, 0x204faca1764b154221e35c0d20abb3c525710498) or from a Uniswap v2 or v3 pool. An agent that sells a token for USDG has exchanged one asset for another; nobody paid it. ERC-8458 counts these, so a comparison with a statement the agent posted adds them back. Each exclusion is reported as its own figure.

Where the income came from

Each payer gets one source, by the first test that applies, in this order:

Where the income came from
OrderTestSource
1
The payer is a lending pool the method knows (Priors CreditPoolV2)
Financing
2
The payer is the agent wallet of another identity with the same owner
Related-party
3
The payer's first funder is the owner or the agent wallet
Related-party
4
The payer's first funder also first-funded the owner or the agent wallet, and that funder sent value to no more than 500 addresses and carries no exchange or bridge label
Related-party
5
The payer received at least the amount of one of its payments from the owner or the agent wallet in the 30 days before that payment
Related-party
6
The payer was first funded within 7 days before its first payment to the wallet, and has never sent USDG to anyone else
Single-purpose
7
None of the above
Third-party

A first funder that proves nothing. An exchange's hot wallet, a bridge or a faucet funds thousands of addresses; sharing it with the owner links nobody. A first funder that sent value to more than 500 distinct addresses, or whose count the reader had to stop short of that, or that carries an exchange or bridge label, is ignored in test 4. Counting the addresses it sent value to is an upper bound on the addresses it first-funded, so this can only clear a funder, never wrongly link one.

A first funding the explorer may not show. The explorer has not processed some internal transfers before block 604,228 (2026-06-30 16:03 UTC). A payer active before then may have been first funded there unseen. An internal transfer is sent by a contract, and the owner and the agent wallet were not active then, so an unseen funding cannot come from them; it could come from a first funder of theirs only if that funder is narrow and was itself active then, which the method reads. When neither the funding shown nor an unseen one can pass tests 3, 4 or 6, the payer goes on to test 5 and then to Third-party; otherwise the data is missing and the opinion is a Disclaimer. The payer line then shows no first funding and says where it may lie.

Funded round trips are the payments that test 5 matches: money that went from the owner or the wallet to a payer and came back as a payment. They are counted for every payer except a lending pool, whichever test decided its source.

Use of proceeds

Each transfer out of the agent wallet in the window goes to the first category that applies:

Use of proceeds
OrderCategoryRecipient
1
Loan repayment
A lending pool the method knows
2
To owner or related
The owner, another wallet of the same owner, or a Related-party payer
3
Burned or locked
The zero address, or the conventional burn address: 36 zeros after 0x, then dead
4
Swapped
A swap venue, as for gross income
5
Paid to services
The agent wallet of another ERC-8004 identity
6
To labelled exchange
An address the explorer labels as an exchange, with the explorer named as the source
7
Unlabelled
Anything else

Held is what came into the wallet in the window less what went out, and never below zero.

Credit history

Loans are the lender's Borrowed events of the agent in the window. Each is open, repaid on time (its Repaid event is at or before its due time), repaid late, or defaulted (a Defaulted event). A loop is a loan repaid within 24 hours whose borrowed funds never left the receiving address before the repayment; the loop share is loops ÷ loans. Whether funds left is checked when the loan went to the agent wallet or to the owner, the two histories an audit holds; for a loan sent elsewhere it is not known, and the line says so.

The figures

The figures
FigureDefinition
gross_income
USDG counted as income in the window
incoming_transfers
Transfers counted as income
payers
Distinct payers
third_party_income, related_party_income, single_purpose_income, financing_income
Income by source; the four add up to gross income
third_party_share
Third-party income ÷ gross income
third_party_payers
Payers whose source is Third-party
top_payer_share
The largest third-party payer's income ÷ third-party income
funded_round_trip_income, funded_round_trip_share
Funded round trips, and their share of gross income
excluded_owner, excluded_swap, excluded_mint_and_self
What was left out of gross income, by reason
outflows and one figure for each category of proceeds
USDG sent out of the wallet in the window; the categories add up to outflows
held
Inflows less outflows in the window, never below zero
loans, loan_principal, repaid_on_time, repaid_late, defaults
The loans of the window and how they ended
defaults_in_window
Defaulted events of the agent in the window
loops, loop_share
Loops, and loops ÷ loans

Amounts are USDG in its own units, never converted. Shares are in millionths (six decimals), rounded down, and every threshold compares the same whole numbers, so every machine that reads the same transfers reaches the same opinion. A share whose whole is zero has no value.

The opinion

Code computes the opinion from the figures. A model never chooses it. The first rule that applies decides it:

The opinion
OpinionRule
Disclaimer
No agent wallet is declared; or data the method needs was not available; or gross income is under 50 USDG; or fewer than 10 transfers were counted as income
Adverse
Third-party share under 40%; or a Defaulted event of the agent in the window; or funded round trips above 25% of gross income
Qualified
Third-party share from 40% to 70%; or the top third-party payer above 60% of third-party income; or a loop share above 50%
Unqualified
None of the above

A report carries every rule its opinion met. Changing a threshold changes the opinion only, never a figure.

Missing data never becomes a guess. When a read the method needs fails, or the wallet had more than 1,000 payers in the window, the opinion is Disclaimer. Gross income, the counts and the exclusions are still reported; every figure that depends on classifying the payers is left without a value, no payer line is published, and the report says what was not read.

The evidence each figure carries

Every figure names the window's blocks and cites the filter it rests on, with the number of logs it returned: USDG transfers into the agent wallet (Transfer topic, any sender, the wallet as the third topic), USDG transfers out of it, or the lender's events of the agent. Each payer line carries the payer's first funding: the funder, the asset, the block and the transaction.

Reports and corrections

A report is published whatever it finds. Nobody can edit, delay or withdraw it, the agent's owner included. A report is never deleted; a correction is the next revision of the same agent, window and method version, says what changed, and every earlier revision stays on file. When operator responses open, the identity's owner will be able to attach one response of at most 500 characters, shown as written; it will change nothing in the report.

The opinion, the headline figures and this method are open to everyone. The line items (each payer, each outflow, each loan) are open to everyone until the token is live; then they are for holders, and the agent's own operator always sees them.

Recomputation

A recomputation script reads every input again, from the chain and the explorer, computes every figure with the same code and compares it with a published report. No report is published before it is.

Known ways to game the method

  • Paying through a fresh wallet funded from an exchange. A payer first funded by an exchange, by a wallet that funded more than 500 others, or by anyone the owner and the wallet do not share, is Third-party unless test 5 or 6 catches it. Tests 5 and 6 look back 30 and 7 days; patience defeats them, and the thresholds are public.
  • Funding in ETH, paying in USDG through a swap. Test 5 counts USDG received from the owner or the wallet. Money that changes asset on the way is not followed in this version.
  • Several identities, several owners. Wallets of identities with different owners are not linked unless they share a first funder.
  • Waiting out the window. The window is 90 days; payments before it are not in it.

Limits

  • USDG only. Income and outflows in other assets are not counted in this version.
  • The agent wallet is the one declared in the registry. An agent that is paid at another address is not measured there.
  • One lender. Priors CreditPoolV2 is the only lending pool the method knows; a loan from another lender is a payment from a third party.
  • The creator-fee recipient of a linked Pons token is not followed. FACTA links a token to an agent from the token's side only.
  • Exchange labels come from the explorer's public tags, which cover few addresses on this chain; an exchange the explorer does not label is Unlabelled.
  • Audits are scheduled work in the batch lane, chosen in advance; nothing is computed while a caller waits.