clabby

Results 58 comments of clabby

> @clabby this seems like a great idea. do u have the capacity to implement this? Bandwidth constrained at work over the next couple of weeks, but can soon! Spoke...

> Can you confirm @clabby ? That decision hasn't been made. I still think we should remove this.

* **#266** 👈 * `main` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @clabby and the rest of your teammates on Graphite

Closing this PR. If we are to upgrade the dispute system, I think that we should consider using [Dave](https://arxiv.org/pdf/2411.05463) by Cartessi. It's an elegant design with a proper formal definition,...

* **#177** * **#259** 👈 (View in Graphite) * `main` This stack of pull requests is managed by Graphite. Learn more about stacking.

@axelKingsley > My other question is around the selection of the Merkle Tree. Seems a good choice for compact storage, but this doc also points out that it only requires...

Hoping this will be fixed in #429 - let me know if you still experience this issue.

* **#353** 👈 * `main` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @clabby and the rest of your teammates on Graphite

We will not be including this in our first release for the upcoming alpha deployment. Please do not merge this PR just yet. Waiting on https://github.com/ethereum-optimism/optimism/pull/11055

> The timestamp invariant should be independent of the snapshot construction. I buy this. In the proof, we have context of the snapshot construction, but I can see how leaking...