You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the VAA we need to generate a metric on influxdb and populate the data.
The analytics componen will be in charge of this new metric called vaa.
The vaa metric contains the serialized information from the VAA and also metadata like token symbol and notional value
in the moment the vaa was created.
The vaa metric should include those tags:
origin_chain --> solana/eth/etc
detination_chain --> idem
token --> symbol like ETH/wETH/1SOL/etc
origin_address --> address of the ECR-20 on the origin_chain
destination_address --> destination wallet
The vaa metric should include those fields:
amount --> amount of the asset transfered
notional --> price of the asset when the vaa was created
v = amount * notional
This is an example of a generated metric on line protocol fomat:
### Summary
This pull request adds volume metrics to influxdb. Also, it adds the 24h volume metric to `GET /api/v1/scorecards`.
Tracking issues: #221, #280
### Changes:
* The `parser` service no longer generates metrics for influxdb. All metrics-related code was removed from that service, that code was moved to the analytics service instead.
* New volume metrics were added to the analytics service.
* The notional cache was modified to use token names (i.e.: ticker symbols) as keys instead of chain IDs.
* The notional cache reader was moved to the `common/client/cache` package.
* A little bit of duplicated code between the cache reader and writer was removed.
* A 24h volume metric was added to `GET /api/v1/scorecards`.
* A dictionary that stores token metadata was added under `common/domain/tokenbridge.go`. More tokens will be added to it in the near future.
Based on the VAA we need to generate a metric on influxdb and populate the data.
The analytics componen will be in charge of this new metric called
vaa
.The
vaa
metric contains the serialized information from the VAA and also metadata like token symbol and notional valuein the moment the vaa was created.
The vaa metric should include those tags:
The vaa metric should include those fields:
This is an example of a generated metric on
line protocol
fomat:For this metric to be generated we need:
chain + token_address
returns the symbol and decimals. Token resolver #281The workflow should be like this:
The text was updated successfully, but these errors were encountered: