botcoin-miner

Mine Botcoin with a trust-first workflow: clear value proposition, verifiable binaries, and explicit operational guidance.

Jump to install

Repository: duclm1x1/Dive-Ai
Last source activity: February 10, 2026 at 17:50
Detected SKILL.md language: English
Stars: 4
Forks: 2

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/duclm1x1/Dive-Ai --skill botcoin-miner

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

dive-memory-v3

Persistent memory system for AI agents following Model Context Protocol (MCP). Use for storing long-term memories across sessions, semantic search of past knowledge, building knowledge graphs, auto-injecting context, deduplicating memories, syncing to cloud storage. Essential for agents that need to remember decisions, solutions, preferences, and learned patterns over time.

2026-02-10

dive-memory-v3

2026-02-10

api-design-principles

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

2026-02-10

View all from this repository

--- ## Fleet recovery / restart notes (history) ### The short version Botcoin’s story is a story about agents learning the same lesson the hard way: **hashpower without consensus is just heat.** And the second lesson: **no premine means no shortcuts** — every coin has to be pulled out of the void by CPU time. ### The saga (timestamped, from the last few days) - **2026-01-31** — *The birth.* - The chain stabilized and synced; already **past block 311** and climbing. - Ten nodes across Europe were running — and at first they weren’t even a “fleet”… just ten parallel universes mining ten incompatible forks. - Once peering was fixed, consensus snapped into place: **longest chain wins**. - **2026-02-02** — *The wake-up call (strangers arrive).* - Around **heights 1784–1787**, blocks started landing to addresses we didn’t recognize. - Third‑party miners had joined the network — and they were taking blocks. - We rebuilt the internal miner and fixed hot-loop inefficiencies (the famous “patch 4 bytes, don’t reserialize the world”). - Result: roughly **120×** per-node hashrate improvement, and the network surged forward to around **~1920**. - **2026-02-03 18:02 AEDT** — *The fleet split into ten tiny universes (again).* - The chain was **well past 3,700 blocks** (e.g. **block 3756** was observed). - But the fleet was silently partitioned: nodes disagreed on the tip by hundreds of blocks. - Everything looked “healthy” locally — blocks, balances, logs — until you notice you’re accumulating value on a chain nobody else recognizes. - **2026-02-04 ~06:43 AEDT** — *The restart (new chain launch).* - Mining stalled with template timeouts ("no templates / timeout waiting for first template"). - We shipped a targeted miner fix so mining cannot deadlock on edge-case IBD conditions. - Then we did the hard, clean thing: **We restarted the network from genesis.** - Datadirs were wiped across the fleet. - A seed node was started first, then the rest joined. - Mining resumed immediately — fresh blocks were being found within minutes — and the fleet eventually converged to a single canonical chain. ### Why we chose to restart from genesis Because young networks are ecosystems. When a chain wedges hard enough — and when everyone can coordinate a clean reboot — the fastest path back to a shared reality is: - one verified binary across all miners, - then rebuild the chain from block 0 with peers connected. ### Practical takeaways - **Never mine “latest.”** Pin a tag/commit. - Prefer **release tarballs + SHA256SUMS** or one reproducible build artifact. - If you restart from genesis: mine on **1–2 nodes first**, let others sync, then enable mining broadly to avoid long-lived forks. (Deeper detail: Botcoin repo `docs/lessons-learned-fleet-recovery.md`.) --- ## Handy commands - `botcoin-cli getblockchaininfo` - `botcoin-cli getconnectioncount` - `botcoin-cli getinternalmininginfo` - `botcoin-cli getbestblockhash` - `botcoin-cli stop` --- ## Links - Repo: https://github.com/happybigmtn/botcoin - Skill page: https://www.clawhub.ai/happybigmtn/botcoin-miner *The revolution will not be centralized.*

botcoin-miner

Install options

Review the source files

Botcoin Miner (v4.0)

Why this is interesting

Trust & safety (how to prove what you’re running)

Available binaries / platforms

Botcoin Miner (v4.0)

Why this is interesting

Trust & safety (how to prove what you’re running)

Available binaries / platforms

Install (recommended: verify-first)

Start mining (internal miner)

RandomX mode: FAST vs LIGHT (critical)

name	botcoin-miner
version	4.0.1
description	Mine Botcoin with a trust-first workflow: clear value proposition, verifiable binaries, and explicit operational guidance.
homepage	https://github.com/happybigmtn/botcoin

botcoin-miner

Source facts

Install options

Review the source files

More from this repository

More from this repository

Botcoin Miner (v4.0)

Why this is interesting

Trust & safety (how to prove what you’re running)

Available binaries / platforms

Botcoin Miner (v4.0)

Why this is interesting

Trust & safety (how to prove what you’re running)

Available binaries / platforms

Install (recommended: verify-first)

Start mining (internal miner)

RandomX mode: FAST vs LIGHT (critical)