AddLeaf: use cheaper gRPC endpoint since we already have the inclusion proof #2580
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.
AddLeaf
queues the proposed entry for inclusion into the Trillian log, and then polls to see that an inclusion proof exists for that hash. Finally, we need the integration timestamp to pass back along to the client as a timestamp, and the only way to get that value is to fetch the entire entry again. We currently do that by callingGetEntryAndProof
, which results in a Trillian having to recompute the inclusion proof (which it's already given us) which is more expensive than just reading the leaf itself usingGetLeavesByRange
.This swaps over to the less-complex
GetLeavesByRange
for a lower overhead implementation with equivalent function.