On registry https://registry.npmjs.org, the "latest" version (v2.4.3) of dependency bugsnag has the following deprecation notice:

All projects should upgrade to our universal JS notifier: "@bugsnag/js". See https://github.com/bugsnag/bugsnag-js/blob/master/UPGRADING.md for more details.

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about bugsnag's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

0x7F2209AdC8D504AB5ea37153D6cb526887F24229

Please kindly advice why this token is unable to view?

It is available at https://ethplorer.io/address/0x7f2209adc8d504ab5ea37153d6cb526887f24229?from=search

The number of pending fills (https://api.0xtracker.com/fills?status=pending) has slowly been increasing since 24th November. Investigate why, and fix the issue.

Description

Changes will be made to the event extractor to ensure v2.1 events are tagged as 2.1 rather than 2. The worker will need to be updated first to ensure it can continue processing 2.1 events. The only difference in processing will be that fills are tagged with a protocolVersion of 2.1 rather than 2.

Description

Update the create fills job to handle new fields introduced by the v3 exchange contract. Fills should be created with a protocolFee field. The maker and taker fee asset data should be parsed and the resulting assets stored in a fees field.

Description

The v3 exchange contract will allow for multiple maker/taker fees to be charged in any type of token. A new fees property will be used on fills to support this, and it will closely follow the assets shape. The existing convert fees job will need to be updated to support this fees field.

The job should pull prices for all fees which are denominated in a base token (see src/constants.js). It should convert the token amount to USD and store that against the fill.

Notes

It may actually make sense to introduce a new job rather than updating the existing job to handle two different data structures.

The index fill (src/consumers/index-fill.js) and bulk index fills (src/consumers/bulk-index-fills.js) consumers should be updated to store fill value in Elasticsearch.

Once fills have been measured (src/jobs/measure-fills), they should be scheduled for re-indexing to ensure the fill value is kept in sync with Elasticsearch.

Dependencies

#368

https://medium.com/lakeproject

On registry https://registry.npmjs.org, the "latest" version (v2.4.3) of dependency bugsnag has the following deprecation notice:

All projects should upgrade to our universal JS notifier: "@bugsnag/js". See https://github.com/bugsnag/bugsnag-js/blob/master/UPGRADING.md for more details.

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Please take the actions necessary to rename or substitute this deprecated package and commit to your base branch. If you wish to ignore this deprecation warning and continue using bugsnag as-is, please add it to your ignoreDeps array in Renovate config before closing this issue, otherwise another issue will be recreated the next time Renovate runs.

Affected package file(s): package.json

Description

Adding full support for v3 fees will likely take a substantial amount of effort. As an interim measure the convert fees job should be updated to ignore v3 fills. This will help to ensure a quick transition to v3 support and will provide some legroom in building out full support.

Description

Trust wallet has migrated their assets to a new repository (https://github.com/trustwallet/assets). The old repository still exists which means 0x Tracker hasn't been negatively impacted but it does mean that we don't receive any new token images.

The job for fetching token images should be updated to use this new repository instead of the old one.

Hi,

I recently seen several swap transaction that are not showing on 0xTracker for MetricExchange app. But I believe it is happening for all other apps as well

here are some I identified:

• https://etherscan.io/tx/0xfa2497ca6bc68c5c8d7813c5e3464372a0cd5c3ba7cd56b7bc85e55434994b28
• https://etherscan.io/tx/0x6ba75641d2933d596385821c6e3783973563d654d797b1bb2c5f74ad2b988f27
• https://etherscan.io/tx/0xb239ba895f4a229daf66e2ff0cbb843cad1edf9783fe6f636e8dc8fb4c4a1d0f

After some more debugging it seems the fills are not created due to missing Bridge events. In fact when the worker processes tries to create the TransformedERC20 fill it abort with following message:

TransformedERC20 event has no associated ERC20BridgeTransfer or BridgeFill events

Another thing I noticed is that the TransformedERC20 event is categorised of version 3 whereas the swap are all done using v4. So It might be an issue with event-extractor as well.

Also the issue seems to have started only less than 24h ago, before I never saw missing fills

Many thanks

Token names, symbols and decimals are currently fetched from Ethplorer. This integration is potentially redundant because many tokens embed metadata within their contracts.

A few tasks to be completed:

1. Perform an analysis of traded tokens and see what percentage of their contracts contain metadata
2. Update the existing task to fetch token details from contracts
3. Depending on the results of point 1, remove integration with Ethplorer

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>0xTracker/renovate-config-0x-tracker)

Description

V3 of the exchange contract will introduce a new protocolFeePaid field which denominates the amount of ETH paid as a protocol fee. In order to localize the fee amount on 0x Tracker it's necessary to introduce a job which fetches the ETH price on the fill date.

The job should work on fills which have not yet had their protocol fee converted. The job should fetch the ETH price, calculate the USD value of the fee, and then store both values against the fill. The existing conversions and rates fields can be used for this purpose.

There is an increasing volume with 0xBitcoin base pair. 0xchange.org is a "reference implementation" (or poster-child implementation...) of the Launch Kit and that volume will be missed in statistics because 0x Tracker dismisses the $USD value of these pairs.

Website: https://0xbitcoin.org/
Contract: 0xb6ed7644c69416d67b522e20bc294a9a9b405b31
0x Tracker: https://0xtracker.com/tokens/0xb6ed7644c69416d67b522e20bc294a9a9b405b31

Description

The event extractor is currently blocked from supporting V3 because any V3 events created by the extractor will be processed by the worker. To resolve this, ensure that the worker ignores events which don't have one of the following protocol versions:

• 1
• 2
• 2.1