Hakim Raja

Thanks @martinpaljak Tried that but still get 0x6A80 ``` # gp -dviF --domain 0101010101010101 --params 810202008202202087022020 --key 404142434445464748494A4B4C4D4E4F # GlobalPlatformPro 21.12.32 # Running on Mac OS X 13.0.1 aarch64, Java...

I am building the token-2022 program from the master branch, locally and running the local validator like this: solana-test-validator -r \ --bpf-program TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb \ /target/deploy/spl_token_2022.so I can create the mint...

yes, that was indeed the error with 3.3.0. Just built and tried with 3.4.0 and both transfer/withdraw work fine too. Thanks for your quick pointer. Are audit keys supported yet?

I can confirm the same issue when using 1.4.1+L2 w/ 4337 modules. web-ui loads the safe on sepolia, polygon and gnosis, fine. But complains about unsupported base contract for optimism...

> Looks like it was fixed, https://app.safe.global/settings/setup?safe=arb:0x7c74e813daEE4c9b475cFFC6352FD79616f81AA1 is shown as 1.4.1+L2 ✅ and there's no warning. I'm surprised it is working for you. I just tried the safe you pointed...

> Hmm, I wonder if in this case it is an issue where the Safe v1.4.1 addresses aren't correctly configured in either the CGW or in the web interface for...

Here's my config for the safe; ``` { entryPoint: ENTRYPOINT_ADDRESS_V07, safeVersion: "1.4.1", saltNonce: 0n, addModuleLibAddress: "0x2dd68b007B46fBe91B9A7c3EDa5A7a1063cB5b47", safe4337ModuleAddress: "0x75cf11467937ce3F2f357CE24ffc3DBF8fD5c226", safeProxyFactoryAddress: "0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67", safeSingletonAddress: "0x29fcB43b46531BcA003ddC8FCB67FFE91900C762", multiSendAddress: "0x38869bf66a61cF6bDB996A6aE40D5853Fd43B526", multiSendCallOnlyAddress: "0x9641d764fc13c8B624c04430C7356C1C7C8102e2", // setupTransactions: [paymasterApproval], }...

using the latest client 4.0.1

Let me clarify. We use your node-js client but not sure if it is related to just this client but the underlying api. Passing an empty string to your verify...

yes, that was the json object :)