Solana Developers Weigh Shared Protocol Specification
Solana builders should watch whether this shared record becomes the reference for how network changes are documented.
Updated on Nov. 7, 2026 in Business Strategy

Anza CEO Brennan Watt has proposed a shared Solana protocol specification to record how network changes are defined, opening discussion on Oct. 30. The draft runs 18 chapters and covers transactions, networking, state transitions, and consensus. It sets no adoption decision or implementation date, and it has not changed Solana's rules. Operators building on Solana should note the proposal is still at the discussion stage.
Why it matters
Watt's rationale is that descriptions of protocol behavior can vary across individual proposals, and new contributors may have to infer rules from client software. A single shared record would give builders a fixed reference point for how the network is meant to behave, rather than relying on reading client code.
The draft specification is 18 chapters long and is anchored to Mainnet epoch 1072, with epoch 1073's first bank left undefined. The discussion sets no adoption decision or implementation date, and the current SIMD process documents proposals individually rather than as one shared record.
The players
Anza
Anza is a Solana infrastructure company whose CEO, Brennan Watt, proposed the shared protocol specification.
Brennan Watt
Brennan Watt is the CEO of Anza, a Solana infrastructure company, who proposed the shared specification.
Solana Mainnet
Solana Mainnet is the live production network of the Solana blockchain, where protocol changes become active once adopted.
The details
Under the proposal, detailed changes would be submitted as pull requests to the shared specification, and each pull request would merge when the change becomes active on Mainnet. The draft states that a later Mainnet activation would require a revised specification, which would tie the document's accuracy to ongoing network upgrades. 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 moves Solana's documentation away from the current SIMD process, which records each proposal individually. A shared specification would give developers and new contributors one consolidated reference, reducing reliance on inferring rules from client software.
Developers building on Solana should track whether the shared specification is adopted, since it could become the reference for how network changes are documented. No implementation date has been set, so current planning should not assume the document is binding.
The takeaway
Operators should treat the shared specification as a proposal still awaiting developer agreement, not a settled standard. Watch whether SIMD-0001 is updated and whether a baseline specification and hosting location are decided in the coming discussion.
Further reading
For the broader context on how companies position themselves in crypto infrastructure, see Business Strategy.
Source note: This article includes information reported by TokenPost.


