### Description
This pull request implements an improvement in the processing logic of the `tx-tracker` service to avoid processing a message more than once.
### Summary
The `api` component was importing and initializing the notional cache, but not using it.
This pull request removes the unnecessary dependency.
### Description
Tracking issue: https://github.com/wormhole-foundation/wormhole-explorer/issues/499
This pull request adds support in the `tx-tracker` service for the blockchains Terra, Injective, Acala and Karura.
Also, deployment settings were updated with reasonable defaults.
* redis prefix support for caches
* fly support for prefix
* unit tests
* redis prefix for notional cache updater
* fix test
* fix tests
* use redis-prfix from config map
### Description
This pull request adds support for Oasis and Algorand in the `tx-tracker` service.
With this change, the sender addresses for those chains will become available in the UI.
### Description
Tracking issue: https://github.com/wormhole-foundation/wormhole-explorer/issues/418
This pull request modifies the `tx-tracker` service to support `ChainIDTerra2` and `ChainIDXpla`. In particular, this will make sender addresses from these blockchains available for the Wormhole Scan UI.
Support for `ChainIDTerra` was left out due to lack of working public RPC nodes (`https://lcd.terra.dev` doesn't seem to be functioning correctly at the moment).
### Description
This pull request modifies the `tx-tracker` service to support the Moonbeam and Klaytn blockchains.
In particular, this will make sender addresses for these particular blockchains available for the Wormhole Scan UI.
### Description
This pull request adds support for Aptos in the `tx-tracker` service.
This will lead to improvements for the wormhole Scan UI:
1. The transaction hash that was being previously displayed for Aptos VAAs was incorrect. This pull request fixes the issue.
2. The sender addresses for Aptos VAAs will now become available for for the UI.
### Description
This pull request modifies the `tx-tracker` service to support the Sui blockchain.
In particular, this will make the Sui sender addresses available for the Wormhole Scan UI.
### Summary
Tracking issue: https://github.com/wormhole-foundation/wormhole-explorer/issues/404
The WormholeScan UI needs to display the sender address for each token bridge VAA. This pull request modifies the `tx-tracker` service to obtain that information for Solana and eight EVM chains.
The transaction sender will become accessible through the following endpoints:
* `GET /api/v1/global-tx/{chain}/{emitter}/{seq}`: field `originTx.from`.
* `GET /api/v1/transactions`: field `originAddress`.
In both cases, the field is nullable (i.e.: sometimes it may not be available due to eventual consistency or internal errors)
### Description
Tracking issue: https://github.com/wormhole-foundation/wormhole-explorer/issues/377
This pull request modifies the analytics service so that it persists price information for a VAA in MongoDB. Data is stored only for token bridge VAAs, and only if the price is cached for the symbol being used.
A new collection `transferPrices` has been created, with the following document model:
```
{
"_id": "22/0000000000000000000000000000000000000000000000000000000000000001/18087",
"price": "0.999684",
"symbol": "USDC",
"timestamp": 2023-06-06T14:04:47.000+00:00
"tokenAmount": "0.1",
"usdAmount": "0.0999684"
}
```
### Summary
Tracking issue: https://github.com/wormhole-foundation/wormhole-explorer/issues/320
This pull request adds the `24h_messages` field to the response in `GET /api/v1/scorecards`. This field indicates the total number of VAAs emitted in the last 24 hours, including messages from PythNet.
Also, the analytics component has been updated to generate a new metric for this purpose. There is a task that summarizes data every 5 minutes to speed up query times. The data is retained for 24 hours only. For this particular metric, writes to InfluxDB are being batched to improve performance.
### Summary
Tracking issue: https://github.com/wormhole-foundation/wormhole-explorer/issues/254
For all chains except Solana, the data in `globalTransactions.sourceTx` was somewhat duplicated, since we already had that data in the `vaas` collection.
This pull request changes the `tx-tracker` service so that no redundant data will be written, and also changes the API to look up the data from the `vaas` collection instead.
The responses from the endpoint `/api/v1/global-tx` will no longer contain the field `originTx.from`.
ftocal
agodnic
walker-16
gipsh