Curio currently has a temporary workaround in shouldSkipFWSSActivationTerminationBoundary to skip terminated FWSS PDP rails where endEpoch == activationEpoch.
This exists because the current FWSS contract cannot settle that boundary case: validatePayment allows toEpoch == activationEpoch, but the proving-period helper treats that epoch as invalid, leaving Curio with no valid settlement target.
Once the upgraded FWSS contracts are deployed and active, remove this workaround and its tests. Curio should then rely on the contract to handle the activation-boundary case correctly instead of skipping those rails client-side.
This issue should be resolved with a PR once FilOzone/filecoin-services#544 is deployed
Curio currently has a temporary workaround in shouldSkipFWSSActivationTerminationBoundary to skip terminated FWSS PDP rails where endEpoch == activationEpoch.
This exists because the current FWSS contract cannot settle that boundary case: validatePayment allows toEpoch == activationEpoch, but the proving-period helper treats that epoch as invalid, leaving Curio with no valid settlement target.
Once the upgraded FWSS contracts are deployed and active, remove this workaround and its tests. Curio should then rely on the contract to handle the activation-boundary case correctly instead of skipping those rails client-side.
This issue should be resolved with a PR once FilOzone/filecoin-services#544 is deployed