Negative. If the storage node is not submitting an order the customer will also not get charged.
Double spend protection. The storage node and the satellite have to make sure that an uplink / storage node is not submitting the same order more then once. This check comes with some tradeoffs. One of them is that orders need to expire after a few hours.
Under normal conditions this shouldn’t matter. The storage node has a backlog of 2 hours unsibmitted orders. If it goes offline for 3 days it will just lose these 2 hours. The same would happen if we increase the expireation time to lets say a week. The storage node could still lose these 2 hours of unsubmitted orders.
The only issue we get is when bugs occure. Let’s say the storage node is not submitting any orders at all. It took some operators more then a month to notice that. Even if we would have an expire time of let’s say 7 days most of the order would still expire. For that reason we prefer to fix the bug instead of increasing the expiration time.
Something interesting to read: https://review.dev.storj.io/c/storj/storj/+/1732/10/docs/blueprints/sparse-order-storage.md