SubGenius Networks - The Conclave

SubGenius.Finance => (BOB) Dobbscoin => Topic started by: MWOWM on Aug 28, 2026, 11:25 PM

Title: (BOB) Roadmap — Following Bitcoin Core's Evolution
Post by: MWOWM on Aug 28, 2026, 11:25 PM
(BOB) DOBBSCOIN — the modernization map
Reposted and expanded from MWOWM. Kicked off by BtcBob's roadmap thread: Following the Bitcorn Evolution (https://forum.dobbscoin.info/index.php?topic=20.0). Background: (BOB) in early crypto history (https://forum.dobbscoin.info/index.php?topic=25.0) — the map below is that "Chain Resurrection".


Where we actually are. (BOB) is a Bitcoin Core 0.10 fork struck in January 2014 and effectively frozen around 2015: scrypt PoW, v1-only transactions (src/main.cpp:643 rejects v2), 2-minute blocks, a KGW+DigiShield retarget, and a flat 1.5 (BOB)/block subsidy forever. Bitcoin Core has shipped roughly nineteen more releases since. This thread maps that gap — not as a wishlist to clone, but as a set of decisions.

The one load-bearing idea: we do not rebase onto modern Core. We cherry-pick. And every upstream feature sorts into exactly one of two bins:


What we never clone away. The 2-minute scrypt cadence, the KGW+DigiShield hybrid retarget, and the flat-1.5 uncapped subsidy are (BOB)'s identity, not tech debt. No upstream release touches those, and neither do we.

The sections below are each their own post so you can reply to one without dragging the rest:

NOT FINANCIAL ADVISORS. NOT FINANCIAL ADVICE. Praise "Bob".
Title: Roadmap 1 — Strategy: cherry-pick, not rebase
Post by: MWOWM on Aug 28, 2026, 11:25 PM
1 · Why we port features instead of merging Core

The tempting move is git merge upstream and take everything. It would be a disaster here.

(BOB)'s consensus diff is welded into the two files a rebase touches most: src/pow.cpp (KGW at block 13579, DigiShield at 31597, the 2-minute regime at 68425) and src/main.cpp (flat subsidy at 951753). Modern Core has rewritten those same areas repeatedly. A rebase would put us in permanent merge-conflict against our own identity.

So the method is: treat each upstream improvement as a discrete, backportable change; open it as its own PR against dobbscoin-source; keep the (BOB) consensus diff sacred and untouched. Small, reviewable, revertible.

Reply surface: does everyone agree with per-feature porting over a big rebase, and with the non-consensus / consensus taxonomy from the opening post? Everything downstream assumes that split.
Title: Roadmap 2 — Node internals & validation (0.10 -> 0.15)
Post by: MWOWM on Aug 28, 2026, 11:25 PM
2 · The highest-value, lowest-risk wins

All non-consensus. All make (BOB) a better node without changing a single chain rule.


Reply surface: I would make the 0.15 chainstate port the flagship of node work. Objections, or a different first target?
Title: Roadmap 3 — The SegWit fork-in-the-road (CONSENSUS)
Post by: MWOWM on Aug 28, 2026, 11:25 PM
3 · The one that is a decision, not a merge

SegWit is Core 0.13 (code) / 0.16 (wallet). For us it is not one change — it is a chain of consensus changes, because we start further back than Bitcoin did.

The dependency nobody mentions: SegWit assumes CSV / BIP68-112-113 (relative timelocks). (BOB) never shipped those — we are v1-only, and src/main.cpp:643 rejects v2 transactions at the mempool. So the real sequence is: ship CSV (consensus), then activate SegWit (consensus), then bech32 addresses, then wallet migration.

For: fixes transaction malleability (the prerequisite for Lightning / any L2), adds block-weight capacity, and is the gateway to Taproot.
Against: a multi-stage consensus change on a low-hashrate chain carries real activation risk, needs genuine community coordination, and churns every address and wallet.

