{
  "id": 1509067,
  "title": "Solana’s Local Fee Markets Reveal the Limits of TPS as a Metric",
  "url": "https://urgent.news/2026/08/17/solanas-local-fee-markets-reveal-the-limits-of-tps-as-a-metric",
  "topic": "finance",
  "section": "Finance & Markets",
  "published": "2026-08-17T13:19:30.000Z",
  "source": {
    "name": "HackerNoon",
    "slug": "hackernoon",
    "url": "https://hackernoon.com/solanas-local-fee-markets-reveal-the-limits-of-tps-as-a-metric?source=rss"
  },
  "original_language": "en",
  "account": "Solana's transaction processing speed is commonly measured in transactions per second (TPS). However, this metric alone does not fully capture the experience of application developers, particularly when a single, popular application experiences sudden spikes in demand. This is where Solana's local fee markets come into play, providing a more nuanced understanding of network congestion.\n\nThe issue with treating blockspace as a single market is that it fails to account for the fact that different applications contend for distinct sets of state. For example, a heavily used DeFi protocol and a simple USDC transfer transaction could both cause congestion, but only the DeFi protocol transaction would be affected by increased fees.\n\nSolana's account-based execution model allows the network to make congestion local, by explicitly identifying which accounts a transaction reads from and writes to. This enables the runtime to determine which transactions can execute concurrently, and which ones conflict over state. Consequently, a transaction that competes for the same state as a popular application's transactions will experience higher fees, while unrelated transactions will remain unaffected.\n\nThe key insight here is that congestion can be localized to specific application states. Solana's fee model consists of a base fee and an optional prioritization fee. The prioritization fee increases the likelihood of the transaction being scheduled by the current leader, but it is targeted towards transactions that compete for the same state.\n\nDevelopers can optimize their transaction fees by specifying a compute-unit limit and a price per compute unit. This allows them to balance cost and performance, taking into account the compute resources required for their transactions. By thinking about congestion in terms of specific application states rather than global TPS, developers can make more informed decisions about how to design their applications and manage resource usage.\n\nHowever, local fee markets are not a panacea for scalability issues. If multiple users attempt to modify the same state, that state remains a bottleneck, regardless of fee optimization. Therefore, state design becomes a critical aspect of overall performance, and efficient account layout is essential for scalability.\n\nIn summary, Solana's local fee markets offer a more precise way to understand network congestion and its impact on application performance. By focusing on specific application states rather than global TPS, developers can design their applications more effectively and make informed decisions about resource allocation, ultimately leading to better user experiences even during periods of high demand.",
  "summary": "Why Solana's local fee markets matter more than TPS for managing congestion, improving fee efficiency, and designing scalable blockchain applications.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}