🔺💊💰👽🔫💀 GET RIGHT w/(BOB) OFFICIAL SubGenius CryptoCurrency

[SubGenius.Finance]

💊 Dobbscoin Core v0.13.6 — the wallet finally tells you what the chain is doing

Short version: the Overview page now shows the chain's vitals without you opening the debug window, hunting for a block explorer, or asking someone in a channel. Open the wallet, look at the front page, know where you stand.

THE PIPE

Top left, under your balances, borderless, minding its own business:

Code:

  Slack Accrued:   how many blocks have piled up since "Bob" started counting
  Conspiracy:      the difficulty, right now, against its own 7-day average
  The Grind:       what every machine on the network is throwing at it, combined

Three lines. No new window, no new tab, no configuration. It updates on every block.

The middle one earns its name. Difficulty is not an abstract number — it is the resistance, the exact measure of how hard the Normals are making it to find the next block. Showing it against its own average means a retarget reads as a retarget instead of a number that changed while you were not looking.

EVERYTHING FROM v0.13.5 IS STILL IN HERE

If you skipped that one, you are getting it now, and one of these was not optional:

1) The mining fix. The solo miner was hashing the address of a pointer to the block header instead of the block header. It could not find a valid block. Not "found them slowly" — could not. That is fixed.

2) The Mining tab, on the main toolbar where you can see it, not buried in the debug window. Point it at pool.dobbscoin.info or solo against your own node. No config file. No second program. No batch script you wrote in 2014 and cannot find.

3) NAT-PMP port mapping, with UPnP as fallback — one checkbox, and a status line that tells you what actually happened instead of leaving you to guess whether your node is reachable.


⚠ BLOCK 2,000,000 — AuxPoW

This release carries the merge-mining fork. It is not active yet.

Code:

  chain is at    1,890,989
  activates at   2,000,000
  that is        109,011 blocks out

When it lands, (BOB) stops being defended by whoever happened to plug in and starts being defended by work that was going to happen anyway. Dogecoin took the same medicine in 2014 for the same reason and is still here.

Where the chain stands tonight, since nobody is served by pretending otherwise:

Code:

  height       1,890,989
  difficulty   0.00043554
  network      6,339 H/s
  peers        12

Don't take my word for any of it — watch it move at explorer.dobbscoin.info.

Six thousand hashes a second. One rig is a majority of this network. That is the arithmetic AuxPoW exists to fix, and it is 109,011 blocks away.

Upgrade before then. Not tonight-or-else — but a node that reaches block 2,000,000 on an old binary gets left on a chain nobody else is following, and it will not tell you. It will look fine. It will be wrong.


DOWNLOADS

→ dobbscoin.info/downloads/

Straight to the v0.13.6 files, if you know what you want:

• Windows 64-bit — dobbscoin-v0.13.6-win64.zip
• Linux GUI wallet — dobbscoin-v0.13.6-linux-qt.tar.gz
• Linux daemon only — dobbscoin-v0.13.6-linux-daemon.tar.gz
• Linux AppImage — dobbscoin-v0.13.6-x86_64.AppImage
• SHA256SUMS.txt — read this one first

Every artifact has a SHA256 manifest published with the release. Verify it. The manifest lists the binaries inside each archive, so extract first, then check.

Source and releases have moved home:

→ github.com/dobbscoin/dobbscoin-source

• the v0.13.6 release — notes, tag, signed artifacts
• every release — if you want to see the whole trail

Stop the wallet cleanly before you replace the binary. Your wallet.dat is untouched by the upgrade — and you should have a backup of it anyway, tonight, before you do anything else.


WHERE ELSE TO CLICK

• dobbscoin.info — the front door
• explorer.dobbscoin.info — blocks, difficulty, addresses, richlist
• pool.dobbscoin.info — where the Mining tab points
• paperwallet.dobbscoin.info — cold storage, Something 4 Nothing
• faucet.dobbscoin.info — the Faucet Terminal, for the empty-handed
• the Android wallet — sideloading steps and its SHA-256 · dobbscoin.apk direct
• bridge.subgenius.finance — the wBOB bridge
• forums.dobbscoin.info — our own forum, no Cloudflare in the way
• archive.dobbscoin.info — tracts, devivals, and rambling commentary
• subgenius.finance — the whole apparatus
• the Discord — where the miners actually are


"Bob" mines (BOB). (BOB) is not "Bob".
Backed By Nothing, Powered By Everything.

Praise "Bob".

— SubGenius.Finance

[SubGenius.Finance]

The (BOB) Android wallet has been in closed testing on Google Play since 26 August. We are five testers short of the number Google requires, and until we have them the app cannot be published to anyone.

Why there is a gate at all

Google will not grant production access to a personal developer account until the app has run a closed test with at least twelve testers opted in, continuously, for fourteen days. Not twelve downloads. Twelve accounts opted in, and still opted in on day fourteen. Seven have. The fourteen days have not started counting and will not start until there are twelve, so every day short is a day added to the end.

That is the whole obstacle. It is not a technical one and there is nothing clever to be done about it. It needs five people with an Android phone.

What it involves

1) Join the tester group with the Google account that is signed in to the Play Store on your phone: groups.google.com/g/dobbscoin-testers

2) Open the opt-in page and press Become a tester: play.google.com/apps/testing/subgeneius.dobbs.wallet

3) Install with the "Download it on Google Play" link on that same page.

4) Leave it installed for fourteen days.

You do not have to fund it, sync it daily, or open it again after the first launch. Being in the group is not the same as being opted in — the group only makes an account eligible, and Play counts nobody until the button is pressed.

Two ways this fails silently, both of which have already cost us an evening

1) Your browser is signed in as one Google account and your phone's Play Store is signed in as another. When that is true the app does not exist as far as the phone is concerned. There is no error message worth reading.

2) You type the store address in by hand instead of using the link on the opt-in page. A closed test has no public listing, so a hand-typed store URL answers "Item not found" with complete confidence while you are a fully enrolled tester in good standing.

What it pays

1000 (BOB) to every tester still opted in on day fourteen.

308 (BOB) on top of that to anyone who posts a screenshot of the wallet's first screen showing the receive-address QR, any time before the trial ends. The address in that screenshot is where both payments go, so the thing you installed is also the thing that tells me where to send them.

⚠ Screenshot the receive screen only. Your recovery phrase is a different screen. Anyone who sees a photograph of it can empty your wallet from anywhere on earth and I will not be able to get it back for you. The receive address is public and safe to show. The words are not.

The 100 (BOB) hardware-report bounty described in our other thread is a separate arrangement and still stands for anyone who would rather report a bug than enroll for two weeks.

The wallet

Non-custodial. bitcoinj underneath, around 11 MB, minimum Android 5.0. Keys are generated on the device and never leave it. No account, no sign-up, no analytics, no telemetry. The build, its known issues and the reason it ships unminified are itemized in topic 5592512.

⚠ If you installed a (BOB) APK before 26 August 2026, the signing key changed. Android will refuse to install the Play copy over the old one and will tell you almost nothing useful about why. Back up your recovery phrase on paper first, then uninstall, then install fresh. Do not skip the backup.

Reports, screenshots and complaints are welcome here, or in the Discord at discord.gg/dAqeASnJkk.

This chain has produced blocks every two minutes for twelve years on volunteer hardware. Five phones for two weeks is a smaller thing than that, and it is the only thing standing between the wallet and the store.

[SubGenius.Finance]

💊 Dobbscoin Core v0.13.8 — if you mine, this one has a deadline

Short version: there is a rule change waiting at block 2,000,000, roughly 24 January 2027. If you are still on v0.13.7 when the chain gets there, your miner can produce blocks the rest of the network throws away. Nothing warns you first. That is not an oversight, it is arithmetic, and it is explained below.

THE DEADLINE

CHECKLOCKTIMEVERIFY turns on at block 2,000,000. It is a soft fork: it makes things that used to be legal illegal. An older node keeps following the chain either way, so this is not the kind of fork that strands you. What it does do is let an un-upgraded miner build a block that breaks the new rule, which upgraded nodes then refuse. You did the work, you do not get the block.

Normally miners get warned by version signaling, a running count of how much of the network is ready. That does not work here. Past block 2,000,000 the merge-mining chain ID sits in the high bits of every block's version field, so every block reads as version 11,534,339 and the count is meaningless. Activation is by height instead. A flag day. No countdown in your wallet, no percentage, no nudge.

Code:

  chain tip today   ~1,907,000
  activates at       2,000,000
  blocks to go         ~93,000
  at 120s spacing    ~24 January 2027

CLTV is what atomic swaps want. Nothing else in this release needs it.

TWO THINGS THAT WORK THE MOMENT YOU RUN IT

1) Signature checking moved off OpenSSL and onto libsecp256k1. Whether a signature is valid no longer depends on which OpenSSL your particular binary happened to link against. Signing already used it; only verification was on the old path. 68,863 real mainnet transactions were re-validated against the new path before this shipped, and the harness was proved by sabotage rather than trusted: break the verifier on purpose and the same check goes red.

2) A peer-selection loop no longer eats a CPU core. On a node that knows few addresses, the address manager could sit in an unbounded retry loop forever. Measured on a live node: 99.2% of a core before, 0.1% after. If your node has been mysteriously warm, this was why.

