nautechsystems/nautilus_trader · critical

Failed to initialize AES-256-GCM payload key

Error message

Failed to initialize AES-256-GCM payload key

What it means

payload_key constructs a RandomizedNonceKey for AES-256-GCM from a 32-byte key. If the AEAD primitive cannot be initialized with the supplied key material, the error is returned instead of panicking. This almost always indicates a crypto runtime failure rather than user input, since any 32-byte key is nominally valid for AES-256-GCM.

Source

Thrown at crates/adapters/blockchain/src/execution/sealing.rs:496

}

fn decode_key(value: &str) -> anyhow::Result<Zeroizing<[u8; 32]>> {
    let value = value.strip_prefix("0x").unwrap_or(value);
    hex::decode_to_array::<_, 32>(value)
        .map(Zeroizing::new)
        .map_err(anyhow::Error::from)
}

fn key_id(key: &[u8; 32]) -> [u8; KEY_ID_LEN] {
    digest(&SHA256, key)
        .as_ref()
        .try_into()
        .expect("SHA-256 output is 32 bytes")
}

fn payload_key(key: &[u8; 32]) -> anyhow::Result<RandomizedNonceKey> {
    RandomizedNonceKey::new(&AES_256_GCM, key)
        .map_err(|_| anyhow::anyhow!("Failed to initialize AES-256-GCM payload key"))
}

#[cfg(test)]
mod tests {
    use alloy::primitives::{address, b256};
    use rstest::rstest;

    use super::*;

    const ACTIVE_KEY: [u8; 32] = [0x11; 32];
    const RETIRED_KEY: [u8; 32] = [0x22; 32];
    const OTHER_KEY: [u8; 32] = [0x33; 32];

    fn key_set(active: [u8; 32], retired: Vec<[u8; 32]>) -> PayloadKeySet {
        PayloadKeySet::from_key_bytes(
            Zeroizing::new(active),
            retired.into_iter().map(Zeroizing::new).collect(),
            "deployment-a".to_string(),

View on GitHub (pinned to 18893faf8b)

Solutions

1. Check CPU AES support (grep aes /proc/cpuinfo on Linux) and enable AES-NI or switch to a software AES backend
2. Rebuild with crypto crate features that include a portable fallback (e.g. aes with the soft feature)
3. Log the key length and verify 32 bytes are passed; regenerate the key if it may be malformed
4. Upgrade the aes/rand-chacha dependency versions to a known-good combination

let key = match payload_key(&key_bytes) {
    Ok(k) => k,
    Err(e) if e.to_string().contains("Failed to initialize AES-256-GCM") => {
        // fatal: fail startup with a clear message about CPU crypto support
        anyhow::bail!("crypto backend unavailable: {e:#}");
    }
    Err(e) => return Err(e),
};

When it happens

Trigger: Calling from_key_bytes() where RandomizedNonceKey::new(&AES_256_GCM, key) fails — e.g. the AES-NI/hardware crypto feature is unavailable on the CPU, or the crypto backend was compiled without the needed feature flags.

Common situations: Running on hardware without AES instruction support with a ring/aes backend requiring it; an unusual RustCrypto feature-gating combination in the build; CPU with disabled crypto extensions in a VM.

Related errors

• Latency model should be initialized
• Execution client should be initialized
• Database is not initialized, so we cannot properly bootstrap
• Pool is not initialized and it doesn't contain initial price
• Pool profiler for {instrument_id} is not initialized

AI-assisted analysis of nautechsystems/nautilus_trader@18893faf8b (2026-09-08). Data as JSON: /api/errors/7f9ee1520bbd5a97. Report an issue: GitHub.