Skip to content

CAP-66: Update the initial/updated config setting values. #1734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leighmcculloch merged 1 commit into from
May 14, 2025
Merged

CAP-66: Update the initial/updated config setting values. #1734

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions core/cap-0066.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -319,7 +319,7 @@ For this reason, rent fees for `CONTRACT_DATA` will continue to be based on the

#### Initial Network Config Settings

Initially, all disk read limits and fees should match exactly the limits and fees of reads today. Limits must not
Initially, all disk read limits should match exactly the limits and fees of reads today. Limits must not
decrease from current values in order to prevent bricking existing contracts. In the worst case, a contract can read
up to `txMaxReadEntries - 1` classic entries today (all classic entries + SAC instance). Current limits have been
carefully measured assuming disk access only, so the addition of in-memory state should not negatively affect the network
Expand All @@ -334,7 +334,16 @@ Note, that there is also a 'soft' limit on the maximum number of reads per trans

When the protocol is upgraded to version 23 the initial values of the new configuration settings will be set to the following values:
- `txMaxInMemoryReadEntries` will be set to the current value of `txMaxDiskReadEntries` (renamed from `txMaxReadLedgerEntries`) in order to prevent breakages of any existing contracts
- `feeWrite1KB` will be set to `10000` stroops, which roughly matches the current Soroban write fee per 1 KB
- `feeWrite1KB` will be set to `3'500` stroops, which is roughly 2x of the current Soroban read fee per 1 KB. Note, that this fee is decoupled from the rent write fee now.

#### Rent-related network settings update

Since Soroban live state will be used for the rent write fee computation, the fee-related configuration will be updated. The goal of the update is to keep the current rent write fee around `11'000` stroops, which is the rent write fee for Stellar mainnet. This update assumes that the live Soroban state on protocol upgrade is around 600 MB.

- `sorobanStateTargetSizeBytes` set to `1'500'000'000` (1.5 GB)
- `rentFee1KBSorobanStateSizeLow` set to `10'633`
- `rentFee1KBSorobanStateSizeHigh` set to `11'550`
- `sorobanStateRentFeeGrowthFactor` will stay at its current value

#### `archivedEntries` Vector

Expand Down