Runtime size of VRFCoordinatorV2_5Mock exceeds the permissible limits of EVM.

[web3pavlou]

I am currently on lesson "33.Fund Subscription" on Smart Contract Lottery lesson.I ve eben trying to run this script command:

ETHERSCAN_API_KEY=<my etherscanapi key> forge script script/Interactions.s.sol:FundSubscription   --rpc-url $SEPOLIA_RPC_URL   --account myAccount   --broadcast

everything seems to run smoothly except i get this one error in my logs:

Error: `Unknown0` is above the contract size limit (25068 > 24576).

I did some digging with this command forge build --sizes and found out that VRFCoordinatorV2_5Mock has a runtime size of 25,068 bytes (492 bytes above the 24,576 byte contract size limit) which exceeds the permissible limit of EVM.

What should be my next steps?Should i keep pushing forward and burn GAS even though i know it will revert or should i make adjustments anywhere in my project?

Edit:
I checked this topic here #3593 but besides an interesting article about downsizing a contract i couldnt find the solution,as every function inside VRFCoordinatorV2_5Mock seems important to me and i dont have the confidence yet breaking it up into 2 contracts and managing the storage accordingly.

[EngrPips]

I saw someone comment out some functions their code didn't use from the VRFCoordinatorV2_5Mock, to make the size fit the limit, maybe you can do the same.

[EngrPips]

You can import console in the VRFCoordinatorV2_5Mock file and use console.log in every function of the file and any function that didn't print to the console is assumed not to be used in your process and you can comment it out.

[web3pavlou]

You can import console in the VRFCoordinatorV2_5Mock file and use console.log in every function of the file and any function that didn't print to the console is assumed not to be used in your process and you can comment it out.

Ok,i ll try this out and get back with an answer.Thanks for your patience.

[EngrPips]

Any time, Friend. I am looking forward to how things play out.

[web3pavlou]

---

Update

After I ran several console.log statements on VRFCoordinatorV2_5Mock.sol, I ended up at this function, which turned out not to be needed anywhere:

function removeConsumer(
    uint256 _subId,
    address _consumer
) external override onlySubOwner(_subId) onlyValidConsumer(_subId, _consumer) nonReentrant {
    if (!s_consumers[_consumer][_subId].active) {
        revert InvalidConsumer(_subId, _consumer);
    }
    address[] memory consumers = s_subscriptionConfigs[_subId].consumers;
    uint256 lastConsumerIndex = consumers.length - 1;
    for (uint256 i = 0; i < consumers.length; ++i) {
        if (consumers[i] == _consumer) {
            address last = consumers[lastConsumerIndex];
            s_subscriptionConfigs[_subId].consumers[i] = last;
            s_subscriptionConfigs[_subId].consumers.pop();
            break;
        }
    }
    s_consumers[_consumer][_subId].active = false;
    emit SubscriptionConsumerRemoved(_subId, _consumer);
}

Although I experimented with commenting it out and excluding other parts of the file, it always ended up breaking something due to interface requirements.

Solution: Stub Implementation

At the end, I removed the logic from inside the function and made a "Stub Implementation," which reduces code size but keeps the interface satisfied. That made the contract deployable and everything else ran as expected.

function removeConsumer(uint256, address) external override {
    // Stub: Intentionally left blank to reduce runtime size and satisfy the interface.
}

---

Results

When I run:

forge build --sizes

I get:

| Contract                | Runtime Size (B) | Initcode Size (B) | Runtime Margin (B) | Initcode Margin (B) |
|-------------------------|------------------|-------------------|--------------------|---------------------|
| VRFCoordinatorV2_5Mock  | 24,113           | 26,156            | 463                | 22,996              |

So now I’m able to deploy without problems, as 24,576 > 24,113 (the runtime size limit is not exceeded).

---

Note for Others

I have the feeling that many will stumble upon this issue when trying to run the script with:

forge script script/Interactions.s.sol:FundSubscription --rpc-url $SEPOLIA_RPC_URL --account myAccount --broadcast

This stub solution works well to satisfy interface requirements and stay within size limits.

---

I believe this was a solid solution for this one—thanks for helping me out!

---

[EngrPips]

I am glad you figured it out. Keep crushing it.

[matcherbudz]

Update

After I ran several console.log statements on VRFCoordinatorV2_5Mock.sol, I ended up at this function, which turned out not to be needed anywhere:

function removeConsumer(
    uint256 _subId,
    address _consumer
) external override onlySubOwner(_subId) onlyValidConsumer(_subId, _consumer) nonReentrant {
    if (!s_consumers[_consumer][_subId].active) {
        revert InvalidConsumer(_subId, _consumer);
    }
    address[] memory consumers = s_subscriptionConfigs[_subId].consumers;
    uint256 lastConsumerIndex = consumers.length - 1;
    for (uint256 i = 0; i < consumers.length; ++i) {
        if (consumers[i] == _consumer) {
            address last = consumers[lastConsumerIndex];
            s_subscriptionConfigs[_subId].consumers[i] = last;
            s_subscriptionConfigs[_subId].consumers.pop();
            break;
        }
    }
    s_consumers[_consumer][_subId].active = false;
    emit SubscriptionConsumerRemoved(_subId, _consumer);
}

Although I experimented with commenting it out and excluding other parts of the file, it always ended up breaking something due to interface requirements.

Solution: Stub Implementation

At the end, I removed the logic from inside the function and made a "Stub Implementation," which reduces code size but keeps the interface satisfied. That made the contract deployable and everything else ran as expected.

function removeConsumer(uint256, address) external override {
    // Stub: Intentionally left blank to reduce runtime size and satisfy the interface.
}

Results

When I run:

forge build --sizes

I get:

| Contract                | Runtime Size (B) | Initcode Size (B) | Runtime Margin (B) | Initcode Margin (B) |
|-------------------------|------------------|-------------------|--------------------|---------------------|
| VRFCoordinatorV2_5Mock  | 24,113           | 26,156            | 463                | 22,996              |

So now I’m able to deploy without problems, as 24,576 > 24,113 (the runtime size limit is not exceeded).

Note for Others

I have the feeling that many will stumble upon this issue when trying to run the script with:

forge script script/Interactions.s.sol:FundSubscription --rpc-url $SEPOLIA_RPC_URL --account myAccount --broadcast

This stub solution works well to satisfy interface requirements and stay within size limits.

I believe this was a solid solution for this one—thanks for helping me out!

Thank you!! I'm reviewing this lesson and I remember not being able to figure out how to fix this issue. Now that I understand more I'm excited to get to testing out the mocks and getting it posted to my github