-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Report: Abstract Account Transactions Not Being Included in Blocks #239
Comments
Hi there! Sorry to hear you are having issues. Can you provide some additional details as to what you are trying to do here?
|
Thank you for your kind assistance! After setting the nonce of a new transaction to 25, it was successfully packed into a block. |
I used the code above to deploy the smart contract, but the transaction is still not being packed. Could this possibly be due to an issue with the contract bytecode? |
I believe it's not an issue with the contract bytecode. When I deploy using an EOA account, everything works fine. However, when I try to deploy using an abstract account, the transaction never gets packed into a block. |
🚨 Critical Severity
Funds are currently locked in the abstract account as no transactions can be executed.
Issue Description
After deploying a smart contract, all transactions initiated from my abstract account (including the deployment transaction) are not being included in blocks. Transactions are not appearing in mempool despite no error messages. Most critically, I am unable to transfer funds out of the account.
Impact
CRITICAL: Funds are locked in the abstract account
Unable to execute any transactions
Unable to deploy contracts
Unable to transfer assets to other addresses
Environment
Abstract Account: 0x22470F391055455fd2699bC652826f820b9bD0d0
Framework: viem
Library: @abstract-foundation/agw-client
Network: Abstract Mainnet
Expected Behavior
Transactions should be included in mempool and subsequently packaged into blocks.
Actual Behavior
Prior State
The account was functioning normally before this issue, successfully sending transactions.
Reproduction Steps
The text was updated successfully, but these errors were encountered: