nautechsystems/nautilus_trader · error

Contract address should be set in logs

Error message

Contract address should be set in logs

What it means

parse_fee_protocol_collect_event_hypersync unwraps log.address with expect() because the CollectProtocol event's emitting address defines the pool identifier. Hypersync logs are expected to always carry an address; if absent, the parser panics, as documented in its # Panics section.

Source

Thrown at crates/adapters/blockchain/src/exchanges/parsing/uniswap_v3/fee_protocol_collect.rs:83

    let recipient = extract_address_from_topic(log, 2, "recipient")?;

    if let Some(data) = &log.data {
        let data_bytes = data.as_ref();

        // Validate the data contains 2 parameters of 32 bytes each
        if data_bytes.len() < 2 * 32 {
            anyhow::bail!("CollectProtocol event data is too short");
        }

        let decoded = match <FeeProtocolCollectEventData as SolType>::abi_decode(data_bytes) {
            Ok(decoded) => decoded,
            Err(e) => anyhow::bail!("Failed to decode CollectProtocol event data: {e}"),
        };

        let pool_address = Address::from_slice(
            log.address
                .clone()
                .expect("Contract address should be set in logs")
                .as_ref(),
        );
        let pool_identifier = PoolIdentifier::Address(Ustr::from(&pool_address.to_string()));

        Ok(FeeProtocolCollectEvent::new(
            dex,
            pool_identifier,
            extract_block_number(log)?,
            extract_transaction_hash(log)?,
            extract_transaction_index(log)?,
            extract_log_index(log)?,
            sender,
            recipient,
            decoded.amount0,
            decoded.amount1,
        ))
    } else {
        anyhow::bail!("Missing data in CollectProtocol event log");

View on GitHub (pinned to 18893faf8b)

Solutions

1. Include address in the Hypersync query field selection.
2. Guard calls with a check that log.address.is_some() and skip otherwise.
3. Convert expect to ok_or + anyhow error for graceful failure.

Example fix

// before
let pool_address = Address::from_slice(
    log.address.clone().expect("Contract address should be set in logs").as_ref(),
);
// after
let raw_address = log.address.as_ref()
    .ok_or_else(|| anyhow::anyhow!("missing contract address in CollectProtocol log"))?;
let pool_address = Address::from_slice(raw_address.as_ref());

if log.address.is_none() {
    log::warn!("skipping CollectProtocol log without contract address");
    return Ok(());
}
let event = parse_fee_protocol_collect_event_hypersync(dex.clone(), &log)?;

fn has_address(log: &HypersyncLog) -> bool {
    log.address.is_some()
}

match parse_fee_protocol_collect_event_hypersync(dex, &log) {
    Ok(event) => handle(event),
    Err(e) => log::error!("failed to parse CollectProtocol log: {e:#}"),
}
// Note: missing address panics via expect(); pre-check log.address before calling.

When it happens

Trigger: Invoking parse_fee_protocol_collect_event_hypersync with a HypersyncLog missing address — from queries that did not select address, partial upstream rows, or fixtures without address, when the data decodes as a CollectProtocol event.

Common situations: Hypersync projection configuration errors; client library upgrades altering field optionality; manually constructed logs in tests like test_hypersync_rpc_match.

Related errors

• Contract address should be set in logs
• Contract address should be set in logs
• Contract address should be set in logs
• Contract address should be set in logs
• Contract address should be set in logs

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