Repository navigation
Add the 400-entry footprint cap to the smart-contracts limits table - #171
Merged
Merged
Conversation
The table listed 200 / 200 as 'ledger entries read / written', which reads as a cap on every footprint entry. Since Protocol 23 the 200 limit counts disk reads only (classic entries plus archived entries being restored), and a separate tx_max_footprint_entries (400 on Mainnet) caps the whole footprint. Rename the read rows to disk reads, add the footprint row, and add an eval scenario.
|
Contributor
Author
|
🤖 Automated message from the Stellar Triage Bot. Verified at
Merging. |
stellar-triage-bot
Bot
deleted the
issue-agent/164-footprint-entry-cap
branch
November 2, 2026 22:38
3 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Automated message from the Stellar Triage Bot.
Closes #164
The resource-limits table in
skills/smart-contracts/development.mdhad no row for the total footprint cap. Its "read" rows also looked like limits on every footprint entry.evals/scenarios/smart-contracts/07-footprint-entry-limits.json.Sources:
getLedgerEntries, ledger 65274557):tx_max_footprint_entries400,tx_max_disk_read_entries200,tx_max_write_ledger_entries200,tx_max_disk_read_bytes200000.TransactionFrame.cpp: the 400 cap counts read-only plus read-write entries. Disk reads count classic entries plus archived Soroban entries.