folia-app/eip-2929

to fix `.transfer()` methods directed to gnosis safe because of berlin hardfork (aka fix eip-2929 with eip-2930)

Fix eip 2929 with eip 2930

After the berlin hardfork eip 2929 was added which increased the cost for state access opcodes. This broke any contract which used address.transfer(eth) to gnosis safes because the hard-coded 2300 gas was no longer enough to execute the transaction. In order to help contracts that were affected they made eip 2930 which adds an access list to the transaction. Any address added to this access list has gas prepaid on their behalf as part of the total gas calculation. This reduces the gas required when interacting with them which allows the original 2300 gas to succeed.

Note: Apparently this only works with ethers at the moment.

For our situation we needed to run endAuction(11000003) on our auction contract that would allow the transfer to two different gnosis safes to occur.

Look at ./index.js for a complete example.

(shout out @rmeissner for the help here)

eip-2929's Issues

Where can I find my Gnosis Safe related addresses?

Hi,

I wonder what do these addresses correspond to:

• admin gnosis safe proxy address ?
• proceedsRecipient gnosis safe proxy address ?
• gnosis safe master address ?

Are they specific per Gnosis Safe ?

In this article they say we should whitelist "the receiving Safe and the address of the Safe singleton".

Also what should I put in storageKeys ?

Thanks a lot.