[Spike] Investigate atomic commit for public and quorum private data

hyperledger / besu

An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu

https://www.hyperledger.org/projects/besu

Apache License 2.0

1.52k stars 847 forks source link

[Spike] Investigate atomic commit for public and quorum private data #1849

Closed pinges closed 1 year ago

pinges commented 3 years ago

Find out how we might resolve this.

vmichalik commented 3 years ago

Currently atomicity isn't guaranteed with the public and private transactions. There's a small possibility for these to fall out of sync and cause the private state to diverge.

vmichalik commented 3 years ago

Timebox this to two days

non-fungible-nelson commented 1 year ago

Closing for GoQuorum privacy deprecation in Besu.