Method
How a check works, and where it stops
The sixteen checks
| Slot | Check | Reads | Limit |
|---|---|---|---|
| 0 | Identity registered | Registered event and ownerOf in the ERC-8004 identity registry | Registration is open to anyone. It proves an id exists, not who runs the agent or what it does. |
| 1 | Current owner | ownerOf(agentId) at the latest block | An owner is a wallet. Whether a person, a team or another program holds its key is not visible on chain. |
| 2 | Owner changes | Transfer events of this agent id after registration | Counts transfers inside the registry only. A sold or shared private key changes nothing on chain. |
| 3 | Agent wallet | getAgentWallet(agentId) | The wallet the owner declared for payments. Funds can still move through other wallets. |
| 4 | Metadata link | tokenURI(agentId), the agent's registration file link | The link is whatever the owner set. Its host can change the file without any chain event. |
| 5 | Metadata file and hash | One fetch of the link (https, ipfs through a public gateway, or data:), keccak-256 of the bytes | The hash is of what this fetch received at this time. Another fetch may get different bytes. |
| 6 | File names this identity | The registrations list inside the file, compared with this agent id and registry | The file is written by the owner. Matching ids show consistency, not truth of the description, services or skills. |
| 7 | Profile changes on chain | URIUpdated and MetadataSet events of this agent id | Only changes made through the registry are on chain. Edits to the hosted file itself are not. |
| 8 | Code at the address | eth_getCode: size and keccak-256 of the runtime bytecode | No code means a key-held account (or a contract not deployed yet). Code says nothing about intent. |
| 9 | Source published | Sourcify (no key) and Blockscout (when the site has a key) | Published source matches the bytecode. It is not a review of what the code does. |
| 10 | Deployer and age | Creation transaction from Sourcify or Blockscout; registration block for an agent id | Known only when a source service recorded the creation. Otherwise shown as not available. |
| 11 | Upgradeable proxy | EIP-1967 implementation, admin and beacon slots; EIP-1167 minimal proxy pattern | Other proxy designs exist. A plain contract can also hand control to another contract in its own way. |
| 12 | Implementation changes | Upgraded and BeaconUpgraded events at the address | Reads standard events only. A proxy that does not emit them can change silently. |
| 13 | Owner or admin role | owner() and the EIP-1967 admin slot | Other role systems are common. Absence of owner() does not mean nobody controls the contract. |
| 14 | Control changes | OwnershipTransferred, RoleGranted, RoleRevoked and AdminChanged events | Standard events only. Custom role systems may log differently or not at all. |
| 15 | Account activity | Transaction count (nonce) and native balance at the latest block | A count, not a history. Activity says nothing about whether past actions were good. |
Status words
- Found: the source answered and the thing exists (an owner, a file, code, a role).
- None found: the source answered and there is nothing of that kind.
- Changed: the history shows changes after the start (transfers, new links, upgrades, role changes).
- Worth a look: something a person should read, such as an upgradeable proxy or a metadata file that does not name this identity. It is not a warning that something is wrong.
- Not available: the source did not answer or refused; nothing is guessed.
- Not run: the check does not apply to this kind of subject.
“Changed” is neither good nor bad. Owners move agents between wallets and fix their metadata for ordinary reasons; the watch exists so you notice, not so you conclude.
Limits
- Intora gives no security guarantee, no score and no recommendation. It does not run agents, hold funds, lend, back or insure anything.
- Registration in the ERC-8004 registry is open to anyone. An id proves that someone registered it, nothing about who they are.
- A metadata file is written by the agent's owner. Intora checks that it can be fetched, hashes it and compares the identity it claims; it does not check whether the description, services or skills are true.
- A hosted file can change without any chain event. The file hash catches that only when you look again.
- Code and role checks read standard patterns (EIP-1967, EIP-1167, owner(), OpenZeppelin role events). Other designs exist and can be missed.
- The chain's RPC refuses log queries over 10,000,000 blocks, so history is read in windows. A window the node refuses or does not answer is named as a gap; it is never skipped silently.
- A check describes one block. Anything can change after it.
The report
A report is the subject, the block, the time of reading, every fact with its sources and coverage, the notes and your own note, in JSON with sorted keys and no spaces (schema intora.check/1). Its keccak-256 hash is what the check book stores. Anyone can recompute it from the file on the reports page or with any keccak library.
The check book
IntoraCheckBook is a contract with no owner, no admin, no fee and no upgrade path, and it never holds funds. A reviewer files a report hash with one 4-bit status code per check and an optional link, can publish revisions or withdraw, but never delete. Any other wallet can mark the latest revision reproduced or different, once. The agent's current owner in the registry (or the account itself) can attach a response. The contract is new and not yet deployed; when it is, its address and source will be published here.
Planned, not built
- Advanced reports across several agents, an API quota for scripts, and paid monitoring. If they come, $INTORA may be used to pay for them; that need is unproven.
- Notifications outside the browser. Today the watch compares only when you look.
Questions
Does Intora say whether an agent is safe?
No. A check returns sixteen separate facts with their sources and limits. Nothing is added up and there is no safe or unsafe label. An agent with a tidy record can still misbehave, and a new agent with little history is not therefore bad.
Does Intora run, host or pay agents?
No. It reads public data. It holds no funds, lends nothing and calls no agent endpoint. The services listed in a metadata file are shown as text and never contacted.
Where does the data come from?
Robinhood Chain (chain id 4663) through its RPC, the ERC-8004 identity registry at 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432, Sourcify, Blockscout when this site has a key, and one fetch of the agent's metadata link.
Why is a fact marked Not available?
A source did not answer, refused a request, or the record does not exist there. The check says so instead of guessing. Log history that could not be read is named by block range.
Do I need $INTORA?
No. Every check, the change watch, saved reports and the check book work without the token. Paid features such as an API quota or advanced reports are planned, and their need for a token is unproven.
Is anything stored about me?
Saved reports and the watch list stay in your browser. The server keeps a short cache of public check results and rate-limit counters by network. Filing in the check book is a public transaction from your wallet.