Skip to content

docs: add Base Fee Model section to fee specification#30

Merged
snario merged 4 commits intomainfrom
docs/fee-spec-base-fee-model
Feb 24, 2026
Merged

docs: add Base Fee Model section to fee specification#30
snario merged 4 commits intomainfrom
docs/fee-spec-base-fee-model

Conversation

@snario
Copy link
Contributor

@snario snario commented Jan 23, 2026

Adds a Base Fee Model subsection to the fee specification page.

Changes

  • Added Base Fee Model subsection under Fee Units
  • Documents fixed base fee (vs EIP-1559 dynamic)
  • Explains congestion management mechanisms:
    • Payment lanes for reserved TIP-20 blockspace
    • Priority fees for bidding during high demand
    • Block gas limits for computation constraints
  • Added title to frontmatter for SEO

This addresses the documentation gap around how Tempo handles congestion with fixed fees, which came up during RFP preparation.

Add documentation explaining Tempo's fixed base fee model:
- Fixed base fee vs EIP-1559 dynamic fees
- Target cost of $0.001 for TIP-20 transfers
- Congestion management via payment lanes, priority fees, and gas limits

Also adds title to frontmatter for SEO.
@vercel
Copy link

vercel bot commented Jan 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Error Error Feb 24, 2026 3:19pm
tempo-docs Error Error Feb 24, 2026 3:19pm

Request Review

@snario snario requested a review from danrobinson January 23, 2026 16:49
- Add explicit note that Tempo has no native token and fees are USD-denominated
- Clarify that this removes need to hold volatile assets for gas
- Expand base fee model to explain predictable unit economics for applications
- Add detail on payment lanes preventing crowding from other network activity
- Specify ~94% blockspace reserved for payments, 6% for general computation
- Note allocation is conservative and may increase as throughput scales
- Clarify that general congestion cannot affect payment throughput or fees

Congestion is managed through:

- **Payment lanes**: Reserved blockspace for TIP-20 transfers as specified in the [Payment Lane Specification](/protocol/blockspace/payment-lane-specification). Approximately 94% of blockspace is reserved for payment transactions, with the remaining 6% available for general computation. This allocation is conservative and may increase over time as total throughput scales.
Copy link
Contributor

Choose a reason for hiding this comment

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

consider "This allocation is conservative and the blockspace available for general computation may increase over time as total throughput scales."

Copy link
Contributor

@malleshpai malleshpai left a comment

Choose a reason for hiding this comment

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

minor suggestion

@snario snario merged commit df2d66e into main Feb 24, 2026
5 of 7 checks passed
@snario snario deleted the docs/fee-spec-base-fee-model branch February 24, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants