A map of the agent-mandate ERCs — what each one actually does
Corrected 14 August. The ERC-8226 row originally described its enforcement as taking place in a regulated token’s pre-transfer hook. That is one of three venues its specification defines, not the definition — corrected below after @thamerdridi pointed it out. Thread activity figures are still as collected on 13 August. If you are trying to work out how to bound what an autonomous agent may do on-chain, you will find a dozen ERCs that sound like they answer the question. Most of them answer a different one. Working out which is which took me a week, so here is the map, with the method attached so you can check it rather than trust it. This is not a critique of anyone’s work. Several of the standards below deliberately exclude what I was looking for, and say so. Method Titles are misleading in this space — “agent”, “delegation” and “permission” appear in proposals that have nothing to do with each other. So I ranked the corpus by content. Every ERC in ethereum/ERCs was listed ( 611 files ), those numbered ≥ 7000 kept ( 271 ), their full text downloaded (~5.1 MB) and scored against 11 concept patterns: delegation, attenuation, sub-agent, inheritance, cap, revocation, expiry, identity, AI-agent, caveat, session. The top of that ranking was then read end to end — specification and discussion thread, not abstracts. Five threads, 73 posts. The ranking is a filter, not a verdict. ERC-7303 scored third and is a false positive — token-based role access control, nothing to do with agents. Scope limit, stated up front. The corpus is the merged ethereum/ERCs tree. Open pull requests and forum-only drafts are outside it — ERC-8165 (PR #1549 , open since February) is one such case, and it sits on the intent/solver layer rather than this one. The map (thread activity as of 13 August 2026) ERC What it actually does Status Thread 8226 Regulated Agent Mandate A principal grants a scoped, capped, time-bounded mandate to one agent. Per-transaction and cumulative caps, freeze, compliance provider. Enforcement is venue-agnostic : a regulated token’s pre-transfer hook, an EIP-7702 delegated account, or a dedicated executor — all read the same mandate. Draft live — 12 posts, last 2026-08-12 8196 AI Agent Authenticated Wallet Executes only with cryptographic proof that the action complies with an owner-defined policy. Hash-chained audit trail, entropy commit-reveal against host manipulation. Layer 2 of a stack with ERC-8126. Final 14 posts, last 2026-07-20 8199 Sandboxed Smart Wallet Containment by isolation: the agent’s wallet fully detached from the owner’s, the relationship one-directional. Draft dormant — 2 posts, 93 views 8273 Attestation-Gated Agentic Actions Per-operation attestation, authorized in EIP-1153 transient storage and cleared at the end of the transaction. Draft — 7715 Request Permissions from Wallets The request side: a JSON-RPC method for a dapp to ask a wallet for permissions. Requires 4337 and 7710. Draft 10 posts, last 2026-04-29 7710 Smart Contract Delegation A single function, redeemDelegations , for redeeming a delegation against a Delegation Manager. Draft dormant — 35 posts, 6.2k views, last 2025-04-30 Three things that are easy to get wrong from the abstracts: 8273 is not a session system. Its own text: “There is no expiration mechanism, and there are no long-lived or session-based attestations.” Authorization exists for one transaction. If you need state that outlives a call, this is the wrong axis — not a weaker version of the right one. 7710 does not specify caveats. The ERC is one function. Caveat enforcement, delegation chains and revocation appear only as features of the MetaMask Delegation Framework , its reference implementation. The standard also declares acquisition out of scope: “The process by which a delegate obtains a delegation is intentionally left out of scope.” Its Security Considerations section currently ends with Needs discussion. . 8196 is Final. Whatever you think of it, it is not going to change. The empty square None of the 271 standardizes attenuated re-delegation : a child agent that comes into existence already bounded by its parent, on every clause, with the bound non-strippable. The closest candidate is ERC-8226, and it is worth being precise about why it is not that. Its mandate is keyed by (agent, principal) ; only the principal can grant. An agent holding a valid mandate cannot create anything. Searching its reference implementation for the vocabulary of lineage — grep -rniE "child|parent|sub-?agent|inherit|lineage|spawn|attenuat" contracts/ test/ — returns only @inheritdoc , a Solidity documentation tag. The concept is absent from the code, not merely from the prose. That is not a defect. @thamerdridi made the point directly on my own thread, and was right to: a spawned child inherits nothing under RAMS, including the authority to act , so reproduction cannot be used to escape a mandate. Inheritance is out of scope by design. The honest phrasing is “ERC-8226 does not define mandate inheritance”, not “ERC-8226 can be bypassed.” The same care applies to the others. 8199 refuses granular sharing on principle, arguing that session-key-style approaches “inherently bring in permission evasion issues” . 8273 is transaction-scoped by construction. 7715 is a request protocol, not an enforcement layer. None of these is an oversight; they are four different answers to four different questions. The square is empty because nobody has claimed it, not because everybody missed it. Reproduce it gh api repos/ethereum/ERCs/contents/ERCS --paginate | jq -r '.[].name' curl -sL https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-8226.md curl -s "https://ethereum-magicians.org/t/28208.json?include_raw=true&print=true" ERC-8226’s reference implementation compiles and its own test suite passes — 72 tests, 0 failures — with OpenZeppelin resolved from master (the v5.1.0 tag does not exist) and forge-std supplied locally. Worth doing: reading a specification and running it are not the same activity, and the second one is cheap. Disclosure I work on ERC-8370, which is an attempt at the empty square. That is why I read all of this, and you should weigh the map accordingly — though every claim above is checkable with the three commands in the previous section, which is rather the point. Corrections welcome, especially from the authors of anything listed here. If I have mischaracterized your standard’s scope, say so and I will fix it — the version I keep updated lives at interop/standards-map.md in the ERC-8370 repository. 8 posts - 5 participants Read full topic
TL;DR
In August 2026 the Federal Reserve fined American Express for AML lapses, the CFTC gave markets a path to true perpetual futures, MEXC posted reserve ratios above 100% for major assets, and the Sweat Foundation announced its wallet and token will close on Dec 30 2026. These moves highlight tighter regulation, increased transparency, and the fragility of token‑reward models.
Key facts
- The Federal Reserve announced an enforcement action against American Express on August 13, 2026.
- The CFTC issued no‑action relief for converting perpetual‑style index futures to true perpetual futures, expiring on October 20, 2026.
- MEXC’s August 2026 proof‑of‑reserves shows a BTC reserve ratio of 288% covering 4,282.20 BTC.
- Sweat Wallet and the SWEAT token will end in their present form on December 30, 2026.
On August 13, 2026 the Federal Reserve announced an enforcement action against American Express for failures in its anti‑money‑laundering program, while the CFTC issued a no‑action letter allowing designated contract markets to convert perpetual‑style index futures into true perpetual contracts. In the same week MEXC published its August proof‑of‑reserves showing BTC coverage of 288% and USDT coverage of 115%, and the Sweat Foundation disclosed that its Sweat Wallet and SWEAT token will cease operating in their current form on December 30, 2026. The announcements involve major financial regulators, a leading crypto exchange, and a high‑profile wellness‑linked token project.
Background
The Federal Reserve’s enforcement action stems from a broader regulatory focus on money‑laundering controls in the payments sector. The Board highlighted deficiencies in American Express’s enterprise‑wide AML program, especially at its national‑bank subsidiary, and noted that the Office of the Comptroller of the Currency has also taken separate action against that bank. Meanwhile, the Commodity Futures Trading Commission’s Division of Market Oversight has been reviewing the structure of perpetual futures contracts, concluding that designated contract markets may remove expiration dates from existing broad‑based security index futures provided they meet specific customer‑protection conditions. In the crypto market, exchanges have been under pressure to demonstrate solvency. MEXC responded by releasing a monthly proof‑of‑reserves audit conducted by Hacken, showing reserve ratios well above 100% for major assets and detailing its insurance and guardian funds. At the same time, the Sweat Foundation, which operated the Sweat Wallet and the SWEAT token that rewarded users for verified movement, announced an orderly wind‑down of its current model due to an unsustainable economic environment, loss of exchange listings, and a security incident earlier in the year. The announcement gave users 90 days to claim tokens and migrate assets, contrasting with the foundation’s standard 14‑day notice period.
What happened
The Federal Reserve Board released a statement on August 13, 2026 announcing an enforcement action against American Express Company for failing to sufficiently detect and report suspicious activity related to money laundering. The Board also cited significant deficiencies in the firm’s enterprise‑wide anti‑money‑laundering program, particularly at its national‑bank subsidiary, and noted that the Office of the Comptroller of the Currency has issued a separate enforcement action against that bank. On the same day, the Commodity Futures Trading Commission issued Release Number 9308‑26, granting no‑action relief to designated contract markets that wish to convert existing perpetual‑style broad‑based security index futures into true perpetual futures. The CFTC outlined conditions such as soliciting feedback from market participants, providing advance notice and exit opportunities, offering risk disclosures, and filing amendments under CFTC Regulations 40.5 or 40.6. The no‑action relief is set to expire on October 20, 2026. In parallel, MEXC published its August 2026 proof‑of‑reserves report, independently audited by Hacken, showing a BTC reserve ratio of 288% covering 4,282.20 BTC and a USDT reserve ratio of 115% covering 1,691,925,884.19 USDT, along with similar coverage for USDC, ETH, and other assets. The exchange also highlighted its Futures Insurance Fund of 751 million USDT and a Guardian Fund planned to expand from $100 million to $500 million over two years. Finally, the Sweat Foundation announced that Sweat Wallet and the SWEAT token in their present form will cease on December 30, 2026. The foundation gave users until mid‑December to back up private keys, claim earned SWEAT, withdraw from Grow Jars, and move balances on Ethereum, Base, BSC, or Arbitrum to personal wallets or bridge them to NEAR. The announcement cited a prolonged crypto market downturn, loss of exchange listings, a security incident in April 2026, and insufficient profitability as reasons for the wind‑down.
Market impact
The Federal Reserve’s action against American Express may prompt other payment processors to review AML controls, potentially increasing compliance costs across the sector. The CFTC’s no‑action relief could accelerate the migration of perpetual‑style index futures to true perpetual contracts, influencing trading volumes on designated contract markets that meet the stipulated conditions. MEXC’s proof‑of‑reserves figures, with a BTC reserve ratio of 288% and USDT coverage of 115%, suggest a strong liquidity buffer that may attract risk‑averse traders and reinforce confidence in the exchange’s ability to meet redemption demands. The disclosed Futures Insurance Fund of 751 million USDT and the planned expansion of the Guardian Fund to $500 million indicate a substantial capacity to absorb liquidation losses, which could stabilize futures trading on the platform. The Sweat Foundation’s wind‑down announcement signals the removal of a token that once attracted over 22 million users, potentially reducing on‑chain activity related to SWEAT and affecting liquidity on NEAR and bridged EVM chains. Users moving assets before the December deadline may generate short‑term sell pressure on SWEAT and associated bridge tokens, while the cessation of Grow Jar contracts could impact yield‑generating strategies tied to the token.
Why it matters
The enforcement action against American Express underscores heightened regulatory scrutiny of AML compliance in the payments industry, signaling that large financial institutions cannot overlook detection and reporting obligations. The CFTC’s no‑action letter provides a regulatory pathway for markets to innovate with perpetual futures, which could reshape how investors hedge and speculate on broad‑based security indexes. MEXC’s audited reserve ratios and insurance mechanisms demonstrate a growing emphasis on transparency and risk mitigation in the crypto exchange space, setting a benchmark for other platforms. The orderly shutdown of Sweat Wallet and the SWEAT token highlights the challenges of sustaining token‑based incentive models amid market downturns and security incidents, offering a cautionary tale for projects that rely on continuous user acquisition and token economics. Collectively, these developments illustrate a convergence of regulatory enforcement, market structure evolution, and operational risk management that will influence participant behavior across traditional finance and decentralized finance ecosystems.
DeFi Intel’s take
Editorial analysis, not a statement of fact.
DeFi Intel's take: the simultaneous regulatory actions and market disclosures suggest a tightening of oversight and a push for greater transparency across both legacy finance and crypto. The Federal Reserve’s enforcement against American Express may encourage other payment firms to pre‑emptively strengthen AML systems, while the CFTC’s no‑action relief could accelerate the adoption of true perpetual futures, offering traders more flexible instruments. MEXC’s high reserve ratios and expanding insurance funds indicate that exchanges are responding to user demand for safety, potentially raising the bar for industry standards. The Sweat Foundation’s wind‑down reflects the fragility of token‑reward models when market conditions sour, warning new projects to build more resilient economics. Overall, these signals point to a landscape where compliance, risk buffers, and sustainable token design become critical success factors.
Sources used for this analysis
- federalreserve.gov/newsevents/pressreleases/enforcement20261008a.htm
- cftc.gov/PressRoom/PressReleases/9308-26
- coinjournal.net/news/mexcs-august-2026-proof-of-reserves-confirms-user-assets-fully-backed
- cryptobriefing.com/sweat-wallet-and-the-sweat-token-as-they-exist-today-end-on-30-december
DeFi Intel wrote this analysis from the reporting above. Any figure or quotation can be checked against those pages.
Frequently asked questions
What regulatory action did the Federal Reserve take against American Express?
The Federal Reserve announced an enforcement action on August 13, 2026, citing failures in American Express’s anti‑money‑laundering program, especially at its national‑bank subsidiary, and noted a separate action by the Office of the Comptroller of the Currency against that bank.
What does the CFTC’s no‑action letter allow designated contract markets to do?
The CFTC’s letter permits designated contract markets to remove expiration dates from existing perpetual‑style broad‑based security index futures and convert them into true perpetual futures, provided they meet customer‑protection conditions, give advance notice, disclose risks, and file amendments under Regulations 40.5 or 40.6.
What are the key figures from MEXC’s August 2026 proof‑of‑reserves report?
MEXC’s audited report shows a BTC reserve ratio of 288% covering 4,282.20 BTC, a USDT reserve ratio of 115% covering 1,691,925,884.19 USDT, a USDC ratio of 114% covering 170,998,567.28 USDC, and an ETH ratio of 113% covering 58,457.33 ETH, alongside a Futures Insurance Fund of 751 million USDT.
Direct answers
Short answers, written to be quoted.
- Why did the Federal Reserve take action against American Express?
- The Federal Reserve acted because American Express failed to sufficiently detect and report suspicious activity related to money laundering and had significant deficiencies in its enterprise‑wide AML program.
- What conditions must designated contract markets meet to convert futures contracts under the CFTC’s relief?
- They must solicit feedback from participants with open positions, give advance notice and exit opportunities, provide risk disclosures, avoid changing other material terms, file amendments under Regulations 40.5 or 40.6, and certify compliance.
- What steps does the Sweat Foundation advise users to take before the wallet shuts down?
- Users should back up private keys and NEAR account IDs, claim earned SWEAT, withdraw from Grow Jars, and move balances on Ethereum, Base, BSC, or Arbitrum to personal wallets or bridge them to NEAR before mid‑December 2026.
DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at Ethereum_magicians.
Entities in this story
Discussion
Comments are reviewed before publication.
Want the full article?
Continue reading on Ethereum_magicians →
No comments yet.