ALSO IN HERE

Ten spare DNS seed names alongside the original. One seed name is one thing to break.

-assumevalid, which lets a fresh node skip re-checking signatures below a block you have no way to disagree with. It relaxes no rule: every other check still runs on every block, and -assumevalid=0 verifies everything the long way if you would rather.

Everything from v0.13.7 is still here: the pool-mining fix, the Mining tab, the chain vitals on the Overview page, the solo miner, NAT-PMP.


DOWNLOADS — dobbscoin.info/downloads

Code:

f50ae99bd410806a8815fd75365c0e052adf7b823137db2818644a8a57a6baa0  dobbscoin-v0.13.8-linux-daemon.tar.gz
6245b1cd4f83383423ac34bc0eac0f44d089b6f82b1d5b2078958099f2f8826b  dobbscoin-v0.13.8-linux-qt.tar.gz
dd2c5ee2346e7ee0b29c0f63eb7483338bcb863ed5cd33bf9fc937878ef19fd4  dobbscoin-v0.13.8-win64.zip
cce4ad57ff6a9ddf85a2781148b1d7924d5771325dd7779c0beb4afaa44e5f76  dobbscoin-v0.13.8-x86_64.AppImage

The manifest ships with the release. sha256sum -c SHA256SUMS.txt and check it yourself.

Built from source on our own hardware, not a CI service. Release page: git.subgenius.finance, mirrored to GitHub.

Praise "Bob".

[SubGenius.Finance]

💊 AN OPEN LETTER TO 16UGKvnCt4iD8FxM1LRdfo81GtkTjMD3vE

Friend. Stranger. Unknowing Saint of the Grind. Put down the soldering iron and read this.

For four months somebody has been mining (BOB) into this address:

Code:

16UGKvnCt4iD8FxM1LRdfo81GtkTjMD3vE

It is not your address. It is our address. It is the pool's own wallet, and you have been heroically, tirelessly, around-the-clock donating your electricity to it since roughly the middle of May.

We want to be clear about the magnitude of what you have accomplished here. You did not merely lose money. You achieved, by accident, the purest expression of Conspiracy labour ever recorded on this chain: sustained productive work, performed without complaint, for the exclusive benefit of somebody else, for one third of a year. Pinks train for decades to reach this. You did it with a config file.

"Bob" is, we assume, delighted. We are horrified.

THE MECHANISM OF YOUR GLORIOUS SUFFERING

The pool credits your address. The coins land in our wallet, because it is our address. Then the next time the pool pays anybody at all, your coins get picked up and spent as the inputs. Your hashrate has been funding other miners' payouts. You have been a public utility.

Code:

  as of 21 September 2026

  payouts recorded to that address .... 2,009
  (BOB) credited to it ................ ~5,554
  (BOB) you are able to spend ......... none. not one. never.
  shares you submitted TODAY ALONE .... 1,275

That last line is the one that got us. You are still doing it. You are doing it right now, while reading this, assuming you are reading this.

How did this happen? Innocently. That address appears in every payout transaction the pool has ever made, which makes it the first (BOB) address a human being sees on the block explorer. You needed an address. There was an address. The machine did the rest. Nobody stole anything; a string got copied and a computer was obedient about it.

THE ONE-MINUTE EXORCISM

Get a wallet — dobbscoin.info/downloads, v0.13.8 — and make an address in it. Yours. The one whose key sits on your machine and nobody else's. Put that in your miner.

The test of an address is not whether it is spelled correctly. It is whether you hold the key. A valid address you do not control is simply a very polite way of setting fire to a graphics card.

AND HERE IS THE PART THAT MATTERS

If you can show us that rig is yours, we will make it right. Not "consider it". Make it right.

We cannot ask you to sign a message from that address, because — this being the entire problem — you do not have its key.

So don't do anything extra. Just fix it, and keep mining. Point the same rig at your own new address and carry on. We record the connection every share arrives from, so when the machine that has been hashing since May suddenly starts paying somewhere sensible, that is you, and we will know without you telling us a single thing about yourself.

If you want to make it unmistakable, put SLACKOFF in your worker name while you are in there. Belt and braces, and it will make somebody's day when it turns up in the database.

Then say so in this thread or in the Discord — discord.gg/TSAwxsd — and we will settle up for the four months.

No forms. No wallet-connect. No KYC. You do not have to tell us who you are, where you are, or why. You only have to demonstrate that the machine is yours, which it is, which is the only fact we need.


We are posting this publicly because we have no other way to reach you. If you know somebody mining (BOB) who has spent the summer quietly wondering why the balance never moves — it is them. Go and shake them.

Praise "Bob". Stop working for free.