# Features Configuration
Antidote can be configured to use different transaction protocols and recovery strategies.
### Options for environmental variables
| Parameter | Value | Description |
| ------------------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| txn\_cert | true | Write operations are certified during commit. The transaction is aborted if a write conflict is detected (i.e. snapshot isolation is ensured for the updates within a single DC, updates across DCs are not checked) (default). |
| | false | Transactions perform no certification check and always commit (if they do not crash). |
| txn\_prot | clocksi | Uses the [Cure protocol](https://pages.lip6.fr/Marc.Shapiro/papers/Cure-final-ICDCS16.pdf) to define snapshots and causal dependencies (default). |
| | gr | Uses the [Gentle-rain](https://infoscience.epfl.ch/record/202079) protocol to define snapshots and causal dependencies. |
| recover\_from\_log | true | When starting a node, it loads any operations stored on the disk log to the in memory cache of the key-value store (default). |
| | false | When starting a node, the key-value store is empty. |
| recover\_meta\_data\_on\_start | true | Meta-data state is loaded from disk on restart including connection state between other DCs and node names and configurations. Nodes automatically reconnect to other DCs on restart (default). |
| | false | meta-data concerning node names and connections to other DCs is not loaded on restart. |
| sync\_log | true | Local transactions are stored in the log synchronously, i.e., when the reply is sent, the updates are guaranteed to have been stored to disk (this is very slow in the current logging setup). |
| | false | All updates are sent to the operating system to be stored on disk (eventually), but are not guaranteed to be stored durably on disk when the reply is sent (default) |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://antidotedb.gitbook.io/documentation/architecture/configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.