# Project Overview ## Mission Make the semantic of each blockchain entity universally accessible, and understandable, cultivating an ecosystem where information is transparent, reliable, and readily available for all. ## Motivation Blockchain label data is predominantly confined within walled gardens, primarily driven by commercial interests, as label sourcing, curation, and serving can be costly. This limitation hinders the democratization of blockchain data and slows down development efficiency. We aim to create an open system that enables systematic label sourcing, ensures data quality, rewards contributors, and maintains an open dataset accessible to the community. ## End Game The ultimate objective is establishing a robust, high-quality blockchain entity metadata infrastructure, serving as a fundamental public resource for the crypto community. This foundation will empower the crypto community to host and access the data, enabling seamless integration and allowing community members to confidently rely on this critical infrastructure for their projects and initiatives. ## Governance Entity The ideal goal of the governance model is to build a versatile and sustainable DAO to enable a collaborative approach to source and curate this data, leveraging the collective intelligence and resources of the global blockchain community.To bridge to the DAO version - Microscope protocol unique interest group governance (Microscope protocol SIGG). 1. It consists of **7** governance members from the core development team and representatives. 2. Key decisions are made through this group until the DAO is established. 3. SIGG is responsible for initiating and coordinating development and community efforts, and here are some of its responsibility. * Guiding vision: The president may help define and maintain the DAO's mission, values, and long-term goals, ensuring that community decisions align with the organization's objectives. * Facilitating communication: The president could liaise between the DAO members and external stakeholders, including partners, regulators, and the broader community. This may involve communicating the DAO's progress, challenges, and successes to maintain transparency. * Coordinating efforts: The president may help streamline efforts by organizing and coordinating working groups or committees focused on specific tasks or projects within the DAO. * Conflict resolution: As a neutral party, the president may assist in resolving disputes or disagreements among members, fostering a healthy and collaborative environment. * Encouraging participation: The president could motivate and inspire members to actively contribute to the DAO's initiatives and governance processes. * Continuous improvement: The president may work with members to assess the DAO's governance structure and processes, identifying areas for improvement and implementing changes as needed. 4. A president's role is defined as facilitating coordination within SIGG. ## Definition of Roles **SIGG members**: a group of key members who contribute to the vision and mission of Microscope protocol, to transit the group to be a sustainable DAO. **Core dev**: core developer contributes to the code base. **Members**: people and entities that contribute to the community in some form. ## Community Contacts ## Reference Original Doc: [OpenMeta Mission and Governance draft](https://docs.google.com/document/d/1mCttbfbZQA-ntj9JynqL83XWF-ElzXZq3ZtRgcjSdJs/edit#) # Operation Principles Here are some principles to keep in mind when contributing to open metadata ## **Collaboration** Collaboration is at the heart of metadata development, and therefore, contributions should be made with an **`open`**, **`respectful`**, and mutually beneficial mindset. This entails sharing ideas, knowledge, and constructive feedback in a respectful manner that promotes open dialogue and constructive debate. ## **Consistency** Conforming to established guidelines and best practices is essential for ensuring consistency in metadata. As such, contributors should strive to align their contributions with existing **`standards`** and **`conventions`**, to maintain coherence and facilitate interoperability with other systems and tools. ## **Quality** The open metadata community prioritizes contributions of the highest quality. To maintain consistency with existing standards and conventions, contributors should adhere to established guidelines and best practices. It is crucial that metadata is accurate and reliable in order to be valuable, therefore, contributors must ensure that their contributions are both **`correct`** and **`up-to-date`**. ## **Community** The open metadata community is built on the principle of openness. This means that contributions should be **`transparent`**, **`accessible`**, and **`available`** for reuse by others. The community also welcomes contributions from all individuals regardless of their background, experience, or skill level. Everyone has something valuable to contribute. ## **Privacy** Metadata privacy is a critical consideration in contributing to open metadata. To safeguard against the disclosure of personally identifiable information (PII) and individual notations, contributors should **`prioritize public entities`** and refrain from providing sensitive or private information in their contributions. # FAQ ## **On using data** ### **Q1:** What data that the project aims to offer? A: The primary objective of Microscope protocol is to foster collaboration in annotating crypto addresses with labels. These labels comprise four main elements: **`category`**(e.g., "CEX", "Hot wallet"), **`entity`**(e.g., "Uniswap", "Coinbase"), **`name`**(e.g., "Uniswap-1") and **`source`** (e.g., “ground-truth”, “ML”). As a demonstration, we believe that using this label data alongside additional data and analytics technology could enable the development of applications for on-chain security, reputation scoring, AML compliance, and more. For further details, please refer to the respective pages: [label data schema](/onboarding/data/schema),[ all categories](/onboarding/data/categories), [tracked entities](/onboarding/data/entity) and [possible sources](/onboarding/data/source). (Note: The structure, categories, and design documentation are subject to community-driven iteration and improvement over time.)​ ### **Q2:** What are the constraints when developing applications using annotated data? A: We, the founding contributors to this project, reached a consensus to adopt the Apache License ([https://www.apache.org/licenses/LICENSE-2.0](https://www.apache.org/licenses/LICENSE-2.0**)). We would like to share some thoughts around the decision as well. Our ultimate goal is to establish data as a fundamental building block, enabling applications that aim to enhance the overall quality of the Web3 and cryptocurrency sectors. Nevertheless, the precise policy will be formulated, taking into account an incentive mechanism that fosters a robust and continually evolving system. Regardless, the applications we aspire to support or empower may tackle issues in areas such as security, compliance, and reputation scoring, among others, but are by no means limited to these. ## **On contributing** ### **Q3:** Who can contribute? A**:** Contributions to this project are welcomed from both organizations and individuals, encompassing various roles. We are looking for contributions in creating accurate labeled data, developing software, designing taxonomy, evangelizing our efforts, and promoting applications, among other potential roles. Initially, we will focus on inviting a select group of industry organizations to establish a foundational batch of label data, essential infrastructure, and community policy drafts. In the long term, we envision a fully community-driven, permissionless project that welcomes diverse contributions from individuals and organizations, continuously enriching the label data. Our goal is to make it the de-facto source for the most comprehensive blockchain label datasets, enabling the development of related data applications. ### ​**Q4:** What are responsibilities and rewards, if you make contributions? A: In terms of responsibilities and rewards, we welcome and appreciate voluntary contributions. As our project aims to serve as a mission-critical building block for empowering impactful initiatives that enhance security, compliance, and trustworthiness in web3, we expect contributors to commit to the quality of their work. This includes the accuracy of data labels (or transparent communication of uncertainties) and the development of robust software, among other role-specific tasks. While we will not penalize well-intentioned contributors, we will reward contributions based on various factors such as impact, quality, and scarcity. We are working on details. **​** ## **On understanding data** ### **Q5:** What is a data schema, and what are the essential elements of a labeled data record? A**:** To facilitate data sharing and labeling collaboration, we have designed a [**`common`** **`schema`**](/onboarding/data/schema) and taxonomy system that all contributed labeled data records can fit into. This system enables a seamless two-way pipelines for label contribution and consumption. Each member organization can maintain their **`own schema`**, which can exchange information with data in the common schema. For the taxonomy system, we have identified key elements and their possible values, along with their definitions, in separate pages for [**`categories`**](/onboarding/data/categories) , [**`entities`**](/onboarding/data/entity), and [**`sources`**](/onboarding/data/source). These elements provide a consistent and standardized way of categorizing and labeling data, which can be used across multiple datasets and organizations in our project. # Data {% content-ref url="/pages/4ii5YpXJTAxmmKSnhaWV" %} [Schema](/onboarding/data/schema) {% endcontent-ref %} {% content-ref url="/pages/xY3LYUadBQNRKcFXTgTY" %} [Chain](/onboarding/data/chain) {% endcontent-ref %} {% content-ref url="/pages/GJqfnczGxlGixWu0jnFV" %} [Entity](/onboarding/data/entity) {% endcontent-ref %} {% content-ref url="/pages/jFDW7XyUkDFZoAfo9hnI" %} [Name](/onboarding/data/name) {% endcontent-ref %} {% content-ref url="/pages/TSUReTKQEkrFabVGLB6W" %} [Categories](/onboarding/data/categories) {% endcontent-ref %} {% content-ref url="/pages/taD6LdrXEODKI9sKzoTI" %} [Source](/onboarding/data/source) {% endcontent-ref %} {% content-ref url="/pages/Rhz7KFAAibuNXn89xsF2" %} [Submitted By and Submitted On](/onboarding/data/submitted-by-and-submitted-on) {% endcontent-ref %}
# Schema Our project's primary objective is to foster industry-wide data sharing by employing a common schema to define data structures. Simultaneously, each participating organization can maintain their own schema with variations from the common one, streamlining the process of transferring data to the Microscope protocol database. 1. [Meta Schema](https://github.com/openchainmeta/chainmetareader/blob/main/chainmeta_reader/schema/meta_schema.json): defines the common structure of blockchain label data in this project. We have designed the schema with primary objectives focused on enabling capabilities such as comprehensive blockchain label data sharing, version control for taxonomy iteration, contribution measurement, and potential tracking of data record consumption 2. Examples of per-organization schemas: * [Coinbase](https://github.com/openchainmeta/chainmetareader/blob/main/chainmeta_reader/schemas/coinbase_schema.json): * [Chaintool](https://github.com/openchainmeta/chainmetareader/blob/main/chainmeta_reader/schemas/chaintool_schema.json): {% code lineNumbers="true" %} ```javascript { "$schema": "", "title": "ChainMeta", "description": "An object designed to uniformly describe blockchain metadata from different providers", "type": "object", "required": [ "community", "provider", "version", "revision", "introduction", "chainmetadata" ], "properties": { "community": { "description": "The community name of this open source project", "type": "string", "enum": [ "openchainmeta" ] }, "provider": { "description": "Basic information of the data provider", "type": "object", "required": [ "provider_name", "provider_id", "provider_signature" ], "properties": { "provider_name": { "description": "Provider's name", "type": "string" }, "provider_id": { "description": "Provider's unique id", "type": "string", "pattern": "^ocm[0-9]{6}$" }, "provider_signature": { "description": "Provider's signature", "type": "string" } } }, "version": { "description": "The version of provider's metadata", "type": "string" }, "revision": { "description": "The revision of provider's metadata", "type": "integer" }, "introduction": { "description": "Introduction of provider's metadata", "type": "string", "format": "uri" }, "chainmetadata": { "description": "Details of provider's metadata", "type": "object", "required": [ "schema", "artifact" ], "properties": { "schema": { "description": "Schema of provider's metadata, explain how data is read", "type": "string", "format": "uri" }, "artifact": { "description": "Storage details of provider's metadata", "type": "array", "minItems": 1, "items": { "type": "object", "required": [ "path", "fileformat", "signature" ], "properties": { "artifact_type": { "description": "Type of artifact", "type": "string", "enum": [ "s3", "remote path", "local file" ] }, "path": { "description": "Path of the metadata file", "type": "string", "format": "uri" }, "fileformat": { "description": "Format of the metadata file", "type": "string", "enum": [ "json", "parquet", "csv" ] }, "signature": { "description": "Signature of the metadata file", "type": "string" } } } } } } } } ``` {% endcode %} # Chain > Github： ## Description This field provide information about which blockchain network that a given address belongs to, which include both L1 and L2 networks. # Entity {% hint style="info" %} *Please note that while the information presented on this page is intended for **human consumption** and is accurate to the best of our knowledge, the official **source of truth** for our project is the corresponding codified files hosted on GitHub. We strive to maintain up-to-date and accurate information on this page, but please refer to the GitHub repository for the most current and reliable information.* {% endhint %} > Github: ## Description The ‘Entity’ field, together with the ‘Name’ fields, contains the actual label information for a given address. It provides the information about whether a given address belongs to a specific entity - for example, the user may find an address with the address name ‘Binance deposit address’ and ‘Binance por address’ both under entity ‘Binance’.
# Name ## Description The ‘Name’ field, together with the ‘Entity’ fields, contain the actual label information for a given address. It provides address ownership information - for example, it tells users whether this is a Binance address or it is a Coinbase address. # Categories > Github: ## Description This field provides information about any common characteristics that that a particular group of labelled addresses are shared with each other. It can be for functionality characteristics such as whether a specific address is used by CEX or DeFi protocols or it can be behaviour characteristics such as whether a specific address is a risky address (e.g. participated in any illicit activities). Each single address can have more than one categories assigned. The list of values that are available for ’Categories’ are in the table below:
INDEXCATEGORYDESCRIPTIONEXAMPLE
1Cold StorageAn offline wallet used to securely store large amounts of cryptocurrency for extended periods of time.Ledger Nano X
2Hot walletAn online wallet that offers easy and quick access to cryptocurrency funds for everyday use.Coinbase Wallet
3DeprecatedA smart contract that is no longer in use and has been deprecated by the protocol or development team.EIP-20
4MultisigAn address that requires approval from multiple parties to access cryptocurrency funds, providing an additional layer of security. Commonly used by exchanges and institutional investors.Gnosis Safe Multisig
5VaultA smart contract-based system that automatically invests cryptocurrency funds to generate yield for users, commonly used in decentralized finance (DeFi) applications and managed by the protocol or community.Yearn Finance Vault
6Vault UserAn address that interacted with a smart contract-based system that automatically invests cryptocurrency funds to generate yield for users, commonly used in decentralized finance (DeFi) applications and managed by the protocol or community.Yearn Finance Vault User
7VulnerableAn address whose private keys have been compromised or are publicly available, exposing it to the risk of unauthorized access or theft.Mt. Gox hack victim
8Smart ContractAn address used by developers or teams to deploy smart contracts on a blockchain for decentralized applications or other projects.Uniswap
9NFTAn address controlled by an NFT marketplace that facilitates the buying, selling, or trading of non-fungible tokens.OpenSea
10DEXAn address or wallet used in decentralized exchanges to facilitate peer-to-peer trading of cryptocurrencies without a central authority.Uniswap
11DEX UserAn address that interacted with a smart contract for a decentralized exchange used to facilitate peer-to-peer trading of cryptocurrencies without a central authority.Uniswap User
12CEXA centralized exchange (CEX) that allows users to trade cryptocurrencies in exchange for fiat or other cryptocurrencies.Binance
13ExchangeAddresses used by centralized or decentralized exchanges to interact with smart contracts and blockchain networks.OKX
14ATMRelated to a cryptocurrency ATM that allows users to buy or sell cryptocurrencies using cash or debit/credit cards.Bitcoin Depot
15AuctionRelated to an auction that can be held by a variety of entities, including law enforcement agencies (LEA).US Marshals Service Bitcoin Auction
16GamblingRelated to a gambling website that allows users to place bets on various games using cryptocurrencies.Bitcasino.io
17GamingRelated to a gaming platform or game that allows users to buy, sell or trade digital assets or in-game items.Axie Infinity
18LE (Law Enforcement)An address or wallet certified to belong to a law enforcement agency (LE).FBI
19LendingRelated to lending or borrowing activities in the crypto space, such as those belonging to lending platforms or peer-to-peer lending services.

BlockFi,

Celsius Network, Aave, Compound, Nexo

20Lending UserAn address that interacted with a smart contract belonging to lending platforms or peer-to-peer lending services.BlockFi User
21MerchantAddresses or wallets that are associated with merchants who accept payment in cryptocurrencies.

Overstock.com, Starbucks,

Tesla,

Microsoft

22MixerAddresses or wallets that are associated with crypto mixers or tumblers, which are services that mix multiple transactions together in order to obfuscate the origin of the funds.Wasabi Wallet, Samurai Wallet, CoinJoin
23Payment ProcessorRelated to a business that facilitates transactions between buyers and sellers using cryptocurrency as payment.BitPay
24Business or Services, OtherRelated to a business or service that operates within the crypto ecosystem but does not fit into any of the other categories.Crypto tax service provider
25Token TeamAn address or wallet that is controlled by the team responsible for creating and maintaining a particular cryptocurrency token.Ethereum Foundation
26Ethereum FoundationAn address or wallet that is involved in the sale or exchange of weapons using cryptocurrency.DarkMarket
27Marketplace AggregatorRelated to a business or service that consolidates data from multiple decentralized exchanges or NFT markets in order to provide users with a comprehensive view of the market.1inch
28L2An address or wallet associated with a layer 2 scaling solution built on top of the Ethereum network.Polygon
29InsuranceRelated to A business or service that provides insurance coverage for cryptocurrency assets stored on the blockchain.Nexus Mutual
30Asset ManagementRelated to A business or service that manages cryptocurrency assets on behalf of clients.Grayscale Investments
31StreamingRelated to A business or service that provides streaming media content using cryptocurrency payments.Livepeer
32InfraRelated to A business or service that provides infrastructure services to support the operation of blockchain networks.Infura
33OracleRelated to A service that provides off-chain data to smart contracts. Oracles allow smart contracts to interact with external data sources, making them more versatile and useful.Chainlink
34DAORelated to A DAO is an organization that is run by rules encoded as computer programs called smart contracts.MakerDAO
35YieldRelated to a yield service allows users to earn interest on their cryptocurrency deposits.Aave
36Yield Aggregator UserAn address that interacted with a smart contract used for yield farming strategies where users can deposit cryptocurrencies to earn rewards and/or fees on a decentralized platform.Aave User
37WalletA wallet is a software or hardware device used to store cryptocurrency private keys and sign transactions.MetaMask
38FundA fund is an entity that pools capital from multiple investors and uses it to invest in a variety of assets, including cryptocurrencies.Grayscale Bitcoin Trust
39DerivativesA derivatives entity is an organization that specializes in trading cryptocurrency derivatives, such as futures, options, and swaps.Deribit
40E-CommerceAn e-commerce entity is an organization that uses cryptocurrency as a payment method for goods and services.Overstock.com
41IdentityAn identity entity is an organization that provides on-chain identity-related products, such as decentralized identifiers (DIDs) and verifiable credentials.uPort
42Mining PoolAn organization that brings together multiple miners to collectively mine cryptocurrency.

