Callum Waters

The same reason why the LN would be preferred to the celestia client in all cases, security. The LN verifies headers and samples which is more secure than the celestia...

> However as you mentioned headers and samples are needed for particular users. Yeah, it's unclear to me whether a light node using a paid API provider will: 1. Get...

p2p network fallback could be a cool follow up but is probably not needed for the first implementation. What could also be done (doesn't need to be immediately) is to...

I think most nodes should use "pruning: everything". Unless you're running some indexing service you don't need to save any more than the previous 2 or 3 states.

So the state pruning also affects snapshots. I thought they were saved separated (in the snapshots directory and were unaffected by this parameter). We also discussed reducing the snapshot interval...

If the pruning options do affect snapshotting than I would propose ``` case PruningDefault: return PruningOptions{ KeepRecent: 60, Interval: 10, Strategy: PruningDefault, } ``` And a snapshot interval of 200....

What about the write methods in the blob module and about SubmitTx for the other node methods that involve transaction submission > The easiest way (without breaking) is to introduce...

> re: SubmitTx - we don't expose that as we removed it a long time ago, but we can as long as it's just a shim for TxClient's SubmitTx method...