Skip to main content
Technical proposal SIMD-0175 Accepted

Disable Partitioned Rent Updates

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

Decision brief

Why this proposal matters

Partitioned rent collection should be removed since it will no longer be useful after rent collection is disabled by https://github.com/solana-labs/solana/issues/33946 (https://github.com/solana-foundation/solana-improvement-documents/pull/84) and account rewrites are disabled by https://github.com/solana-labs/solana/issues/26599.

Source-backed reading aid · source language: EN

Proposal at a glance

What changes

  • Partitioned rent collection should be removed since it will no longer be useful after rent collection is disabled by https://github.com/solana-labs/solana/issues/33946 (https://github.com/solana-foundation/solana-improvement-documents/pull/84) and account rewrites are disabled by https://github.com/solana-labs/solana/issues/26599.

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

Improved block processing performance by removing the need to load all accounts once per epoch for no good reason. Note that the epoch accounts hash calculation similarly loads all accounts once per epoch but serves the important role of ensuring that all validators have the same set of account state.

Action may be required
Users & stakers Impact unknown

No proposal-specific evidence was found for this group.

Action requirement unknown
Governance & ecosystem Medium impact

Partitioned rent collection should be removed since it will no longer be useful after rent collection is disabled by https://github.com/solana-labs/solana/issues/33946 (https://github.com/solana-foundation/solana-improvement-documents/pull/84) and account rewrites are disabled by https://github.com/solana-labs/solana/issues/26599.

Action may be required

Exact source revision

Full proposal document

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

Summary

Partitioned rent collection should be removed since it will no longer be useful after rent collection is disabled by https://github.com/solana-labs/solana/issues/33946 (https://github.com/solana-foundation/solana-improvement-documents/pull/84) and account rewrites are disabled by https://github.com/solana-labs/solana/issues/26599.

Motivation

Since partitioned rent collection is no longer necessary for collecting rent or updating the account rent epoch field, it should be removed to speed up block production and block replay.

New Terminology

NA

Detailed Design

Disabling partitioned rent collection is very straightforward. Partitioned rent collection is initiated during bank freezing and can simply be not performed if a feature gate is activated.

Alternatives Considered

NA

Impact

Improved block processing performance by removing the need to load all accounts once per epoch for no good reason. Note that the epoch accounts hash calculation similarly loads all accounts once per epoch but serves the important role of ensuring that all validators have the same set of account state.

Security Considerations

Rent related code changes often come along with a lot of edge cases to consider so changes should be made carefully to avoid introducing any bugs.

Drawbacks (Optional)

Why should we not do this?

Backwards Compatibility (Optional)

Changes require feature gates for activation to avoid any backwards incompatiblity

Evidence graph

Related proposals and rollout

One or more sources are unavailable.

Upstream review record

Upstream discussion & review

GitHub review is editorial context, not evidence of on-chain support, voting, or outcome.

PR #175 · merged SIMD-0175: Disable partitioned rent collection 15 comments and reviews · Jan 26, 2026
@brooksprumo

I'm ok with doing this all under one SIMD/feature-gate.

GitHub ↗
@brooksprumo

I'm ok with doing this all under one SIMD/feature-gate.

GitHub ↗
@brooksprumo

@jstarry When you feel it is ready, can you request reviews from Firedancer as well, please?

GitHub ↗
@HaoranYi

While making them under one feature makes activation easier, separating them can allow the sub features to be activated earlier (as you mentioned), without waiting for other dependent features, i.e. skipping rewrites. Either way is fine with me. Just make sure that we are agreed upon what to do.

GitHub ↗
@jstarry

Ok let's use a single feature gate

GitHub ↗
@jstarry

@lheeger-jump can you or someone else on the firedancer team review this please? Should make your lives easier

GitHub ↗
@joncinque

Looks like there's consensus here -- if no one objects within the next week, I'll merge on 25 November.

GitHub ↗
@jstarry

Amendment proposed here: https://github.com/solana-foundation/solana-improvement-documents/pull/230

GitHub ↗

simd.watch community discussion · SIMD-0175

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.
2

SIMD

Deployment Status

Document lifecycleAccepted
CategoryCore protocol
Devnetactive Epoch 896
Testnetactive Epoch 795
Mainnet-Betaactive Epoch 808
2B2SBNbUcr438LtGXNcJNBP2GBSxjx81F945SdSkUSfC

Exact source revision

Sources & integrity

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

One or more sources are unavailable.