Check proof compatibility before pointing a Filecoin sealing lab at a network
A small local devnet can support a different set of proof types from a public network. A sealing pipeline that works on the lab profile may be unsuitable after changing endpoints.
Read the network's proof parameters
Send the request to the endpoint selected by the sealing deployment. Inspect NetworkName, SupportedProofTypes, PreCommitChallengeDelay and BlockDelaySecs. Compare the registered proof IDs with the IDs expected by the lab's configuration.
{"jsonrpc":"2.0","id":1,"method":"Filecoin.StateGetNetworkParams","params":[]}
Translate the challenge delay carefully
If a lab uses a 12-epoch delay and 10-second epochs, the nominal delay is 120 seconds. Use values returned for the actual network. The allowed proof type and nominal timing say nothing about worker hardware readiness, proof-parameter files or onchain message inclusion latency.