Validate provider collateral for a 32 GiB verified market deal
A proposal builder should check collateral bounds for the actual piece size and verified status. Copying a value from a previous deal can fail when network conditions change.
Use the padded piece size
The example describes a verified proposal with a 32 GiB padded piece, expressed as 34359738368 bytes. Use the padded size of the proposed piece and the matching verified flag when asking your Lotus node.
{"jsonrpc":"2.0","id":1,"method":"Filecoin.StateDealProviderCollateralBounds","params":[34359738368,true,[]]}
Validate before signing the proposal
Parse Min and Max as attoFIL integers and compare the provider's proposed collateral against both limits. Keep the sampled tipset with the calculation and recheck delayed proposals. Satisfying the bounds checks only one requirement; funding and the rest of the deal terms still matter.