new

.commitlintrc.yaml

@@ -0,0 +1,3 @@
+extends:
+  - "@commitlint/config-conventional"
+

.github/ISSUE_TEMPLATE/task.yml

@@ -0,0 +1,35 @@
+name: 更新任务
+description: 更新任务信息
+title: "[Task]: "
+labels: [task]
+assignees:
+  - izayl
+body:
+  - type: dropdown
+    id: type
+    attributes:
+      label: 这个 PR/issue 属于什么类型?
+      multiple: false
+      options:
+        - bug 修复（Bugfix）
+        - 创建新的基础任务
+        - 创建新的进阶任务
+        - 更新任务内容
+        - 任务认领
+  - type: input
+    id: task
+    attributes:
+      label: 涉及的任务是哪个
+      description: 请填写任务名
+      placeholder: 例如：uniswap-v3
+    validations:
+      required: true
+  - type: textarea
+    id: info
+    attributes:
+      label: 详细信息
+      description: Bug详细信息，或者更新、创建任务的内容
+      placeholder: Tell us what you see!
+      value: ""
+    validations:
+      required: false

.github/PULL_REQUEST_ISSUE_TAEMPLATE.md

@@ -0,0 +1,17 @@
+<!-- PULL REQUEST TEMPLATE -->
+<!-- (将 "[ ]" 换成 "[x]" 来选择列表项) -->
+
+**
+
+- [ ] bug 修复（Bugfix）
+- [ ] 创建新的基础任务
+- [ ] 创建新的进阶任务
+- [ ] 更新任务内容
+
+**涉及的任务是哪个？（必填）**
+
+<!-- 例如：Uniswap-V2 -->
+
+**其他信息：**
+
+<!-- 具体更新/创建任务的内容有哪些 -->

.github/workflows/codeql-analysis.yml

