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
Refactor explain-card and show-card templates to enhance clarity and detail. Update content structure for explain-cards, including comprehensive sections on introduction, core concepts, use cases, and related topics. Remove outdated cards (EIP-1559, ERC721, ERC1155, FDV, KYC, Op Stack, TPS, TVL, and others) to streamline the repository and improve overall organization.
Copy file name to clipboardExpand all lines: .cursor/rules/explain-card.mdc
+23-23Lines changed: 23 additions & 23 deletions
Original file line number
Diff line number
Diff line change
@@ -9,29 +9,29 @@ alwaysApply: false
9
9
10
10
When creating or updating an `explain-card`, ensure the following aspects are covered. The AI assistant should generate a logical content outline based on these key elements and the specific nature of the concept being explained.
11
11
12
-
**1. Introduction:**
13
-
- Clear and concise definition of the concept (at least 2 sentences, longer if complex).
14
-
- Analogy (optional, to clarify for beginners).
15
-
- Importance/Purpose: Why the concept exists and its significance in Web3.
- Key Components: Essential parts or elements, explained clearly and deeply.
20
-
- Mechanism/How it Works: The processor workflow involved (diagrams can be described in text).
21
-
- Technical Details: Relevant specifications, protocols, or algorithms, explained accessibly.
22
-
- Variations/Types(if applicable): Different implementations or types of the concept.
23
-
24
-
**3. Use Cases & Implications:**
25
-
- Specific Examples: Real-world Web3 project examples (link to `show-card`s if available).
26
-
- Benefits: Advantages or positive outcomes.
27
-
- Limitations/Challenges: Drawbacks, risks, or difficulties.
28
-
- Comparison (optional): To alternative concepts or Web 2.0 approaches.
29
-
30
-
**4. Related Concepts (Optional but Recommended):**
31
-
- Prerequisites: Concepts to understand first.
32
-
- Building Blocks: Component concepts.
33
-
- Related Ideas: Similar, contrasting, or co-discussed concepts.
34
-
- Further Reading: Advanced concepts building upon this one.
12
+
**1. Introduction & Definition:**
13
+
- Comprehensive Definition: Provide a clear, thorough, and nuanced definition of the concept. Go beyond a simple one-liner; explain its core meaning and context within Web3. This section should establish a solid foundational understanding.
14
+
- Analogy/ELI5 (Explain Like I'm 5): If the concept is complex, include a relatable analogy or a simplified explanation suitable for beginners to grasp the fundamental idea quickly. Ensure the analogy is accurate and helpful.
15
+
- Importance & Purpose: Clearly articulate *why* this concept is important in the Web3 space. What problems does it solve, what capabilities does it enable, or what paradigm does it represent? Detail its significance and the reasons for its existence.
16
+
- Target Audience & Relevance: Identify the primary audience(s) who would benefit from understanding this concept (e.g., developers, users, investors, researchers). Explain its relevance to each group.
17
+
18
+
**2. Core Principles & Detailed Mechanism:**
19
+
- Key Components/Elements: Break down the concept into its essential constituent parts or elements. For each component, provide a detailed explanation of its function, characteristics, and how it contributes to the overall concept.
20
+
- In-depth Mechanism/How it Works: Provide a step-by-step, thorough explanation of the process, workflow, or operational principles involved. If technical, explain the sequence of operations and interactions between components. Diagrams (described textually if necessary) should be used to clarify complex interactions or flows.
21
+
- Underlying Technical Details: Delve into relevant technical specifications, protocols, algorithms, data structures, or mathematical foundations. Explain these in an accessible yet comprehensive manner, providing enough detail for a technical reader to gain a solid understanding. Reference primary sources or whitepapers where appropriate.
22
+
- Variations, Types, or Implementations (if applicable): Discuss different existing or theoretical variations, classifications, or specific implementations of the concept. Highlight their differences, trade-offs, and specific use cases.
23
+
24
+
**3. Practical Applications, Use Cases & Implications:**
25
+
- Concrete Examples & Real-World Applications: Provide specific, detailed examples of how this concept is used in real-world Web3 projects or scenarios. Link to relevant `show-card`s if they exist. The examples should clearly illustrate the concept in action.
26
+
- Benefits & Advantages: Enumerate and elaborate on the advantages, positive outcomes, or improvements offered by this concept. Quantify benefits where possible or provide strong qualitative arguments.
27
+
- Limitations, Challenges & Criticisms: Discuss any known drawbacks, risks, difficulties, scalability issues, security concerns, or common criticisms associated with the concept. Provide a balanced perspective.
28
+
- Comparative Analysis (Optional but Encouraged): Compare and contrast the concept with alternative or similar concepts, or with traditional (e.g., Web 2.0) approaches. Highlight key differences in mechanism, efficiency, security, etc.
29
+
30
+
**4. Broader Context & Further Exploration (Optional but Recommended):**
31
+
- Foundational Concepts/Prerequisites: List and briefly explain any foundational concepts that are essential for a deeper understanding of this topic. Link to their respective `explain-card`s.
32
+
- Constituent Building Blocks: Identify if this concept is composed of other, more fundamental concepts. Explain how they combine and link to their `explain-card`s.
33
+
- Related & Adjacent Ideas: Discuss other concepts that are closely related, often discussed in conjunction, or represent contrasting approaches. Link to relevant `explain-card`s.
34
+
- Advanced Topics & Future Research: Suggest avenues for further learning, advanced topics building upon this concept, or open research questions and future development directions.
Copy file name to clipboardExpand all lines: .cursor/rules/show-card.mdc
+26-19Lines changed: 26 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -10,35 +10,42 @@ alwaysApply: false
10
10
When creating or updating a `show-card`, ensure the following aspects are covered. The AI assistant should generate a logical content outline based on these key elements and the specific nature of the project/tool/service being showcased.
11
11
12
12
**1. Overview:**
13
-
- Concise summary of the project/tool/service (1-2 sentences).
14
-
- Problem Solved: The issue it addresses in Web3.
15
-
- Value Proposition: Its unique benefit or advantage.
13
+
- Comprehensive summary of the project/tool/service, going beyond a brief introduction. Explain its purpose and significance in the Web3 space.
14
+
- Problem Solved: Clearly articulate the specific problem(s) it addresses within the Web3 ecosystem and detail *how* the project aims to solve them.
15
+
- Value Proposition: Elaborate on its unique benefits, advantages, and differentiators. If possible, provide context or comparison against existing solutions.
16
16
- Official Website: Link to the official site.
17
-
- Status (e.g., Live, Beta, In Development, key dates).
17
+
- Status & Roadmap: Current development status (e.g., Live, Beta, In Development). Include key historical dates/milestones and an overview of the public roadmap or future plans.
18
18
19
19
**2. Key Features:**
20
-
- Main functionalities or capabilities, with brief explanations of each and their benefits.
20
+
- Main functionalities or capabilities. For each feature, provide a **detailed explanation** of what it does, *how it works* from a user perspective, and its specific benefits and potential use cases. Ensure this section is comprehensive and informative, reflecting deep knowledge.
- Blockchain/Platform: Specify the underlying blockchain(s) or platform(s) it is built on or interacts with (e.g., [[Ethereum]], [[Solana]], Standalone).
24
+
- Architecture: Provide a detailed explanation of the high-level technical design, its core components, and their interactions. Diagrams are encouraged for clarity if complex. Explain the rationale behind architectural choices.
25
+
- Core Mechanism(s): Detail the key technical innovations, algorithms, or processes that underpin the project. Explain *how* these mechanisms work and their significance. Code snippets or pseudo-code can be included for illustration if it aids understanding.
26
+
- Smart Contracts (if applicable): List key smart contracts, link to them on a block explorer, and briefly explain their primary functions. Mention audit status and link to audit reports if available.
- Tokenomics (if applicable): Native token's utility, supply, distribution (link to `[[Token Name]]` card).
29
+
- Target Audience: Describe the primary users or beneficiaries (e.g., Developers, DeFi Traders, NFT Collectors) and explain *why* and *how* the project caters to them.
30
+
- How it's Used (Detailed Use Cases): Provide specific, illustrative examples of how users interact with the project. These should be step-by-step or scenario-based where appropriate to offer a clear understanding.
31
+
- Integrations: List notable projects, platforms, or protocols it integrates with. Explain the nature and benefits of these integrations for users and the ecosystem.
32
+
- Tokenomics (if applicable): If there's a native token, provide a detailed explanation of its utility within the ecosystem, its role in governance (if any), supply metrics (total, circulating, max), distribution model, and emission schedule. Link to the `[[Token Name]]` card.
33
33
34
34
**5. Getting Started & Resources:**
35
-
- Accessing: How to start using it (e.g., web app, download, API signup).
36
-
- Documentation: Link to official documentation.
37
-
- Community: Link to Discord/Telegram/Forum.
38
-
- Support: Link to support channel/FAQ.
39
-
- Source Code: Link to GitHub/GitLab (if open source).
35
+
- Accessing: Clear instructions on how to start using or interacting with the project/tool (e.g., web app URL, download links, API signup process).
36
+
- Comprehensive Documentation: Link to official, detailed documentation.
37
+
- Community Channels: Links to active official community channels (e.g., Discord, Telegram, Forum).
38
+
- Support Resources: Links to official support channels, FAQs, or knowledge bases.
39
+
- Source Code (if open source): Link to the primary code repositories (e.g., GitHub, GitLab), and mention the main license if known.
40
40
41
-
**6. Related Concepts:**
41
+
**6. Team and Project History:**
42
+
- Team: Introduce the core team members or key contributors. Highlight their relevant experience, expertise, and past projects if publicly known and significant.
43
+
- Project History & Milestones: Detail the project's development journey, including key milestones, significant achievements, major version releases, and any pivotal moments in its history. Outline future plans and long-term vision if available.
44
+
45
+
**7. Comparative Analysis (if applicable):**
46
+
- Similar Projects: Identify key similar or competing projects. Provide a balanced and detailed comparison, highlighting similarities, differences, respective strengths, weaknesses, and unique selling points. This section should offer readers a clear understanding of the project's position in the market.
47
+
48
+
**8. Related Concepts:**
42
49
- Links to relevant `explain-card`s (underlying technologies, e.g., Built using [[Optimistic Rollups]]).
43
50
- Links to relevant `awesome-card`s (e.g., See [[Awesome DeFi Tools]]).
**Anti-Money Laundering (AML)** refers to a set of laws, regulations, and procedures intended to prevent individuals and organizations from disguising illegally obtained funds as legitimate income. Money laundering is the process of making "dirty" money—proceeds from criminal activities like drug trafficking, terrorism, or corruption—appear "clean." AML measures are crucial for maintaining the integrity of financial systems and combating crime.
6
+
7
+
-**Importance/Purpose:** AML regulations aim to detect and deter money laundering and terrorist financing. They typically require financial institutions and other regulated entities to monitor customer transactions, verify identities ([[Know Your Customer (KYC)]]), and report suspicious activities.
8
+
-**Target Audience:** Financial institutions, regulators, law enforcement agencies, businesses in regulated sectors (including many [[Centralized Exchange (CEX)|cryptocurrency exchanges]]), and compliance professionals.
9
+
10
+
## Core Concepts & Mechanism
11
+
12
+
### Key Pillars of AML
13
+
14
+
1.**Know Your Customer (KYC):** Verifying the identity of customers to understand who they are and assess their risk profile. This is a foundational element of AML.
15
+
2.**Customer Due Diligence (CDD) / Enhanced Due Diligence (EDD):** Beyond initial identification, CDD involves ongoing monitoring of customer transactions and risk assessment. EDD is applied to higher-risk customers (e.g., Politically Exposed Persons - PEPs) and involves more intensive scrutiny.
16
+
3.**Suspicious Activity Reporting (SAR):** Requiring institutions to report transactions or activities that appear unusual or potentially linked to illicit activities to relevant authorities (e.g., Financial Crimes Enforcement Network - FinCEN in the US).
17
+
4.**Record Keeping:** Maintaining comprehensive records of customer identities and transactions for a specified period, which can be used for investigations.
18
+
5.**Compliance Programs:** Obligating institutions to develop and implement internal AML policies, procedures, controls, designate a compliance officer, provide ongoing employee training, and conduct independent audits of the program.
19
+
20
+
### The Money Laundering Process (Typically Three Stages)
21
+
22
+
1.**Placement:** Introducing illicit funds into the financial system (e.g., depositing cash into bank accounts, often in small amounts to avoid detection – known as smurfing).
23
+
2.**Layering:** Conducting complex financial transactions to obscure the source and ownership of the funds (e.g., wire transfers through multiple accounts, converting cash into financial instruments, investing in assets).
24
+
3.**Integration:** Making the laundered funds appear legitimate by re-introducing them into the economy (e.g., investing in legitimate businesses, real estate, or luxury assets).
25
+
26
+
### AML in the Context of Cryptocurrencies
27
+
28
+
Cryptocurrencies present unique challenges and opportunities for AML:
29
+
30
+
-**Challenges:** The pseudonymous nature of many cryptocurrencies, the global reach of transactions, and the emergence of privacy-enhancing technologies (like [[Privacy Coins]] and mixers) can make it harder to trace illicit funds.
31
+
-**Opportunities:** The transparency of public blockchains (like [[Bitcoin]] and [[Ethereum]]) means that all transactions are recorded on an immutable ledger. Blockchain analytics firms specialize in tracing cryptocurrency transactions and identifying links to illicit activities.
32
+
-**Regulation:** Regulators globally are increasingly applying AML rules to cryptocurrency exchanges, wallet providers, and other virtual asset service providers (VASPs). The Financial Action Task Force (FATF) has issued guidance, including the "Travel Rule," which requires VASPs to collect and share information about the originators and beneficiaries of crypto transfers.
33
+
34
+
## Use Cases & Implications
35
+
36
+
### Why AML is Important
37
+
38
+
-**Combats Crime:** Disrupts the financial networks of criminals and terrorists.
39
+
-**Protects Financial System Integrity:** Prevents financial institutions from being used for illicit purposes.
40
+
-**International Cooperation:** AML standards facilitate cooperation between countries in fighting cross-border financial crime.
41
+
-**Regulatory Compliance:** Failure to comply with AML regulations can result in severe penalties, fines, and reputational damage for institutions.
42
+
43
+
### Limitations & Challenges
44
+
45
+
-**Cost of Compliance:** Implementing robust AML programs can be expensive for financial institutions.
46
+
-**Customer Friction:** KYC and CDD processes can be cumbersome for customers.
47
+
-**Effectiveness Debate:** Critics argue that current AML regimes are overly burdensome and not always effective in stopping sophisticated money launderers, while potentially excluding legitimate users from financial services.
48
+
-**Evolving Threats:** Money launderers constantly adapt their methods, requiring AML strategies to evolve continuously.
49
+
-**Cross-Jurisdictional Complexity:** Differing AML regulations across countries can create compliance challenges for international businesses.
[[Binance]] is one of the world's largest cryptocurrency exchanges by trading volume. Founded in 2017 by Changpeng Zhao (CZ), it offers a comprehensive suite of crypto-related services, including trading, staking, lending, and its own blockchain ecosystems (BNB Chain).
-**Status:** Active and a dominant player, though facing regulatory scrutiny in various jurisdictions.
12
+
13
+
## Features
14
+
15
+
- Extensive range of tradable cryptocurrencies and trading pairs.
16
+
- Advanced trading interface with various order types and charting tools.
17
+
- Binance Earn: A suite of products for earning passive income on crypto holdings (staking, savings, liquidity farming).
18
+
- Binance Launchpad and Launchpool: Platforms for new token offerings and yield farming.
19
+
- Binance NFT Marketplace.
20
+
- Trust Wallet: Binance acquired Trust Wallet, a popular self-custodial mobile wallet.
21
+
- BNB Chain: A dual-blockchain architecture consisting of BNB Beacon Chain (for governance, staking) and BNB Smart Chain (BSC) (for smart contracts, EVM-compatible).
22
+
- Strong emphasis on liquidity and low trading fees (especially when using BNB to pay fees).
23
+
- Requires [[Know Your Customer (KYC)]] for most services.
24
+
25
+
## Ecosystem
26
+
27
+
-**BNB Chain:** A significant blockchain ecosystem with a wide range of dApps, particularly in DeFi and gaming. BNB Smart Chain (BSC) is known for its low transaction fees and fast transaction times, though it has faced criticism for being more centralized than Ethereum.
28
+
-**Trust Wallet:** A widely used mobile wallet.
29
+
-**Binance Labs:** An incubator and venture capital arm that invests in blockchain projects.
30
+
-**Binance Academy:** An open-access learning hub providing free blockchain and crypto education.
31
+
32
+
## Why it Matters in Web3
33
+
34
+
Binance is a major force in the Web3 world due to its:
35
+
36
+
- Massive user base and trading volume, providing significant liquidity to the market.
37
+
- BNB Chain ecosystem, which offers an alternative platform for dApp development and usage, particularly appealing to users and developers looking for lower fees compared to Ethereum (though with trade-offs in decentralization).
38
+
- Role in token launches and fostering new projects through Binance Launchpad and Labs.
39
+
- Educational initiatives that help onboard new users to Web3.
40
+
- Global reach, though this has also attracted significant regulatory challenges.
0 commit comments