[WIP][DNM] Initial investigations into Late Locking #507
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Late Locking is definitely a better name to describe it clearly. Nice. |
Closed
|
Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this PR is just to explore what we've been calling 'Lock-free transactions` but I think I'm going to just call 'Late Locking' for now, first outlined here https://forum.grin.mw/t/mostly-lock-free-transactions/7313. Will likely require an RFC if we aim to put this in production.
Preliminary work for this was done pre-HF4, so this is just an exploration of how easily it will be to implement and see what issues might come up. From what I can gather now, deciding how to handle the fee is the largest unknown.
WIP, and doesn't yet work, hoping to bring this to a point where a late-lock workflow is implemented in tests.