Skip to content

Refresh Lite FullNode page against current source code#609

Open
abn2357 wants to merge 8 commits into
tronprotocol:masterfrom
abn2357:fix_lite_node
Open

Refresh Lite FullNode page against current source code#609
abn2357 wants to merge 8 commits into
tronprotocol:masterfrom
abn2357:fix_lite_node

Conversation

@abn2357
Copy link
Copy Markdown
Contributor

@abn2357 abn2357 commented May 26, 2026

Summary

  • Tighten the snapshot description: it covers all state DBs, not only account state, and the outdated "≈3%" size ratio is replaced with a qualitative comparison.
  • Note that the snapshot's 65,536-block recent window is a hardcoded constant in the toolkit and cannot be changed via configuration, and explain that the value (= 2^16) matches TRON's transaction ref_block_hash window — a Lite FullNode must retain at least this many recent blocks to validate incoming transactions.
  • Sharpen the description of openHistoryQueryWhenLiteFN: enabling it re-opens the filtered APIs, while pre-snapshot history remains unavailable.
  • Correct the Lite FullNode API behavior description (it disables, not supports, historical queries) and add the missing link to the maintenance-section pruning tool.
  • Link the HTTP / gRPC filter references to their source files on the master branch.
  • Unify capitalization to FullNode / Lite FullNode throughout the page and drop a duplicated blank line above the maintenance heading.

Test plan

  • mkdocs serve renders the page without warnings.
  • In-page links toolkit.md/#lite-fullnode-data-pruning and backup_restore.md/#lite-fullnode-data-snapshots jump to the correct sections.
  • HTTP / gRPC GitHub links resolve on the master branch.

abn2357 added 8 commits May 26, 2026 16:05
- Change 'supports historical data queries' to 'disables historical
  data queries' so the description matches actual Lite Fullnode behavior.
- Link 'Lite Fullnode Pruning Tool' in the Maintenance section to the
  toolkit page, consistent with the Deployment section.
The snapshot size is bounded by a fixed block count (~65,536) and the
account state, while a Fullnode's data grows over time, so the 3%
ratio is not stable. Replace it with a qualitative comparison.
- Unify capitalization to FullNode throughout the page.
- Link HTTP and gRPC filter references to their source files on master.
- Reword the Extendable Functionality bullet so it precisely describes
  the flag's effect (re-opens the filtered APIs) and the data
  limitation (no pre-snapshot history).
The DbLite snapshot dataset is built from every database except the
archive DBs (block / block-index / trans), so it covers all state DBs
(account, contract, asset, witness, votes, delegation, exchange,
proposal, market, ...), not only the account state.
Drop the approximate '~' qualifier and add an explicit sentence stating
the value is hardcoded in the toolkit and cannot be changed via
configuration.
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.

1 participant