Gully Safe

Gully Safe is a Safe multisig for teams, treasuries and DAOs on GullyChain: several owners, a confirmation threshold, batched transactions and an on-chain record of every confirmation. It is the Safe product you know, branded for GullyChain.

#What runs where

#Why the addresses differ

Safe's canonical addresses come from Safe's signed singleton factory, which the Safe team deploys per chain on request. It is not on GullyChain yet (Not deployed yet). So Gully Labs replayed the exact canonical deployments (same creation code, same salts) through the Arachnid CREATE2 factory. The code is byte-for-byte Safe's audited code; only the deployer, and therefore the address, differs.

#Contracts

The rest of the suite (SimulateTxAccessor, SafeToL2Setup, SafeToL2Migration, TokenCallbackHandler) is on Contract addresses.

#Passkey owners

The Safe passkey modules are deployed, so a passkey can be a Safe owner: SafeWebAuthnSignerFactory creates a signer contract for a passkey's public key, and SafeWebAuthnSharedSigner lets a new Safe use a passkey owner from its first transaction. P-256 signatures verify through the RIP-7212 precompile (0x…0100, GullyChain runs ArbOS 51) with the Daimo verifier at 0xc2b78104907F722DABAc4C69f826a522B2754De4Copy as the fallback.

#Use Gully Safe from code

With permissionless.js on viem, pass the Gully addresses:

import { toSafeSmartAccount } from "permissionless/accounts";

const safe = await toSafeSmartAccount({
  client: publicClient,                       // a viem client on chain 485590
  owners: [owner],
  version: "1.4.1",
  entryPoint: { address: "0x0000000071727De22E5E9d8BAf0edAc6f37da032", version: "0.7" },
  safeSingletonAddress: "0x76667330c237Fb40f28d74563cdAAae4b06C23Ec",   // SafeL2 1.4.1
  safeProxyFactoryAddress: "0xd9d2Ba03a7754250FDD71333F444636471CACBC4",
  multiSendAddress: "0x7B21BBDBdE8D01Df591fdc2dc0bE9956Dde1e16C",
  multiSendCallOnlyAddress: "0x32228dDEA8b9A2bd7f2d71A958fF241D79ca5eEC",
  safe4337ModuleAddress: "0x75cf11467937ce3F2f357CE24ffc3DBF8fD5c226",
  safeModuleSetupAddress: "0x2dd68b007B46fBe91B9A7c3EDa5A7a1063cB5b47",
});

Then use it with a smart account client on the bundler and paymaster, exactly like a Kernel account. Check the option names against the permissionless.js version you install.

#Not available yet

• Spending limits. The Safe AllowanceModule is not deployed, so the spending-limit feature is off in the app.
• Canonical addresses. If the Safe team deploys its singleton factory on GullyChain, the canonical addresses can be deployed next to these. Existing Gully Safes keep working at their addresses.