# ERC-8452 Draft Would Let Lenders Count Agent Defaults Onchain

Published 2026-10-20 · Crypto.world Team · Crypto.world

> A draft standard proposes a shared contract for recording loan defaults tied to agent identities and their owners. Lenders could query records from reporters they trust, while the proposal leaves cure rights and cross-chain reads open for discussion.

> “A default at one lender is invisible to the next: an agent, or its owner through another agent, borrows again elsewhere.”
>
> [Priors-agents, the proposal’s author](https://ethereum-magicians.org/t/erc-8452-agent-default-registry/30026)

A draft standard posted to the Ethereum Magicians forum on October 20 proposes a shared contract for recording loan defaults tied to agent identities. ERC-8452 would let lenders check records from other lenders when opening a credit line, rather than relying solely on their own loan histories. The draft is not yet submitted to the Ethereum ERC repository, and its number remains provisional.

## ERC-8452 ties each default to an agent and owner

The proposed registry records each default as an individual loan event, keyed to an ERC-721 identity token and the owner address recorded for that loan. Each entry also includes the asset, principal and a loan reference that cannot be reused by the same reporter; another reporter, such as a lender and servicer, may record the same loan. A later cure can be recorded with the amount recovered, allowing readers to distinguish open defaults from cured ones.

That owner-level index addresses a specific lending risk in the proposal: an agent owner could borrow through another agent identity after a default. The draft says a lender’s contract could query both an identity’s history and its owner’s history during the transaction that opens a credit line. Its reference implementation and tests are in the [project’s GitHub repository](https://github.com/priors-agents/ERC-8452).

## Each lender decides which reporters count

Anyone may submit a default record, but the registry does not make every submission authoritative. A contract reading the registry counts only entries from reporters it trusts, leaving lenders to choose their own sources rather than rely on a universal score. The draft says query costs grow with the reader’s list of trusted reporters, not with the total number of records submitted by everyone else.

The proposal distinguishes that record-by-record approach from ERC-8004 feedback, which it describes as averaging values, and ERC-8419 KYA, which it says keeps one latest assertion per issuer. Neither, the draft argues, is designed to count separate loan defaults. ERC-8452 instead keeps each reported loan outcome available for a contract to inspect.

## Cure rights and cross-chain reads remain unresolved

The proposer raises two open design questions in the forum post: whether an agent’s owner should be able to record a cure with the lender’s signature, or whether only the original reporter should do so; and whether a per-chain registry is sufficient or lenders need cross-chain reads from the start. Those choices affect who can update a record and whether a lender can see a history that spans networks. The draft does not settle either question.

## The draft has code, but no submitted ERC

The repository labels ERC-8452 a draft that has not been submitted and says the number is the next one available as of October 20, subject to confirmation by ERC editors. It includes a reference contract, an interface and Foundry tests; the repository says the implementation is not audited. The proposal’s immediate scope is therefore a record-and-query design, not a deployed standard or a cross-chain credit system.

*Update, October 22:* After this story was published, the proposal’s forum thread was retitled “ERC-TBA: Agent Default Registry”, dropping the 8452 number that the repository had said was subject to confirmation by ERC editors. In a forum reply late on October 20, the author settled one of the questions the post had left open: a cure “stays reporter-only”, so only the reporter that recorded a default can mark it cured. The author also proposed letting a reporter name a primary address, so that a loan recorded from two of a lender’s addresses counts once, and letting a reporter void its own record within a short window after recording it.

## Sources

1. Original source [Fellowship of Ethereum Magicians](https://ethereum-magicians.org/t/erc-8452-agent-default-registry/30026) ethereum-magicians.org

Other pages read

2. [GitHub](https://github.com/priors-agents/ERC-8452) github.com

## Related stories

- [ERC-8454 Draft Adds a Bar Against Double-Counting Agent Claims](https://crypto.world/news/erc-8454-draft-agent-economic-units-double-counting)
- [THORChain v3.21 Packs Fixes for Rujira and Halted Trading](https://crypto.world/news/thorchain-v321-rujira-halted-trading-fixes)
- [Crypto Lending Vaults Top $10B as Regulators Weigh Oversight](https://crypto.world/news/crypto-lending-vaults-top-10-billion-regulatory-scrutiny)
- [France Seeks MiCA Accountability Rules for DeFi Gateways](https://crypto.world/news/france-mica-accountability-defi-gateways)
- [Aerodrome and Velodrome Relaunch as Seven-Chain DEX Aero](https://crypto.world/news/aerodrome-velodrome-relaunch-seven-chain-dex-aero)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/erc-8452-agent-default-registry
