feat(pdp): add AddRoots tracking endpoints #535
Merged
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.
From #530 for the
synapse
branch.Summary is that
AddRoots
is currently a blind operation, you throw it over to Curio and cross your fingers. This is unlikeCreateProofSets
where you get aLocation
header response which points you to a URL which will give you both the transaction to watch on chain and the status as far as Curio is concerned.This adds similar capabilities for
AddRoots
; you get aLocation
header and the ability to track an AddRoots operation. It also fills in the stub implementation of handleGetProofSetRoot which is a generalised "get me root info" endpoint.This is being used to do the full onboarding lifecycle from the client end, allowing the end-user to track the transaction both on chain and getting Curio confirmation that it agrees it's landed.
and (bugfix):
and: