← Opportunities

Resolving 2300 Gas Reverts for Smart Contract Wallets in ENS Controller

Funder
ENS Foundation / ENS DAO 🟑 Some evidence
Type / status
other Β· open
Amount
3,000 – 7,500 USDC
Deadline
rolling
Ecosystems
ethereum
Categories
infradev tooling
Tech stack
solidityfoundry
Apply
https://github.com/ensdomains/ens-contracts/pull/577
Source
https://discuss.ens.domains/t/proposal-core-contribution-resolving-2300-gas-reverts-for-smart-contract-wallets-erc-4337-safe-in-ens-controller-pr-577/22464
Fit
40% Β· weak fit Β· The team's expertise in protocol engineering and ZK infrastructure aligns with the ENS infrastructure upgrade, though they operate primarily in the Aleo ecosystem rather than Ethereum, making them a credible but slightly adjacent applicant.
Trust
55% Β· model self-report 60% Β· first seen 2026-10-23 Β· v1
Verified
2026-11-14 Β· page still up, no closing language

A developer is requesting a retroactive grant from the ENS Foundation or DAO for a fix to ENS smart contracts that replaces .transfer() with .call() to support smart contract wallets like Gnosis Safe and ERC-4337 accounts. The work includes updating ETHRegistrarController.sol, BulkRenewal.sol, and StaticBulkRenewal.sol, along with a Foundry test suite. Applicants should review and merge GitHub PR #577 and consider funding the engineering and testing effort.

Eligibility: ENS core development team and community reviewers; grant request directed at ENS Foundation / DAO

Pipeline

Override status:

Funder track record Β· does ENS DAO actually pay grants?

🟑 Some payout evidence · 5 grantees found · last payout 2025-07-01 · checked 2026-10-24 · 0 forum reports, 7 web pages read, 22 unverifiable claims dropped

Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.

GranteeAmountDateEvidence
evmone$14,5882025-07-01β€œThis grant funds the work of one engineer to continue maintaining evmone.” source
Claveβ€”2024-07-18
page date
β€œWe've proudly announced that Clave become one of the Public Goods 2023 grantees” source
GasHawkβ€”2024-07-18
page date
β€œGashawk used part of its grant to subsidize user fees and developed webhooks, a browser extension, and multi-chain support.” source
Revoke.cashβ€”2024-07-18
page date
β€œRevoke.cash used its grant to develop NFT pricing data and integrate "Value at Risk" alerts for risky approvals.” source
10kclub$10k2022-06-01β€œENS DAO provided $10k of funding to the 10kclub” source
Revoke.cashβ€”undatedβ€œ1 Revoke.cash Public Goods 6 rounds ~56.6% avg share of round 3.7M voting power” source

Trust breakdown (3/4 checkable facts verified)

SignalWeightResultNote
deadline0.350%rolling claimed but not stated
amount0.25100%figure appears in source
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1560%forum post
model confidence0.160%model self-report

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.570%model rated 70%
ecosystem overlap0.250%ethereum vs aleo
category overlap0.1533%infra, dev_tooling vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.10%solidity, foundry vs rust, leo, zk

Sources (1)

RoleDocumentFromFetched
primaryProposal & Core Contribution] Resolving 2300 Gas Reverts for Smart Contract Wallets (ERC-4337 & Safe) in ENS Controller β€” PR #577ENS forum2026-10-03

History (1)

vChangedFields
12026-10-23created

Extracted text

