Gnosis Safe – Issues Using in Fuji Testnet

gnosis-safe

I have problems using gnosis safe in fuji testnet.
On this page https://docs.gnosis-safe.io/learn/safe-core-api/available-services
there is no corresponding url for connecting, only for Avalanche network.

I use this code to get pending transactions, but service returns "not found" error:

const address = '0xCbCb5119c2239C4AeA74fBC91AEc3e9B1166Ef79';

const provider = new ethers.providers.JsonRpcProvider(
    'https://api.avax-test.network/ext/C/rpc',
);
const owner1Signer = new ethers.Wallet(
    process.env.SERVICE_WALLET_SECRET_KEY,
    provider,
);
const ethAdapterOwner1 = new EthersAdapter({
    ethers,
    signerOrProvider: owner1Signer,
});
const txServiceUrl = 'https://safe-transaction-avalanche.safe.global/';
const safeService = new SafeServiceClient({
    txServiceUrl,
    ethAdapter: ethAdapterOwner1,
});
const { results } = await safeService.getPendingTransactions(address);
console.log(results);

I think this happen because i use 'https://safe-transaction-avalanche.safe.global/' url.
Can anyone help with this?

Best Answer

There is no service available for fuji testnet, you can run your own using https://github.com/safe-global/safe-infrastructure

Related Solutions

Gnosis Safe – How to Fix 404 Error When Loading Just Created Safe Wallet

The services are indeed monitoring the events from the L2 Safe contracts. To properly monitor this it is required to setup the service with the correct contract addresses.

The easiest is if you deploy the contracts to your local network using the tagged version of the safe-contracts repo. This should result in the same contract addresses as on mainnet.

Then you need to add the proxy factory in the django admin.

After this you also need to add the master copy of your network.

For the block numbers you should be able to use 0 or if you want to do it more correctly use the block number of the deployment of the Safe contracts.

gnosis-safe – Using personal_sign with WalletConnect and Gnosis Safe: A Comprehensive Guide

If safeProxyContract.isValidSignature(msgHash, signature) (See CompatibilityFallbackHandler.sol#L66) returns the EIP1271 magic value, then the message with the msgHash is signed. If it doesn't, then it isn't signed

const UPDATED_EIP1271_MAGIC_VALUE = '0x1626ba7e'

let isValidSignature = await safeProxyContract.isValidSignature(msgHash, signature)

// if isValidSignature() returns the EIP-1271 magic value, the signature is valid
if (isValidSignature == UPDATED_EIP1271_MAGIC_VALUE) {
  signatureValid = true
}

But what I couldn't figure out was when to make the call to isValidSignature(). Because the WalletConnect modal actually resolves 0x right after the user issues the txn, without waiting for the txn to be confirmed. So there is no way to know the txn hash, nor when/if the sign message txn was mined or not

But GnosisSafe contract emits an event during those txn. So I added a once event listener to the contract to listen for that event, and then check isValidSignature()

const msgHash = ethers.utils.hashMessage(rawMessage)
const getMessageHash = await wsSafeProxyContract.getMessageHash(msgHash)
// login() only after the _signMessage() txn is mined and SignMsg(msgHash) event emitted
wsSafeProxyContract.once(wsSafeProxyContract.filters.SignMsg(getMessageHash), async () => {
  await login()
})

Thanks @Richard for helping out!

Related Topic