wormhole-explorer/parser
ftocal 5c2f91d935
Add backfiller command to process vaa saved in database (#349)
* Add endpoint to parse a vaa

* Add backfiller command to process vaa saved in database
2023-05-24 16:52:22 -03:00
..
cmd Add backfiller command to process vaa saved in database (#349) 2023-05-24 16:52:22 -03:00
config Add backfiller command to process vaa saved in database (#349) 2023-05-24 16:52:22 -03:00
consumer Add backfiller command to process vaa saved in database (#349) 2023-05-24 16:52:22 -03:00
http Add backfiller command to process vaa saved in database (#349) 2023-05-24 16:52:22 -03:00
internal Feature/refactor parser to use sns sqs (#148) 2023-02-16 10:55:54 -03:00
parser [API/PARSER] Chain activity and last transaction endpoints (#175) 2023-03-07 16:25:42 -03:00
processor Add backfiller command to process vaa saved in database (#349) 2023-05-24 16:52:22 -03:00
queue Feature/refactor parser to use sns sqs (#148) 2023-02-16 10:55:54 -03:00
.env.example Feature/add parser pipeline (#46) 2023-01-18 12:42:14 -03:00
.gitignore [PARSER/PIPELINE] Update .gitignore (#174) 2023-03-06 14:35:53 -03:00
Dockerfile [API/PARSER] Chain activity and last transaction endpoints (#175) 2023-03-07 16:25:42 -03:00
Makefile [PARSER/PIPELINE] Update .gitignore (#174) 2023-03-06 14:35:53 -03:00
README.md Add backfiller command to process vaa saved in database (#349) 2023-05-24 16:52:22 -03:00
go.mod Add backfiller command to process vaa saved in database (#349) 2023-05-24 16:52:22 -03:00
go.sum Add backfiller command to process vaa saved in database (#349) 2023-05-24 16:52:22 -03:00

README.md

Parser

This component is in charge of parsing the VAA payload and persists it.

VAA parsing is delegated to external service so that users can add custom parsers in the external service without affecting this service.

Usage

Service

parser service

Backfiller

parser backfiller [flags]

Command-line arguments

  • --end-time string maximum VAA timestamp to process (default now)
  • --log-level string log level (default "INFO")
  • --mongo-database string mongo database
  • --mongo-uri string mongo connection
  • --page-size int VAA payload parser timeout (default 100)
  • --start-time string minimum VAA timestamp to process (default "1970-01-01T00:00:00Z")
  • --vaa-payload-parser-timeout int maximum waiting time in call to VAA payload service in second (default 10)
  • --vaa-payload-parser-url string VAA payload parser service URL

Running parser as service with localstack

Here are some aws commands to configure localstack with the necessary resources

Config sns topic

aws --profile localstack --endpoint-url=http://localhost:4566 sns create-topic --name vaas-pipeline.fifo  --attributes FifoTopic=true,ContentBasedDeduplication=false

Config SQS FIFO with dead letter queue localstack

aws --profile localstack --endpoint-url=http://localhost:4566 sqs create-queue --queue-name=wormhole-vaa-parser-dlq-queue.fifo --attributes "FifoQueue=true"
aws --profile localstack --endpoint-url=http://localhost:4566 sqs create-queue --queue-name=wormhole-vaa-parser-queue.fifo --attributes FifoQueue=true,MessageRetentionPeriod=3600,ReceiveMessageWaitTimeSeconds=5,VisibilityTimeout=20,RedrivePolicy="\"{\\\"deadLetterTargetArn\\\":\\\"arn:aws:sqs:us-east-1:000000000000:wormhole-vaa-parser-dlq-queue.fifo\\\",\\\"maxReceiveCount\\\":\\\"2\\\"}\""

Subscribe SQS FIFO to vaas-pipeline.fifo topic

aws --profile localstack --endpoint-url=http://localhost:4566 sns subscribe --topic-arn arn:aws:sns:us-east-1:000000000000:vaas-pipeline.fifo --protocol sqs --notification-endpoint http://localhost:4566/000000000000/wormhole-vaa-parser-queue.fifo

Check message in the dead letter queue localstack

aws --profile localstack --endpoint-url=http://localhost:4566 sqs receive-message --queue-url=http://localhost:4566/000000000000/wormhole-vaa-parser-dlq-queue.fifo