Admin
Tools in the Admin category produce data related to scraping the chain, producing the indexes, and querying the status of the system. Additional data related to sharing the indexes via IPFS and pinning the same are also produced by tools in this category.
Status
The chifra status tool reports on the state (and size) of the various TrueBlocks local binary caches. TrueBlocks produces nine difference caches: abis, blocks, monitors, names, objs, prices, recons, slurps, traces, txs. In general practice, these caches may take up a few GB of hard drive space, however, for very popular smart contract the size of the caches may grow rather large. Keep an eye on it.
The following commands produce and manage status:
| Tools | |
|---|---|
| chifra status | report on the status of the TrueBlocks system |
Status data is made of the following data fields:
| Field | Description | Type |
|---|---|---|
| client_version | the version string as reported by the rpcProvider | string |
| client_ids | netword_id and chain_id from the rpcProvider | string |
| trueblocks_version | the TrueBlocks version string | string |
| rpc_provider | the current rpcProvider | string |
| balance_provider | the current archive node balance provider (defaults to rpcProvider) | string |
| config_path | the path to config files | string |
| cache_path | the path to the local binary caches | string |
| index_path | the path to the local binary indexes | string |
| host | the host portion of the local API server | string |
| is_testing | true if the server is running in test mode |
bool |
| is_api | true if the server is running in API mode |
bool |
| is_docker | true if running under a docker image |
bool |
| is_scraping | true if the index scraper is running |
bool |
| is_archive | true if the rpcProvider is an archive node |
bool |
| is_tracing | true if the rpcProvider provides Parity traces |
bool |
| has_eskey | true if an EtherScan key is present |
bool |
| has_pinkey | true if a Pinata API key is present |
bool |
| ts | the timestamp when this status data was produced | timestamp |
Cache
The chifra status
The following commands produce and manage caches:
| Tools | |
|---|---|
| chifra status | report on the status of the TrueBlocks system |
Cache data is made of the following data fields:
| Field | Description | Type |
|---|---|---|
| type | the type of the cache (one of the nine different types) | string |
| path | the physical path to the cache on the hard drive | string |
| nFiles | the number of files in the cache | uint64 |
| nFolders | the number of subfolders in the cache | uint64 |
| sizeInBytes | the size of the cache in bytes | uint64 |
PinnedChunk
The TrueBlocks index scraper periodically creates a chunked portion of the index so that it can be more easily stored in a content-addresable data store such as IPFS. We call these periodically-created chunks, PinnedChunks. The format of said item is described here. A pinned chunk is effectively a relational table relating all of the addresses appearing in the chunk with a list of appearances appearing in the chunk.
The following commands produce and manage pinnedchunks:
| Tools | |
|---|---|
| chifra scrape | scan the chain and update the TrueBlocks index of appearances |
| chifra pins | manage pinned index of appearances and associated Bloom filters |
Pinnedchunk data is made of the following data fields:
| Field | Description | Type |
|---|---|---|
| fileName | for each chunk, the range of blocks contained in that chunk | string |
| bloomHash | the IPFS hash of the bloom filter at that range | ipfshash |
| indexHash | the IPFS hash of the index chunk at that range | ipfshash |
Manifest
The Manifest details the index of appearance’s PinnedChunks. Each record in the Manifest details the block range represented by the chunk as well as the IPFS hash of the index chunk along with the associated IPFS hash for the Bloom filter of the chunk. The manifest itself is also pushed to IPFS and the IPFS of the hash of the manifest is published periodically to the Unchained Index smart contract.
The following commands produce and manage manifests:
| Tools | |
|---|---|
| chifra scrape | scan the chain and update the TrueBlocks index of appearances |
| chifra pins | manage pinned index of appearances and associated Bloom filters |
Manifest data is made of the following data fields:
| Field | Description | Type |
|---|---|---|
| indexFormat | IPFS cid of file describing the file format of an index chunk | string |
| bloomFormat | IPFS cid of file describing the associated bloom filter | string |
| firstPin | the block number of the first pin in the manifest (always zero) | blknum |
| lastPin | the most recent block included in this manifest | blknum |
| pins | a list of all the pins in the unchained index | CPinnedChunkArray |
Base types
This documentation mentions the following basic data types.
| Type | Description | Notes |
|---|---|---|
| blknum | an alias for a uint64 | |
| bool | a value either true, false, 1, or 0 |
|
| ipfshash | a multi-hash produced by IPFS | mixed-case |
| string | a normal character string | |
| timestamp | a 64-bit unsigned integer | Unix timestamp |
| uint64 | a 64-bit unsigned integer |