Upcoming Features

Planned Base protocol features and their ballpark target quarters, tracked independently of a specific network upgrade.

This page lists Base protocol features that are planned or in development, independent of the named upgrade that eventually ships them. Each entry links to its specification where one exists.

Targets are ballpark quarters and may change. A feature moves onto a named upgrade page (for example, Cobalt) only once that upgrade is scheduled and locked in, at which point the official activation dates and final feature list are published.

Planned Features

Feature	Summary	Details	Target
200ms Native Blocks	Five canonical blocks per second, replacing Flashblocks with canonical block and RPC streams.	200ms Native Blocks	Q4 2026
B20 Improvements	Pay fees in B20s, scheduled multiplier updates, and composite policies for the B20 token standard.	B20 changelog	Q3 2026
Validity Transactions	A transaction type with onchain predicate checks for safer, conditional execution.	Validity Transactions	Q3 2026
Dynamic Upgrades	An onchain upgrade schedule that lets nodes activate forks live, without a client restart.	Dynamic Upgrades	Q3 2026
TEE Migration	Migrate Base infrastructure to run inside a Trusted Execution Environment.	Specification pending	Q3 2026
Native Account Abstraction (EIP-8130)	Onchain smart accounts, scoped session keys, and native gas sponsorship, with no bundlers or relays.	Native Account Abstraction	TBD

How Features Ship

1. Proposed — a feature is designed and, where applicable, written up as a specification. It appears in the table above with a ballpark target.
2. Scheduled — once an upgrade that carries the feature is locked in, a named upgrade page is published with official Base Sepolia and Base Mainnet activation dates.
3. Live — the upgrade activates and moves to the Upgrades timeline.