> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gol.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported accounts

> The exact smart-account configurations GOL supports and how each owner signs.

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.

| Family                                 | Implementation                                                 | GOL installation                | Owner approval format                                                            | Owner operations                                |
| -------------------------------------- | -------------------------------------------------------------- | ------------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------- |
| Safe 1.4.1 (`safe`)                    | Safe L2 singleton `0x29fcB43b46531BcA003ddC8FCB67FFE91900C762` | Safe module (`enableModule`)    | `SafeMessage` typed data under the Safe's domain; threshold signatures preserved | Safe transaction signed as `SafeTx` typed data  |
| Biconomy Nexus 1.0.0 (`nexus`)         | `0x000000039dfcAd030719B07296710F045F0558f7`                   | ERC-7579 executor               | ERC-7739 `PersonalSign` typed data, K1 validator prefix                          | EntryPoint v0.7 user operation, `personal_sign` |
| ZeroDev Kernel v0.3.1 (`kernel`)       | `0xBAC849bB641841b44E965fB01A4Bf5F074f84b4D`                   | ERC-7579 executor               | `Kernel(bytes32 hash)` typed data, root validator                                | EntryPoint v0.7 user operation, `personal_sign` |
| Alchemy Modular Account v2 (`alchemy`) | `0x00000000000002377B26b1EdA7b0BC371C60DD4f`                   | ERC-6900 validation at entity 1 | `ReplaySafeHash` typed data, owner entity 0                                      | EntryPoint v0.7 user operation, `personal_sign` |

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.