feat: modify shuttle for snapchain migration #2413
Closed
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.
We need a way to upload hub messages to snapchain nodes. The exiting
submitMessage
endpoint doesn't work because snapchain uses qualified module names in protos while existing hubs don't. This means existing hub clients can't communicate with the snapchain servers viasubmitMessage
.Merge Checklist
Choose all relevant options below by adding an
x
now or at any time before submitting for reviewPR-Codex overview
This PR introduces enhancements and new features to the
shuttle
application, including improved message reconciliation, support for a newSNAPCHAIN_HOST
, and updates to the database schema for better handling of on-chain events.Detailed summary
SNAPCHAIN_HOST
to the environment configuration.CLEAR_DB
option for database management.docker-compose.yml
to include a newpostgres2
service.worker.ts
for job processing.BasicHubSubscriber
class for handling event streams.allActiveDbMessagesOfTypeForFid
function for improved database querying.App
class for reconciling on-chain events.