Filecoin Project released Lotus Node v1.36.2 as a recommended patch release focused on Ethereum JSON-RPC correctness, StateWaitMsg behavior, dependency reliability and operator tooling. The main upgrade warning concerns tracing: the deprecated Jaeger exporter has been replaced by an OTLP HTTP exporter, and LOTUS_JAEGER_* environment variables are no longer supported. Operators need to move to the documented OTEL endpoint and insecure-transport settings where applicable.
In the Ethereum-compatible API, eth_call and eth_estimateGas now accept a from address that is an EVM contract or does not yet exist on chain, aligning behavior with Geth and unblocking cases such as Safe SDK EIP-1271 checks and gas estimation before funding an account. Transaction and receipt RPCs now return null for hashes replaced before execution, and filters with more than four topic positions are rejected in line with Ethereum JSON-RPC semantics.
StateWaitMsg is fixed so a non-zero confidence request actually waits even when the message was already executed by the current head when the call began. Full nodes reject confidence above chain finality while lotus-gateway has its own configurable limit. Explicit null epochs are also handled more carefully in block-execution ETH APIs instead of silently resolving to a previous tipset where that would be semantically incorrect.
For FIL, this is an operational compatibility patch rather than a token-economics event. The important operator tasks are migrating tracing configuration, validating downstream Ethereum tooling and confirming applications that depend on StateWaitMsg or null-epoch RPC behavior after rollout.