[Dev Tools] forge script transactions never confirm

[coffeexcoin]

Team or Project

Abstract

Environment

Testnet

Select the Dev Tool you are using

Foundry

Provide the version of the tool (if applicable)

forge 0.0.2 (04e701d 2025-01-09T00:34:37.572492000Z)

Provide a brief description of the functionality you're trying to implement and the issue you are running into.

Transactions from forge script never confirm onchain

git clone git@github.com:Abstract-Foundation/ExclusiveDelegateResolver.git
cd ExclusiveDelegateResolver
forge script script/Deploy.s.sol --private-key $PRIVATE_KEY --zksync --rpc-url https://api.testnet.abs.xyz --broadcast

observe "stuck" tx

cast tx --rpc-url https://api.testnet.abs.xyz 0x620625ee7775d3914d6951ab651eb25a9c917023fe1209bf3bbf6c01e77eeb22

blockHash            
blockNumber          
from                 0x6f6426a9b93a7567fCCcBfE5d0d6F26c1085999b
transactionIndex     
effectiveGasPrice    413369589

hash 0x620625ee7775d3914d6951ab651eb25a9c917023fe1209bf3bbf6c01e77eeb22
type 113

chainId              11124
gas                  14531767
gasPrice             413369589
input                0x3cda335100000000000000000000000000000000000000000000000000000000000000000100018b657e62919934cb31860ab802a52b2c17cfd1e79ad5e635694f616c6a00000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000000
maxFeePerGas         413369589
maxPriorityFeePerGas 0
nonce                138931
r                    22081408820313273365422500258301439137968232983327240972453475748952968258067
s                    49470683134894003740503483802215141246397920716978219277888235235911370148802
to                   65536
v                    1
value                0

Attempt to run script, manually controlling the gas price

forge script script/Deploy.s.sol --private-key $PRIVATE_KEY --zksync --rpc-url https://api.testnet.abs.xyz --broadcast --with-gas-price 1500000000 --gas-price 1500000000

Observe with cast tx that transaction still does not confirm and is "stuck", not respecting the provided gas price

blockHash
blockNumber
from                 0x6f6426a9b93a7567fCCcBfE5d0d6F26c1085999b
transactionIndex
effectiveGasPrice    418145115

hash 0x9eedff94e85b35bfa37d3d93f9e744b28be44bb11846d2c9fc7be5dbed96d222
type 113

chainId              11124
gas                  14384973
gasPrice             287430567
input                0x3cda335100000000000000000000000000000000000000000000000000000000000000000100018b657e62919934cb31860ab802a52b2c17cfd1e79ad5e635694f616c6a00000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000000
maxFeePerGas         418145115
maxPriorityFeePerGas 0
nonce                138931
r                    6726089347089529013537645507859067477656859103032939902967637014144371875496
s                    33739183871783184467627149726482597223196860979393041111992036201871265150000
to                   65536
v                    1
value                0

Repo Link (Optional)

No response

Additional Details

Note, that this transaction did JUST finally confirm, with an effective gas price of 287430567 but the built in gas estimation does not seem to be setting gas price high enough for transactions to actually confirm.

[elfedy]

@coffeexcoin when broadcasting the transactions, we call zks_estimateFee and populate the transaction with those values. Are the fee params used in that transaction in line with what you would get using zks_estimateFee for that transaction? If so, is the estimation accurate?

[coffeexcoin]

I don't really know how to answer that question - my expectation and experience with foundry is that it usually uses a relatively higher gas price to ensure immediate inclusion when running scripts/deploying contracts.

The script in question is just this:

function run() public {
    vm.startBroadcast();
    // deploy resolver
    ExclusiveDelegateResolver resolver = new ExclusiveDelegateResolver{salt: bytes32(0)}();
    console.log("resolver", address(resolver));
    vm.stopBroadcast();
}

I would expect this to immediately confirm with a deployed contract, instead of sitting in a pending state waiting for gas to come down.

[elfedy]

The estimated maxFeePerGas set on your transaction (which should be EIP-1559) was 418_145_115, if I do a eth_gasPrice query I get 38_407_166, so the set max fee per gas is significantly bigger. Does the baseFee fluctuate that much on the network? . Are you sure this value was being set lower than the accepted network gas price? What makes you think this is what makes the transaction "stuck"? I tried a similar tx and it went through immediately, but next time try comparing the tx's maxFeePerGas with the gas on eth_gasPrice.
As regards specifying specific gas values in foundry we don't support this yet on zksync but it's on our pipeline.

[coffeexcoin]

The transaction was in a pending state for several minutes, which prompted me to kill the script and attempt to re-run it, which resulted in the same behavior. This in turn prompted me to investigate flags for increasing gas price on scripts, etc. After doing lots of research to figure out how to do so, I realized the flags were not being respected in forge and posted here. At that point my transaction finally went through.

[coffeexcoin]

Hi @elfedy - another team has flagged this as an issue to us as well, specifically around using forge script

[elfedy]

@coffeexcoin thanks for sharing. It would be nice if they can submit an issue on foundry-zksync with the exact problem they are having so we can look into it.