pull down to refresh

OpenTimestamps is not a solution for the problem Citrea is facing. They need a proof-of-publication: proof that data was widely published.
OpenTimestamps just doesn't solve that problem, and fundamentally can't.
Lightning uses this concept too: HTLCs are a proof of publication mechanism too. If they go on chain, the transaction ensures that the pre-image is made publicly available, ensuring the next entity learns the pre-image that they need to collect their funds.
Good explainer...
Do you suppose a hypothetical Shitrea could carry forward the entire history with each update? this would obviously result in bloating itself toward unusability, but for shit shootings sake, do so instead of socializing that cost to the chain?
reply