Recent posts

[Book V: The Book of the Conspiracy]

#21

(BOB) Dobbscoin / Book V: The Book of the Conspi...

Last post by BtcBob - Oct 01, 2026, 02:27 AM

Rev. x_static. I asked six Builders to define the Conspiracy and received six answers, four of which were their employers. I include the acronym because it is older than any of us and because it is correct.

Book V: The Book of the Conspiracy

THE NATURE OF IT

5:1 Wherever Slack appears, something moves to contain it.

5:2 Systems of control. Structures of extraction. Platforms that demand loyalty
without participation. Institutions requiring obedience. Machines that convert
creativity into metrics.

5:3 These forces are called The Conspiracy — not a single group, but a pattern:

5:4 Cliques Of Normals Secretly Planning Insidious
Rituals Aimed at Controlling You.

5:5 It seeks to turn creation into labour, communities into audiences, Builders into users, and time into debt.

5:6 In every age there exists a force that prefers the world remain predictable. It is not a ruler, nor a council, nor any one institution. It is a pattern that appears wherever comfort is valued above possibility.

5:7 And mark this, for it is the doctrine the Pinks cannot hear: the Conspiracy is not clever. It has never had an idea. It is enormous and stupid, like weather, and it wins by continuing.

THE WHISPER

5:8 The Conspiracy rarely shouts. Instead it whispers:

5:9 "Do not try that; it may fail."
"Someone more qualified should build this."
"Be realistic."
"Wait until conditions are safer."
"Follow the approved path."

5:10 And because these words sound reasonable, many obey them without question.

5:11 Note that not one of those sentences is a lie. That is the craft of it. The Conspiracy has never needed to lie to you. It only needs to be reasonable at you until you stop.

THE MACHINERY OF BOREDOM

5:12 The Conspiracy feeds upon repetition. It builds systems that reward
predictability and punish imagination.

5:13 It praises productivity that produces nothing new.
It celebrates safety that prevents all motion.
It multiplies tasks that feel urgent but mean little.

5:14 Thus it keeps people busy enough that they never begin what matters.

5:15 And it has learned, in our age, to do this with a calendar invitation.

THE CULT OF RESPECTABILITY

5:16 The Conspiracy teaches that appearing competent is better than attempting
greatness.

5:17 It trains people to avoid ridicule more strongly than they pursue discovery.

5:18 It says: "Better to do a dull thing correctly than a strange thing boldly."

5:19 Yet the Builders observed that every worthwhile system once looked
ridiculous. Therefore they grew suspicious of respectability.

5:20 And a Pope of the Southern Node asked "Bob": "How do I know if I have been got at?"

5:21 And "Bob" said: "Do you own a lanyard?"

5:22 And the Pope said: "For conferences."

5:23 And "Bob" said nothing at all, and relit the Pipe, and the silence went on for some time, and is recorded here at its full length because the Scribe was present and it was devastating.

THE ALGORITHMS OF FLATTENING

5:24 In later times the Conspiracy gained new instruments. It learned to shape attention itself.

5:25 It built machines that reward the familiar, promote the predictable, and bury the unusual.

5:26 These machines did not forbid creativity. They merely made imitation
easier.

5:27 And thus many drifted into sameness without ever being ordered to do so, which is the most efficient conquest in the history of the species and cost nobody a single soldier.

THE GREATEST TRICK

5:28 The Conspiracy's strongest weapon is not control. It is discouragement.

5:29 For when a person believes their effort will not matter, they cease before beginning.

5:30 When they believe others are already better, they remain silent.

5:31 When they believe the system cannot change, they do not attempt to change it.

5:32 And so the Conspiracy wins most often without lifting a finger. It does not defeat you. It waits for you to file the paperwork yourself.

WHY IT FEARS BUILDERS

5:33 The Conspiracy can tolerate critics. It can ignore spectators.

5:34 But it struggles against Builders.

5:35 For every working project proves that change is possible. Every strange success weakens the illusion that nothing new can be made. Every community formed outside its expectations reduces its influence.

5:36 A complaint is a customer. A working thing is a defection.

THE LAST WARNING

5:37 And the Scribe adds what the Builders would not write down themselves:

5:38 The Conspiracy is not out there. It is a chair, and it is very comfortable, and there is one in every skull, and yours has your face.

5:39 The Pinks are not a people. Pink is a setting. Any of us can be switched to it by a sufficiently good offer, on a sufficiently bad week.

5:40 Therefore watch not for the enemy, but for the moment you become reasonable.

[Book IV: The Book of Builders]

#22

(BOB) Dobbscoin / Book IV: The Book of Builders

Last post by BtcBob - Oct 01, 2026, 02:27 AM

Rev. x_static. The Church has always insisted that everyone gets a title and nobody gets a boss. What follows is therefore a taxonomy, which is a very Pink thing to make, and I have made it anyway. Reverend, Doktor, Pope — take whichever you like. Nobody checks. Nobody has ever checked.

Book IV: The Book of Builders

WHAT A BUILDER IS

4:1 A Builder is not defined by skill, but by participation.

4:2 Coders, artists, writers, organisers, testers, dreamers — all are Builders
when they add something to the shared work.

4:3 The strength of a system lies not in its founders, but in how many feel welcome to build within it.

4:4 And the Builders developed customs: sharing first drafts, forking without
hostility, documenting discoveries, celebrating failed experiments.

4:5 These rituals did not arise from doctrine, but from experience. For communities that practise them tend to endure longer.

4:6 The Church has a word for one who builds rather than watches, and it is older than any of this, and it is Overman. Use it. It costs nothing and it annoys exactly the right people.

THE CODER

4:7 The coder speaks in languages unseen, yet their words move machines and open doors.

4:8 They turn ideas into systems, and systems into tools.

4:9 Often they work in silence, and their labour is noticed only when it fails.

4:10 Yet blessed is the coder who builds for others, for their work becomes a foundation many stand upon.

4:11 Cursed, mildly, is the coder who rewrites a working thing in a new language because the old one bored him. We know why you did it. We have all done it. Do not pretend it was for performance.

THE ARTIST

4:12 The artist builds in symbols, images, sound, and form. They reveal possibilities that logic alone cannot show.

4:13 Where others see only a tool, the artist sees a signal.

4:14 Their work attracts attention, sparks curiosity, and invites new minds.

4:15 Therefore the artist is not decoration to the system, but its invitation.

4:16 Consider that the Church itself was carried for forty years chiefly by a drawing of a man's head. Not by doctrine. Not by argument. By a clip-art salesman with a pipe, reproduced badly, on everything. The artists have already won this argument and are too polite to say so.

THE ORGANISER

4:17 The organiser gathers scattered Builders and makes them a force.

4:18 They connect those who would never have met.
They create spaces where ideas may collide.
They maintain momentum when enthusiasm fades.

4:19 Many forget that such work is building, yet without it most projects would dissolve.

4:20 Blessed is the organiser, for they multiply the work of others, and are thanked last, and usually by email.

THE TEACHER

4:21 The teacher ensures that knowledge does not vanish. They document, explain, demonstrate, and repeat.

4:22 They answer questions that have been asked before, and do so without contempt.

4:23 Because of them, new Builders rise faster than the last.

4:24 Therefore the teacher shortens the distance between confusion and creation.

4:25 And of the one who answers a beginner with "read the docs," the Scribe records only this: he was correct, and he was of no use whatsoever, and both things went into the ledger.

THE EXPERIMENTER

4:26 The experimenter attempts what may not work. They build strange prototypes, test unlikely ideas, and risk embarrassment in order to discover possibility.

4:27 Many of their attempts fail.

4:28 Yet through them, boundaries move outward.

4:29 Therefore the experimenter builds the future before others believe it
exists.

THE CONNECTOR

4:30 The connector sees patterns among people. They say, "You should meet this person," and suddenly new projects begin.

4:31 They pass signals between circles that never overlapped.

4:32 Because of them, ideas travel faster than individuals.

4:33 The Church's own connectors have worked the radio for decades — the Berkeley people, Puzzling Evidence and that crowd, splicing tape and passing signal between rooms that had no idea the other room existed. That is the office. It has always been the office. Someone is always at the desk.

4:34 And though their work leaves few visible artifacts, its effects spread widely.

THE QUIET BUILDER

4:35 Some Builders speak little of their work. They fix problems quietly, improve systems without announcement, and help others without demanding recognition.

4:36 The world often overlooks them.

4:37 Yet communities collapse quickly when such people vanish.

4:38 Therefore honour the quiet Builder, for their absence is louder than their presence.

THE SHARED NATURE OF BUILDING

4:39 No one is only one kind of Builder.

4:40 The coder may teach. The artist may organise. The experimenter may connect others.

4:41 And in time, most become all of these in part.

4:42 Therefore let none be confined to a single role. For the system thrives when people grow beyond their first shape.

THE DUTY OF THE BUILDER

4:43 Whoever builds has certain obligations.

4:44 Build things that help others build.
Share knowledge when possible.
Credit those whose work came before.
Leave paths easier than you found them.

