gnosisgnosis-chaingnosis-safe
The SafeSdk & the gateway API is great, but can it support full offchain signing?
From the doc:
User1 signs: safeSdk.signTransaction() is offchain,
User2 signs with: safeSdk.approveTransactionHash() <-- but this is an onchain call and requires gas.
Can user2~n just call safeSdk.signTransaction() as well and have this recorded on the safe-gateway so that its available in the queue (from getTransactionQueue)??
Thanks
The Safe Core SDK takes all the safe contracts and network configuration from safe-deployments. Specifically on this case, from here, meaning that if the Mumbai chainId (80001) is not present below the networkAddresses key, the Safe contracts are not deployed in that network.
When that happens, you need to deploy the contracts manually. Once deployed, the Safe Core SDK offers the possibility to use Safe contract instances from networks that are not supported in safe-deployments. This can be done this way:
import { ContractNetworksConfig } from '@gnosis.pm/safe-core-sdk'
const chainId = await ethAdapter.getChainId()
const contractNetworks: ContractNetworksConfig = {
[chainId]: {
multiSendAddress: '<MULTI_SEND_ADDRESS>',
safeMasterCopyAddress: '<MASTER_COPY_ADDRESS>',
safeProxyFactoryAddress: '<PROXY_FACTORY_ADDRESS>'
}
}
const safeFactory = await SafeFactory.create({ ethAdapter, contractNetworks })
Where MULTI_SEND_ADDRESS, MASTER_COPY_ADDRESS and PROXY_FACTORY_ADDRESS are the addreses of your recently deployed Safe contracts in Mumbai network.
Now you can create a new Safe with your safeFactory instance:
const safeSdk = await safeFactory.deploySafe(safeAccountConfig, safeDeploymentConfig)
When instantiating the Safe Core SDK to be used with an unsopported network, you will always need to use this same contractNetworks parameter the same way:
import { ContractNetworksConfig } from '@gnosis.pm/safe-core-sdk'
const chainId = await ethAdapter.getChainId()
const contractNetworks: ContractNetworksConfig = {
[chainId]: {
multiSendAddress: '<MULTI_SEND_ADDRESS>',
safeMasterCopyAddress: '<MASTER_COPY_ADDRESS>',
safeProxyFactoryAddress: '<PROXY_FACTORY_ADDRESS>'
}
}
const safeSdk = await Safe.create({ ethAdapter, safeAddress, contractNetworks })
Find here the latest documentation regarding the SafeFactory and Safe Core SDK API references with all the optional params
Can you see the methods inside EthersAdapter class if you expand it?
Best Answer
Yes, all the signers can sign a transaction off-chain and send the signature to the Safe Transaction Service, so it appears on the queue in the web UI.
The
@gnosis.pm/safe-core-sdkpackage allows to sign a transaction off-chain like this:The
@gnosis.pm/safe-service-clientpackage allows to send that signature to the Transaction Service:You will find a more complete answer following this guide: https://github.com/safe-global/safe-core-sdk/blob/main/guides/integrating-the-safe-core-sdk.md#confirm-transaction