ljedrz

Other than the fact that I agree that we should instead have something like https://github.com/AleoHQ/snarkOS/issues/1554 in place, this workaround should be adjusted as follows: 1. the first few early returns...

The CI jobs should succeed once https://github.com/AleoHQ/snarkOS/pull/1625 is merged and this PR is rebased on top of it.

Rebased, fixed the related `clippy` lint, added `Map::abort_atomic` and 2 unit tests. > Question 1: what happens if a method return Err(..) in between start_atomic and finish_atomic? Is it possible...

@howardwu are we still pursuing this?

Not applicable to testnet3.

the `clippy` job failure is unrelated: https://github.com/briansmith/ring/issues/1469

Rebased.

Rebased.

My primary concern was that something was broken in the new pool-related messages that the nodes were sending, but it turns out it's a very mild issue after all. >...

Not applicable to testnet3.