[code cleanup] fix handleGetPayload to save every payload once the signature is verified #512
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.
📝 Summary
Previously, the payloads were only saved by the goroutine at the end of the function if the publication was successful. This caused an issue where we didn't save a delivered payload despite receiving a valid signature from the proposer.
I modified the function to be deferred immediately after the signature is successfully verified.
⛱ Motivation and Context
Once the signature is verified, the payload should be saved no matter what. Even if the publication fails for whatever reason, we want to store the cryptographic evidence that the proposer signed the header.
✅ I have run these commands
make lint
make test-race
go mod tidy
CONTRIBUTING.md