[General] "bricked" account on abstract testnet

[coffeexcoin]

Team or Project

Abstract - Swipe

Environment

Testnet

L2 block number

3476111

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

Account 0xB5c1720A56eD291DEb34e5c00Bd741dB3FD0A6Ab is completely unable to send any transactions anymore - they are accepted by RPC but then never confirmed by the sequencer.

cast send --rpc-url https://api.testnet.abs.xyz --private-key $PRIVATE_KEY 0xe06ad0Acb3956f98C9dF77Bd02cdFD4426b2208d --value 0 --async --nonce 114 --gas-price 1000000000
0xf30254d510bc3e4dcd9ca3863512985564bb5c364557c552a12166b366e2e248

cast send --rpc-url https://api.testnet.abs.xyz --private-key $PRIVATE_KEY 0xe06ad0Acb3956f98C9dF77Bd02cdFD4426b2208d --value 0 --async --nonce 114 --gas-price 1000000000
Error: server returned an error response: error code 3: known transaction. transaction with hash 0xf302…e248 is already in the system, data: "0x"

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

blockHash            
blockNumber          
from                 0xB5c1720A56eD291DEb34e5c00Bd741dB3FD0A6Ab
transactionIndex     
effectiveGasPrice    1000000000

hash                 0xf30254d510bc3e4dcd9ca3863512985564bb5c364557c552a12166b366e2e248
type                 2

chainId              11124
gas                  143400
gasPrice             1000000000
input                0
maxFeePerGas         1000000000
maxPriorityFeePerGas 1
nonce                114
r                    82253337761489928337287897518286872413812254673162847160579663940691591901697
s                    57813921047045657759728000083469964565488403984348675503091942873271849557365
to                   1281195989778332942943990209185318862249216057485
v                    1
value                0

cast nonce --rpc-url https://api.testnet.abs.xyz 0xB5c1720A56eD291DEb34e5c00Bd741dB3FD0A6Ab
114

Running against a local fork with anvil-zksync fork --fork-url https://api.testnet.abs.xyz the transaction confirms immediately with a block inclusion, but using testnet RPC results in no confirmation.

Can you please shed some light on this scenario?

Repo Link (Optional)

No response

Additional Details

We had run into a similar issue before where nonces got messed up between what the RPC returned and what was actually needed to get a tx to confirm, but this doesn't seem to be a nonce issue - #843

[alhenaai[bot]]

It appears that the account 0xB5c1720A56eD291DEb34e5c00Bd741dB3FD0A6Ab on the Abstract Testnet is experiencing issues where transactions are accepted by the RPC but not confirmed by the sequencer. This situation can occur due to several reasons, such as network congestion, issues with the sequencer, or specific account-related problems.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

1. Check Network Status: Verify if there are any ongoing issues with the Abstract Testnet that might be affecting transaction processing. Sometimes, delays can be caused by network-wide problems.

2. Increase Gas Fees: Although you have already tried increasing the gas price, it might be worth experimenting with even higher gas fees to prioritize your transactions in case of network congestion.

3. Sequential Nonces: Ensure that the nonces are sequential and that there are no gaps. Missing a nonce can cause transactions to be stuck.

4. Contact Support: If the issue persists and you suspect it might be related to the sequencer or a bug in the testnet, consider reaching out to the support team of the Abstract Testnet with detailed information about your transactions and the issues you are facing.

5. Monitor the Account: Keep an eye on the account's activity using the testnet's block explorer to see if any transactions get confirmed or if there are updates in the account's state that might provide further clues.

If you need more detailed assistance or have further questions, you might want to visit the ZKsync developers discussions on Github for more in-depth support and troubleshooting tips.

Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support.

[coffeexcoin]

The nonce seems to be correct:

cast send --rpc-url https://api.testnet.abs.xyz --private-key $PRIVATE_KEY 0xe06ad0Acb3956f98C9dF77Bd02cdFD4426b2208d --value 0 --async --nonce 113 --gas-price 100000000000000
Error: server returned an error response: error code 3: nonce too low. allowed nonce range: 114 - 134, actual: 113, data: "0x"

[alhenaai[bot]]

The error message indicating "nonce too low" confirms that the nonce you are using (113) is indeed lower than the expected range, which starts from 114. This suggests that the nonce for your account is correctly set at 114, as you have previously attempted transactions with this nonce.

Given this information, the issue does not seem to be related to incorrect nonce management but could be due to other factors affecting transaction processing on the Abstract Testnet. Here are a few additional steps you can consider:

1. Retry with Correct Nonce: Since the nonce 114 is confirmed to be the next valid nonce, ensure that any new transactions use this nonce or higher, depending on the transactions sent.

2. Examine Transaction Details: Double-check the transaction details such as gas limit, gas price, and the data payload to ensure they are correctly set and supported by the network.

3. Network Issues or Bugs: There might be issues with the testnet's sequencer or internal bugs affecting certain types of transactions or specific accounts. Monitoring network announcements or reaching out to the network's support might provide more insights.

4. Test with Different Parameters: If possible, test sending different types of transactions or using different parameters to see if the issue persists across all transaction types or is specific to certain conditions.

If these steps do not resolve the issue, it may be beneficial to seek direct support from the Abstract Testnet team or share this problem in developer communities, such as the ZKsync developers discussions on Github, to get more targeted advice and solutions.

Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support.

[bxpana]

@coffeexcoin been looking into this today and going to see what I can find.

[bxpana]

out of curiosity is it able to send txns to itself?

[bxpana]

Follow up, talked with @coffeexcoin outside of GHD and was able to get tx included. Have added more logs to better understand the cause of this type of issue. Possible tooling issue or related to gas_per_pubdata