@@ -0,0 +1,71 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [ main ]
+  schedule:
+    - cron: '39 1 * * 5'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'javascript', 'python' ]
+        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
+        # Learn more:
+        # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v2
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v1
+      with:
+        languages: ${{ matrix.language }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+        # queries: ./path/to/local/query, your-org/your-repo/queries@main
+
+    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
+    # If this step fails, then you should remove it and run the build manually (see below)
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v1
+
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 https://git.io/JvXDl
+
+    # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
+    #    and modify them (or add more) to build your code if your project
+    #    uses a compiled language
+
+    #- run: |
+    #   make bootstrap
+    #   make release
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v1

.github/workflows/lint-pr.yml

@@ -0,0 +1,17 @@
+name: Lint PR
+
+on:
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+
+jobs:
+  main:
+    name: Validate PR title
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/action-semantic-pull-request@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/markdown-links.yml

@@ -0,0 +1,21 @@
+name: Check Markdown links
+on: 
+  workflow_dispatch:
+
+
+jobs:
+  markdown-link-check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Link Checker
+        id: lychee
+        uses: lycheeverse/lychee-action@v2.0.2
+
+      - name: Create Issue From File
+        if: env.lychee_exit_code != 0
+        uses: peter-evans/create-issue-from-file@v4
+        with:
+          title: Link Checker Report
+          content-filepath: ./lychee/out.md
+          labels: report, automated issue

.gitignore

@@ -1,8 +1,12 @@
 */node_modules
-*/sk.txt
-*/sk*.txt
-*/sk*.json
-*/package-lock.json
+**/.env
+**/sk.txt
+**/env.py
+**/sk*.txt
+**/sk*.json
+**/__pycache__
+**/Uniswap
+**/package-lock.json
 # dependencies
 /node_modules
 /.pnp
@@ -14,9 +18,11 @@
 **/*.bytecode.js
 **/*.abi.js
 **/*.address.js
-*/yarn.lock
-*/artifacts
-*/cache
+**/yarn.lock
+**/artifacts
+**/cache
+**/debug
+**/target
 
 # testing
 coverage
@@ -26,7 +32,7 @@ build
 
 # misc
 .DS_Store
-.env*
+.env
 
 # debug
 npm-debug.log*
@@ -35,3 +41,4 @@ yarn-error.log*
 
 .idea
 .vscode
+mnemonic.txt

.gitmodules

@@ -0,0 +1,9 @@
+[submodule "lib/openzeppelin-contracts"]
+path = lib/openzeppelin-contracts
+url = https://github.com/OpenZeppelin/openzeppelin-contracts
+[submodule "dao/dao/Openzeppelin-DAO"]
+path = dao/dao/Openzeppelin-DAO
+url = https://github.com/tamphill/openzeppelin_dao.git
+[submodule "basic/79-hardhat-foundry/lib/openzeppelin-contracts"]
+	path = basic/79-hardhat-foundry/lib/openzeppelin-contracts
+	url = https://github.com/Openzeppelin/openzeppelin-contracts

.husky/commit-msg

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npx commitlint --edit "$1"

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npx lint-staged

.lycheeignore

@@ -0,0 +1,2 @@
+https://sepolia.infura.io/v3
+http://127.0.0.1

.prettierignore

@@ -0,0 +1 @@
+README.md

.prettierrc

@@ -0,0 +1,25 @@
+{
+  "printWidth": 150,
+  "tabWidth": 2,
+  "semi": true,
+  "singleQuote": true,
+  "trailingComma": "es5",
+  "tslintIntegration": true,
+  "insertSpaceBeforeFunctionParenthesis": false,
+  "overrides": [
+    {
+      "files": ["*.js", "*.ts"],
+      "options": {
+        "semi": true,
+        "singleQuote": true
+      }
+    },
+    {
+      "files": "*.sol",
+      "options": {
+        "semi": true,
+        "tabWidth": 4
+      }
+    }
+  ]
+}

.solhint.json

@@ -0,0 +1,16 @@
+{
+  "extends": "solhint:recommended",
+  "rules": {
+    "code-complexity": ["warn", 7],
+    "function-max-lines": ["warn", 50],
+    "max-line-length": ["error", 120],
+    "func-param-name-mixedcase": "warn",
+    "modifier-name-mixedcase": "warn",
+    "ordering": "warn",
+    "compiler-version": ["error", "^0.8.20"],
+    "func-visibility": ["warn", { "ignoreConstructors": true }],
+    "immutable-vars-naming": "off",
+    "one-contract-per-file": "off",
+    "no-console": "off"
+  }
+}

.solhintignore

@@ -0,0 +1,2 @@
+lib
+node_modules/

BTC/Advanced/Lighting Network/README-EN.md

@@ -0,0 +1,42 @@
+# Lightning Network
+
+The Lightning Network is a Layer 2 payment protocol for Bitcoin, designed to enable fast, low-cost transactions by reducing on-chain transactions. Built on top of the Bitcoin blockchain, it aims to solve Bitcoin's current scalability and transaction speed issues. Here's a detailed introduction to the core concepts and functions of the Lightning Network:
+
+### 1. **Core Concept: Payment Channels**
+
+The Lightning Network operates through payment channels. The specific process is as follows:
+   - **Creating Payment Channels**: When two parties need frequent transactions, they can create a payment channel. This requires both parties to deposit initial funds into a multi-signature wallet, recorded on the blockchain as a single on-chain transaction.
+   - **Off-chain Transactions**: Once the channel is established, both parties can directly exchange signed balance updates off-chain, without requiring network-wide confirmation, greatly improving transaction speed.
+   - **Closing Channels**: When parties no longer need to continue transacting, they can choose to close the channel. The final balance state of the channel is then recorded on the Bitcoin blockchain as an on-chain transaction. This greatly reduces blockchain burden as multiple transactions only require two on-chain transactions (opening and closing).
+
+### 2. **Transaction Mechanism in Lightning Network**
+
+In the Lightning Network, transactions within channels are instantly confirmed. The specific process is:
+   - **Incremental Balance Updates**: Each off-chain transaction only updates the balance state in the payment channel, without broadcasting to the Bitcoin blockchain.
+   - **Decentralized Trust Transactions**: Each state update is confirmed by signatures from both parties, ensuring neither party can tamper with transaction balances, preventing attempts to take excess funds.
+
+### 3. **Cross-Channel Payment Routing**
+
+The Lightning Network supports not only direct payments between two channel users but also multi-hop payments, allowing funds to be transferred to target users through multiple channels. The specific process is:
+   - **Path Finding**: If there's no direct channel between two users, the network finds suitable paths through other nodes to complete the payment.
+   - **Payment Atomicity**: The entire payment only completes when all intermediate nodes in the path agree and complete their part of the payment, ensuring funds aren't intercepted during multi-hop processes.
+
+### 4. **Main Advantages**
+
+   - **Scalability**: Through off-chain transactions, the Lightning Network significantly reduces Bitcoin blockchain load, theoretically supporting millions of transactions per second.
+   - **Lower Fees**: Most transactions occur off-chain, with very low transaction fees, only requiring a fraction of on-chain transaction fees.
+   - **Instant Payments**: Lightning Network transactions are almost instantaneous, making them suitable for daily consumption, unlike on-chain transactions that might take minutes.
+
+### 5. **Challenges and Limitations**
+
+   - **Liquidity Requirements**: To ensure large transactions flow smoothly, each node in the path must have sufficient funds in the channel, otherwise transactions might be blocked.
+   - **Channel Management**: Users need to manually open and close channels, each operation requiring on-chain fees, making frequent operations costly.
+   - **Security Risks**: While the Lightning Network is highly secure, it's not without risks. Nodes need to stay online to prevent attackers from broadcasting outdated transactions.
+
+### 6. **Lightning Network Applications and Future**
+
+   - **Micropayments**: Due to low fees, the Lightning Network is ideal for micropayments, such as content tipping, small donations, and in-app purchases.
+   - **Merchant and Retail**: With near-real-time transaction speeds, the Lightning Network can make Bitcoin an ideal payment method for retail, dining, and daily consumption.
+   - **Cross-border Payments**: It enables quick and low-cost international remittances, providing a convenient path for cross-border payments.
+
+The Lightning Network continues to evolve with ongoing development and user growth. It provides a promising solution to Bitcoin's scalability, but to fully realize its potential, it requires support from a reliable and robust node network.

BTC/Advanced/Lighting Network/README.md

@@ -0,0 +1,40 @@
+**闪电网络**（Lightning Network）是一种比特币的第二层支付协议，旨在通过减少链上交易数量，实现快速、低成本的交易。这一网络在比特币区块链之上构建，旨在解决比特币当前的扩展性和交易速度问题。以下是对闪电网络的核心概念及其功能的详细介绍：
+
+### 1. **核心概念：支付通道**
+
+闪电网络的基本运行机制是通过支付通道。具体操作如下：
+   - **创建支付通道**：两方需要频繁交易时，可以通过创建支付通道来进行。这需要双方向一个多签名钱包存入初始资金，并记录在区块链上作为一次链上交易。
+   - **链下交易**：通道建立后，双方可以直接交换签名的余额更新，这些更新是链下进行的，不需要经过全网确认，从而大大提高了交易速度。
+   - **关闭通道**：当两方不再需要继续交易时，可以选择关闭通道。此时通道的最终余额状态会作为一次链上交易记录在比特币区块链上。这样可以极大减少区块链的负担，因为多笔交易只需记录两次链上交易（开通和关闭）。
+
+### 2. **闪电网络中的交易机制**
+
+在闪电网络中，通道内的交易是即时确认的。具体过程如下：
+   - **增量余额更新**：每次链下交易只更新支付通道中的余额状态，而不广播至比特币区块链。
+   - **去中心化的信任交易**：每次状态更新都由双方签名确认，确保任何一方都无法篡改交易余额，避免了一方试图多拿资金的可能。
+
+### 3. **跨通道支付的路由**
+
+闪电网络不仅限于两个通道用户间的直接支付，还支持多跳支付，使得资金能够通过多个通道转账给目标用户。具体过程如下：
+   - **路径查找**：如果两个用户之间没有直接的通道，网络会寻找合适的路径通过其他节点完成支付。
+   - **支付的原子性**：只有在路径中所有中间节点同意并完成自己的部分支付时，整个支付才会完成，确保资金在多跳过程中不被截留。
+
+### 4. **主要优势**
+
+   - **扩展性**：通过链下交易的方式，闪电网络大幅减少了比特币区块链的负载，理论上可以支持每秒数百万次交易。
+   - **降低费用**：大部分交易是链下进行的，交易费用很低，仅需链上交易费用的一小部分。
+   - **即时支付**：闪电网络的交易几乎是即时完成的，使其适用于日常消费，而不像链上交易那样可能需要数分钟。
+
+### 5. **挑战与局限性**
+
+   - **流动性要求**：为了确保大额交易畅通，路径中的每个节点必须在通道中拥有足够的资金，否则可能会阻塞交易。
+   - **通道管理**：用户需要手动开通和关闭通道，每次操作都需支付链上费用，因此频繁操作的成本较高。
+   - **安全风险**：虽然闪电网络安全性较高，但它并非没有风险。节点需要保持在线以防止攻击者试图广播过时的交易。
+
+### 6. **闪电网络的应用场景及未来**
+
+   - **小额支付**：由于费用低廉，闪电网络非常适合进行小额支付，如内容打赏、小额捐赠和应用内购买等。
+   - **商户和零售**：交易速度接近实时，闪电网络能使比特币成为零售、餐饮等日常消费的理想支付方式。
+   - **跨境支付**：它能快速且低成本地实现国际汇款，为跨境支付提供了一种便利的途径。
+
+闪电网络随着开发和用户的持续增长在不断发展。它为解决比特币的扩展性提供了一个极具前景的方案，但要充分发挥其潜力，还需要一个可靠且强大的节点网络支持。