F2Pool,

Slush Pool, BTC.com

43Liquid StakingCompanies that allow users to stake their PoS tokens and receive liquid staking derivatives in exchange.

Staked,

Lido,

Ankr,

StakeWise

44PaymentsAssociated with companies providing on-chain payment processing services, allowing users to send and receive cryptocurrency payments on the blockchain.

BitPay,

Coinbase Commerce

45SidechainAssociated with sidechain solutions built on top of the Ethereum blockchain, allowing developers to deploy decentralized applications with increased throughput and scalability.

Polygon,

xDai

46RouterAssociated with router services that allow users to swap tokens across multiple liquidity pools.

1inch,

Uniswap

47Coin SwapperAssociated with services that allow users to swap one cryptocurrency for another without requiring users to deposit funds into the service wallet first.ShapeShift, Changelly
48SportAssociated with sport-related products or services, including fantasy sports, sports betting, and collectibles.NBA Top Shot, Sorare
49Privacy (not Mixer)Associated with products or services that provide privacy solutions on the blockchain.Tornado Cash, Incognito
50ValidatorAssociated with validators that help secure Proof-of-Stake (PoS) blockchain networks.

Staked,

Figment Networks

51CharityControlled by an organization that accepts crypto donations for charitable causesThe Giving Block
52DonationControlled by an organization that accepts crypto donations for any purposeRed Cross
53DeployerAddresses that has been used to deploy smart contractsOpenZeppelin Smart Contract SDK
54Company FundsAddresses managed by companies, projects or foundations, which are usually used for treasury management, paying salaries or other expensesConsenSys
55Eth 2 stakerAddresses that have staked Ether at the Ethereum 2.0 Beacon Chain to help secure the network and earn rewardsPrysmatic Labs
56Yield FarmingAddresses used for yield farming strategies where users can deposit cryptocurrencies to earn rewards and/or fees on a decentralized platformSushiSwap
57ICOAddresses used to receive funds during an initial coin offering (ICO) or other crowdfunding mechanismsEOS
58StablecoinAddresses used for stablecoin projects, including centralized and decentralized stablecoinsTether
59StakingAddresses used for staking, where users can lock up their cryptocurrency to help secure a network and earn rewardsTezos
60Token SaleAddresses used during a token sale where users can buy tokens at an initial price, including initial coin offerings (ICO) and initial dex offerings (IDO)Uniswap
61DefiAddresses used for decentralized finance (DeFi) projects, including decentralized exchanges, yield farming, lending, and more.Aave
62Defi UserAn address that interacted with a smart contract used for decentralized finance (DeFi) projects, including decentralized exchanges, yield farming, lending, and more.Aave User
63AdvertisingAddresses used for advertising-related activities in the crypto environment.Google Ads, Facebook Ads
64EnergyAddresses used by entities that are bringing energy-related products into the blockchain.WePower
65FIATAddresses controlled by businesses that allow customers to trade fiat currencies.Coinbase, Binance
66KYCUsed for exchanges or other service that require customers to provide a valid ID document to trade fiat-to-crypto or crypto-to-crypto.Coinbase, Gemini
67NO KYCUsed for exchanges or other service that do not require customers to provide a valid ID document to trade fiat-to-crypto or crypto-to-crypto.LocalBitcoins, Bisq
68DarknetAddresses belonging to services hosted on the dark web, or being involved in dark web transactions.Silk Road, AlphaBay
69Money LaunderingAddresses certified belonging to money laundering activities.Liberty Reserve
70MalwareAddresses belonging to malware campaigns.WannaCry ransomware, Emotet malware
71RansomAddresses that have been identified as being involved in ransomware attacks.WannaCry ransomware campaign
72ScamAddresses that have been identified as being involved in fraudulent activities or scams.PlusToken scam
73TerrorismAddresses that have been identified as being involved in financing terrorism.ISIS
74TheftAddresses that have been identified as being involved in theft or hacking of cryptocurrencies.Cryptopia hack
75SanctionedAddresses that have been sanctioned by some government in the world (excluding the US).Al-Qassam Brigades
76PhishingAddresses related to phishing scams.N/A
77PonziAddresses related to Ponzi schemes.N/A
78SpamAddresses related to spamming.N/A
79Fake KYCAddresses related to fake KYC procedures.BitMax.io
80Malicious Mining ActivitiesAddresses used for mining cryptocurrencies with malware or botnets.N/A
81Financial Crime, OtherAddresses related to financial crimes such as money laundering, fraud, and tax evasion.N/A
82CybercrimeAddresses related to cybercrimes such as hacking, data theft, and ransomware.N/A
83HoneypotAddresses related to fake tokens or ICOs that are designed to scam investors or traders.
84Black Mail ActivitiesAddresses that threaten to reveal sensitive information or personal data in exchange for ransom payments.
85Constrained by ServiceAddresses that have been restricted or blocked from using centralized or decentralized exchanges due to suspicious activities or high risk status.
86High Risk, OtherAddresses that are associated with suspicious, fraudulent, or illigal activities that are not covered by other categories.
87Dapp, OtherAddresses used by decentralized applications (dApps) to interact with smart contracts and blockchain networks.
88BridgingAddresses used by platforms or projects that provide interoperability solutions to connect different blockchain networks.ChainBridge
89Bridge UserAn address that interacted with a smart contract used by platforms or projects that provide interoperability solutions to connect different blockchain networks.ChainBridge User
90MultichainAddresses used by platforms or projects that enable communication and transfer of assets between multiple blockchain networks.Cosmos
91Factory ContractSmart contracts used to create and deploy multiple instances of other smart contracts.OpenZeppelin
92Fraud ProofSmart contracts used to prove fraudulent activities or invalid state transitions on layer 2 protocols.OptimismFraudProof
93GenesisGenesis addresses used to mint/burn.
94MEV BotAddresses used by MEV bots for transaction extraction and prioritization.Archer DAO
95ProxyContract that acts as a proxy to another contract and is used to upgrade the logic of the target contract without changing its address.OpenZeppelin Proxy
# Source {% hint style="info" %} Please note that while the information presented on this page is intended for **human consumption** and is accurate to the best of our knowledge, the official **source of truth** for our project is the corresponding codified files hosted on GitHub. We strive to maintain up-to-date and accurate information on this page, but please refer to the GitHub repository for the most current and reliable information. {% endhint %} > Github: ## Description The ‘Source’ field provides information about where are the address labels (i.e. the address name and address entity name) from. The list of values available for this fields are provided in the table below:
ValueDescriptionExample
Ground Truth

