pub struct CCAssetMetadata {Show 36 fields
pub id: i32,
pub type_: String,
pub id_legacy: Option<i32>,
pub id_parent_asset: Option<i32>,
pub id_asset_issuer: Option<i32>,
pub symbol: String,
pub uri: String,
pub asset_type: String,
pub asset_issuer_name: Option<String>,
pub parent_asset_symbol: Option<String>,
pub created_on: i64,
pub updated_on: i64,
pub public_notice: Option<String>,
pub name: String,
pub logo_url: String,
pub launch_date: i64,
pub previous_asset_symbols: Option<Vec<CCPreviousAssetSymbol>>,
pub asset_alternative_ids: Option<Vec<CCAssetAlternativeId>>,
pub asset_description_snippet: Option<String>,
pub asset_decimal_points: Option<i32>,
pub supply_max: f64,
pub supply_issued: Option<f64>,
pub supply_total: Option<f64>,
pub supply_circulating: Option<f64>,
pub supply_future: f64,
pub supply_locked: Option<f64>,
pub supply_burnt: Option<f64>,
pub supply_staked: Option<f64>,
pub last_block_mint: Option<f64>,
pub last_block_burn: Option<f64>,
pub burn_addresses: Option<Vec<CCSpecialAddress>>,
pub locked_addresses: Option<Vec<CCSpecialAddress>>,
pub asset_industries: Option<Vec<CCAssetIndustry>>,
pub consensus_mechanisms: Option<Vec<CCConsensusMechanism>>,
pub consensus_algorithm_types: Option<Vec<CCConsensusAlgorithmType>>,
pub hashing_algorithm_types: Option<Vec<CCHashingAlgorithmType>>,
}Expand description
Asset: Full Asset Metadata
Fields§
§id: i32The unique identifier for the asset entry.
type_: StringType of the message.
id_legacy: Option<i32>The legacy previous asset management system ID.
id_parent_asset: Option<i32>This refers to the base, parent, or main asset to which a token is linked or pegged, signifying that the token acts as a representation of the parent asset. When a token loses its connection to a parent asset due to events such as hacks or the issuing entity’s decision to not honor the peg—similar to how TerraUSD detached from its USD peg—the PARENT_ASSET_SYMBOL is removed because the token no longer serves as a true representation of the parent asset. In order to remove the parent we need clear communication from the company who is in charge of keeping the peg. We add add a plublic notice and the include the communication in the Other Document URLs.
id_asset_issuer: Option<i32>This field identifies the original creator of the token. It provides essential information about the entity, individual or contract rules responsible for issuing the token initially and/or maintaining the supply. In the case of of bridged assets, this is the bridge operator and the parent will have its own issuer. You can go up the parent chain and figure out what counterparty risk you are exposed to when trading a specific asset. This clarification ensures that users can directly trace the origin of the token, understanding its issuance history and the primary issuer’s credentials.
symbol: StringInternal mapped symbol for a specific asset.
uri: StringThe uri path that this asset will be found on / url-slug.
asset_type: StringThe asset class/type.
asset_issuer_name: Option<String>This field identifies the original creator of the asset. It provides essential information about the entity individual or contract rules responsible for issuing the asset initially and/or maintaining the supply. In the case of of bridged assets, this is the bridge operator and the parent will have its own issuer. You can go up the parent chain and figure out what counterparty risk you are exposed to when trading a specific asset. This clarification ensures that users can directly trace the origin of the asset, understanding its issuance history and the primary issuer’s credentials.
parent_asset_symbol: Option<String>This refers to the base, parent, or main asset to which a token is linked or pegged, signifying that the token acts as a representation of the parent asset. When a token loses its connection to a parent asset due to events such as hacks or the issuing entity’s decision to not honor the peg—similar to how TerraUSD detached from its USD peg—the PARENT_ASSET_SYMBOL is removed because the token no longer serves as a true representation of the parent asset. In order to remove the parent we need clear communication from the company who is in charge of keeping the peg. We add add a plublic notice and the include the communication in the Other Document URLs.
created_on: i64Asset internal creation unix ts in our system.
updated_on: i64Asset internal last updated unix ts in our system.
public_notice: Option<String>A public notice for this asset.
name: StringThe full name of the asset, e.g. Bitcoin.
logo_url: StringThe image that appears when you see this asset.
launch_date: i64The launch date of the asset is indicated as (yyyy-mm-dd). However, if the asset was initially established as a token before being integrated into a blockchain, the launch date is reset to the creation of the first block when the blockchain is launched for the token.
previous_asset_symbols: Option<Vec<CCPreviousAssetSymbol>>A list of symbols that were previously associated with this asset.
asset_alternative_ids: Option<Vec<CCAssetAlternativeId>>Alternative data platforms that also support this asset with their specific asset id.
asset_description_snippet: Option<String>The shortest form description text only for this asset. This is a lot more limited than the summary. Generally this is a one or maximum two sentences.
asset_decimal_points: Option<i32>The total decimal places this asset can be divided into. E.g. 8 for BTC (1 Satoshi), 18 for ETH (1 Wei). Generally blockchains store all units as integers and this is the number you need to divide the lowest unit of accounting by to get the common unit of measure used for the asset.
supply_max: f64The maximum number of asset parts (coins/tokens) that will ever be issued (supply_circulating + supply_burnt + supply_locked + all supply that has not been issued yet but is planned to be issued in the future). For assets (coins/tokens) that have infinite supply, we use -1.
supply_issued: Option<f64>The number of asset parts (coins/tokens) that have been issued so far. (supply_circulating + supply_locked + supply_burnt).
supply_total: Option<f64>The number of asset parts (coins/tokens) that have been issued so far excluding burnt tokens. (supply_circulating + supply_locked).
supply_circulating: Option<f64>Also referred to as free float or public float. The number of asset parts (coins/tokens) that are available to be traded and it excludes burnt supply and locked supply.
supply_future: f64The number of asset parts (coins/tokens) that are planned to be issued in the future. (supply_max - supply_issued).
supply_locked: Option<f64>The number of asset parts (coins/tokens) that are currently not transferable until certain conditions are met. Locked supply is generally held by team members, DAOs, foundations, bridges, stakers, liquidity pools, etc.
supply_burnt: Option<f64>The number of asset parts (coins/tokens) that have been sent to addresses/locations that are no longer accessible. They are permanently removed from the circulating supply on purpose, this does not include lost tokens sent to wallets that do not exist or sent to wallets that users no longer have access to, the address of burnt tokens is determined by the project team.
supply_staked: Option<f64>The current number of asset parts (coins/tokens) that are locked as part of PoS and PoS partial chains.
last_block_mint: Option<f64>New asset parts (coins/tokens) created in the most recently issued block.
last_block_burn: Option<f64>The total amount of asset parts (coins/tokens) that were taken out of circulation in the most recently issued block.
burn_addresses: Option<Vec<CCSpecialAddress>>The list of addresses that are considered burn addresses for this asset.
locked_addresses: Option<Vec<CCSpecialAddress>>The list of addresses that are considered locked addresses for this asset.
asset_industries: Option<Vec<CCAssetIndustry>>The asset industries that asset operates in.
consensus_mechanisms: Option<Vec<CCConsensusMechanism>>The types of consensus mechanisms this network / blockchain / token uses. This is a list of the fault-tolerant mechanism families that are used to achieve the necessary agreement on a single data value or a single state of the network among distributed processes or multi-agent systems.
consensus_algorithm_types: Option<Vec<CCConsensusAlgorithmType>>The types of consensus algorithms this blockchain uses. This is dependent on the consensus mechanisms used by the network / blockchain / token. For blockchains that are proof of work this would in most cases have the mining algorithm. For hybrid assets, this would be a list of mining and proof of stake and other algorithm used for reaching consensus.
hashing_algorithm_types: Option<Vec<CCHashingAlgorithmType>>The types of algorithms this blockchain uses for hashing blocks, transactions etc.