ERC-8210’s “Delegated Funding (Reserved)” section sets third-party Backers aside for “a separate ERC”. We have drafted one and would like to bring it here first, so the agent ERC family ends up with one backer standard, not two.
Agent Credit Backers lets a third party (a staker, a collateral vault, an insurer) stand behind a lender’s line to an agent identity, with the identity owner’s EIP-712 consent. The lender asks the backer before each draw (canBorrow), tells it of each draw (onBorrow), and on a default takes the principal from the backer and tells it (onDefault, with what was paid); lowered, removed or replaced lines are told once each (onRelease). Neither a backer nor the lent asset can block a repayment, a default or a removal: notifications run with a fixed gas budget, failures are logged, and calls to the asset are bounded too. It extends the Agent Credit Lines draft. An ERC-8320 GUARANTEE claim states a guarantee; these hooks are what enforce it on each draw and default.
Questions for the ERC-8210 authors and readers:
- Would you rather fold this into ERC-8210’s reserved section, or keep it a separate ERC that 8210 references?
depositFor(agent, amount)in 8210’s plan funds an agent directly; here a backer stands behind a lender’s line. Should one standard cover both?- Take-then-notify on default (the lender takes the principal, then tells the backer) versus notify-then-take, which would let a collateral vault convert collateral inside the hook.