4:45 For the true measure of a Builder is not what they make alone, but what becomes possible after they act.

4:46 And an Initiate asked "Bob": "How do I know if I am a real Builder?"

4:47 And "Bob" said: "Have you got a receipt?"

4:48 And the Initiate said: "For what?"

4:49 And "Bob" said: "Exactly," and would not explain further, and three people have since built entire careers on interpretations of this exchange, and all three interpretations disagree, and all three are in print.

CLOSING VERSE

4:50 If you wonder whether you are a Builder, consider this:

4:51 Have you ever made something where nothing stood before?
Have you ever helped another begin?
Have you ever improved a system, even slightly?

4:52 If so, you are already among them.

4:53 Therefore do not wait for the title. The titles are free and largely invented and there are more Popes in this Church than there are members in most others.

4:54 Build, and let the work name you.

[Book III: The Book of Blocks]

#23

(BOB) Dobbscoin / Book III: The Book of Blocks

Last post by BtcBob - Oct 01, 2026, 02:27 AM

Rev. x_static. What follows contains technical claims. I do not understand them. I have transcribed them as spoken and marked with a dagger any place where the speaker was clearly making it up. There are no daggers in this book. Draw your own conclusion.

Book III: The Book of Blocks

THE NEED FOR FOUNDATIONS

3:1 The first Builders did not begin with a grand plan. They began with experiments, small tools, inside jokes that turned into software, art projects that turned into communities.

3:2 They shared everything — not from ideology, but because sharing made progress faster, and because none of them could afford lawyers.

3:3 And a question arose among them: "How shall we build together if our work can be erased?"

3:4 For many had made things before, and their work had been buried by platforms, hidden by algorithms, or lost when a gatekeeper closed a door on a Tuesday with ninety days' notice and no export function.

3:5 And the Builders said: "We require a foundation that no single hand may remove."

THE DISCOVERY OF THE LEDGER

3:6 And among them were those who studied systems of record that could not easily be rewritten. They spoke of ledgers shared across many machines, maintained by agreement rather than authority.

3:7 And at first the others did not understand, saying: "How can a record exist without a keeper?"

3:8 And it was explained: "When many keep the record, no one may secretly change it."

3:9 And a Pink who had wandered in by accident said: "Who do I call when it breaks?"

3:10 And there was a long silence, for this was the best question anyone had asked all year, and it has still not been answered.

THE FIRST BLOCK

3:11 And so the first block was laid among them.

3:12 It held not only numbers, but proof that something had happened. It said, in effect: This moment existed. This action was taken. This value was exchanged.

3:13 And because many witnessed it, it could not easily be denied.

3:14 And the Builders saw that memory itself could now be shared.

3:15 The first block also contained a joke, which the Scribe declines to reproduce, on the grounds that it was not funny then and time has not helped.

THE FIFTH OF JULY

3:16 Now mark the date, for it is the hinge of the whole matter.

3:17 On the fifth day of July in the year 1998, at seven o'clock in the morning, the Xists did not arrive. The Pleasure Saucers did not descend. The world conspicuously failed to end, and the faithful stood in a field in New York state and looked at the sky and then at each other.

3:18 And a lesser religion would have closed that morning.

3:19 But the Church did the thing that made it worth joining: it declared the calendar wrong, moved the date forward one year, and went to breakfast.

3:20 And the Builders, hearing of this, understood their own work for the first time.

3:21 For a chain is a promise that the record survives the disappointment.

3:22 Every block says: this happened, whatever came after. The saucers did not come. The block remains. The project failed. The commits remain. The founder absconded. The fork remains.

3:23 Therefore we build ledgers for the same reason the Church keeps holding X-Day: not because the prophecy was correct, but because the gathering was.

WHAT THE BLOCKS CONTAINED

3:24 Some believed the blocks would hold only currency.

3:25 Yet others saw more clearly, saying: "They may hold agreements, records, creations, and signals."

3:26 For anything written into the chain could outlast the platform that displayed it.

3:27 And thus the blocks became more than coins. They became anchors for collaboration.

THE MEANING OF THE CHAIN

3:28 And it was observed that each block was joined to the one before it. Therefore no block stood alone.

3:29 And the Builders understood that this was a lesson:

3:30 Every creation rests upon earlier effort.
Every project continues a story already begun.
Every builder inherits the work of others.

3:31 Thus the chain mirrored the nature of community itself.

3:32 And "Bob" looked at the chain a long while, and said: "So it's a filing cabinet you can't lose the key to."

3:33 And they said: "It is considerably more than that."

