Daniel

I see you are executing now transactions with the correct configuration. We don't have any error like the one you describe above, so I would need to see a current...

@Malikrehman00107 that contract is just a Safe contract. I would need to see either the current SDK implementation and the code of this smart contract https://sepolia.etherscan.io/address/0x419Fe9f14Ff3aA22e46ff1d03a73EdF3b70A62ED

@faisal-anwar825 could you remove the safeTxGas from `safeTransactionData`? Also, could you tell me which versions of the SDK are you using? Could you tell me which line the code is...

Ok, those are old versions that are not supported anymore. There were some gas estimation issues that were solved in v2 specially affecting some specific RPC providers, which may be...

Yes, that is expected. From `api-kit`v2 is not necessary to specify the transaction service URL if you use [one of the public available ones](https://docs.safe.global/advanced/api-supported-networks). You can instead just leave the...

@faisal-anwar825 I see you are creating plenty of transactions currently with 2 signatures. But is not possible to execute those transactions because the previous transactions should be executed first https://app.safe.global/transactions/queue?safe=sep:0x159bd467fafcfa348d2b5f357b23aa1d70e814a0...

You can use the protocolKit instance for that. ``` const protocolKit = await Safe.create({ ethAdapter, predictedSafe }) const balance = await protocolKit.getBalance() ``` `Safe.create()` will not deploy the Safe right...

Could you please share the versions of the packages you are using? Also could you share the code snippet? With the code I shared above, if you are using the...

@francelwebdev could you also share the code fragment and also the chain you are using? Thank you

Ok, I see the issue now. The initialization you are using inside `getBalance` is fine for a deployed Safe, but not for a Safe that wasn't deployed yet. If you...