ord.yaml

# example config

# see `ord --help` for setting documentation

bitcoin_data_dir: /var/lib/bitcoin
bitcoin_rpc_password: bar
bitcoin_rpc_url: https://localhost:8000
bitcoin_rpc_username: foo
chain: mainnet
commit_interval: 10000
config: /var/lib/ord/ord.yaml
config_dir: /var/lib/ord
cookie_file: /var/lib/bitcoin/.cookie
data_dir: /var/lib/ord
first_inscription_height: 100
height_limit: 1000
hidden:
- 6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0
- 703e5f7c49d82aab99e605af306b9a30e991e57d42f982908a962a81ac439832i0
index: /var/lib/ord/index.redb
index_addresses: true
index_cache_size: 1000000000
index_runes: true
index_sats: true
index_spent_sats: true
index_transactions: true
integration_test: true
no_index_inscriptions: true
server_password: bar
server_url: http://localhost:8888
server_username: foo

# DB must already exist, tables will be automatically created
db_connection_string: mysql://username:password@localhost:3306/database_name

# if you want to reindex (i.e. new db/new db format/new s3 bucket), this will setting will start the indexer from the desired number, rather than the last populated number in db
# start_number_override: 0

# AWS S3 bucket name
s3_bucket_name: vermilion-ordinals

# Skip uploading inscription numbers before this number. Saves money if you have already uploaded inscriptions to s3
s3_upload_start_number: 0

# Make a HEAD request to s3 to check if inscription content exists before making a POST upload
# Useful if unsure what inscription numbers have been uploaded. HEAD requests are 8% the price of a POST, so can save money.
s3_head_check: true