Will

@coryschwartz we would have to keep a k8s controller in those other regions active to do this, right? maybe a couple more could be reasonable for now?

we have hooks. eg bots call https://github.com/filecoin-project/dealbot/blob/main/engine/engine.go#L363 an example of such is https://github.com/filecoin-project/dealbot/tree/main/scheduler/hooks this is saying that there should be an argument in the scope of a new bot that...

we disabled the long test, right @hannahhoward ? does it still make sense to merge this?

i think i'd probably be okay saying that we would prefer to do this by shutting down the current bot, and spinning up a new one with the newer version.

dealbot will be accessing these deal statuses over the API, so it may have different semantics that what you see on the CLI

@pooja who's the right person to work with in order to ingest such a dataset for deals?

this is doable. what format do you want to provide the tuples in? `, ` (a CSV), or something else?

current discussion here is to support a strict PoDSI deal structure first, while continuing to understand what expectations should be made around arbitrary non-car deals

Boost, as a PL project, continues to push for content addressed formatting of deals. This is part of broader ecosystem alignment as well - while you correctly note that there...

The padding implied by PODSI packing is a significantly higher overhead and financial issue to work through than CAR overhead.