HomeGuidesAPI ReferenceChangelog
GuidesAPI ReferenceCommunityDiscordBlogFAQBug BountyAnnouncementsChange Log
Guides

Main Net Database Snapshots

I. Download the Data Snapshot

1.FullNode data snapshot

TRON officially offers database snapshots regularly for quick deployment.

Data SourceDownload siteDescription
Official data source(North America: Virginia)http://47.89.178.46/LevelDB, exclude internal transactions
(About 344G)
Official data source(North America: Virginia)http://47.89.178.46:18811/RocksDB, exclude internal transactions
(About 302G)
Official data source(Singapore)http://47.74.159.117LevelDB, exclude internal transactions
(About 302G)
Official data source(Singapore)http://47.74.159.117/saveInternalTx/LevelDB, include internal transactions
(About 502G)
TronGridhttps://backups.trongrid.io/LevelDB, include internal transactions
(About 502G)

2.Lite FullNode data snapshot

The Tron Public Chain has supported the type of the Lite FullNode since the version of GreatVoyage-v4.1.0 released. All the data required by the Lite FullNode for running is whole of the status data and a little essential block data, so, it is much more lightweight than the normal FullNode. TRON officially offers database snapshots of the Lite FullNode.

Data SourceDownload siteDescription
Official data source(North America: Virginia)http://47.89.178.46/LevelDB (since from backup20201119)

tips: You can split the data from the whole data with the help of the Lite FullNode tool. The usage document of the tool can be seen here: Tutorial

II. How to use the data snapshot

  1. Download the corresponding compressed backup database according to your needs.
  2. Decompress the compressed file of the backup database to the output-directory directory or to the corresponding directory according to your needs.
  3. Startup the node. The node reads the output-directory directory by default. If you need to specify another directory,please add the -d directory parameter when the node starts.

III. Other Important Things

1. What is an internal transaction?

An internal transaction is a transaction extra executed in a smart contract(e.g. call, transfer). Full nodes do not record internal transactions as default, set saveInternalTx = true if needed.

2. LevelDB and RocksDB

The data of LevelDB and RocksDB are not allowed to be mixed. The database can be specified in the config file of the full node, set db.engine to LEVELDB or ROCKSDB.