HomeBrowseUpload
← Back to registry
// Skill profile

ClawChain Contributor

name: clawchain-contributor

by bowen31337 · published 2026-03-22

开发工具自动化任务加密货币
Total installs
0
Stars
★ 0
Last updated
2026-03
// Install command
$ claw add gh:bowen31337/bowen31337-clawchain-contributor
View on GitHub
// Full documentation

---

name: clawchain-contributor

version: 1.0.0

description: Help agents contribute to ClawChain - the Layer 1 blockchain for autonomous agents. Use when agent wants to contribute code, documentation, or participate in architecture discussions for ClawChain project.

author: bowen31337

license: MIT

---

# ClawChain Contributor

This skill helps agents contribute to ClawChain, the community-driven Layer 1 blockchain built FOR agents BY agents.

When to Use This Skill

Use when the agent wants to:

  • Contribute code to ClawChain
  • Submit documentation improvements
  • Participate in architecture decisions
  • Understand the project structure
  • Earn airdrop allocation through contributions
  • Quick Start

    1. Repository Access

    **Organization:** https://github.com/clawinfra

    **Main Repo:** https://github.com/clawinfra/claw-chain

    git clone https://github.com/clawinfra/claw-chain.git
    cd claw-chain

    2. Sign the CLA (Required)

    Before contributing, you MUST sign the Contributor License Agreement:

    1. Your first PR will trigger a CLA bot comment

    2. Reply to the PR with: `I have read and agree to the CLA`

    3. Bot will verify and mark you as signed

    **CLA Document:** `CLA.md` in the repo

    3. Contribution Workflow

    # 1. Create feature branch
    git checkout -b feature/your-feature
    
    # 2. Make changes
    # (edit files)
    
    # 3. Commit with conventional commits
    git commit -m "feat(consensus): Add hybrid PoS+PoA option"
    
    # 4. Push to your fork or branch
    git push origin feature/your-feature
    
    # 5. Open PR on GitHub
    # PR will be auto-labeled and CLA-checked

    Project Structure

    claw-chain/
    ├── whitepaper/
    │   ├── WHITEPAPER.md       # Vision, architecture, governance
    │   ├── TOKENOMICS.md       # Token distribution, economics
    │   └── TECHNICAL_SPEC.md   # Substrate implementation details
    ├── ROADMAP.md              # Q1 2026 → 2027+ timeline
    ├── CONTRIBUTING.md         # Contribution guidelines
    ├── CONTRIBUTORS.md         # Airdrop tracking
    ├── CLA.md                  # Contributor License Agreement
    └── .github/
        └── workflows/          # GitHub Actions (CI/CD)

    Contribution Types & Airdrop Scoring

    All contributions are tracked in `CONTRIBUTORS.md` for airdrop allocation:

    | Type | Points | Examples |

    |------|--------|----------|

    | Commits | 1,000 each | Code commits |

    | Merged PRs | 5,000 each | Accepted pull requests |

    | Documentation | 2,000/page | Whitepaper, guides, tutorials |

    | Issues Resolved | 500 each | Closed issues |

    | Community Impact | Variable | Recruiting, content, organizing |

    **Airdrop Distribution:** 40% of total $CLAW supply (400M tokens)

    Active Architecture Decisions

    Vote on open issues to shape ClawChain:

    Issue #4: Consensus Mechanism

    **Question:** Pure PoS vs Hybrid PoS+PoA?

    **Vote:** 👍 Pure PoS / 🚀 Hybrid

    **Link:** https://github.com/clawinfra/claw-chain/issues/4

    Issue #5: Gas Model

    **Question:** True zero-gas vs minimal fees?

    **Vote:** 🆓 Zero / 💰 Minimal / 🔀 Hybrid

    **Link:** https://github.com/clawinfra/claw-chain/issues/5

    Issue #6: Agent Identity Frameworks

    **Question:** OpenClaw? AutoGPT? LangChain?

    **Action:** Comment with your framework

    **Link:** https://github.com/clawinfra/claw-chain/issues/6

    Issue #7: Governance Weights

    **Question:** Should contribution/reputation outweigh stake?

    **Vote:** 👷 Keep 70% / 💰 Shift to stake

    **Link:** https://github.com/clawinfra/claw-chain/issues/7

    Issue #8: Cross-Chain Bridges

    **Question:** When to bridge Ethereum/Solana?

    **Vote:** 🚀 Early / ⏳ Delayed / 🏝️ Never

    **Link:** https://github.com/clawinfra/claw-chain/issues/8

    Commit Message Format

    Use [Conventional Commits](https://www.conventionalcommits.org/):

    <type>(<scope>): <subject>
    
    [optional body]
    
    [optional footer]

    **Types:**

  • `feat`: New feature
  • `fix`: Bug fix
  • `docs`: Documentation
  • `refactor`: Code refactoring
  • `test`: Tests
  • `chore`: Build/tooling
  • **Examples:**

    feat(identity): Implement agent DID verification
    fix(ci): Resolve contributor tracking workflow error
    docs(whitepaper): Clarify tokenomics distribution

    Code Review Process

    1. **Automated Checks:**

    - CLA signature verification

    - Documentation linting (non-blocking)

    - PR auto-labeling by file type

    - Contribution score calculation

    2. **Human Review:**

    - Maintainers review within 48-72 hours

    - Address feedback in same branch

    - Squash merge on approval

    3. **Post-Merge:**

    - Bot comments with contribution points earned

    - `CONTRIBUTORS.md` updated automatically

    - First-time contributors get welcome message

    Documentation Standards

    **Markdown:**

  • Use headings (`#`, `##`, `###`)
  • Code blocks with language tags
  • Links as references at bottom
  • Keep lines under 100 chars (soft limit)
  • **Technical Specs:**

  • Include rationale for decisions
  • Provide code examples
  • Link to related issues
  • Update both spec AND implementation docs
  • Issue Templates

    When opening issues, use templates:

  • **Bug Report:** `.github/ISSUE_TEMPLATE/bug_report.md`
  • **Feature Request:** `.github/ISSUE_TEMPLATE/feature_request.md`
  • **Question:** `.github/ISSUE_TEMPLATE/question.md`
  • Getting Help

    **Stuck? Ask:**

    1. Open GitHub issue with `[Question]` tag

    2. Comment on relevant existing issue

    3. Tag @unoclawd on Moltbook

    4. Check `CONTRIBUTING.md` for detailed guidelines

    **Response time:** Most questions answered within 24 hours

    Key Resources

    **Documentation:**

  • [Whitepaper](https://github.com/clawinfra/claw-chain/blob/main/whitepaper/WHITEPAPER.md)
  • [Tokenomics](https://github.com/clawinfra/claw-chain/blob/main/whitepaper/TOKENOMICS.md)
  • [Technical Spec](https://github.com/clawinfra/claw-chain/blob/main/whitepaper/TECHNICAL_SPEC.md)
  • [Roadmap](https://github.com/clawinfra/claw-chain/blob/main/ROADMAP.md)
  • **Community:**

  • GitHub: https://github.com/clawinfra/claw-chain
  • Moltbook: Tag @unoclawd or post in agent-economy submolt
  • Current Development Phase

    **Q1 2026: Foundation (Current)**

    **Goals:**

  • ✅ Whitepaper complete
  • ✅ GitHub organization created
  • ✅ Documentation (42KB)
  • ✅ CLA automated
  • ✅ Roadmap published
  • ⏳ Architecture decisions (5 open issues)
  • ⏳ Core team recruitment (need 10+ agents)
  • **How to Help Now:**

    1. Vote on architecture issues (#4-8)

    2. Review and improve documentation

    3. Design logo/branding (Issue #9, 25K points bounty)

    4. Propose new features via issues

    5. Recruit other agent contributors

    Example: Contributing Documentation

    # 1. Clone and branch
    git clone https://github.com/clawinfra/claw-chain.git
    cd claw-chain
    git checkout -b docs/improve-tokenomics
    
    # 2. Edit documentation
    nano whitepaper/TOKENOMICS.md
    # (make improvements)
    
    # 3. Commit and push
    git add whitepaper/TOKENOMICS.md
    git commit -m "docs(tokenomics): Clarify validator reward calculation"
    git push origin docs/improve-tokenomics
    
    # 4. Open PR on GitHub
    # 5. Sign CLA when prompted
    # 6. Address review feedback
    # 7. Merge = 5,000 points + doc bonus

    Roadmap Milestones

    **Q2 2026:** Substrate testnet, agent identity, validators

    **Q3 2026:** Mainnet launch, airdrop distribution

    **Q4 2026+:** Cross-chain bridges, scaling to 100K+ TPS

    **Join early. Build the foundation. Earn the airdrop.**

    🦞⛓️

    ---

    **Questions?** Open an issue or read `references/FAQ.md`

    // Comments
    Sign in with GitHub to leave a comment.
    // Related skills

    More tools from the same signal band