Record state transition: snapshot submission to relayer #41
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.
Fixes #40
Checklist
Current behaviour
As further detailed in the pooler issue PowerLoom/pooler#40, at present there is no information captured on the state transitions that a snapshot goes through from the point an epoch is released to it being finalized on the protocol state contract.
One of the important state transitions happens to be
RELAYER_SEND
- Payload commit service has sent the snapshot to a transaction relayer to submit to the protocol state contractThis information is required to be captured by the payload commit service to offer a complete view of the state transition status of a snapshot.
New expected behaviour
The payload commit service records the responses returned from the relayer or the barebones EVM node to which it sends raw transactions.
audit-protocol/go/payload-commit/service/service.go
Lines 255 to 265 in 406fdba
This information is stored against the Redis key REDIS_KEY_EPOCH_STATE_ID with the following data structure:
audit-protocol/go/goutils/datamodel/data_model.go
Lines 12 to 17 in 406fdba
Change logs
Added
Deployment Instructions
NA