//! The extension for optionally checking the metadata hash. For information how it works and what
//! compile time, it requires a little bit more setup. To have this environment variable available
//! recommended to only enable the metadata hash generation when doing a build for a release or when
/// The metadata hash is cryptographical representation of the runtime metadata. This metadata hash
/// is build as described in [RFC78](https://polkadot-fellows.github.io/RFCs/approved/0078-merkleized-metadata.html).
/// This metadata hash should give users the confidence that what they build with an online wallet
/// that the online wallet is not tricking the offline wallet into decoding and showing an incorrect
/// extrinsic, the offline wallet will include the metadata hash into the additional signed data and
/// verification will fail and thus, the transaction will be rejected. The RFC contains more details
/// controlling if the metadata hash should be added to the signed data or not. Mode `0` means that
/// the metadata hash is not added and thus, `None` is added to the signed data. Mode `1` means that
/// the metadata hash is added and thus, `Some(metadata_hash)` is added to the signed data. Further
/// environment variable is for example set by the `substrate-wasm-builder` when the feature for
/// generating the metadata hash is enabled. If the environment variable is not set and `mode = 1`