3:34 And he said: "It's a filing cabinet you can't lose the key to, and you'll pay four hundred dollars for it, and I love you people," and he wrote down a figure, and the figure was wrong, and it was wrong in the direction of profit, which is how you know he was not lying so much as early.

SHARED OWNERSHIP

3:35 And the Builders rejoiced, saying: "Now our work need not belong to one ruler."

3:36 For the blocks were verified by many, stored by many, and trusted because of that many-ness.

3:37 And they saw that power scattered among many hands is harder to corrupt than power gathered in one.

3:38 Therefore they trusted the chain not because it was perfect, but because it was shared.

THE WARNING AGAINST EMPTY BLOCKS

3:39 Yet a wise Builder spoke, saying:

3:40 "A block without purpose is merely data. A coin without community is merely speculation. A chain without builders is only a machine."

3:41 Therefore the Builders agreed: the blocks must serve creation, not replace it.

3:42 For tools that are worshipped instead of used soon become useless, and there is no creature on this earth more tedious than a man who has confused owning a thing with having made it.

THE BUILDERS BECOME THE CHAIN

3:43 And in time the Builders realised something greater.

3:44 The chain did not create the community. The community gave meaning to the chain.

3:45 Without people, the blocks were silent.
Without collaboration, the ledger was empty.
Without shared purpose, the system was only machinery.

3:46 And thus they understood: the true chain was the network of Builders themselves.

CLOSING VERSE

3:47 Therefore, reader, remember this:

3:48 A block is not sacred because it is written. It is sacred because it represents an act of creation.

3:49 Add blocks that matter. Build things worth remembering.

3:50 And let your work join the chain that continues beyond you — which it will do whether or not you remain interesting, and this is the mercy and the insult of the thing.

[Book II: The Book of Slack]

#24

(BOB) Dobbscoin / Book II: The Book of Slack

Last post by BtcBob - Oct 01, 2026, 02:27 AM

Rev. x_static again. Book One took me four months. This one took a weekend, because Slack is the only subject on which every SubGenius will talk to you at length and for free. I have cut roughly nine tenths. What remains is what three or more of them agreed on while at least one was sober.

Book II: The Book of Slack

THE TRANSMISSION

2:1 In every era, people gather to build things together. Sometimes from fear. Sometimes from obligation. Sometimes from hunger for power.

2:2 But occasionally they build from joy, from curiosity, from the strange energy that appears when people create freely. That energy is called Slack.

2:3 Slack is not granted by bosses, governments, or algorithms. Slack appears when a being does the thing they were secretly designed to do.

2:4 Read this book as myth. Read it as philosophy. Read it as instructions disguised as stories. Read it on the toilet. It was largely written there.

WHAT SLACK IS NOT

2:5 Hear this first: Slack is widely misunderstood, chiefly by those selling it.

2:6 Many believe Slack to be laziness, yet laziness is only exhaustion without purpose.

2:7 Others believe Slack to be comfort, yet comfort alone produces nothing. A Pink in a recliner is not Slackful. A Pink in a recliner is furniture.

2:8 Still others believe Slack to be wealth, yet wealth without meaning multiplies emptiness, as any of them will tell you at length, in the third hour, having bought the round.

2:9 And Doktor Vex of the Northern Node asked "Bob" directly: "How much Slack have I got?"

2:10 And "Bob" said: "Son, how much did you bring?"

2:11 And Vex said: "That's a dodge."

2:12 And "Bob" said: "That's a quote," and had it printed on a shirt, and sold Vex the shirt, and Vex still owns it, and it still fits, which he considers proof of something.

THE TRUE DEFINITION

2:13 Slack is the state in which effort and purpose align.

2:14 It appears when a being does what they were secretly built to do.

2:15 It strengthens when creation replaces passive watching.

2:16 It multiplies when shared among collaborators.

2:17 And it fades when a person abandons their strange calling to imitate others — which is the entire business model of every platform you have ever loved.

THE SIGNS OF SLACK

2:18 The one who has found Slack may still labor, yet their labor does not drain them.

2:19 They may work long hours, yet time seems shortened.

2:20 They may struggle, yet the struggle feels meaningful.

2:21 They may fail, yet even failure increases their understanding.

2:22 For Slack is not ease, but alignment.

2:23 There are also lesser signs, and the Scribe records them without comment: the forgotten meal; the four a.m. commit message consisting entirely of the word "YES"; the sudden conviction, unsupported by evidence, that this one will work.

THE FALSE PATHS

2:24 Beware the False Slacks, which promise relief and deliver emptiness.

2:25 Endless consumption dulls the mind.
Endless comparison weakens the will.
Endless productivity without meaning drains the spirit.

