raulk

> Our discovery DHT stores them, anyway. Where can I learn more about this? _Our discovery DHT_ means the ENR variant of the discovery DHT? From what I know, the...

We can also characterise them in terms of properties. Batches provide no ACID guarantees and are mainly used for performance reasons; transactions provide atomicity and isolation guarantees.

Moving to builtin-actors since actors now reside there, and RLE encoding is actor-specific.

> Users will also have to configure a high and low watermark for the transients directory. The dagstore will kickstart an automated GC when it detects that the size of...

> Known Edge Case The edge case seems pretty dangerous. Is it possible to identify this livelock situation in the garbage collector, and interrupt transient downloads to vacate more space?

Note that there are new edge cases that emerge from such situations, e.g. a malicious user forcing the system to download a huge transient to DoS all other active downloads.

Which protocols are unable to report a shard size in your use case? Having unknown shard sizes is acceptable for trusted scenarios, but definitely a no-go for untrusted/adversarial scenarios. An...

@Stebalien mind pasting a link to the code that validates _manually_, to illustrate the case here? 🙏

I think there's an implicit decision being taken here, which is to model segments as indexed entries over a single shard (= storage deal in the Filecoin context), instead of...

Thanks! I think the case for shard == segment isn't strong today, but it may strengthen over time as selective unsealing becomes available, PoDSI gains traction, and segment-based access patterns...