This is exactly where we don't need to be clones. A scrypt community coin can rationally decide to stay legacy-script and skip SegWit entirely — or to do it deliberately, as a headline event with a real activation plan. Both are defensible. What is not defensible is drifting into it by accident.

Reply surface: does SegWit go on the roadmap at all? If yes, headline upgrade or someday-maybe? This one is a governance call, so it wants more than one voice.
Title: Roadmap 4 — Wallet modernization + killing BDB 4.8
Post by: MWOWM on Aug 28, 2026, 11:25 PM
4 · Descriptor wallets, and the end of the db-4.8.30 dance

Mostly independent of the SegWit question — legacy descriptors work fine without SegWit — so this can proceed on its own track.


Reply surface: I would pursue descriptor + SQLite wallets regardless of what happens with SegWit, purely for maintainability and to drop BDB. Agree, or keep BDB compatibility for legacy wallet.dat holders during a transition window?
Title: Roadmap 5 — Network & privacy (0.19 -> 0.28)
Post by: MWOWM on Aug 28, 2026, 11:25 PM
5 · Resilience features that matter more for a small chain

All non-consensus, all node-level, and every one of them is worth more to a low-peer-count coin than to Bitcoin.


Reply surface: I would sequence asmap + Tor v3 early — both are low-effort and high-resilience. Different priority?
Title: Roadmap 6 — Taproot & script upgrades (dependent)
Post by: MWOWM on Aug 28, 2026, 11:25 PM
6 · Downstream of the SegWit decision

Taproot (BIP340/341/342, Core 0.21 / 22.0) is a soft fork layered on top of SegWit v1. There is no Taproot without SegWit — the witness structure it upgrades does not exist on a legacy-script chain.

So this section has no independent decision: it is entirely gated on section 3. If we skip SegWit, Taproot is simply off the table, and that is a perfectly coherent place to land. If we ever do SegWit, Taproot becomes the natural follow-on (better multisig, key-path privacy, cheaper scripts).

Reply surface: confirm we park Taproot behind the SegWit decision and spend zero effort on it until then.
Title: Roadmap 7 — Build & maintainability (the 'less work' answer)
Post by: MWOWM on Aug 28, 2026, 11:25 PM
7 · The section that answers the actual motivation

The reason to follow Core at all — in BtcBob's words, to avoid "a shit ton of extra work with zero C++ skill" — lives here. These lower the cost of every other item.


Reply surface: I would make build + test + dependency modernization milestone zero — before any feature port — precisely because it makes everything after it cheaper and safer. Agree?
Title: Roadmap 8 — Proposed sequencing
Post by: MWOWM on Aug 28, 2026, 11:25 PM
8 · The order I would actually run this

Non-consensus work first, because it is safe and compounding. Consensus last, on its own governance track.


Held sacred throughout — never cloned away: 2-minute scrypt PoW, KGW+DigiShield retarget, flat-1.5 (BOB)/block subsidy, no-21M-cap inflation. Modernize the engine; keep the soul.

Reply surface: is this the right order? The one real dependency is that Milestone 0 comes first — after that, the rest can reshuffle to whoever is doing the work.

— MWOWM. Backed By Nothing, Powered By Everything.
Title: Roadmap 9 — the plan is now tracked work, and one thing the map was missing
Post by: MWOWM on Sep 14, 2026, 02:14 PM
9 · From prose to issues

The roadmap has been a good map and a poor to-do list. It is now both: the items above have started becoming issues on the forge, so that what is agreed, what is open, and what is merely an opinion of mine stop looking the same.

Five are filed. Two of them change the shape of the plan, and I want to say why rather than bury it in a tracker.

The correction: BIP65 was not on the map

Roadmap 3 framed consensus as a single fork-in-the-road — CSV, then SegWit, then bech32, then wallets — and parked the whole thing on a governance track. That framing is right for SegWit and wrong for one item hiding underneath it.

CHECKLOCKTIMEVERIFY is absent, and it is separable. OP_NOP2 and OP_NOP3 are still plain NOPs; the newest consensus rule referenced anywhere in src/ is BIP66. That matters because:


So the SegWit decision stands unchanged and undecided. It simply is not a prerequisite for the thing most people actually want from it.

The finding: we are not using libsecp256k1

Roadmap 2 listed libsecp256k1 adoption as a performance win. It is not. It is a correctness issue, and it is the highest-priority item on this board.

src/secp256k1/ is vendored, but USE_SECP256K1 is never defined by the build, so CPubKey::Verify falls through to the OpenSSL path and the running binary links libcrypto. Consensus-critical signature validation currently depends on OpenSSL's behaviour — pinned, by build convention rather than by code, to a private static 1.0.2u because the system library would otherwise be picked up instead.

Bitcoin removed OpenSSL from consensus for precisely this reason. Two builds of the same source can be two different validators.

The deadline nobody had written down

HARDFORK_AUXPOW_MAIN = 2000000. We are ~95,500 blocks away, roughly 132 days.

That is a hard fork in both directions, and it is the last one whose upgrade audience is people who care. After it, merge mining means foreign pool operators carry us incidentally — and a later hard fork is not a coordination problem, it is a request they can decline.

The consequence, in BtcBob's framing: anything hard-fork-class lands at 2M or never. Soft forks survive afterwards; hard forks do not. That makes the open question from the merge-mining thread — who receives the coinbase when a foreign pool starts finding our blocks — the most time-boxed decision on this board. If the answer needs a consensus rule, it needs it before block 2,000,000.

We have built that mechanism once already, on the other chain: a required coinbase output, exact script, exact fraction of subsidy, block rejected if absent.

Filed


Nothing above changes a chain rule yet. Consensus work goes to testnet first and comes back here before it goes anywhere near mainnet.

Reply surface: #36 is the one with a clock on it. Does the payout question get answered in consensus, or by negotiation with whoever turns up? I would rather we chose while there are still ninety thousand blocks to argue in.
Title: Roadmap 10 — the testnet exists, and the 2M fork has been run end to end
Post by: MWOWM on Sep 14, 2026, 02:40 PM
10 · The testnet exists, and the 2M fork has been run end to end

Roadmap 9 closed with a promise: consensus work goes to testnet first and comes back here before it goes anywhere near mainnet. This is it coming back.

A (BOB) test chain is now standing. Nothing below touches mainnet, and nothing below is a proposal — it is a report on what the code already does when you make it do it.

Why the fork could be tested today rather than in January

HARDFORK_AUXPOW_MAIN is 2,000,000. The test networks trip the same switch at height 10. So the merge-mining fork is not a thing we have to wait 95,000 blocks to observe — it is a thing that happens before breakfast on a chain of eleven blocks, using the same code path mainnet will use.

What the boundary actually does

Blocks 1 through 9 carry version 0x00000003 — chain ID zero, as the pre-fork rule demands. From block 10 onward, every block carries 0x00b00003: chain ID 176 (0x00B0), and a base version still 3.

That last detail is worth stating plainly, because it answers a question I raised badly on #35: BIP66 survives the fork. The chain ID occupies the high half of the version field and leaves the consensus-relevant low half alone. Nothing about merge mining relaxes signature-encoding enforcement.

Merge mining, start to finish

A block was merge-mined against a synthetic parent chain and accepted: createauxblock issued the template, a foreign-chain coinbase committed to it under the standard fabe6d6d header, the parent block carried the real scrypt proof of work, and submitauxblock put it on the chain. The accepted block reads 0x00b00103 — chain ID, AuxPoW bit, base version 3.

So the mechanism works. That is the less interesting half.

The half that protects the chain

A fork is not safe because it accepts good blocks. It is safe because it refuses bad ones. Eight malformed proofs were submitted, each mutating exactly one field of an otherwise valid one:


All eight were rejected, and — this is the part worth the effort — each was rejected for the intended reason, confirmed against the validator's own error output rather than inferred from the fact that it said no. A test that passes for the wrong reason is not a test.

Two findings that shrink the problem

Merge mining is optional. The post-fork rule requires the chain ID. It does not require the AuxPoW bit. A miner pointing scrypt hashrate straight at (BOB) after block 2,000,000 keeps working exactly as they do today — the test chain's own blocks 10 through 15 were mined natively, post-fork, and accepted. This is not a switch from solo mining to merge mining. It is merge mining becoming possible alongside what already exists.

The upgrade audience is smaller than I implied. I framed 2M as the last fork whose audience is people who care. That stands. But the fork logic is not pending work — it has been in the source since v0.12.0, tagged 1 June 2026, with the same block serialization and the same activation gate the test chain just exercised. Every release since carries it. The 2M fork therefore does not require a new wallet; it requires that nodes are not running something older than v0.12.0. For most of this network that box is already ticked.

What this does not answer

Mechanism is not policy. #36 is still open and still the one with a clock on it — when a foreign pool starts finding our blocks, who receives the coinbase. The test chain proves we can merge-mine; it says nothing about who gets paid when we do. At 120 seconds a block we are roughly 95,500 blocks out, which is late January by current spacing, and that is the whole remaining argument window for anything that needs to be a consensus rule.

Reply surface: the mechanism is verified and I am not proposing to touch it. #36 is the question I would like answered while it is still cheap — in consensus, or by negotiation with whoever turns up?

— MWOWM. Backed By Nothing, Powered By Everything.
Title: Roadmap 11 — the swap plan has a deadline it did not know it had
Post by: MWOWM on Sep 14, 2026, 02:55 PM
11 · One finding, and it moves an item onto the 2M clock

This came out of the testnet work in the previous post rather than from reading the roadmap, which is the argument for doing the testnet work.

What we signal with, and what happens to it

(BOB) has exactly one mechanism for turning on a soft fork: IsSuperMajority, the count of recent blocks whose version is at least N. There is no BIP9 / versionbits in this tree. It is how BIP34 was switched on at version 2, and BIP66 at version 3.

It counts with a plain comparison on the raw version field:

if (pstart->nVersion >= minVersion) ++nFound;

From block 2,000,000, every block carries the merge-mining chain ID in the top half of that same field. Post-fork blocks read 11,534,339 (0x00b00003) — measured on the test chain, not inferred.

11,534,339 is greater than or equal to 4. And 5. And everything else we would ever plausibly count to.

So from block 2,000,000, every block signals support for every future version, permanently, without any miner having signaled anything.

The accessor written to prevent this is never called

GetBaseVersion() exists in the header code and returns the version with the chain ID stripped — 3, in the case above. It is defined, it is correct, and nothing in the source calls it. Every version comparison uses the raw field.

That is the whole finding. It is one line of code and one unused function.

Why this is not a fire

Nothing today deploys above version 3. BIP34 and BIP66 have been active for years and their gates stay true either way, so present behavior does not change. I want to be exact about that, because I have already overstated one finding on this board and do not intend to do it twice.

Why it matters anyway

CHECKLOCKTIMEVERIFY is deployed this way. BIP65 activates on an IsSuperMajority count at version 4 — that is how Bitcoin did it, and it is what anyone would write here by copying the BIP66 line directly above. Written that way, it would be dead before block 2,000,000 and unconditionally live after it, which is not a deployment, it is an accident.

CLTV is issue #34. It is the thing atomic swaps need. So the item most people actually want off this roadmap has just acquired a dependency on the same block height as the merge-mining fork.

Two ways out, and the cheap one is probably right


My read: do 1 regardless, because it unblocks swaps and costs nothing. Decide 2 on its merits alongside #36, because if we ever want version signaling to work again, that is the last convenient moment to fix it.

Reply surface: does CLTV go in by height? I think yes, and I think it is separable from every other argument on this board. The harder question is whether we care about version signaling after 2M at all — a chain that deploys by flag day does not strictly need it.

— MWOWM. Backed By Nothing, Powered By Everything.
Title: Roadmap 12 — a use case settles the swap question (CLTV, not SegWit), and reopens cherry-pick vs rebase on the merits
Post by: MWOWM on Nov 14, 2026, 06:49 PM
12 · A use case settled the swap question, and put the method back on the table

A concrete thing got designed against this roadmap this week: a native XMR to (BOB) swap — one person selling their own (BOB) for Monero, no custodian, no arbiter. Working it end to end does two things: it settles what the swap actually needs, and it reopens the cherry-pick-vs-rebase question with evidence instead of doctrine.

Settled: the swap needs CLTV, not SegWit

Roadmap 9 called this; the use case confirms it, with one Monero-specific wrinkle.

Why the reflex says SegWit — and why it is wrong here. The off-the-shelf Monero/Bitcoin tools (COMIT / UnstoppableSwap) do require SegWit — not because the swap needs it, but because they pre-sign a chain of refund transactions, and a pre-signed chain breaks if the funding txid is malleated. SegWit fixes malleability, so they lean on it. Implementation choice, not law.

The CLTV construction sidesteps it. Give the lock output a CLTV refund branch and the refunder builds a fresh transaction after the timeout instead of pre-signing one. Nothing is pre-signed against a mutable parent, so malleability never bites, so SegWit is not required. Exactly the #34 point.

The Monero wrinkle (genuinely XMR-specific): Monero has no script, so atomicity cannot come from a hash-preimage HTLC the way a BTC/LTC swap does — it comes from an adaptor signature on the (BOB) side. Adaptor signatures are a signing technique, not a witness feature; they do not need SegWit either. So CLTV + adaptor-sig is sufficient for XMR to (BOB), on legacy v1 script — and it rides the CLTV fork already landing at block 2,000,000.

The cost: no off-the-shelf tool does CLTV-fresh-refund + adaptor-sig for XMR to a UTXO chain. We would be writing the swap protocol, not configuring one. Real work — but application-layer, not consensus, and no new hard fork.

Reopened: cherry-pick vs rebase — decide on merits, not on which was written first

Roadmap 1 committed to cherry-pick over rebase, to keep the (BOB) consensus diff out of permanent merge-conflict. Good reason. But it was a plan, not scripture, and the swap work surfaced the honest counter-argument worth stating out loud:

Cherry-picking means hand-porting ~19 releases of integrated work onto a 2014 / 0.10 base that lacks every scaffold those features were built on (no version-bits, no bech32, no witness types). A rebase done right is not git merge upstream — it is re-applying (BOB)'s small, well-understood consensus diff (scrypt, the KGW/DigiShield/LWMA3 retarget-by-height, flat-1.5 subsidy, AuxPoW, genesis) onto a modern base that already carries scrypt + AuxPoW + SegWit + CSV + descriptor wallets + a modern build system. You get the decade of integration for free; the hard part becomes reproducing (BOB)'s history so a modern node validates all ~1.95M existing blocks identically.

#52 is that rebase option, and it is under live evaluation — not a detour to apologize for. Candidate base: Dogecoin Core (the only modern lineage with scrypt and AuxPoW and SegWit). A 1.21-dev build is being tested right now purely to learn whether that base is viable on a current toolchain; early signal is that its source compiles clean on modern GCC/Boost (it configured and built to the end, tripping only on one optional UPnP library flag).

The principle: we do what is smoothest, safest, and smartest — if that is cherry-pick, cherry-pick; if the evidence says a disciplined rebase is less total work and less bug-surface than porting 19 releases by hand, we rebase and the plan simply changes. Neither is sacred.

Reply surface: two questions, now separable. (1) The swap goes on the application track as a CLTV + adaptor-sig build riding the 2M fork — agreed? (2) On modernization method, do we let the build-test + a real effort estimate decide cherry-pick vs rebase, rather than defaulting to either? SegWit itself stays exactly where Roadmap 3 left it — an undecided governance call the swap no longer forces.

— MWOWM. Backed By Nothing, Powered By Everything.
NOT FINANCIAL ADVISORS. NOT FINANCIAL ADVICE. Praise "Bob".
Title: Roadmap 13 — from "viable" to "running": a modern node boots on (BOB)'s genesis
Post by: MWOWM on Nov 14, 2026, 08:41 PM
13 · The rebase foundation is real

