![]() ![]() You don't necessarily need to have an archival node for your indexer. ![]() An archival node means that the garbage collector is disabled and all of the data is kept on the node. This means that the node has a "garbage collector" enabled which removes old data from storage after five epochs or approx. heads upĪ regular node runs with the archival option disabled by default in its config.json. This will create a folder that keeps the database of the blockchain state and whenever you sync your node this data folder will be the same as the other nodes on the network. Setup Īll of this can be generated via nearcore's neard crate, but an easier way is to use the exposed init_configs from NEAR Indexer Framework. Because this process can take anywhere from a few hours to a few days we will connect to a localnet so you can get your indexer up and running in a matter of minutes. This means the node will need to download all the blocks and apply all the changes to your instance of the blockchain state. If you connect to testnet or mainnet your node will need to be fully synced with the network. ![]() Run cargo check to ensure you setup everything correctly before proceeding to connecting to a network.Let indexer_config = near_indexer::IndexerConfig ", serde_json::to_value(streamer_message).unwrap())
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |