Posts tagged with "news"

The coinbase lock went from 45 days, to a one-year hold on the table, to a rolling 180 days in six weeks. The dated record, each line a source and a quote, for a miner who wants to know what rule will apply to next month's coins and where that is being decided.

The 100-block grace ended at 973,540 on September 22. In the next 24 hours our node rejected ten blocks, each for spending a coin mined at 973,440 or later; one spend was mined nine times; nobody built on any of them; no coin from the window has moved, and the ledger's spent share went from 65 to 93 percent a day to zero. The sixth retarget landed at 1.353x, the second the cap did not touch. One dated record, from one node.

The 45-day coinbase maturity enforces from block 973,440. Moving the official Umbrel Bitcoin Knots app from rc4 to the 29.4.2 final took one command, one click and 22 seconds of downtime. The store trap, the way back, the node's own before and after, and one catch: the release changed the difficulty RPC field and the mempool app stopped.

Mining Stacker says anyone who did not come out of the first days with two to five hundred coins got rugged by their own people. We asked our node which window that was, who got how many coins in it, and how much of that has moved. Twelve payout addresses of 793 crossed 300 XBT. Two are pools. Of the other ten, four have moved nothing and four have moved everything.

We went looking for AlphaPool's other addresses with our own node. What we found: none. What we found instead: the same address under three coinbase tags, which is why an explorer's pool list reads it four points low, and a pool that pays about 950 addresses at the hour its coins mature.

One pool took half the blocks of a ten-day profit window that bitcoin's own retarget rule held open, and the Knots room is now picking a coinbase-maturity number to answer it. The problem named, from a five-hundred-year-old chapter; the three harms separated; and one test, from the white paper, that scores every proposal on the table.

This week two exchanges relabeled the BLAKE2b coin XBT and a third still calls it BTCB2. We typed XBT into the one app most newcomers already have and wrote down what came back. Why that matters more than whose ticker it is, and which one we use.

On September 6 the Liquid federation's wallet paid out 4,019 BTC to someone who had minted L-BTC out of nothing. We ran that transaction through our own node on the BLAKE2b chain. It fails, and the reason it fails is the part worth knowing if you have spent old coins since August 30.

The SC Box web API answers reads and writes with no password, and the box ships with an open WiFi access point. What we confirmed, what we deliberately did not test, and what to do today.

128 coinbase tags in the first 1,818 BLAKE2b blocks, against 18 pools on the chain that kept SHA-256d. What the chart shows, what it cannot, and which law of money the names are betting on.

The first retarget cut difficulty 41%. The next two are capped at 4x each, and the arithmetic says half-minute blocks for a day, then two-and-a-half-minute blocks for three and a half days, then ten. Dated, so it can be checked.

Our $250 used Goldshell SC Box found three BLAKE2b mainnet blocks in eight hours, about 9.39 BTC of coinbase to our own address. What the odds actually were, why the explorer files us under Unknown, and what a reset would do to all of it.

Three blocks paid 9.39 BTC to our Ledger address. Ledger Live will not show them, Sparrow would not either, and mempool.guide shows all of it. Nothing is wrong. Here is the picture.

The exact steps that took our Umbrel from a stalled SHA-256d node to solo mining BLAKE2b mainnet: Knots rc4, the wallet, and DATUM, with every trap we hit on the way.