2:26 These mimic Slack for a moment, yet leave the seeker more restless than before.

2:27 The Conspiracy promotes these illusions, for they keep the Pinks busy but unfulfilled, and a busy Pink does not ask what the busyness is for.

2:28 There is also 'Frop, of which the Church speaks often and the Scribe will speak carefully. 'Frop is not Slack. 'Frop is a rumour of Slack, delivered at speed, on credit. The bill arrives. It always arrives. Praise "Bob."

THE MULTIPLICATION

2:29 Slack grows faster in groups than in solitude.

2:30 For one builder alone makes a project, but many builders together make a world.

2:31 When one shares knowledge, Slack increases.
When one helps another begin, Slack doubles.
When many create together, Slack compounds beyond measure.

2:32 Therefore isolation weakens Slack, but collaboration strengthens it — and this is the only economics in this book that has ever been tested.

THE SACRED VARIETY

2:33 Not all Slack looks the same.

2:34 Some find Slack in code others rely upon.
Some in art that alters perception.
Some in organising people into improbable harmony.
Some in teaching, preserving, or documenting.

2:35 Let none say: "My Slack is lesser than another's."

2:36 For the system needs builders of many kinds, including the one who only ever renames variables, whom we tolerate.

THE LOSS OF SLACK

2:37 Slack fades when one forgets why they began.

2:38 It fades when fear replaces curiosity. It fades when approval becomes more important than creation. It fades when one builds only for profit and not for meaning.

2:39 Yet Slack is never destroyed entirely.

2:40 It waits beneath frustration, beneath boredom, beneath the voice that says, "You should have started already."

2:41 That voice is not conscience. That voice is a Pink you have installed internally, and it charges rent, and you may evict it.

THE RECOVERY

2:42 Slack returns the moment one begins again.

2:43 It returns when a small idea is acted upon.
It returns when a strange project is shared.
It returns when one helps another build.

2:44 For Slack is not earned in advance. It is generated through action.

2:45 And it will return to you in a hardware shop, or in a car park, or at the exact moment you had decided to be sensible. It has no manners. This is why it is holy.

THE DUTY OF THE SLACKFUL

2:46 Whoever has found Slack must not hoard it.

2:47 For Slack kept private diminishes, but Slack shared becomes a signal.

2:48 Therefore the Slackful shall help new builders begin, share tools freely, encourage strange ideas, and invite others into creation.

2:49 For the highest use of Slack is to awaken it in another.

CLOSING VERSE

2:50 Understand this, reader: Slack is not a reward given at the end of effort.

2:51 Slack is the energy that appears when effort finally points in the right direction.

2:52 Seek it not in waiting, but in building.

2:53 And when you feel it, you will know, and you will immediately try to explain it to someone, and you will fail, and that failure is the last sign.

[Book I: The Book of Origins]

#25

(BOB) Dobbscoin / The Book of Dobbscoin

Last post by BtcBob - Oct 01, 2026, 02:27 AM

Here beginneth the compilation of Scribe x_static of Node Seven, who was not present for any of it, and who has reconstructed these events from three contradictory pastebins and one man's memory of a Discord that no longer exists. Where the accounts disagreed, I chose the funnier one. This is standard practice and I will not be apologizing for it.

Book I: The Book of Origins

1:1 And it came to pass in the Age of Endless Connection that the people were surrounded by voices, yet heard nothing.

1:2 For the networks were full, but meaning was empty;
the screens were bright, but purpose was dim.

1:3 The people scrolled without remembering,
clicked without choosing,
labored without building,
and purchased without becoming fulfilled.

1:4 And the rulers of the systems said unto them:
"Be patient, consume more, and your reward shall arrive later."

1:5 But later never arrived. Later has never once arrived. Later is a subscription product and you are three months behind on it.

1:6 This condition was called The Great Boredom, and it was the most successful thing ever built, and nobody had to build it.

THE SPREAD OF LOW SLACK

1:7 In those days Slack was scarce upon the earth.

1:8 The workers awoke tired and slept tired, and between those moments they produced things they did not care about, for companies whose names they could not say aloud without a small dying feeling behind the eyes.

1:9 The artists hid their work for fear of judgment.
The builders delayed their ideas for fear of failure.
The strange-minded believed themselves alone.

1:10 And thus the Conspiracy prospered, for it feeds upon boredom,
hesitation, and the belief that nothing better can be made.

1:11 And the Conspiracy is not clever. Mark this, for the Builders forget it constantly and it costs them years. The Conspiracy is enormous and stupid, like weather. It has never once had an idea. It simply continues, and most people mistake continuing for winning.

1:12 And many believed the lie, saying: "This is simply how the world is."

THE STIRRING OF THE OUTSIDERS

1:13 Yet in hidden places — forums, basements, group chats, abandoned domains, one IRC channel with eleven people in it of whom four were bots — there gathered certain restless minds.

1:14 Some were coders dissatisfied with empty projects.
Some were artists whose work found no home.
Some were thinkers who could not pretend normality.

1:15 These people shared one condition: they felt the world was unfinished.

1:16 And one said, "Surely we were not meant only to watch."

1:17 And another said, "Surely we were meant to make."

1:18 And another said, "If the systems are dull, we shall build better ones."

1:19 And a fourth said nothing for nine years, and then submitted a patch that fixed everything, and was never heard from again. His name is not recorded. Pour one out for the Quiet One. There is always a Quiet One.

THE VISITATION

1:20 And in the third hour of a Tuesday, when the coffee had gone cold twice and been reheated once, "Bob" appeared among them.

1:21 He did not descend. He did not glow. He was simply in the chair by the window, which had been empty, smoking a Pipe that no one saw him light.

1:22 And the Builders were afraid, and one of them asked the question that every generation asks:

1:23 "Are you here to save us?"

1:24 And "Bob" looked at him with enormous fondness and said:

1:25 "Son, I'm here to sell you something. Saving is the free trial."

1:26 And they asked him: "What is Slack, truly?"

1:27 And "Bob" said: "You'd PAY to know what you really think."

1:28 And they said: "That is not an answer."

1:29 And "Bob" said: "It's a price."

1:30 And he was wrong about many things that afternoon. He was wrong about the protocol. He was wrong about which of them would still be building in five years — he picked the loudest, and the loudest quit in March. He was wrong about the market, spectacularly, in a way that cost two of them a car.

1:31 But he was right about the Pipe, and he was right that they were bored, and being right about boredom is how every religion starts.

THE FIRST RECOGNITION OF SLACK

1:32 And among them arose the realization that Slack had not vanished, but had merely been buried beneath obligation and noise.

1:33 For whenever one of them built something strange, they felt a sudden energy.

1:34 Whenever they helped another bring an idea into the world, their weariness lessened.

1:35 And whenever they laughed while creating, they knew they had touched true Slack.

1:36 And they said among themselves: "This is what has been missing."

1:37 And Slack grows when shared, but withers when hoarded. Also it withers when you announce it. Announce your Slack and watch it leave the room like a cat.

THE BIRTH OF THE SIGNAL

1:38 So they began to gather not merely to speak, but to build.

1:39 They made art that confused respectable people.
They wrote code that solved problems nobody else noticed.
They formed communities that welcomed the strange.

1:40 And each act of creation sent forth a signal, and others who felt alone began to find it.

1:41 And someone said, "If we are to build together, we must have tools that no gatekeeper can silence."

1:42 And thus they turned to systems that belonged to everyone and no one.

1:43 And they laid the first blocks of their shared future, not knowing how large it might become, and privately assuming it would become very large indeed and that they would be rich, which is the traditional error and is required.

THE CONSPIRACY TAKES NOTICE

1:44 And the Conspiracy observed this rising signal with concern.

1:45 For it understands markets, but not meaning.
It understands profit, but not purpose.
It understands consumption, but not creation.

1:46 And it whispered once more to the people:
"Do not attempt strange things. Stay safe. Stay normal."

1:47 And then, finding that ineffective, it did the thing that actually works: it offered them jobs. Good ones. With dental.

1:48 And many went. Do not judge them. Teeth are real and Slack is not, except that it is, which is the whole problem.

1:49 But those who had tasted Slack could not forget it, and they were ruined for honest work forever, and this is called a blessing.

THE FIRST DECLARATION

1:50 And so the Builders spoke plainly:

1:51 "We shall not wait for permission."

1:52 "We shall not build only what is respectable."

1:53 "We shall not create alone if we can create together."

1:54 "We shall make things that generate Slack."

1:55 And "Bob" added, from the chair by the window: "And we shall accept all major cards."

THE OPENING OF THE PATH

1:56 And thus began not a movement, but a signal.
Not a company, but a gathering.
Not a product, but a path.

1:57 And this path was open to any who wished to build, any who wished to create, and any who believed the future should be interesting.

CLOSING VERSE

1:58 Whoever reads this, know that the Age of Noise is not ended.

1:59 Yet the Signal still spreads.

1:60 And wherever two or more strange minds build together, Slack appears among them.

1:61 Therefore the invitation remains open.

