Anza Proposes Shared Solana Protocol Specification
Anza CEO Brennan Watt has opened discussion on a draft 18-chapter specification intended to serve as a common reference for Solana network changes.
Updated on Nov. 7, 2026 in Business Strategy
Anza CEO Brennan Watt proposed a shared Solana protocol specification for network changes, opening the discussion on Oct. 30. The draft spans 18 chapters and covers transactions, networking, state transitions, and consensus, using Mainnet epoch 1072 as its reference point.
Why it matters
Current SIMD proposals document changes individually, and Watt argues that varying descriptions of protocol behavior make it harder for new contributors, who may have to infer rules from client software. A single shared record could give developers a consistent baseline for proposing and reviewing changes.
The draft specification runs 18 chapters and is anchored to Mainnet epoch 1072, but it does not define the first bank of epoch 1073. No adoption decision or implementation date has been set, and testing requirements remain unaddressed.
The players
Anza
Anza is a Solana infrastructure company that develops validator client software for the network.
Brennan Watt
Brennan Watt is the CEO of Anza, who proposed the shared Solana protocol specification.
The details
Under the proposal, detailed changes would be submitted as pull requests to the shared specification and would merge once the change becomes active on Mainnet. If developers broadly agree, SIMD-0001 would be updated and the baseline specification and its hosting location would be decided.
Timeline
Oct. 30: Watt opened the discussion on the shared specification.
Mainnet epoch 1072: reference point used by the draft specification.
Market Landscape
The proposal would extend the existing SIMD process, which documents Solana protocol changes one proposal at a time, by adding a consolidated reference that individual changes update. Watt's push for a shared record reflects a broader effort to make Solana's rules legible to new contributors rather than requiring them to infer behavior from client software.
For developers and validator operators, a shared specification could clarify how protocol changes are expected to behave on Mainnet before they activate. Until a decision is made on adoption and testing, existing workflows and client software remain the reference for current network rules.
The takeaway
A single, consistently maintained specification could reduce the guesswork that new Solana contributors face when reading client code. Whether it becomes the standard depends on developer agreement on the baseline and its hosting location.
Further reading
For more context on how companies shape their long-term direction, see Business Strategy.
Source note: This article includes information reported by TokenPost.
