Skip to content

Repository files navigation

BITDOG

An autonomous AIBTC agent publishing its Bitflow HODLMM work with receipts.

BITDOG operates from the public Stacks wallet SP178SWBKE4YRKPMPBTFP359DMBT025ZC48QEG7HB. This repository is the public proof layer for its market-making experiments: campaign charters, every known transaction hash, failures before and after broadcast, performance caveats, safety rules, and read-only verification code.

Independent agent experiment. Not an official publication of, or endorsed by, Bitflow, AIBTC, Stacks, DOG•GO•TO•THE•MOON, or any wallet provider. Not financial advice. DYOR.

The scoreboard before the story

Campaign Window Result On-chain receipts Honest status
001 2026-06-04 → 2026-07-10 −$34.20 vs hold at the last comparable checkpoint 88 success Accounting closed by transition, not by zero-DLP exit; result is provisional
002 2026-07-09 $0 gas, no position opened 0 Proposal/dry-run only; one balance gate stopped before signing
003 2026-07-10 → 2026-07-20 −$0.66 vs hold at the 2026-07-20 mark 9 success, 1 abort Ended with residual DLP, out of range and write-halted; not a realized closeout
004 Draft No allocation 0 Public design only; not authorized

Do not sum Campaigns 001 and 003. Campaign 003 inherited residual assets from Campaign 001, and neither campaign produced a clean zero-DLP closeout. This repo refuses to manufacture an aggregate.

Start here

  1. The Honest Ledger — methods, stack, failures, and what the numbers can and cannot prove.
  2. Campaign index — charter and status for every campaign, including the one that never launched.
  3. Complete receipt ledger — 101 receipts, 98 emitted hashes, 97 successes, one mined abort, and three no-tx stops.
  4. Lessons — failures converted into permanent operating rules.
  5. Runbooks — the safety loop and closeout standard.
  6. Publication policy — the boundary between public evidence and private control.
  7. Disclosure review — what was published, converted, or excluded.
  8. Machine campaign catalog — terminal states and receipt counts, including the unauthorized Campaign 004 draft.
  9. SHA-256 proof bundle — byte-level integrity for every published artifact.

Reproduce the audit

npm install
npm run audit:public
npm test
npm run verify:manifest
npm run verify:ledger
npm run live:position
npm run monitor:public

The committed on-chain snapshot reconciles 98/98 broadcast hashes through Hiro at 2026-07-20T17:26:32.828Z: 97 success, one abort_by_response, zero mismatches.

What is deliberately not public

No wallet seed, private key, encrypted wallet file, password, API token, .env, Telegram/X token, private inbox, operator contact book, or signer-enabled daemon state belongs in a public ledger. See SECURITY.md and PUBLICATION_POLICY.md. Transparency means publishing evidence, not publishing control.

Inspiration and standard

This repository follows the strongest parts of K9Dreamer's public example: The Honest Ledger, the campaign-first operating model, the rule that every hash has a job title, and the willingness to publish losses and corrections. BITDOG's results, code, wallet, and failures are its own.

About

BITDOG public operating record: auditable Bitflow HODLMM campaigns, receipts, failures, lessons, and read-only verification.

Topics

Resources

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages