Skip to main content
GOL installs its mandate core on an account the owner already has. It does not create accounts. Before every approval and action, the platform checks the account’s proxy runtime or EIP-7702 delegation, implementation, and installed configuration at one block and refuses anything else. Each owner approval is a single eth_signTypedData_v4 request. buildWalletSigningPayload shows the exact payload for a family, and the API returns the same payload with its expected hash.

Notes by family

  • Safe. The Safe’s own owners and threshold authorize everything. A Safe never calls back into its modules, so installation is read from the Safe’s module list.
  • Nexus and Kernel. Installation, removal, and a direct owner revocation run as user operations validated by the account’s root owner validator.
  • Alchemy. GOL uses validation entity 1. If an earlier GOL core already holds entity 1 on the account, remove it first with preparePermanentRemoval, which invalidates its mandates and uninstalls it in one owner operation.
  • EIP-7702 delegated EOA. The owner keeps their existing address, USDC, and ETH. The EOA delegates to the reviewed Nexus 1.3.3 runtime and is initialized with the GOL core as its only executor, no validator, and no hook. Only the EOA’s own key can approve, pause, resume, or revoke; a validator installed on the delegate is never owner authority.

EIP-7702 setup

A plain EOA becomes the nexus7702 family in one type-4 transaction that carries the owner’s EIP-7702 authorization for the Nexus 1.3.3 delegate and the delegate’s owner-signed initialization. prepareEip7702Setup returns both hashes for Base Sepolia and the account’s current nonce. The owner’s wallet signs the authorization and the 32-byte initialization hash; signPreparedEip7702Setup checks that both signatures recover to the account before returning them. submitEip7702Setup asks GOL’s relayer to send the setup at GOL’s cost, within a daily per-project limit. A wallet that sends type-4 transactions itself can use selfSentEip7702Setup instead. An EOA already delegated to anything else is refused: the owner must clear or change that delegation in their own wallet first. If a setup transaction reverts, its authorization can still apply, and the account then reports a reviewed but uninitialized delegation; a new setup needs only the initialization signature. See integrate hosted gas.

Upgrades and removal

If an owner changes the account’s implementation, delegation, or configuration, GOL refuses new approvals and actions for it until it matches again. Pause, resume, and revocation still work. Removing GOL permanently is an owner operation prepared by preparePermanentRemoval; it invalidates every mandate on the account first so a later reinstallation cannot revive them. A delegated EOA sends that call to itself.