Relay policy is a choice, not a rule.
A Bitcoin Core fork proposing two defaults: 3,900,000 weight units instead of 400,000, and 1 satoshi of dust instead of ~546. Consensus is untouched. There is no new chain, no new coin, and nothing to vote on.
bitcoindogmode.com is the public face of this client. It is not a download host. It is the argument, the live diff against Bitcoin Core, and the honest status of the branch.
- The switch — flip Core defaults to the proposed ones and watch a block fill
- Policy vs consensus — the same transaction through both sets of gates
- The live diff — every line that differs from Bitcoin Core, read from GitHub
- Run it — what you can already do with Core config, and what you cannot
- Download — GitHub releases only. There are none yet, and the page says so
These are the numbers the open policy work is aiming at. They are not on the default branch yet.
| Bitcoin Core | DOG Mode (proposed) | |
|---|---|---|
| Max standard tx weight | 400,000 WU (10% of a block) | 3,900,000 WU (97.5%) |
| Dust | ~546 sats | 1 sat |
| Consensus rules | unchanged | unchanged |
A larger transaction is already valid Bitcoin. Core's header file just will not relay it. That is a setting, not a rule.
The client lives at github.com/bitcoindogmode/bitcoin, branch 31.1-dogmode, built from Bitcoin Core v31.1.
As of now the default branch still matches Core on policy. The site's diff page tracks that live. Star that repository if you want the client to exist.
This repository is only the pointer: a pin, a README, a door to the site.
The C.A.T. community built the site for $DOG.