		@@ -26,5 +26,5 @@ "use strict";
		const blockExplorer = {
		addressUrl: address => `https://blockchair.com/litecoin/address/${address}`,
		txUrl: txId => `https://blockchair.com/litecoin/transaction/${txId}`
		addressUrl: address => `https://live.blockcypher.com/ltc/address/${address}`,
		txUrl: txId => `https://live.blockcypher.com/ltc/tx/${txId}`
		};
		exports.blockExplorer = blockExplorer;

package.json

		{
		"name": "@exodus/assets-base",
		"version": "8.0.104",
		"version": "8.0.105",
		"description": "Base level package for supporting Exodus assets.",
		@@ -15,5 +15,5 @@ "main": "lib/index.js",
		"@exodus/elrond-meta": "^0.0.6",
		"@exodus/neo3-meta": "~0.1.3",
		"@exodus/neo3-meta": "^0.2.0",
		"@exodus/terra-meta": "^1.0.0"
		}
		}

README.md

		@@ -25,4 +25,16 @@ # Exodus Assets Base

		## Assets Attributes Documentation
		## "Base" asset vs "Tokens"
		From a technical point of view, a "token" is an asset:
		- such that `asset.name !== asset.baseAsset.name`: it is a "non-primary" asset of the chain
		- that has a specific `assetType` property: `ETHEREUM_ERC20`, `BINANCE_TOKEN`, `SOLANA_TOKEN`, `OTHER` (ontologygas).

		In some cases a token can be a "gas" token(`feeAsset`): the asset used to pay for fees on the given network (e.g ontologygas, vethor, neo3gas).

		At UX level:
		- tokens that are not "gas" tokens are displayed using a chain badge (ERC20s, BEP20, tron tokens, solana tokens)
		- tokens that are "gas" tokens (gas for neo chain, ontologygas for ontology chain, vethor for vechain...) don't use a chain badge.

		Note that the lower level implementation of tokens (`accountState`, nomenclature of variables, imports...) isn't standardized yet but it is planned to unify it in the future.
		## Tokens Attributes Documentation

		The `assets-base/src/<asset>.js` files are where we define our supported assets. These files consists of a list of objects that more/less follow this object definition:
		@@ -77,1 +89,2 @@
		> To solve this, we added a hack which introduced the `old` property. The `old` property was meant to imply that there is an identifical `ticker` for a newer asset. So for the exchange, we skip over the old assets and activate the ones without the `old` property.

@exodus/assets-base - npm Package Compare versions

Fixed alerts