Howard Wu

While I don't have context on the frustration, your report is a valid vulnerability. There's a few remarks I can add to help move this discussion in a positive direction:...

There is the concern that it is possible the user broadcasts 2 or more transactions, whereby the first transaction makes the second (and later) transactions valid. But the verifier will...

Great point, we did add that check in as a preemptive safeguard. I agree it wouldn't be a significant feature change to include this one too. Do you know if...

Closing to prioritize the Demox design

I like the intuition. I would still favor using a lock here over the `Context` even though the `Ledger` is lockable currently. As you know, code changes, and I think...

This design is broken. If the withdrawal address has not been set, a malicious attacker who compromises a validator can use the compromised private key to set a new withdrawal...

Closing as this was superseded by https://github.com/AleoHQ/snarkVM/pull/2385.

This does not seem desirable.

@ljedrz is this issue still relevant? Feel free to propose PRs if there are immediately opportunities to improve memory usage (without impact to runtime performance).

@zhiqiangxu @ljedrz is there a convenient way to `snapshot()` with RocksDB? (that is fast enough to call in consensus) I think this `rollback` approach effectively implements the same `snapshot` mechanism.