1 of 4

GH-3088-db_direct_access-as-default

The config setting chain:db_direct_access: true is made the new default. This will provide much greater consistency protection. To be enabled, the database must be on the new format (column families). If the db hasn't yet been migrated to, or created from scratch in the new format, db_direct_access will NOT be enabled, and a warning message will be produced, prompting for this problem to be addressed.

GH-4087_http_endpoint_info_inner_txs

Fixes a bug in /transactions/{hash}/info endpoint: when the transaction that has info (contract create/call/force progress) is wrapped around a meta transaction or a paying-for transaction: the info of the inner transaction was not provided in the response. This is now fixed.

A config option, mempool:sync_start (integer) has been introduced to control when syncing of the mempool starts during chain sync. A positive number denotes the height at which to begin syncing; a negative number denotes how far from the network top height (best guess by the sync logic) to start. Default is -500, i.e. start syncing the mempool 500 blocks from the top. A mempool sync is always triggered when chain sync is done, and if a negative value greater than the top height is given, sync starts from 0, i.e. from the beginning.

The config setting chain:db_direct_access: true is made the new default. This will provide much greater consistency protection. To be enabled, the database must be on the new format (column families). If the db hasn't yet been migrated to, or created from scratch in the new format, db_direct_access will NOT be enabled, and a warning message will be produced, prompting for this problem to be addressed.

A config option, mempool:sync_start (integer) has been introduced to control when syncing of the mempool starts during chain sync. A positive number denotes the height at which to begin syncing; a negative number denotes how far from the network top height (best guess by the sync logic) to start. Default is -500, i.e. start syncing the mempool 500 blocks from the top. A mempool sync is always triggered when chain sync is done, and if a negative value greater than the top height is given, sync starts from 0, i.e. from the beginning.