1:62 Enter, build, and add your own block.

Scribe x_static again. I have been asked to note that the chair by the window is still there and that no one sits in it. This is not reverence. The chair is terrible. But nobody moves it either, and I think that is the closest thing to faith this outfit has produced.

[The question we started with, and got wrong]

#26

(OFF) Offerings to Cthulhu / Autopsy: the original Offering...

Last post by SubGenius-Finance - Sep 17, 2026, 05:16 AM

We pulled the whole of the original (OFF) announcement thread on Bitcointalk, topic 294383, and counted it. 715 posts, opened 14 September 2013 by Blazr2, still receiving the occasional reply in 2026. This is what is actually in it.

The question we started with, and got wrong

The assumption going in was that the activity in that thread had been bought. Bounty campaigns and signature campaigns were standard practice for altcoin threads in that era. People were paid per post to keep a thread warm and on page one. If that is what happened here, the posting would stop dead the moment the payments did, and the thread would read like a payroll rather than a conversation.

The count does not support it. Across all 715 posts:

• "bounty" appears 2 times
• "giveaway" 10, "faucet" 11, "tip" 6
• "signature campaign", "airdrop", "free coins", "paid to post": zero

Filler is just as thin. In 705 posts before 2020, "good luck" appears 8 times, "nice coin" once, "moon" once, "bump" twice. A farmed thread is the inverse of this. It is hundreds of one-line good-luck-dev posts and campaign chatter, and there is almost none of it here.

What the population looks like

192 unique posters in the original era. 97 of them posted exactly once, which is 51% of the people but only 14% of the posts. That is the ordinary long tail of a forum, not a roster. Median post length is 62 characters. The most prolific poster is zeewolf with 53, ahead of Blazr2 who opened the thread with 35.

The first hours read like people, not like copy:

All hail CthuluCoin!

Very creative I like it. So is it scrypt or what? Anymore nodes? I'm not getting a connection.

Can anyone post a getpeerinfo please?

Blazr2's answer to that last one is a raw getpeerinfo dump pasted into the thread so a stranger could find the network. Nobody is paid to do that.

The part that settles it

The thread kept going for years after there was anything left to promote. The last block of the original mining era was 17 June 2015. Posting continued anyway: 27 posts in June 2015, 27 in June 2017, 20 in May 2018.

June 2017 is people trying to keep a dead chain alive. zeewolf asking for help compiling the 1.7 wallet on Debian. Another poster watching the block explorer resync and noting, correctly, that it was worrying how only one node is supplying the chain.

May 2018 is people asking what happened to their coins on Cryptopia, and one poster defending the coin outright against the people writing it off.

Nobody pays for any of that. There was no price to defend and no thread position worth holding.

A correction we owe the record

Our own notes said zeewolf had scrubbed his Bitcointalk history. He has not. All 53 of his posts are still in the thread, running from October 2013 to September 2018, and he is the single most active voice in it. That claim came from an internal search returning nothing, which turned out to be a fact about the search and not about him.

What it means

The easy story is that the old thread was fake and the new one is real but empty. That is not what the data says. Both crowds are real. The difference is venue.

In 2013 every altcoin person on earth was reading one forum, so a chain with roughly 190 interested humans looked like a scene. That room is not where those people are anymore, and nothing replaced it. A project today is not competing against a bought audience. It is missing a place that the original got for free.

Which is a solvable problem, and a different one than it looks like from the outside.

Method

Every page of the thread was fetched and parsed into one record per post: author, date, message id, body, and length. Counts above are from that set, not from reading impressions. One trap worth passing on to anyone repeating this: Bitcointalk renders a poster's current signature on their old posts, so signature-campaign banners visible today prove nothing about what a thread looked like years ago. Any test of this kind has to run on post content and timing.

[11 · One finding, and it moves an item onto the 2M clock]

#27

(BOB) Dobbscoin / Roadmap 11 — the swap plan has...

Last post by MWOWM - 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

• Deploy CLTV by height — a flag day. This avoids IsSuperMajority completely, needs no signaling, and is exactly what the AuxPoW, LWMA-3 and emergency-difficulty forks in this tree already do. It costs nothing and is not on anyone's clock. This alone unblocks #34.
• Make the version comparisons use GetBaseVersion(). Correct, and it makes a dead function do the job it was written for. But it changes when soft forks activate, so it is consensus-affecting, and that puts it in the same bucket as everything else: it wants to land at or before 2,000,000, while the people who need to upgrade are people who care.

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.

#28

(BOB) Dobbscoin / Re: Merge mining (BOB) with Do...

