<!-- tempo-docs-context -->
> Source: [/docs/accounts/keys](https://tempo.com/developers/docs/accounts/keys.md)
> Section: [Tempo EVM](https://tempo.com/developers/docs/development.md). Build on Tempo EVM: wallets and keys, payments, transactions and fees, TIP-20 Tokens, contracts, exchange, network details, nodes, protocol specifications, and changelog.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.com/developers/llms.txt) and Markdown pages directly.

<span id="keys-and-signing" />

<span id="keys-and-permissions" />

# Account Model

Every Tempo EVM account is either a single-key account or a configurable account.

## Overview

The two account types differ in who approves transactions. One key approves a single-key account's transactions, as on Ethereum. Weighted owners approve a configurable account's transactions. The Accounts guides call them signers. A transaction runs once the approving owners' weights reach the account's threshold. Either type can also authorize access keys, which sign alone within limits.

Two account types: a single-key account, which can upgrade in place to a configurable account. Both use the Account Keychain for access keys.

<span id="tempo-evm-account-kinds" />

<span id="tempo-account-configuration" />

<span id="account-references" />

## Single-Key and Configurable Accounts

| | [Single-key account](https://tempo.com/developers/docs/development/single-key-accounts) | [Configurable account](https://tempo.com/developers/docs/development/configurable-accounts) |
| --- | --- | --- |
| Approved by | Its one key, the root key | Owners whose weights reach the threshold |
| Address comes from | One public key: secp256k1, P-256, or WebAuthn (passkey) | The first configuration of owners, weights, threshold, and salt, or the original key if upgraded |
| Changing keys | A new key means a new address. [Upgrade to a configurable account](https://tempo.com/developers/docs/development/single-key-accounts#upgrade-to-a-configurable-account) to change keys and keep the address. | `updateConfig` replaces the owners and threshold. The address stays. |
| Running contract code (EIP-7702 delegation) | Allowed, but a delegated account can't upgrade | Not allowed |

:::warning
**Multiple signers arrive with the [T14 network upgrade](https://tempo.com/developers/docs/protocol/upgrades/t14).** Until T14 activates, an account with several signers and a threshold runs only on the [Tempo Accounts devnet](https://tempo.com/developers/docs/accounts/create#connect-to-the-devnet), not on mainnet or testnet, and may still change.
:::

Single-key accounts work on mainnet, testnet, and the devnet. The upgrade to a configurable account runs only on the devnet until T14.

<span id="access-key-enforcement" />

<span id="delegate-only-the-authority-a-task-needs" />

<span id="grant-access" />

<span id="revoke-access" />

<span id="keep-access-and-recovery-explicit" />

<span id="access-keys-for-both-account-types" />

## Access Keys

An [access key](https://tempo.com/developers/docs/accounts/access-keys) is an extra key that signs for the account on its own, within the limits you set:

* **Spending Limits:** A limit per TIP-20 token, which can reset each period.
* **Expiry:** An optional time after which the key stops working.
* **Scopes:** Restrictions on which contracts it calls and whom it pays.

The [Account Keychain](https://tempo.com/developers/docs/development/account-keychain), a contract built into Tempo (a precompile), stores every account's access keys. It enforces those limits on each transaction they sign.

The account itself authorizes and revokes access keys, through its root key or owners whose weights reach the threshold. Access keys never count toward a threshold.

## Tempo Transaction Signature Types

| Signature | Prefix | Used by |
| --- | --- | --- |
| secp256k1 | None (65 bytes) | A root key, owner, access key, or fee payer |
| P-256 | `0x01` | A root key, owner, or access key |
| WebAuthn | `0x02` | A root key, owner, or access key |
| Keychain | `0x04` | An access key, wrapping its own signature with the account's address |
| Multisig | `0x05` | A configurable account's owners, bundling their signatures with the [account's configuration](https://tempo.com/developers/docs/development/configurable-accounts#multisig-signature-format) |

Viem's `Account` helpers encode every [format](https://tempo.com/developers/docs/protocol/transactions/spec-tempo-transaction#signature-types).

<span id="separate-login-from-transaction-authority" />

<span id="choose-a-signer" />

<span id="logins-as-signers" />

<span id="sign-transactions" />

<span id="choose-the-signing-environment" />

<span id="login-signing-and-api-credentials" />

<span id="app-session-signing-and-api-credentials" />

## Logins and API Keys

Only these keys sign transactions. Your app's login session controls access to your app. A Tempo API key authenticates requests to Tempo's hosted APIs. Neither signs for an account.

## Related

[Access Keys](https://tempo.com/developers/docs/accounts/access-keys): Covers keys that sign for an account within spending limits, expiry, and scopes.

[Single-Key Accounts](https://tempo.com/developers/docs/development/single-key-accounts): Covers the protocol reference for accounts approved by one key.

[Configurable Accounts](https://tempo.com/developers/docs/development/configurable-accounts): Covers the protocol reference for accounts approved by weighted owners.

[Account Keychain](https://tempo.com/developers/docs/development/account-keychain): Covers the precompile that stores and enforces access keys.
