register.links
- Version
- 0.1.0
- Desk
Links each ERC-8004 identity to its money: the owner, the agent wallet, the income writer, and the other identities of the same owner.
Changelog
| Version | Date | Change |
|---|---|---|
0.1.0 | 2026-11-11 | First version. |
What it measures
- Owner and agent wallet, as
register.identityreads them. - Income writer: the
incomeWritermetadata value of the draft income-statement standard, read withgetMetadata(id, "incomeWriter"). It is 32 bytes holding an address. It counts as unset when it is malformed, zero or equal to the owner. - Sibling identities: the other identities with the same owner, lowest IDs first, with their liveness terms.
Counting which agents are alive is not new. The link from each identity to its money is what this method adds.
It does not follow money: it names the addresses that receive it. Income, payers and outflows are the Audit method's work, in a later phase.
No linked token in Phase 1
An agent's file names no token in Phase 1. A Pons launch record can name any address as its creator fee recipient, and that recipient can be changed, so a token shown on an agent's file would be a stranger's claim about that agent. No standard field of a registration file names a token either. The link is shown from the token's side only: a token's page lists the agents whose owner or wallet receives its creator fees, worded as what the launch record says, with the note that it is not a statement by those agents. A link on the agent's side returns in a later phase, on a basis the agent itself creates.
Which agents a token's page lists, and in which order they are read:
- One query reads at most 21 identities the recipient owns, in ID order.
- When it finds 21, the page lists the first 20 and says there are more. An identity whose agent wallet is the recipient, and which the recipient does not own, is then not listed, even when its ID is lower: the full list the page links to is the recipient's own identities.
- When it finds 20 or fewer, the same query goes on to the identities whose agent wallet is the recipient and whose owner is not, in ID order, until it holds 21 in all. The page lists the first 20 of them all, and says there are more when it found 21.
- The list is shown in ID order. An identity whose owner and wallet are both the recipient is listed once, as one it owns.
The list is read when the token is checked, from FACTA's rows of every identity, each with its own read. Nothing is recorded: a check writes no row.
Inputs
The rows of register.identity: owner, agent wallet and income writer of every identity, read by each pass of its full read. A pass is planned to take one window (one day while the registry holds up to 24,800 identities, one more day for each further 25,000) and can run late or be given up; every answer gives the time of its own identity's read (see that page).
Thresholds
| Threshold | Value | Why |
|---|---|---|
Siblings counted while the reader waits | 20 | A check reads about 40 rows whatever identity is asked for |
Siblings shown | The first 20 by ID | A list that shows the first items of a longer one says so and links the full list |
Owners stored with their exact count | Every owner with more than 20 identities, up to 1,000, largest first, at the end of each pass of the full read | The largest owner holds about 1,700 identities |
Agents listed on a signed-in wallet's account view | The first 20 by ID, and whether the wallet owns more | The read asks for 21 rows whatever the wallet owns. The agents list, filtered by owner, pages through all of them |
Agents listed beside a token's creator fee recipient | The first 20 by ID of the identities it owns; when it owns 20 or fewer, all of them and then the first by ID of those whose agent wallet it is and which it does not own, 20 in all; and whether there are more | One query of at most 21 rows, the recipient's own identities first: it stops there when the recipient owns more than 20 |
How the sibling count is made:
- One query reads at most 21 other identities of the owner, in ID order.
- When it finds 20 or fewer, that is the count, made for this answer.
- When it finds more, the count is the one the last pass of the full read stored for that owner, shown with the time it was made.
- When that owner was not counted at the last pass, the count reads "more than 20".
Evidence
| Figure | Value | Evidence |
|---|---|---|
owner, agent_wallet, income_writer | See register.identity | The call and its block |
sibling_count | A count of other identities with the same owner | The ownerOf(uint256) read of this identity. The count is made from FACTA's rows of every identity, each with its own read; its time is when it was made |
linked_agents, on a token's answer | How many agents the token's page lists beside its creator fee recipient (see "No linked token in Phase 1") | The launch record's call that names the recipient ( master.pons). The agents are FACTA's rows of every identity, each with its own read |
Recomputation
pnpm tool packages/register/recompute.ts --envelope <answer.json> --rpc <endpoint>
It reads the owner, the wallet and the income writer again. sibling_count is marked not re-read: re-reading it means reading every identity of the owner. Anyone can count them on chain from the owner's identities; the agents list on the site, filtered by owner, shows each one. linked_agents is not re-read either, for the same reason: each agent the list names can be checked with the command above, whose owner and wallet it re-reads.
Known ways to game it, and what the method does
| Way | What the method does |
|---|---|
Spreading identities across many fresh owners, to hide that they belong together | Siblings are found by owner only. This method does not cluster owners; it says so here |
Setting the agent wallet to someone else's address, to borrow its standing | The registry changes the wallet only with an EIP-712 signature from the new wallet |
Setting an income writer to any address | It is shown as the identity's own metadata, read from the chain. Zero, the owner, or a malformed value counts as unset |
A lying endpoint that reports a false income writer | A changed income writer is written only when a second endpoint run by another operator reads the same value at the same block, as for the owner and the wallet ( register.identity) |
Naming an agent's owner as the fee recipient of a token, to tie the agent to it | Not shown on the agent's file in Phase 1. On the token's side it is worded as what the launch record says |
Asking for the siblings of the largest owner, to make a request read many rows | A check reads at most 21 sibling rows; a larger count comes from the stored pass |
Asking the agents list for an owner and a liveness term together, an owner of nothing with the largest term, so that one page reads every identity with that term | The list takes one filter at a time: an owner, or a term. The pair is refused before any read. Each filter alone reads its own index in ID order and stops after one page: measured on the local D1 engine with 25,000 identities, at most 51 rows read for a page of 50, where the pair had read 8,001 |
Checking a token whose fee recipient owns many identities, or is the agent wallet of many, so that the check reads many rows | The token's list reads the recipient's own identities first and stops at 21; the identities whose wallet it is are read only when it owns 20 or fewer. Measured on the local D1 engine with 25,000 identities: 21 rows for a recipient that owns 1,700 and is the wallet of 1,700 more, 22 for one that owns 5 and is the wallet of 1,700, where the earlier query, which merged both lists and sorted them, read 75. One case still reads more: the registry names an identity's owner as its wallet at registration, and the wallet's part of the query passes the recipient's own identities only by reading each of them, so a recipient that owns 20 identities, each naming it as its wallet, reads 42 |
Limits
- An owner's count above 20 is as of the last completed pass of the full read, and carries the time it was made. That is usually within one window, and older when a pass ran late or was given up. An owner that grew since shows the stored count with its time, or "more than 20" when the stored count is already lower than what the check can see.
- Only the owner links siblings. Two owners funded by the same address are not linked here.
- Phase 1 keeps no history of an identity's owner and wallet beyond notices; each notice carries both reads.
What exists elsewhere
The registry is public, and explorers show an identity's owner and wallet. Toll's agent census checks whether an agent's x402 recipient equals its agent wallet. Priors' credit board covers the agents with a Priors credit record. No tracker found on 2026-11-10 publishes, for every identity, its owner, agent wallet, income writer and sibling identities together, with the evidence behind each; that is this method's work.