Feature Gate: include transaction loaded accounts data size in base fee calculation

[tao-stones]

Description

Transaction can request limit of loaded accounts data size via compute_budget::set_loaded_account_data_size_limit instruction, or MAX 64MB is automatically applied as default. Transaction should pay fee for requesting memory usage.

This feature changes transaction's base fee, therefore needs to be gated.

Feature ID

EaQpmC6GtRssaZ3PCUM5YksGqUdMLeZ46BQXYtHYakDS

Activation Method

Single Core Contributor

Minimum Beta Version

1.16.0

Minimum Stable Version

No response

Testnet Activation Epoch

No response

Devnet Activation Epoch

No response

Mainnet-Beta Activation Epoch

No response

[tao-stones]

Dev Comm: should communicate and promote instruction compute_budget::set_loaded_account_data_size_limit, see large adaptation of it before enabling this feature. Once feature gate is enabled, the impacts are the CU of transaction's loaded_account_data_size (being user specified value, or default) will contribute to:

1. base fee calculation at bank::calculate_fee(), and
2. block's cost limit in cost model.

[tao-stones]

To make it easier for apps to update to use ix set_loaded_account_data_size_limit, this feature gate should be activated after #27839 and #30366 are activated everywhere.

[brooksprumo]

@tao-stones Is this feature gate still blocked, or can it be scheduled for activation?

[tao-stones]

@tao-stones Is this feature gate still blocked, or can it be scheduled for activation?

Ah thanks for reminder. Looks like the two prerequisite feature gates have all been activated for awhile. I'd like to see wide adaptation of instruction compute_budget::set_loaded_account_data_size_limit before activating this feature gate, otherwise default 64MB per tx will be used, result high transaction fee and lower block utilization.

I'll ping Dev Comm if can promote adaptation of the instruction. Also, do you know if there is a way for user/wallet to easily find out the size of accounts their tx about to load?

[michaelh-laine]

Changing base fees should go through a governance vote, especially in the context of SIMD-0096 debate that is ongoing.

@tao-stones Is this feature gate still blocked, or can it be scheduled for activation?

[tao-stones]

Updated block reason to "requires community gov vote" on Scheduler page.