Generated from:

1) direct interactions (transactions) with the labelled entity, or

2) official sources like OFAC or On-chain protocol page (e.g. Uniswap documentations)

Initiated deposit and withdrawals transactions against Binance to identify Binance addresses on chain.
ExternalGenerated from external parties that are available to general public - e.g like Twitter, Discord, Etherscan, etcBinance PoR addresses from Binance’s official website
HeuristicsGenerated from rule based approaches that are used to clusterize addresses on chain based on their transaction patterns - e.g. common-spend, core addresses, change, etcCommon-spend clusterizers running on Airflow for UTXO based chain - e.g. Bitcoin, Dogecoin
Machine LearningGenerated from machine learning based modelsBased on ground-truth labels, we using GCN, XGB models to train and predict label for new addresses.

# Submitted By and Submitted On These two fields provides information about the timestamps of the metadata entries was last updated and the user identifier (e.g. user-id, DID, crypto addresses) of whom submitted the data. # Community ## **What is the process of altering the common taxonomy?** To enable effective data sharing and collaboration in the rapidly evolving web3 industry, it's crucial to update the taxonomy regularly and stay current with the latest concepts and technologies. We will summarize those steps to maintaining the common taxonomy by involving community as below: 1. **Proposal for changes**: A proposal is made to add or delete a term from the taxonomy. This may involve a discussion and review process to ensure that the proposed change is necessary and appropriate. 2. **Call for community discussion or voting**: Once a proposal has been made, it may be necessary to solicit feedback from the community or hold a vote to determine whether the proposed change should be implemented. This will depend on the governance structure and decision-making processes in place for the taxonomy. 3. **Updating the taxonomy**: If the proposed change is approved, the taxonomy is updated to reflect the addition or deletion of the term. This may involve revising the structure of the taxonomy or updating associated documentation and resources. 4. **Testing the workflow of updating taxonomy**: After the taxonomy has been updated, it is important to test the workflow of updating existing data to ensure that the change has been implemented correctly and does not introduce any errors or inconsistencies. 5. **Communication**: Finally, the change should be communicated to the relevant stakeholders, including users of the taxonomy and any downstream systems or users that may be impacted by the change. TODO: we will discuss the different treatment when dealing with adding a term or deleting an existing terms, particularly the ramification of those potential changes on existing data. ## **How to address label conflict?** To address the issue of a single crypto address having different labels from multiple contributors, we could consider implementing a consensus-based approach or a weighted voting system, which would help resolve conflicts without relying on experts for every address. Here are two possible solutions: 1. **Consensus-based approach**: In this method, you can require a certain threshold of agreement among contributors before accepting a label for an address. When multiple contributors provide labels for the same address, the system would compare the labels and select the one that reaches the consensus threshold. This threshold can be set based on the desired level of confidence and the size of the contributor community. By setting a reasonable consensus threshold, you can minimize the need for expert intervention while maintaining data quality. 2. **Weighted voting system**: In a weighted voting system, you can assign different weights to the votes of contributors based on their expertise, reputation, or past performance. This allows the opinions of more experienced or reliable contributors to have a greater impact on the final label. You can also implement a mechanism to update contributors' weights over time, based on the accuracy of their annotations or feedback from other contributors. By using a weighted voting system, you can efficiently resolve label conflicts while minimizing the need for expert verification. TODO: we should determine which approach we should go # Team ## Governance Team [Leo Liang](https://www.linkedin.com/in/leoliang/) [Ming Jiang](https://www.linkedin.com/in/ming2jiang1/) [Yi Zhang](https://www.linkedin.com/in/beingzy/) [Vincent Wen](https://www.linkedin.com/in/siwen/) [Eskil Tsu](https://www.linkedin.com/in/yufeng-xu-9856a716/) ## Contributors [Boyang Xu](https://www.linkedin.com/in/boyang-xu-19713090/) Chris Steege [David Lai](https://www.linkedin.com/in/david-lai/) [Eskil Tsu](https://www.linkedin.com/in/yufeng-xu-9856a716/) Jiacheng Xu Johnny Yang [Ken Yip](https://www.linkedin.com/in/ken-yip/) [Leo Liang](https://www.linkedin.com/in/leoliang/) [Micheal Kremer](https://www.linkedin.com/in/kremer-michael/) [Ming Jiang](https://www.linkedin.com/in/ming2jiang1/) [Ruiying Jiang](< https://www.linkedin.com/in/ryjiangx >) [Sid Shekhar](https://www.linkedin.com/in/sidshekhar/) [Tammy Yang](https://www.linkedin.com/in/tammy-yang-369b1957/) [Turan Vural](https://www.linkedin.com/in/turanzv/) [Vincent Wen](https://www.linkedin.com/in/siwen/) [Wei Cui](https://www.linkedin.com/in/wei-cui16/) [Yi Dong](https://www.linkedin.com/in/yi-dong-sky/) [Yi Zhang](https://www.linkedin.com/in/beingzy/) [Zhanwu Xiong](https://www.linkedin.com/in/zhanwu/)