Skip to main content
Technical proposal SIMD-0223 Activated

Removes Accounts Delta Hash

  1. Idea
  2. Draft
  3. Review
  4. Accept
  5. Implement
  6. Active

Decision brief

Why this proposal matters

With the introduction of the Accounts Lattice Hash (SIMD-215), the merkle-based Accounts Delta Hash is redundant and can be removed.

Source-backed reading aid · source language: EN

Proposal at a glance

What changes

  • With the introduction of the Accounts Lattice Hash (SIMD-215), the merkle-based Accounts Delta Hash is redundant and can be removed.

Stakeholder map

Who is affected

Builders & client teams Impact unknown

No proposal-specific evidence was found for this group.

Action requirement unknown
Validators & operators Medium impact

Only validators will be impacted, and their performance will improve since the merkle-based hashing of modified accounts per block will no longer be performed.

Action requirement unknown
Users & stakers Impact unknown

No proposal-specific evidence was found for this group.

Action requirement unknown
Governance & ecosystem Impact unknown

No proposal-specific evidence was found for this group.

Action requirement unknown

Exact source revision

Full proposal document

Source-language document. Technical identifiers and evidence remain unchanged. 0616093b2952

Summary

With the introduction of the Accounts Lattice Hash (SIMD-215), the merkle-based Accounts Delta Hash is redundant and can be removed.

Motivation

This SIMD follows on from SIMD-215, and shares its motivation:

The main goal is to scale Solana to billions accounts

When a block is done being processed, it is frozen. The bank hash is calculated during the freezing process, and includes calculating the Accounts Delta Hash. The Accounts Delta Hash is the merkle-based hash of the accounts modified in this block. As established in SIMD-215, merkle-based hashing of accounts hinders scaling. And since SIMD-215 added the Accounts Lattice Hash, which is a hash of the total account state, the merkle-based hash of only the accounts modified per block is redundant. Therefore the Accounts Delta Hash can be removed from the bank hash entirely.

New Terminology

None.

Detailed Design

Remove the Accounts Delta Hash from the Bank Hash.

Alternatives Considered

None.

Impact

Only validators will be impacted, and their performance will improve since the merkle-based hashing of modified accounts per block will no longer be performed.

Security Considerations

None.

Backwards Compatibility

Incompatible. This changes the bank hash, thus changing consensus.

Evidence graph

Related proposals and rollout

One or more sources are unavailable.

Upstream review record

Upstream discussion & review

One or more sources are unavailable.

simd.watch community discussion · SIMD-0223

Powered by Giscus · Sign in with GitHub to comment

Community comments load when this section approaches the viewport.

Provenance

Evidence & technical details

Rollout or chain data, source revisions, freshness and integrity.
3

SIMD

Deployment Status

Document lifecycleActivated
CategoryCore protocol
Devnetactive Epoch 895
Testnetactive Epoch 794
Mainnet-Betaactive Epoch 807
LTdLt9Ycbyoipz5fLysCi1NnDnASsZfmJLJXts5ZxZz

Exact source revision

Sources & integrity

  • Proposal document pinned_commit_blob
    0616093b2952ed6de52c4a27d66aadd11d48d4f9
  • simd-document document · stale · Sep 11, 2026
    0616093b2952ed6de52c4a27d66aadd11d48d4f9

One or more sources are unavailable.

One or more sources are unavailable.