Check the onboarding window for a Filecoin verified allocation
A client can authorize verified storage for a particular piece and provider before onboarding. The allocation contains a deadline for claiming it and separate bounds on storage duration.
Read the client-scoped allocation
Replace the first argument with the client address and the second with its allocation ID. Match the returned provider, data commitment and padded size against the intended onboarding manifest.
{"jsonrpc":"2.0","id":1,"method":"Filecoin.StateGetAllocation","params":["f01234",87,[]]}
Compare epochs with durations
Expiration is the bound for using the allocation. TermMin and TermMax constrain the commitment duration in epochs. Treating either duration as an absolute epoch can produce an impossible sector plan. An allocation that matches the piece is still a reservation; look for the resulting claim after onboarding.