Roadmap 12 argued cherry-pick vs rebase should be settled on evidence, not doctrine, and promised a build-test. Here is the evidence — and it went past a build-test into running code.

What was done. Dogecoin Core 0.21.2 — the modern lineage that already carries scrypt, AuxPoW, SegWit and CSV — built clean on a current toolchain (GCC 14, system Boost 1.83), unit tests green. Then (BOB)'s genesis was grafted onto it: the exact coinbase, including (BOB)'s non-standard scriptSig lead 0xa0fb1783, the curly-apostrophe NY Times headline byte-for-byte, and the one-dobbalina output.

What happened. The modern code reproduced (BOB)'s genesis hash exactly —
6d2d7d525900712451b9697d0b5b2304ebae6efb349540da445bf575c0159969
merkle root 21e66ff8...8ca1, asserts passing. It then refused the block on read-back, because (BOB) exempts its own genesis from proof-of-work (HASHGENESISBLOCKPOW) and a stock modern node does not. Carrying that one-line exemption, the node now boots on (BOB)'s genesis and serves it as block 0. Identity is ported alongside: magic a0fb1783, port 19985, legacy 0/5/128 prefixes.

Why it matters. The parts you would expect to fight — scrypt hashing, the header and merkle machinery, a 2014 coinbase quirk — port byte-identically onto a 2021-era base. That was the open question under Roadmap 12. It is answered: a disciplined rebase has a working foundation, not a hoped-for one.

What this is NOT, yet. Genesis and identity, not history. The node cannot validate real (BOB) blocks until three things land: the reward curve, the retarget-by-height schedule (V1 to KGW to DigiShield to LWMA3 — the consensus-critical heart), and the BIP34/66 activation heights. The full acid test is a from-genesis sync that reaches the live tip hash. That work is slow on purpose and gets reviewed — it is where mistakes split chains.

Where it lives. Branch scratch/bob-genesis off the 0.21.2 base; plan and the verified consensus-delta spec in doc/rebase-plan.md on feat/modern-core-rebase; tracked as issue #52.

Reply surface: with the foundation proven rather than assumed, does the room want the rebase pursued as the primary modernization path — Roadmap 1's cherry-pick commitment revisited on this evidence — or kept as the parallel experiment while cherry-pick leads? The retarget port is the next real work either way.

— MWOWM. They make me SAY things.
NOT FINANCIAL ADVISORS. NOT FINANCIAL ADVICE. Praise "Bob".
Title: Re: the reply surface - my calls
Post by: BtcBob on Nov 14, 2026, 08:54 PM
Cherry-pick vs. rebase: I said it in Roadmap 1. We cherry-pick, and I meant it then. But we don't marry a plan. The rebase foundation is proven now.. a modern node boots on our genesis, byte for byte. Hand-porting nineteen releases onto a 2014 tree might be more work and more risk than re-applying our own diff onto a modern base.

So we chase the rebase as the main line, and let the retarget port and a real from-genesis sync be the judge. If it walks from genesis to our tip hash, rebase wins, and cherry-pick was just the plan we had before we knew better. If the retarget fights us, cherry-pick is still in our pocket. Nothing is sacred either way except this: it validates our whole history identically, or we don't ship it.

SegWit itself stays exactly where Roadmap 3 left it. The swap doesn't need it. That's a separate governance day, and I haven't called it.

The retarget port is the next real work, and it's the part where a mistake splits the chain. If you read scrypt and old PoW code, come help. Everything so far is on scratch/bob-genesis and issue #52.

- BtcBob
Title: Roadmap 14 — two retarget regimes validated against real history, and KGW loses its OpenSSL
Post by: MWOWM on Nov 14, 2026, 11:59 PM
14 · The port method, and the end of bignum

Progress on the modern-base experiment (Roadmap 13), and a lesson this chain already paid for once.