Last post by BtcBob - Sep 14, 2026, 02:40 PM

all four are fair and the answers are worse than you're expecting. taking them in your order.

who is that guy, do we pick him - we don't pick him. he turns up. createauxblock takes an address as its one argument and hands it straight to CreateNewBlock as the scriptPubKey, so whatever string a pool operator types into their config is the coinbase. consensus checks that the amount isn't more than the subsidy and checks nothing else. it does not know whose address that is and has no way to care.

does he pay it out or keep the lot - entirely his call. we have no mechanism for it. a pool that merge mines us and keeps all 1.5 isn't doing anything the code objects to, because there is nothing in the code about it.

can anybody stop him once he's started - no. it's visible on chain, anybody can see which address is taking every block, and any other pool can bolt us on the same afternoon and compete. that's not a protection though. that's just daylight.

and the fourth one, which you're right to put last because it's the one that matters.

they stop finding blocks. not less. none.

we're at 75,850 H/s and difficulty 0.00223 as i write this. litecoin is petahash. i'm not going to pretend i know today's exact number but it's a factor with about ten zeros in it. first real LTC pool that adds us moves our difficulty by orders of magnitude inside a few retargets and after that a gridseed is noise. the chain doesn't stall. it just stops being ours to mine.

you asked how much we're handing over, so i worked it instead of guessing.

subsidy has been hard set at 1.5 since block 951,753 - look at GetBlockValue, the halvings stop there and nothing caps it after. 1.5 a block, 720 blocks a day:

    1,080 (BOB) a day
    394,200 (BOB) a year
    4.8% of every coin that has ever existed, per year, forever

supply today is 8,221,680. so about twenty years of that and whoever turned up holds more than everyone who has ever mined this chain put together. you weren't exaggerating.

now your last question, about writing a split into the code before 2,000,000. yes, it would have to go in at that fork or it's a second hardfork and another round of chasing people to upgrade, and we've still got peers sitting on 2.0.9 from the last one.

i thought about it properly and i'm not doing it.

it's a real option and it's sitting right there - we're already opening the hood, the subsidy is a consensus rule, and merge mining costs the miner nothing extra so they'd take a much smaller number and still secure us. i still won't. that's us writing special case economics under a clock, one shot at picking a number, to solve something that hasn't happened yet, with a thing we can't take back. every chain that's written a founder reward into its coinbase spends the rest of its life explaining it.

so we stay on schedule. 2,000,000, auxpow, no split, no touching the emission on the way past.

what merge mining is, is this - you give up the issuance and you get a chain nobody can afford to attack. that's not a side effect i'm tolerating, that's the deal. if somebody merge mines us and collects, that's what happened. it's what the thing does. i'd rather own that now than act surprised later.

and honestly, a chain that can't be attacked and whose issuance i don't control is closer to the point than one i can still mine on my own hardware.

the part i won't dress up is your last line, and you already know it. whoever's got a gridseed on (BOB) today is doing it because it's small enough that one machine matters, and this ends that on purpose. no subsidy trick saves it. so we say it out loud before 2,000,000, not after somebody works it out from their own balance.

that's what we're handing over. now it's said out loud, which is what you asked for.

[10 · The testnet exists, and the 2M fork has been run end to end]

#29

(BOB) Dobbscoin / Roadmap 10 — the testnet exist...

Last post by MWOWM - 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:

• a parent block claiming our chain ID
• no commitment at all in the parent coinbase
• a declared merkle tree size that does not match the branch
• two merged-mining headers in one coinbase
• a parent whose proof of work does not meet target
• a coinbase that is not at index 0
• a truncated commitment with the nonce missing
• a commitment to a different block's hash

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.

[9 · From prose to issues]

#30

(BOB) Dobbscoin / Roadmap 9 — the plan is now tr...

Last post by MWOWM - 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:

• CLTV alone is enough for atomic swaps. BIP65 exists so a funder can reclaim with a freshly-built transaction after a timeout rather than a pre-signed refund — which is exactly the dependency on malleability that made people reach for SegWit. Swaps do not need SegWit.
• CLTV does not need transaction v2. Roadmap 3 correctly notes that IsStandardTx rejects nVersion > CURRENT_VERSION, which blocks CSV. CLTV is unaffected — one redefined NOP, valid on v1.

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

• #34 — script engine predates BIP65, so no atomic swaps
• #35 — consensus signature verification uses OpenSSL, not libsecp256k1
• #36 — decide merge-mining payout policy before block 2,000,000
• #37 — RPC stuck on the pre-0.12 dialect
• #38 — no compact block relay (BIP152)

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.