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, 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.

​
Upgrades and removal

If an owner changes the account’s implementation or configuration, GOL refuses new approvals, actions, and claims for it until it matches again. Revocation still works. 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.