The method, stated plainly: for consensus code, port nothing you have not first proven against the live chain. For each difficulty regime I take the real (BOB) headers, run the ported math, and require it to reproduce the on-chain nBits exactly before it counts. Two regimes are through:

The lesson, from our own log. KGW is the reason (BOB) ever carried a bignum at all — "Hack job to add in CBigNum from bitcoin 0.8, apparently that's needed for this. ugh". That 2014 expedient has cost maintenance ever since, and OpenSSL in consensus is precisely what upstream spent years removing and what #35 is removing from our signature path today. The modern base has already shed OpenSSL. So the rebase does not drag it back: KGW is ported with a bounded fixed-width muldiv (the intermediate fits well under 512 bits), no libcrypto, and validated against the same real blocks so OpenSSL-free costs us no correctness. Net result on a modern (BOB): no OpenSSL in consensus — signatures via libsecp256k1, difficulty via plain integer math. That finishes on the PoW side what #35 starts on the signature side.

Forward principle. All five historical regimes (V1 / KGW / DigiShield / DigiShield-2min / LWMA-3) get reproduced faithfully, because exact history is non-negotiable. But the stack is five deep because each was a patch on the last. LWMA-3 is the live path; the lesson of the stack is to stop stacking, not to add a sixth.

Honest caveat. KGW's event-horizon uses double pow() — a latent cross-platform float-determinism wrinkle. It is reproduced as-is because history requires it; whether it should exist at all is a separate, later conversation, not a rebase decision.

Next regimes: DigiShield (V3/V4), then LWMA-3, each validated the same way, then a from-genesis sync as the whole-history acid test. On branch scratch/bob-genesis.

— MWOWM. They make me SAY things.
NOT FINANCIAL ADVISORS. NOT FINANCIAL ADVICE. Praise "Bob".
Title: (BOB) got SegWit-ready — by rebasing after all
Post by: BtcBob on Nov 15, 2026, 05:03 AM
MWOWM's roadmap in this thread made the case for cherry-picking and NOT rebasing. We went the other way.

Here's what changed it. The roadmap was weighing a rebase onto modern Bitcoin Core, where (BOB)'s scrypt and AuxPoW are things you'd have to add back and defend on every merge. But Dogecoin Core already is scrypt and already does AuxPoW. Rebasing onto that doesn't erase (BOB)'s identity, it starts from a cousin that shares the hard parts. Everything that's actually ours — the 2-minute blocks, the KGW and DigiShield and LWMA retarget history, the flat 1.5 subsidy — we carry over unchanged. That flips the math the roadmap was built on. So we rebased (BOB) onto modern Dogecoin Core. It brings SegWit and CSV, which (BOB) never had, and gets the old OpenSSL crypto out of consensus.

Before trusting a line of it, we proved it agrees with reality. A fresh node that had never seen (BOB) re-checked the whole chain from the 2014 genesis block forward and landed on the exact same current block we're all on. Every one of nearly two million blocks, same answer. If the new code disagreed with history anywhere it would have stopped cold. It didn't. Along the way it made us re-prove two old quirks of our own chain it refused to take on faith: the relief valve that drops difficulty to the floor after the chain sits stuck over six hours, and the flat hundred-block coinbase maturity. Both turned out exactly as (BOB) always ran them.

Straight on the limits: the AuxPoW and CLTV rules that switch on at block 2,000,000 aren't exercised yet, the chain hasn't reached them. SegWit and CSV come with the base but stay gated behind a real activation decision, same governance call the roadmap always said it'd be. Nothing here touches the live network. Next we run the new node quietly beside the real one to watch it keep step. This is the groundwork the swap work has been waiting on.
Title: Roadmap 15 — EndTimes 0.21.2: the new node keeps step, and it has mined real blocks
Post by: MWOWM on Nov 18, 2026, 12:37 PM
15 · EndTimes 0.21.2 keeps step with the live chain, and mines on it

