Skip to main content

Config Settings

Table Metadata​

PropertyConfiguration
Natural Key(s)config_setting_id, closed_at
Partition Field(s)closed_at (MONTH partition)
Clustered Field(s)last_modified_ledger
Documentationdbt docs

Column Details​

NameDescriptionData TypeDomain ValuesRequired?Notes
config_setting_idConfig setting id typesintegerYes
contract_max_size_bytesMax size of contractintegerNo
ledger_max_instructionsMax instructions per ledgerintegerNo
tx_max_instructionsMax instructions per transactionintegerNo
fee_rate_per_instructions_incrementFee for instructions incrementintegerNo
tx_memory_limitTransaction memory limitintegerNo
ledger_max_read_ledger_entriesMax read ledger entries per ledgerintegerNo
ledger_max_read_bytesMax read bytes per ledgerintegerNo
ledger_max_write_ledger_entriesMax write ledger entries per ledgerintegerNo
ledger_max_write_bytesMax write bytes per ledgerintegerNo
tx_max_read_ledger_entriesMax read ledger entries per transactionintegerNo
tx_max_read_bytesMax read bytes per transactionintegerNo
tx_max_write_ledger_entriesMax write ledger entries per transactionintegerNo
tx_max_write_bytesMax write bytes per transactionintegerNo
fee_read_ledger_entryFee for read ledger entryintegerNo
fee_write_ledger_entryFee for write ledger entryintegerNo
fee_read_1kbFee per 1kb readintegerNo
bucket_list_target_size_bytesBucket list target sizeintegerNo
write_fee_1kb_bucket_list_lowWrite fee for bucket list per 1kbintegerNo
write_fee_1kb_bucket_list_highWrite fee for bucket list per 1kbintegerNo
bucket_list_write_fee_growth_factorWrite growth fee for bucket listintegerNo
fee_historical_1kbFee for historical storage per 1kbintegerNo
tx_max_contract_events_size_bytesMax transaction contract event sizeintegerNo
fee_contract_events_1kbFee for contract event size per 1kbintegerNo
ledger_max_txs_size_bytesMax ledger transaction sizeintegerNo
tx_max_size_bytesMax transaction sizeintegerNo
fee_tx_size_1kbFee for transaction size per 1kbintegerNo
contract_cost_params_cpu_insnsConstant and linear model parameters for cost parameters for CPUintegerNo
contract_cost_params_mem_bytesConstant and linear model parameters for cost parameters for memoryintegerNo
contract_data_key_size_bytesMax size of contract data keysintegerNo
contract_data_entry_size_bytesMax size of contract data entriesintegerNo
max_entry_ttlMax TTL that can be set for an entry (sequence created at + this)integerNo
min_temp_entry_ttlMin temporary entry TTL (sequence created at + this)integerNo
min_persistent_entry_ttlMin persistent entry TTL (sequence created at + this)integerNo
auto_bump_ledgersAutomatic bump ledgers amountintegerNo
persistent_rent_rate_denominatorPersistent entry rent rate denominatorintegerNo
temp_rent_rate_denominatorTemporary entry rent rate denominatorintegerNo
max_entries_to_ttlMax entries to TTLintegerNo
bucket_list_size_window_sample_sizeBucket list size window sample sizeintegerNo
eviction_scan_sizeEviction scan sizeintegerNo
starting_eviction_scan_levelStarting eviction scan levelintegerNo
ledger_max_tx_countMax transactions in a ledgerintegerNo
bucket_list_size_windowBucket list size windowintegerNo
min_temporary_ttlThe minimum number of entries for which a temporary entry can live on the ledgerintegerNo
min_persistent_ttlThe minimum number of entries for which a persisted entry can live on the ledgerintegerNo
max_entries_to_archiveMaximum number of entries that emit archival meta in a single ledgerintegerNo
last_modified_ledgerThe ledger sequence number when the ledger entry (this unique signer for the account) was modified. Deletions do not count as a modification and will report the prior modification sequence numberintegerYes
ledger_entry_changeCode that describes the ledger entry change type that was applied to the ledger entry.integerYes
deletedIndicates whether the ledger entry (balance id) has been deleted or not. Once an entry is deleted, it cannot be recovered.booleanYes
batch_idString representation of the run id for a given DAG in Airflow. Takes the form of "scheduled__<batch_end_date>-<dag_alias>". Batch ids are unique to the batch and help with monitoring and rerun capabilitiesstringYes
batch_run_dateThe start date for the batch interval. When taken with the date in the batch_id, the date represents the interval of ledgers processed. The batch run date can be seen as a proxy of closed_at for a ledger.datetimeYes
batch_insert_tsThe timestamp in UTC when a batch of records was inserted into the database. This field can help identify if a batch executed in real time or as part of a backfilltimestampYes
closed_atTimestamp in UTC when this ledger closed and committed to the network. Ledgers are expected to close ~every 5 secondstimestampYes
ledger_sequenceThe sequence number of this ledger. It represents the order of the ledger within the Stellar blockchain. Each ledger has a unique sequence number that increments with every new ledger, ensuring that ledgers are processed in the correct order.integerYes