Skip to content

remove outdated content from 'resources limits & fee' #2277

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

Open
jeesunikim wants to merge 2 commits into
base: main
Choose a base branch
from
Open

remove outdated content from 'resources limits & fee' #2277

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c803df9
remove outdated content from 'resources limits & fee'
jeesunikim Feb 24, 2026
8ebaa2d
Update docs/networks/resource-limits-fees.mdx
jeesunikim Feb 24, 2026
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
75 changes: 5 additions & 70 deletions docs/networks/resource-limits-fees.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,75 +3,10 @@ sidebar_position: 30
title: Resource Limits & Fees
---

:::info
For the latest live network limits and fees, see Stellar Lab's [Network Limits](https://lab.stellar.org/network-limits).

The values below are for reference. For current resource limits and fees on the live network, see Stellar Lab's [Network Limits](https://lab.stellar.org/network-limits) page.
You can also query current settings from the CLI:

:::

## Resource Limits

:::note

Resource limitations and fees only apply to smart contract transactions. Read more about the inner workings of fees on Stellar in the [Fees section](../learn/fundamentals/fees-resource-limits-metering.mdx).

:::

### Per-transaction limits

These define the maximum amount of work a single Smart contract transaction can do.

| Network Setting | Value |
| ----------------------------------------------------- | ------------------ |
| Max CPU instructions | 100 million |
| Max memory (RAM) | 40 MB |
| Max number of keys in the footprint | 100 |
| Disk reads\* | 100 entries/200 KB |
| Disk writes | 50 entries/132 KB |
| Transaction size | 132 KB |
| Events+return value size bytes | 16 KB |
| Individual ledger key size (contract storage key) | 250 bytes |
| Individual ledger entry size (including Wasm entries) | 128 KiB |

\* Most transactions don't perform any disk reads, as only archived entries and 'classic' entries (G-accounts, trustlines) are considered to be disk reads. Live smart contract state is in-memory and is not counted towards this limit.

### TTL extension parameters

These define TTL extension parameters.

| Network Setting | Value |
| -------------------------------- | -------- |
| Persistent entry TTL on creation | 120 days |
| Temporary entry TTL on creation | 1 day |
| Max ledger entry TTL extension | 6 months |

### Ledger-wide limits

These define the maximum amount of work done by all the transactions in a single ledger (single block).

| Network Setting | Value |
| ----------------------------------- | ------------------ |
| Max CPU instructions | 600 million |
| Max memory (RAM) | no explicit limit |
| Max number of keys in the footprint | no explicit limit |
| Disk reads | 1000 entries/7 MB |
| Disk writes | 500 entries/143 KB |
| Transactions size | 133 KB |
| Events+return value size bytes | no explicit limit |

## Resource Fees

| Network Setting | Cost (stroops) |
| :--------------------------------------------- | :------------------------ |
| 10,000 CPU instructions | 25 (250,000/max tx) |
| Read 1 ledger entry from disk | 6,250 (625,000/max tx) |
| Read 1KB from disk | 1,786 (357,200/max tx) |
| Write 1 ledger entry | 10,000 (500,000/max tx) |
| Write 1KB to disk | 3,500 (462'000/max tx) |
| 1KB of transaction size (bandwidth) | 1,624 (214,368/max tx) |
| 1KB of transaction size (history) | 16,235 (2,143,020/max tx) |
| 1KB of Events/return value | 10,000 (160,000/max tx) |
| 30 days of rent for 1 KB of persistent storage | ~427,000 |
| 30 days of rent for 1 KB of temporary storage | ~213,500 |

Note, that the rent fees provided here may go up in case if a lot of contract data is written to the ledger within a short time period. This happens because the rent fees are designed in such a way that the closer the state size to some validator-defined threshold, the more expensive it gets to write new data or extend the TTLs.
```bash
stellar network settings
```
Comment on lines +6 to +12
Copy link

Copilot AI Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change breaks multiple internal documentation links. The file docs/networks/software-versions.mdx contains anchor links to sections #resource-limits and #resource-fees (lines 461, 462, 524, 525, 588, 589) that no longer exist after removing the detailed content. Additionally, docs/build/guides/archival/test-ttl-extension.mdx links to #resource-fees (line 78). These broken links will result in 404 errors for users navigating the documentation. Consider either keeping the section headers as anchors with redirects to the Stellar Lab URL, or updating all referring pages to link directly to the Stellar Lab.

Copilot uses AI. Check for mistakes.
Comment on lines +6 to +12
Copy link

Copilot AI Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While redirecting to Stellar Lab for live data is appropriate, the removed content provided valuable context that users might find helpful, such as:

  1. A note explaining that resource limitations only apply to smart contract transactions
  2. Explanations of TTL extension parameters
  3. Distinction between per-transaction and ledger-wide limits
  4. Important footnotes about disk reads and rent fee calculations

Consider keeping a brief overview section that explains what resource limits and fees are (with a link to the fundamentals page at docs/learn/fundamentals/fees-resource-limits-metering.mdx for detailed explanations), before redirecting users to Stellar Lab for current values. This would provide educational context while still solving the outdated data problem.

Copilot uses AI. Check for mistakes.
Comment on lines +10 to +12
Copy link

Copilot AI Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CLI command example could benefit from additional context to be more helpful. Consider adding:

  1. A brief explanation of what the command returns (e.g., "This returns JSON output with current network configuration values")
  2. Optionally, an example of how to parse specific values from the output (similar to the example in the linked issue using jq to extract specific settings)
  3. A note that users need to have the Stellar CLI installed and configured for their target network

This would make the page more actionable for users who aren't already familiar with the Stellar CLI.

Copilot uses AI. Check for mistakes.