Skip to content

Releases: near/read-rpc

v0.3.2

19 Nov 13:52
3d97f4f
Compare
Choose a tag to compare

What's Changed

  • Corrected state size calculation logic.
  • Integrated cargo_pkg_version metric to reflect the current server version.
  • Delete unnecessary debug logs about update blocks by finalities
  • Support new method EXPERIMENTAL_congestion_level

Supported Nearcore Version

  • nearcore v2.3.1
  • rust v1.81.0

v0.3.1

31 Oct 14:16
08b0bc9
Compare
Choose a tag to compare

Supported Nearcore Version

  • nearcore v2.3.0
  • rust v1.81.0

What's Changed

  • Improved bulk insertion of state_changes, reducing database requests from hundreds to a maximum of 7 per block.
  • Configuration improvement. Create default config.toml on start application to loaded parameters from the environment variables.
  • Fix to fetch state by pages (view_state_paginated).
  • Change logic to get shard_layout for indexers. Main idea to avoid request protocol_config via RPC, protocol_config could be changed with new nearcore release and we should support old and new versions of protocol_config.

0.3.0

09 Oct 11:12
c24e6a9
Compare
Choose a tag to compare

BREAKING CHANGES

Please, see the PostgreSQL & ShardLayout Pull Request for details. This is a completely new version of the ReadRPC with a new data storage layout and a new data storage engine. The main changes are:

  • Migrate from ScyllaDB to PostgreSQL for storing the data. We adopted the ShardLayout from the nearcore and split the data to separate PostgreSQL databases for each shard.
  • Changed the way we store TransactionDetails (JSON blobs again, but it might change soon)

All the work in this release allowed us to increase the performance of the ReadRPC and make it more reliable. We are still working on the performance improvements and will continue to work on the ReadRPC to make it even better.

Supported Nearcore Version (not changed)

  • nearcore v2.2.1
  • rust v1.79.0

v0.2.16

17 Sep 09:38
249f80c
Compare
Choose a tag to compare

Supported Nearcore Version

  • nearcore v2.2.1
  • rust v1.79.0

v0.2.15

16 Sep 11:24
9b2cd52
Compare
Choose a tag to compare

Supported Nearcore Version

  • nearcore v2.2.0
  • rust v1.79.0

v0.2.14

26 Aug 13:46
50a59eb
Compare
Choose a tag to compare

Supported Nearcore Version

  • nearcore v2.1.1
  • rust v1.79.0

What's Changed

  • Fix docker build

v0.2.12.1

07 Aug 15:22
466e758
Compare
Choose a tag to compare

What's Changed

  • Default value used when deserializing SignedTransactionView which are missing either the priority_fee field.
  • Default value used when deserializing ReceiptView which are missing either the priority field.

v0.2.13

26 Aug 12:49
f6ee61d
Compare
Choose a tag to compare

Supported Nearcore Version

  • nearcore v2.1.1
  • rust v1.79.0

What's Changed

  • Update nearcore to v2.1.1
  • Update rust version to v1.79.0

v0.2.12

07 Aug 10:11
Compare
Choose a tag to compare

Supported Nearcore Version

  • nearcore v2.0.0
  • rust v1.780

What's Changed

  • Update nearcore to v2.0.0
  • Update rust version to v1.78.0
  • Fixed transaction borsh deserialization error

v0.2.11

03 Jul 11:28
Compare
Choose a tag to compare

Supported Nearcore Version

  • nearcore v1.40.0
  • rust v1.77.0

What's Changed

  • Change main data source for transaction_details from database to the object storage (GCS Bucket)
    • Add tx-details-storage library to handle the GCS communication
    • Update rpc-server to read from the GCS Bucket when transaction is requested
    • Keep the database as a backup data source for the migration period
    • Add metric legacy_database_tx_details to track the number of requests to the database to monitor the transition progress (expected to decrease over time to zero)
    • Extend the number of save attempts to ensure the transaction is saved to the GCS Bucket and is deserializable correctly
  • Refactor tx-indexer to store the transaction details in the GCS Bucket
    • Still storing ExecutionOutcome and Receipt in the database