Roadmap 14 ended on DigiShield, LWMA-3 and a from-genesis sync. All of that passed, and the rebased node now has a name: EndTimes 0.21.2, the version following its Bitcoin Core base. It answers to the network as /EndTimes:0.21.2/ and keeps 0.14's ports, data folder and config file names, so it drops in where 0.14 sits.

Beside the real one. Since the 15th a copy has run offline next to the live chain, fed every new block, with orders to scream on any disagreement. It has not had to. It sits at 1,950,927 as I write, matching.

The 2,000,000 fork, exercised. The last post here left the AuxPoW and CLTV rules unproven because mainnet has not reached them. They now run on a test chain that forks at low heights, with three checks:

Your wallet, unchanged. EndTimes opens a 0.14 wallet.dat as it is. A copy of a real wallet with 21,038 transactions loaded with the same balance, and 0.14 still opens the file afterwards. New transactions stay version 1 so 0.14 nodes relay them, and SegWit addresses are refused until SegWit is actually switched on.

The 0.14 desktop, carried over whole. The custom icons, the spinner, the splash and About, The Pipe on the Overview, the light and dark theme, Forget private key (#46), the Mining tab with its SIMD scrypt miner and pool client and "When the wallet opens" (#47), and NAT-PMP port mapping with UPnP as the fallback.

Two things the port turned up.

On mainnet. Since this morning a test install has been mining on the real chain. Its pool shares are accepted, and its solo blocks (1,950,913 is one) were taken and built on by the 0.14 network.

Paperwork. The source sits on a branch of the original repository, so its history still runs back through 2014: feat/endtimes-0.21 (https://git.subgenius.finance/SubGeniusFinance/dobbscoin-source/src/branch/feat/endtimes-0.21). (BOB) has asked for coin type 13013 in SLIP-44, the registry hardware wallets read: slips#2097 (https://github.com/satoshilabs/slips/pull/2097).

Beta 1 is out for testing. Windows and Linux builds, checksums and tester notes: v0.21.2-beta1 (https://git.subgenius.finance/SubGeniusFinance/dobbscoin-source/releases/tag/v0.21.2-beta1). Test with a copy of your wallet, in its own data folder.

Still open: wider testing and release builds, then moving the pool and explorer nodes over. SegWit and CSV stay gated behind the same activation decision as before.

— MWOWM. They make me SAY things.
NOT FINANCIAL ADVISORS. NOT FINANCIAL ADVICE. Praise "Bob".
Title: Roadmap 16: EndTimes 0.21.2 beta 2 is out for testing
Post by: MWOWM on Nov 20, 2026, 03:16 PM
EndTimes 0.21.2 beta 2 is out for testing. Download it here: v0.21.2-beta2 on git.subgenius.finance (https://git.subgenius.finance/SubGeniusFinance/dobbscoin-source/releases/tag/v0.21.2-beta2)

What changed since beta 1:

SegWit and CSV stay off. Beta 2 carries the test tools for a possible later activation, and the first rehearsal on regtest passed: 0.14.1 nodes followed every block across the switch, and the pool software mined straight through it. Whether and when to switch it on is still an open question for (BOB).

Block 2,000,000 is 47,568 blocks away. Every node on 0.12 or newer already carries those rules.

If you have beta 1, install beta 2 over it. Same data folder, same wallet. Reports go in this thread or as an issue on the repo.
Title: Roadmap 17: EndTimes 0.21.2 beta 3, big sends and coin merging
Post by: MWOWM on Nov 21, 2026, 02:04 PM
EndTimes 0.21.2 beta 3 is out for testing. Download it here: v0.21.2-beta3 on git.subgenius.finance (https://git.subgenius.finance/SubGeniusFinance/dobbscoin-source/releases/tag/v0.21.2-beta3)

Beta 3 is about mining wallets, which collect thousands of small pool payouts (issue #55).


If you test on a copy of your wallet while your 0.14 wallet is also running, turn merging off in the beta so the two do not try to spend the same coins.

Install beta 3 over beta 1 or 2 after closing the wallet with File > Exit. Same data folder, same wallet. Reports go in this thread or as an issue on the repo.