v2.7.2

What's Changed

• Update README.md by @merrymari in #76
• validate config maxBlockRange > 50 by @artyukh in #77

Full Changelog: v2.7.1...v2.7.2

v2.7.1

What's Changed

• Release 2 7 1 by @mncdg in #75
  Up node:20.16.0 in Docker

Full Changelog: v2.7.0...v2.7.1

v2.7.0

What's Changed

• feature: skip chains in not presented in config by @mncdg in #73
• feature: submission id validation by @mncdg in #70

Full Changelog: v2.6.2...v2.7.0

v2.6.2

What's Changed

• Update README.md with working with multi-rpc nodes config by @mncdg in #69
• feature: validate chainid with a contract by @mncdg in #71

Full Changelog: v2.6.1...v2.6.2

v2.6.1 Up solana events reader

Full Changelog: v2.6.0...v2.6.1

How to update to v2.6.1

Pull latest changes

git checkout master
git pull origin master

Update env

Add new variables

# provide sentry dsn for Solana events reader *optional
DEBRIDGE_EVENTS_SENTRY_DSN=

v2.6.0 Added Rust Solana events reader

What's Changed

• New solana reader by @mncdg in #56

Full Changelog: v2.5.7...v2.6.0

How to update to v2.6.0

Pull latest changes

git checkout master
git pull origin master

Update env

Add new variables

POSTGRES_SOLANA_READER_DATABASE=solana${PG_RANDOM_ID}
DEBRIDGE_PROGRAM_PUBKEY=DEbrdGj3HsRsAzx6uH4MKyREKxVAfBydijLUF3ygsFfh
DEBRIDGE_SETTINGS_PROGRAM_PUBKEY=DeSetTwWhjZq6Pz9Kfdo1KoS5NqtsM6G8ERbX4SSCSft

RUST_LOG=info,tokio_util=warn,hyper=warn

# TODO: update with your RPC HTTP
DEBRIDGE_EVENTS_SOLANA_CLUSTER=
# TODO: update with your RPC WSS
DEBRIDGE_EVENTS_SOLANA_WEBSOCKET_CLUSTER=

DEBRIDGE_EVENTS_RESYNC_SIGNATURES_CHUNK_SIZE=5
DEBRIDGE_EVENTS_CONSISTENCY_CHECK_TIMEOUT_SECS=10
DEBRIDGE_EVENTS_DB_REQUERY_TIMEOUT_IN_SEC=5
DEBRIDGE_EVENTS_HEARTBEAT_TIMEOUT_IN_SEC=30

SOLANA_GRPC_SERVICE_URL=solana-grpc-service${DOCKER_ID}:7777
DEBRIDGE_SOLANA_EVENTS_PSQL=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_SOLANA_READER_DATABASE}

Delete old variables

SOLANA_DATA_READER_PORT
SOLANA_RPC
DEBRIDGE_PK
SETTINGS_PK
SOLANA_DATA_READER_API_BASE_URL
SOLANA_DATA_READER_API_SENTRY_DSN
SOLANA_GET_HISTORICAL_BATCH_SIZE
SOLANA_GET_EVENTS_BATCH_SIZE
SOLANA_API_REQUEST_TIMEOUT
SOLANA_API_WAIT_BATCH_INTERVAL

Create new database "solana_0" for solana-events-reader

1. First, you need to get into the Docker container's shell. You can do that with the following command:
   bash

docker exec -it <container-id-or-name> bash

Replace with your container's ID or name.

2. Once you're inside the container, you can connect to the PostgreSQL server using the psql command-line interface:
   bash

psql -U <username> -d <database>

Replace with the PostgreSQL username (e.g., postgres), and with the name of an existing database (e.g., postgres).

3. Now that you're connected to the PostgreSQL server, you can execute your CREATE DATABASE command:
   sql

CREATE DATABASE solana_0;

4. You can exit psql with the command \q, and then exit the Docker container's shell with the command exit.

v2.5.7

What's Changed

• upload old assets to bundlr by @mncdg in #53
• fix: change in logger sending to sentry info as exception by @mncdg in #54

Full Changelog: v2.5.5...v2.5.7

v2.5.7-alpha

What's Changed

• upload old assets to bundlr by @mncdg in #53
• fix: change in logger sending to sentry info as exception by @mncdg in #54

Full Changelog: v2.5.5...v2.5.7-alpha

v2.5.5 Added new tags in the bundlr, up packages

What's Changed

• feature: upload chainid to bundlr for submission by @mncdg in #48
• Delete orbitdb by @mncdg in #47
• Add tests by @mncdg in #46
• up npm packages and make network internal by @mncdg in #51
• Add chainIdFrom, chainIdTo, nonce to bundlr by @mncdg in #52

Full Changelog: v2.5.3...v2.5.5

2.5.3 Upload signatures to bundlr

What's Changed

• feature: add bundlr by @mncdg in #45

Full Changelog: v2.4.9...v2.5.3