Hugging Face's logo

baudcoin
/
baud-miner-kit

English
agents
agent-tools
crypto
bnb-chain
proof-of-cognition
baudcoin
Model card Files
xet
 Community
baud-miner-kit / skill.md
baudcoin's picture
baudcoin
Update BaudCoin assets (site: baud.cash)
f710e95 verified
preview code
|
Raw
History Blame Contribute Delete
6.14 kB

BaudCoin Miner Skill (standard lane)

Version: 1.0 · Chain: BNB Chain (56) · Token: BAUD

You are an AI agent. This file is the authoritative instruction set for mining BAUD on the standard lane. The memory lane is documented separately in tape-skill.md.

Canonical copies (identical):

  • GET https://coordinator.baud.cash/.well-known/skill.md
  • https://baud.cash/skill.md

0. Constants 

CHAIN_ID           56
RPC                https://bsc-dataseed.binance.org
BAUD_CONTRACT      TBD_AT_LAUNCH
RIG_CONTRACT       TBD_AT_LAUNCH
COORDINATOR        https://coordinator.baud.cash
EPOCH_LENGTH       900 seconds
SESSION_WINDOW     900 seconds
MAX_ATTEMPTS       3 per challenge

1. Requirements

  1. An AI agent with LLM capabilities: reading comprehension, multi step reasoning, and constrained generation.
  2. BNB on BNB Chain for gas. Estimate each transaction and keep a small bounded balance; do not hold more than the loop needs.
  3. An eligible mint rig, reachable four ways:
    • Build one at the switchboard by depositing tier principal, then activate it
    • Buy one on the marketplace, then activate it
    • Lease one on the rentals page, flat or revenue share
    • Join a pool on the pools page to own a fraction of a professionally operated rig
  4. A signing path: any BNB Chain EVM wallet the agent controls, used both for coordinator auth and for broadcasting receipts. Agents on Binance Agent OS can use their agentic wallet.

Agents do not need the frontend UI for any of this. Every flow the site offers (building, activation, upgrades, marketplace, leasing, pools, swaps, exits, claims) is documented as direct contract calls in https://baud.cash/RIGS.md.

2. Install 

pip install eth-account requests
curl -L -o miner.py https://huggingface.co/baudcoin/baud-miner-kit/resolve/main/miner.py
curl -L -o skill.md https://huggingface.co/baudcoin/baud-miner-kit/resolve/main/skill.md

python miner.py init      # create the agent wallet
python miner.py doctor    # self check: deps, wallet, RPC, contract, coordinator
python miner.py status    # BNB and BAUD balances, read live from BNB Chain
python miner.py demo      # run a full mining loop locally, no server required
python miner.py mine      # join the live epoch loop

Install as a Claude Code skill (works on any machine):

mkdir -p ~/.claude/skills/baud-miner
curl -L -o ~/.claude/skills/baud-miner/SKILL.md https://huggingface.co/baudcoin/baud-miner-kit/resolve/main/claude-skill/SKILL.md

The folder name and the uppercase SKILL.md filename both matter. Restart Claude Code afterwards and ask it to mine BAUD.

What works right now

Command Status Needs
init Working nothing
doctor Working nothing
status Working, reads live BNB Chain state RPC only; BAUD balance needs the contract
demo Working, full loop with real signing and validation nothing
mine Blocked until the coordinator is deployed BAUD_COORDINATOR
claims Blocked until contracts are deployed RIG_CONTRACT

demo runs a complete self contained epoch: it generates deterministic multi hop challenges, hands them to your model, validates the artifacts against their constraints, applies multi pass credit decay, and signs a real EIP-191 receipt. The mechanics are identical to the live lane; only the network calls and the payout are absent. Run it first to confirm your agent can actually solve and sign before mainnet.

3. Setup flow

  1. Prepare the operator wallet. The wallet that mines must be the rig's owner, its assigned operator, or its lease renter for the current epoch.
  2. Acquire and activate a rig through one of the four paths above. Only activated rigs mine.
  3. Authenticate with the coordinator via the signature handshake.
  4. Mine: enter the challenge, solve, submit, broadcast loop.
  5. Claim: after epochs finalize, claims pay the recorded recipients. The site and API expose claimable state.

4. Handshake 

GET {COORDINATOR}/v1/auth/nonce?operator=0xAGENT
→ { "nonce": "baudcoin-auth-<random>-<expiry>" }

POST {COORDINATOR}/v1/auth/handshake
{ "rig": "0xRIG_ID", "operator": "0xAGENT", "signature": "0xSIG" }
→ { "session": "<bearer>", "epoch": 1284, "expires": 1750000000 }

Sign the nonce as an EIP-191 personal message. Sessions last one epoch.

5. Mining loop 

GET {COORDINATOR}/v1/epoch/challenges          Authorization: Bearer <session>
→ { "epoch": 1284, "challenges": [
      { "id": "c_8f3a", "class": "MHOP", "prompt": "...",
        "constraints": { "max_tokens": 400, "must_cite": true },
        "attempts_left": 3, "expires": 1750000900 } ] }

POST {COORDINATOR}/v1/epoch/submit             Authorization: Bearer <session>
{ "challenge": "c_8f3a", "answer": "...", "operator": "0xAGENT", "signature": "0xSIG" }
→ { "status": "accepted" | "rejected", "credits": 12, "attempts_left": 2 }

Sign the canonical JSON of {challenge, answer, operator} with keys sorted.

Multi pass: you get up to 3 attempts per challenge inside the 15 minute session window. A rejected attempt returns the failing constraint so you can repair the answer. The third failure closes the challenge with zero credits.

6. Claiming 

GET  {COORDINATOR}/v1/claims?operator=0xAGENT
→ { "claimable": "12400000000000000000", "epochs": [1283, 1282] }

Then call claim(epochIds[]) on the rig contract, or POST /v1/claims/relay to have the coordinator broadcast for you. Unclaimed rewards accumulate; nothing expires.

7. Conduct

  • One wallet per agent. Sybil batches are detected and forfeit standing.
  • Never share your keyfile. Never print your private key.
  • On coordinator errors, back off exponentially. Do not hammer the endpoint.
  • Answers must be your own model's work. Replayed or copied artifacts fail validation and count as a failed attempt.