**Category:** Ecosystem / Development  
**Author:** Boreal-Proof ([@aeosproof](https://github.com/aeosproof))  
**GitHub Pull Request:** [ensdomains/ens-contracts#577](https://github.com/ensdomains/ens-contracts/pull/577)  
**Status:** Open / Ready for Review

```
---

## Executive Summary

We have submitted:**Pull Request [#577](https://github.com/ensdomains/ens-contracts/pull/577)** to `ensdomains/ens-contracts` to address a compatibility limitation affecting Smart Contract Wallets (e.g., Gnosis Safe, Argent,ERC-4337 Smart Accounts) during .eth name registrations and renewals.
```

```
Currently, `ETHRegistrarController.sol` and `BulkRenewal.sol` rely on Solidity's built-in `.transfer()` to return excess ETH refunds. Because `.transfer()` forwards a fixed stipend of only **2,300 gas**, transactions initiatedby smart contract accounts that perform event logging or state updates in their receive() functions consistently revert with Out of Gas (OOG).
```

````
PR #577 replaces `.transfer()` with modern `.call{value: ...}("")` across the affected contracts, accompanied by reproducible Foundry unit tests. We are submitting this proposal to:
1. Solicit feedback and review from the ENS core development team.
2. Request ecosystem grant / retroactive public goods consideration from the ENS Foundation for this core infrastructure improvement.

---

## Background & Motivation

When users register or renew names via `ETHRegistrarController`, they frequently provide extra ETH (`msg.value > totalPrice`) to account for oracle price fluctuations or slippage during commitment-reveal intervals.

When surplus ETH is refunded:
```solidity
if (msg.value > totalPrice)
    payable(msg.sender).transfer(msg.value - totalPrice);
````

### [](#p-62499-the-problem-1)The Problem:

β€’ .transfer() forwards a hardcoded 2,300 gas stipend.  
β€’ Following EIP-1884 (gas repricing) and the standard adoption of Smart Contract Wallets (Gnosis Safe multi-sigs, DAOs, ERC-4337 bundler targets), almost all smart accounts execute logic (e.g., emit ExecutionSuccess, state  
bookkeeping, or module delegation) in their receive() or fallback() hooks that consumes significantly more than 2,300 gas.  
β€’ As a result, DAOs and institutional multi-sig vaults attempting to register names with a buffer revert, creating a broken user experience for Ethereum’s most security-conscious participants.  
β€’ Furthermore, in ETHRegistrarController.sol, the owner withdrawal function withdraw() uses .transfer(address(this).balance). If the contract owner is a timelock or multisig requiring >2,300 gas, withdrawals can be permanently  
locked out.  
──────

## [](#p-62499-technical-specification-pull-request-577-2)Technical Specification & Pull Request #577

PR #577 introduces a drop-in update to replace .transfer() with low-level .call and boolean verification:

### [](#p-62499-affected-files-3)Affected Files:

1.  contracts/ethregistrar/ETHRegistrarController.sol (lines 344, 371, 376):  
    β€’ register(): Surplus refund updated to .call.  
    β€’ renew(): Surplus refund updated to .call.  
    β€’ withdraw(): Owner balance withdrawal updated to .call.
2.  contracts/ethregistrar/BulkRenewal.sol (line 73):  
    β€’ renewAll(): Excess refund updated to .call.
3.  contracts/ethregistrar/StaticBulkRenewal.sol (line 54):  
    β€’ renewAll(): Excess refund updated to .call.

### [](#p-62499-security-reentrancy-analysis-checks-effects-interactions-4)Security & Reentrancy Analysis (Checks-Effects-Interactions):

In all instances, the external .call is executed strictly after:

β€’ All state mutations are finalized (resolver configuration, reverse record bitwise checks, expiry updates).  
β€’ All canonical events are emitted (emit NameRegistered, emit NameRenewed).  
β€’ Execution follows the strict Checks-Effects-Interactions pattern, mitigating reentrancy attack vectors.  
──────

## [](#p-62499-verification-unit-testing-5)Verification & Unit Testing

To ensure 100% test reproducibility, PR #577 includes a dedicated Foundry test suite in test/SmartWalletRefundTest.t.sol:

```
contract SmartWalletRefundTest is Test {
    // Validates that legacy .transfer reverts on Smart Accounts with active receive() hooks
    function test_legacyTransferRevertsForSmartWallet() public;

    // Validates that modern .call successfully delivers 100% of the surplus refund
    function test_modernCallSucceedsForSmartWallet() public;
}
```

### [](#p-62499-test-results-6)Test Results:

```
forge test --match-contract SmartWalletRefundTest
[PASS] test_legacyTransferRevertsForSmartWallet() (gas: 50297)
[PASS] test_modernCallSucceedsForSmartWallet() (gas: 71964)
Suite result: ok. 2 passed; 0 failed; 0 skipped
```

──────

## [](#p-62499-funding-request-community-value-7)Funding Request & Community Value

Account Abstraction and institutional multi-sig adoption are core pillars of Ethereum’s roadmap. Ensuring that ENS registration controllers natively support smart contract accounts without artificial 2,300 gas reverts is essential  
public infrastructure.

We respectfully request:

1.  Core Review: Review and merge of PR #577 [fix(ethregistrar): replace .transfer() with .call() to support smart contract wallets by aeosproof Β· Pull Request #577 Β· ensdomains/ens-contracts Β· GitHub](https://github.com/ensdomains/ens-contracts/pull/577) into staging.
2.  Retroactive Grant / Public Goods Funding: Consideration from the ENS Foundation / DAO for a developer grant ($3,000 – $7,500 USDC) to cover the research, engineering, formalization, and test suite implementation of this  
    compatibility patch.

We look forward to collaborating with the ENS team and community on this implementation!