Will
This work is progressing in https://github.com/filecoin-project/boost/pull/1495
The request here has evolved a bit through discussion. current design thought is a wrapper around the boxo handler in boost-http * look for signaled request for trailing metadata block,...
for `RetrievalContentFilter` - we should try to understand if there's a way to implement such a filter deterministically rather than in the critical retrieval path
This isn't an issue in this repo. i think the only question is where to move it: is the underlying issue in index provider, dag store, boost, or go-fil-markets
nope - doing partial unsealings at faster speed will take a change in the proof system, which is a larger effort that isn't part of the deal inclusion work
@kubuxu is probably the authority here
filing https://github.com/filecoin-project/go-data-segment/issues/9 to see if we can get a fixture to use for validation
That's a good point, though carv2 indexes are in a way an equally opinionated existing equivalent. I'll see what it would look like for the 'get an index for this...
> Making shard == segment could let us keep the dagstore Filecoin-agnostic, but I suspect is not viable without additional complexity. @willscott could you walk us through the tradeoffs here?...