# Configuration properties · Chromia Docs (concept)

> This topic outlines the key configuration options available in the BaseBlockChainConfiguration, providing descriptions, types, and default values for each…

Source: https://docs.chromia.com/build/configuration/blockchain-properties/

# Configuration properties

On this page

* [How to configure blockchain properties](#how-to-configure-blockchain-properties)
* [Core configuration properties](#core-configuration-properties)
* [Features configuration (under the key features )](#features-configuration-under-the-key-features)
* [Block strategy configuration (under the key blockstrategy )](#block-strategy-configuration-under-the-key-blockstrategy)
* [GTX configuration (under the key gtx )](#gtx-configuration-under-the-key-gtx)
* [Revolt configuration (under the key revolt )](#revolt-configuration-under-the-key-revolt)

This topic outlines the key configuration options available in the `BaseBlockChainConfiguration`, providing
descriptions, types, and default values for each parameter.

## How to configure blockchain properties

You can configure these properties in your `chromia.yml` file under the `config` section of each blockchain:

YAML

```
blockchains:
  my_blockchain:
    module: main
    config:
      signers:
        - "pubkey1"
        - "pubkey2"
      configurationfactory: "net.postchain.devtools.KeyPairHelper"
      features:
        merkle_hash_version: 2
      blockstrategy:
        name: "net.postchain.base.BaseBlockBuildingStrategy"
        maxblocksize: 1048576
        maxblocktransactions: 100
      gtx:
        modules:
          - "net.postchain.rell.module.RellPostchainModuleFactory"
```

## Core configuration properties

| **Name** | **Description** | **Type** | **Required** | **Default** |
| --- | --- | --- | --- | --- |
| `signers` | List of blockchain signers. | array | ✅ |  |
| `sync` | Specifies the synchronization infrastructure implementation. | string |  | `""` |
| `sync_ext` | Extensions for the synchronization infrastructure.   *For [term missing in the official docs], these are the default allowed synchronization extensions:   `net.postchain.d1.icmf.IcmfReceiverSynchronizationInfrastructureExtension`,  `net.postchain.eif.EifSynchronizationInfrastructureExtension`* | array |  | `[]` |
| `configurationfactory` | Defines the configuration factory implementation. | string | ✅ |  |
| `txqueuecapacity` | Maximum number of transactions that can be queued before processing. | int |  | `2500` |
| `historic_brid` | Sets the historical Blockchain RID when forking a blockchain. | bytea |  |  |
| `dependencies` | Specifies blockchain dependencies in raw format (GTV format). | gtv |  |  |
| `config_consensus_strategy` | Defines the consensus strategy for configuration settings. | string |  |  |
| `query_cache_ttl_seconds` | The maximum duration (in seconds) for caching query responses. `0` disables caching entirely. | int |  | `0` |
| `async_query_queue_capacity` | Maximum size of the queue for async queries, `0` disables this feature. | int |  | `0` |
| `async_query_timeout_seconds` | Timeout for async queries in seconds. | int |  | `3600` (1 hour) |
| `async_query_result_retention_seconds` | How many seconds to keep the result of an async query after it is completed. | int |  | `3600` (1 hour) |
| `query_timeout_seconds` | Timeout for sync queries in seconds. Zero or negative value disables the timeout. | int |  | `60` (1 min) |
| `max_block_future_time` | Defines the maximum allowable time difference between a block’s timestamp and the current time (in milliseconds). This ensures that blocks cannot be excessively post-dated, maintaining blockchain integrity. A value of `-1` disables this check entirely. | int |  | `60000` |
| `add_primary_key_to_header` | When enabled, the primary node includes its public key in the block header. However, this value is not verified and should only be trusted for features where nodes are incentivized to honestly include their own key. | boolean |  | `false` |

### Features configuration (under the key `features`)

| **Name** | **Description** | **Type** | **Default** |
| --- | --- | --- | --- |
| `merkle_hash_version` | Specifies the Merkle hash version to use for transaction hashing and RID computation. Version 1 is deprecated due to hash collision bugs. Version 2 is the current recommended version. | int | `2` |

### Block strategy configuration (under the key `blockstrategy`)

| **Name** | **Description** | **Type** | **Default** |
| --- | --- | --- | --- |
| `name` | The block strategy class implementing `net.postchain.core.block.BlockBuildingStrategy`. | string |  |
| `maxblocksize` | Maximum block size in bytes.   *For [term missing in the official docs], the maximum allowed block size is 27262976 (26 MiB).* | int | `26 * 1024 * 1024` |
| `maxblocktransactions` | Maximum number of transactions per block. | int | `100` |
| `mininterblockinterval` | Minimum time (in milliseconds) between two consecutive blocks.   *For [term missing in the official docs], the minimum value allowed for inter block interval is 1000 (1 second).* | int | `25` |
| `maxblocktime` | Maximum time (in milliseconds) to wait before starting to build a block. If the queue is empty, an empty block will be built. | int | `30000` |
| `maxtxdelay` | Maximum time (in milliseconds) to wait after the first transaction is received before building a block. | int | `1000` |
| `minbackofftime` | Minimum time (in milliseconds) to wait before retrying a failed block build. | int | `20` |
| `maxbackofftime` | Maximum time (in milliseconds) to wait before retrying a failed block build. | int | `2000` |
| `maxspecialendtransactionsize` | Maximum size (in bytes) for a special end transaction in a block. | int | `1024` |
| `preemptiveblockbuilding` | Enables or disables preemptive block building. | boolean | `true` |

### GTX configuration (under the key `gtx`)

| **Name** | **Description** | **Type** | **Default** |
| --- | --- | --- | --- |
| `max_transaction_size` | Maximum allowable size (in bytes) for individual transactions. | int | `25 * 1024 * 1024` |
| `max_transaction_signatures` | Maximum number of signatures for a transaction | int | `100` |
| `modules` | Specifies the GTX modules to be included.   *For [term missing in the official docs], these are the default allowed GTX modules:   `net.postchain.rell.module.RellPostchainModuleFactory`,  `net.postchain.gtx.StandardOpsGTXModule`,  `net.postchain.d1.icmf.IcmfSenderGTXModule`,  `net.postchain.d1.icmf.IcmfReceiverGTXModule`,  `net.postchain.d1.iccf.IccfGTXModule`,  `net.postchain.eif.EifGTXModule`,  `net.postchain.web.WebStaticGTXModuleFactory.`* | array |  |
| `allowoverrides` | Determines whether operations and queries with the same name can be overridden by other GTX modules. | boolean | `false` |
| `slow_op_threshold` | The threshold for defining a slow operation, in milliseconds. Operations deemed slow are logged at the INFO level; setting this value to `-1` disables this logging. | int | `-1` |
| `slow_prioritization_query_threshold` | The threshold for defining a slow prioritization query, in milliseconds. Slow queries are logged at INFO level, `-1` disables this logging. | int | `-1` |

### Revolt configuration (under the key `revolt`)

| **Name** | **Description** | **Type** | **Default** |
| --- | --- | --- | --- |
| `timeout` | Default revolt timeout period (in milliseconds). | int | `10000` |
| `exponential_delay_initial` | Initial delay (in milliseconds) before increasing the revolt timeout. | int | `1000` |
| `exponential_delay_power_base` | The power base used to exponentially increase the revolt timeout per round. | string | `1.2` |
| `exponential_delay_max` | Maximum allowable revolt timeout (in milliseconds). | int | `600000` |
| `fast_revolt_status_timeout` | Time (in milliseconds) since the last status message before a node is considered disconnected. | int | `-1` |
| `revolt_when_should_build_block` | Begins counting the revolt timeout when it's considered possible to build a block. | boolean | `false` |

[View this page on docs.chromia.com](https://docs.chromia.com/build/configuration/blockchain-properties/)Content mirrored from the live docs
