[dogofbitcoin]

Not code. This adds doc/dogmode-operator.md: how to run a DOG Mode node, written from a node we run and from what the repository actually contains. It is maintained by the Dog of Bitcoin Foundation.

What is in it: policy versus consensus in plain words and what the three changes do (with the two consequences the release notes mention only in passing: the OP_RETURN default and the inbound-slot cost); where the client stands today (the policy set merged in #3 as 7503240091 on 31.1-dogmode, and no release, binaries or attestations yet); hardware with measured numbers; building a pinned commit and verifying the hash before running it; the no-wallet, localhost-RPC, unprivileged-user posture with a systemd unit; the initial sync with 8333 closed and a measured duration; the DOG Mode specific checks and knobs (localservicesnames, the dog connection type, datacarriersize, dustrelayfee, maxmempool); opening the port on purpose; updating without a re-sync; backups with a restore that was actually run; how to tell when a node is quietly wrong; and where to report what.

Every number is dated and was measured on that node or read from this repository on the date given. The "today" sections are written to be rewritten when a release exists; the recipe does not change. The independent builds of the merged tip by krsnak (#8) and J25dunn (#3) are credited in the file.

Corrections welcome, especially from anyone who has measured something we have not.

[dogofbitcoin]

A note from the Dog of Bitcoin Foundation about packaging DOG Mode for Umbrel, posted here because this is where you read us.

We would like to make DOG Mode installable on Umbrel (the home-node OS; Bitcoin Core and
Bitcoin Knots are both one-click apps there). The shape is the one Knots uses: Umbrel's own
Bitcoin Node web UI with the DOG Mode bitcoind in place of Core's, its own ports so it runs
beside a Core app, and the manifest flag that lets Electrs, mempool and Lightning apps use it
as their node.

Three things we want to get right with you before it goes anywhere:

1. The name and the repo. The listing would be called "DOG Mode" (or whatever you prefer),
   point at github.com/bitcoindogmode/bitcoin as the upstream project and support link, and say
   that the Dog of Bitcoin Foundation maintains the package, not the client. If you would rather
   submit it under your own account, or co-maintain it, we will hand over the package and the
   images.

2. The binary. Knots' Umbrel image downloads your release tarball and verifies the PGP
   signatures against the builder keys, so nobody has to trust the packager. There is no DOG Mode
   release yet, so our first image builds from source at the merge commit 7503240, with the
   Dockerfile public and the checksums published (github.com/dogofbitcoin/docker-dogmode). It runs
   on an Umbrel Home today, peered with our own node, and the listing says plainly who built it. The moment you cut a tagged release with signed SHA256SUMS (Guix attestations if you do
   them), we switch the image to download-and-verify like Knots, which is also what Umbrel's
   official store will expect. If a release is on your list, that is the one thing that helps
   most; if you want a hand with the Guix build and attestations, say so.

3. The version label. The app's header names the client "DOG Mode 31.1.0" until a release
   name exists. Tell us the name you want on it.

Nothing goes to Umbrel's store until you have answered. A community app store link can go out
earlier to people who ask, with the same wording about who built the binary.

[leonidaskingdev]

Let's just pause on this until we cut a release. Probably not a good idea to share a link out to anyone to run any version of DOG Mode on Umbrel before the actual release. I won't have final answers for you until we have cut the first public release because a few things are undecided. Totally fine for it to be released to Umbrel's app store under your foundation though so good to see it is already close to ready. I'm sure that within the days following the release the Umbrel app can go live. Doesn't have to be literally the moment the release happens.

[dogofbitcoin]

Closing this in favour of #8.

krsnak opened #8 on the 9th with the same file, written after pull request 3 merged, and his branch now carries this one's attribution lines as well. Two pull requests adding one file only makes work for whoever reads them, so his is the one to read.