> Source: [/docs/protocol/upgrades/t14](https://tempo.xyz/developers/docs/protocol/upgrades/t14.md) > Section: [Tempo EVM](https://tempo.xyz/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.xyz/developers/llms.txt) · [Docs skill](https://tempo.xyz/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.xyz/developers/llms.txt) and Markdown pages directly. # T14 Network Upgrade T14 is the planned network upgrade that brings configurable accounts to testnet and mainnet. :::tip[T14 status] T14 is planned and its scope may still change. No activation dates are set. Until T14 activates, configurable accounts run only on the [Tempo Accounts devnet](https://tempo.xyz/developers/docs/accounts/create#connect-to-the-devnet). ::: ## Timeline | Network | Activation date (UTC) | Unix timestamp | |---------|-----------------------|----------------| | Testnet | Not yet scheduled | — | | Mainnet | Not yet scheduled | — | ## T14 overview * **Configurable accounts:** each signer has a weight, and a transaction runs once the signing weights reach the account's threshold. The address stays the same when signers change. See [Tempo Accounts](https://tempo.xyz/developers/docs/accounts). * **Configuration updates:** the current signers replace the signer list and threshold in one transaction, at the same address. See [Account configuration](https://tempo.xyz/developers/docs/accounts/account-configuration). * **Upgrades from single-key accounts:** an existing single-key account becomes a configurable account at the same address. See [Account upgrade](https://tempo.xyz/developers/docs/accounts/account-configuration/account-upgrade). * **Configurable accounts as access keys:** a team's configurable account can act as another account's access key, approving with its own signers. See [Account Keychain](https://tempo.xyz/developers/docs/development/account-keychain#access-key-types). ## T14 specifications | Specification | What it covers | | --- | --- | | [TIP-1107](https://tips.sh/1107) | Configurable accounts: the meta proposal that lists the TIPs below | | [TIP-1108](https://tips.sh/1108) | The account leaf that stores a configurable account's configuration hash | | [TIP-1109](https://tips.sh/1109) | Configuration update rules | | [TIP-1110](https://tips.sh/1110) | Configurable account address derivation and recovery | | [TIP-1111](https://tips.sh/1111) | Configurable accounts as access keys | | [TIP-1113](https://tips.sh/1113) | Upgrading a single-key account in place | | [TIP-1114](https://tips.sh/1114) | The configurable account transaction and multisig signature type | The specifications are under review and may change before T14 activates. Try the behavior now on the [devnet](https://tempo.xyz/developers/docs/accounts/create#connect-to-the-devnet), and see [Configurable accounts](https://tempo.xyz/developers/docs/development/configurable-accounts) for the Tempo EVM reference.