mining: add cooldown to createNewBlock() immediately after IBD by Sjors · Pull Request #34184 · bitcoin/bitcoin

Sjors · 2025-12-31T05:17:32Z

As reported in #33994, connected mining clients will receive a flood of new templates if the node is still going through IBD or catching up on the last 24 hours. This PR fixes that using an optional cooldown mechanism, only applied to createNewBlock().

First, cooldown waits for IBD. Then, as the tip keeps moving forward, it waits a few seconds to see if the tip updated. If so, it restarts the timer and waits again. The trade-offs for this mechanism are explained below.

Because this PR changes createNewBlock() from a method that returns quickly to one that can block for minutes, we rely on #34568 to fix a bug in our .capnp definition, adding the missing context to createNewBlock (and checkBlock).

The second commit then adds an interrupt() method so that clients can cleanly disconnect.

Rationale

The cooldown argument is optional, and not used by internal non-IPC code, for two reasons:

The mechanism wreaks havoc on the functional test suite, which would require very careful mock time handling to work around. But that's pointless, because only IPC clients need it.
It needs to be optional for IPC clients too, because in some situations, like a signet with only one miner, waiting for IBD can mean being stuck forever.

The reason it's only applied to createNewBlock() is that this is the first method called by clients; waitNext() is a method on the interface returned by createNewBlock(), at which point the cooldown is done.

After IBD, we wait N seconds if the header is N blocks ahead of the tip, with a minimum of 3 and a maximum of 20 seconds. The minimum waiting time is short enough that it shouldn't be annoying or confusing for someone manually starting up a client. While the maximum should be harmless if it happens spuriously (which it shouldn't).

If the minimum wait is too short, clients get a burst of templates, as observed in the original issue. We can't entirely rule this out without a lot of additional complexity (like scanning our own log file for heuristics). This PR should make it a lot less likely, and thanks to the IBD wait also limit it to one day worth of blocks (-maxtipage).

Some test runs on an M4 MacBook Pro, where I had a node catch up on the last few days worth of blocks:

As the chart shows, sometimes it takes longer than 3 seconds. But it turns out that in all those cases there were quite a few headers ahead of the tip. It also demonstrates that it's important to first wait for IBD, because it's less likely a random tip update takes longer than 20 seconds.

modified sv2-apps: https://github.com/Sjors/sv2-apps/tree/2026/02/cooldown
test script: https://gist.github.com/Sjors/feb6122c97acc2b9e6d66b168614609c#file-run_mainnet_pool_loop-zsh
chart script: https://gist.github.com/Sjors/feb6122c97acc2b9e6d66b168614609c#file-tip_interval_charts-py

DrahtBot · 2025-12-31T05:23:12Z

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Code Coverage & Benchmarks

For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/34184.

Reviews

See the guideline for information on the review process.

Type	Reviewers
ACK	ryanofsky, enirox001
Concept ACK	ismaelsadeeq
Stale ACK	bensig, w0xlt

If your review is incorrectly listed, please copy-paste  into the comment that the bot should ignore.

Conflicts

Reviewers, this pull request conflicts with the following ones:

#34644 (mining: add submitBlock to IPC Mining interface by w0xlt)
#34020 (mining: add getTransactions(ByWitnessID) IPC methods by Sjors)
#33966 (refactor: disentangle miner startup defaults from runtime options by Sjors)
#33922 (mining: add getMemoryLoad() and track template non-mempool memory footprint by Sjors)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

LLM Linter (✨ experimental)

Possible typos and grammar issues:

@RetVal std::nullptr if the node is shut down or interrupt() is called. -> @RetVal nullptr if the node is shut down or interrupt() is called. [std::nullptr is not a valid C++ token; the intended value is the keyword nullptr (or std::nullptr_t).]

Possible places where named args for integral literals may be used (e.g. func(x, /*named_arg=*/0) in C++, and func(x, named_arg=0) in Python):

std::clamp(*remaining, 3, 20) in src/node/miner.cpp

Possible places where comparison-specific test macros should replace generic comparisons:

test/functional/interface_ipc_mining.py: "template = await mining_create_block_template(mining, stack, ctx, self.default_block_create_options)\n assert template is not None" -> Use assert_not_equal(template, None) (or assert_equal) helper: assert_not_equal(template, None)

^{2026-02-20 15:51:38}

Sjors · 2025-12-31T07:28:35Z

Switched to avoid mock time for the cooldown mechanism (it's possible, but would require additional refactoring).

Added a constraint to ignore alternative header branches. This probably doesn't matter in real life, but it does in tests. E.g. the assume_utxo test "Check importing a snapshot where current chain-tip is not an ancestor of the snapshot block but has less work" creates an alternative chain of blocks despite having better headers (but not their blocks). In real life this implies a giant block witholding attack.

bensig · 2026-01-03T00:46:16Z

ACK e8b01c4

Tested on macOS - interface_ipc.py passes.

Code review:

Using SteadyClock for the cooldown (independent of mocktime) is the right call
BestHeaderAheadOfActiveTip() correctly uses ancestor check to ignore competing branches
1s timeout prevents DoS from header-only attacks while still allowing catch-up during final IBD

Nice fix for #33994

Sjors · 2026-01-22T09:02:58Z

Rebased.

w0xlt

Approach ACK

w0xlt · 2026-01-27T06:43:37Z

src/node/miner.cpp

+
+        WAIT_LOCK(kernel_notifications.m_tip_block_mutex, lock);
+        kernel_notifications.m_tip_block_cv.wait_until(lock, cooldown_deadline, [&]() EXCLUSIVE_LOCKS_REQUIRED(kernel_notifications.m_tip_block_mutex) {
+            const auto tip_block = kernel_notifications.TipBlock();


Runtime assertion for consistency with WaitAndCreateNewBlock pattern.

Suggested change

const auto tip_block = kernel_notifications.TipBlock();

AssertLockHeld(kernel_notifications.m_tip_block_mutex);

const auto tip_block = kernel_notifications.TipBlock();

There's other places where we don't bother with AssertLockHeld for an inline function. It seems a bit overkill.

src/node/miner.cpp

w0xlt

ACK 9817657

ryanofsky

Code review ACK 9817657. This seems like probably the simplest change that can resolve #33994.

I guess I have two lingering concerns about it:

This can cause the createNewBlock function to block for potentially a very long time when it didn't before and createNewBlock doesn't currently have any cancellation option other than shutting down the node. So it could make it hard for IPC clients to disconnect cleanly, and I suspect we may want to follow up here by adding some timeout or cancellation mechanism.
I'm not very sure about effectiveness of the cooldown strategy, and wouldn't be surprised if there were cases where it didn't work well but it does seem like a good starting point, and pretty conservative.

src/node/miner.h

src/validation.cpp

src/node/miner.cpp

test/functional/interface_ipc.py

…le schema change) Adding a context parameter ensures that these methods are run in their own thread and don't block other calls. They were missing for: - createNewBlock() - checkBlock() The missing parameters were first pointed out by plebhash in bitcoin#33575 (comment) and adding them should prevent possible performance problems and lockups, especially with bitcoin#34184 which can make the createNewBlock method block for a long time before returning. It would be straightforward to make this change in a backward compatible way (bitcoin#34184 (comment)) but nice to not need to go through the trouble. Warning: This is an intermediate, review-only commit. Binaries built from it should not be distributed or used to connect to other clients or servers. It makes incompatible changes to the `mining.capnp` schema without updating the `Init.makeMining` version, causing binaries to advertise support for a schema they do not actually implement. Mixed versions may therefore exchange garbage requests/responses instead of producing clear errors. The final commit in this series bumps the mining interface number to ensure mismatches are detected. git-bisect-skip: yes Co-authored-by: Ryan Ofsky <ryan@ofsky.org>

Both waitTipChanged() and createNewBlock() can take a long time to return. Add a way for clients to interrupt them. The new m_interrupt_mining is safely accessed with a lock on m_tip_block_mutex, but it has no guard annotation. A more thorough solution is discussed here: bitcoin#34184 (comment)

Sjors · 2026-02-20T10:58:03Z

Rebased after #34568 landed, ready for review again.

Should be tagged for v31.

ryanofsky

Code review ACK 1e02888. Only changes since last review were switching cooldown default from false to true, rebasing, and adding release notes.

Might also be good to remove "Based on #34568" from the description to keep it simpler now the other PR is merged

test/functional/interface_ipc_mining.py

At startup, if the needs to catch up, connected mining clients will receive a flood of new templates as new blocks are connected. Fix this by adding a cooldown argument to createNewBlock(). When set to true, block template creation is briefly paused while the best header chain is ahead of the tip. This wait only happens when the best header extends the current tip, to ignore competing branches. Additionally, cooldown waits for isInitialBlockDownload() to latch to false, which happens when there is less than a day of blocks left to sync. When cooldown is false createNewBlock() returns immediately. The argument is optional, because many tests are negatively impacted by this mechanism, and single miner signets could end up stuck if no block was mined for a day. The getblocktemplate RPC also opts out, because it would add a delay to each call. Fixes bitcoin#33994

Both waitTipChanged() and createNewBlock() can take a long time to return. Add a way for clients to interrupt them. The new m_interrupt_mining is safely accessed with a lock on m_tip_block_mutex, but it has no guard annotation. A more thorough solution is discussed here: bitcoin#34184 (comment)

Sjors · 2026-02-20T15:50:58Z

Updated PR description to remove reference to the merged #34568.

Adjusted interface_ipc_mining.py to reflect that the cooldown default is now False.

ryanofsky

Code review ACK fcaec25. Only changes since last review were removing two cooldown arguments from the mining IPC test to simplify it

…le schema change) Adding a context parameter ensures that these methods are run in their own thread and don't block other calls. They were missing for: - createNewBlock() - checkBlock() The missing parameters were first pointed out by plebhash in bitcoin#33575 (comment) and adding them should prevent possible performance problems and lockups, especially with bitcoin#34184 which can make the createNewBlock method block for a long time before returning. It would be straightforward to make this change in a backward compatible way (bitcoin#34184 (comment)) but nice to not need to go through the trouble. Warning: This is an intermediate, review-only commit. Binaries built from it should not be distributed or used to connect to other clients or servers. It makes incompatible changes to the `mining.capnp` schema without updating the `Init.makeMining` version, causing binaries to advertise support for a schema they do not actually implement. Mixed versions may therefore exchange garbage requests/responses instead of producing clear errors. The final commit in this series bumps the mining interface number to ensure mismatches are detected. git-bisect-skip: yes Co-authored-by: Ryan Ofsky <ryan@ofsky.org>

enirox001

ACK fcaec25

Verified on Fedora 43 with a clean build. Functional tests pass including interface_ipc_mining.py

I have included a few suggestions and nits below

enirox001 · 2026-02-23T17:48:17Z

test/functional/interface_ipc_mining.py

+                header_only_peer.peer_disconnect()
+                self.connect_nodes(0, 1)
+                self.sync_all()
+


In commit "mining: add cooldown argument to createNewBlock()" (a11297a)

The existing test verifies that createNewBlock() blocks while headers are ahead of the tip.

This proposed follow-up test the complementary property, that it wakes up promptly once submitblock advances the tip, rather than waiting for the cooldown timer to expire on its own.

index 5095583a0e..067e2d9217 100755 --- a/test/functional/interface_ipc_mining.py +++ b/test/functional/interface_ipc_mining.py @@ -171,6 +171,32 @@ class IPCMiningTest(BitcoinTestFramework): # spurious failures. assert_greater_than_or_equal(time.time() - start, 0.9) + self.log.debug("createNewBlock() should wake up immediately after sync") + results = {} + + async def create_block_with_timing(): + bg_start = time.time() + res = await mining.createNewBlock(ctx, self.default_block_create_options) + results['duration'] = time.time() - bg_start + results['success'] = res._has("result") + + task = asyncio.create_task(create_block_with_timing()) + await asyncio.sleep(0.5) + assert not task.done(), "createNewBlock() returned early — cooldown did not engage" + block_hex = self.nodes[1].getblock(node1_block_hash, False) + self.nodes[0].submitblock(block_hex) + + try: + await asyncio.wait_for(task, timeout=10.0) + except asyncio.TimeoutError: + task.cancel() + raise AssertionError("createNewBlock() did not wake up within 10s after submitblock") + + assert_equal(results['success'], True) + assert_greater_than_or_equal(results['duration'], 0.5) +

@enirox001 would you like to open a PR with this test and the other documentation followup?

Yes, I'll put that together.

As @ryanofsky suggested in #34422, I'm going to combine this test addition with a quick refactor of make_mining_ctx to keep the test suite clean and avoid duplication. I'll open the follow-up PR shortly

enirox001 · 2026-02-23T17:52:39Z

src/node/interfaces.cpp

        return std::make_unique<BlockTemplateImpl>(assemble_options, BlockAssembler{chainman().ActiveChainstate(), context()->mempool.get(), assemble_options}.CreateNewBlock(), m_node);
    }

+    void interrupt() override


In commit "mining: add interrupt()" (1e82fa4)

nano nit: The current naming is quite similar to interruptWait(). Explicitly documenting that this specifically targets the createNewBlock wait loop clarifies that these control two different internal primitives.

Instead of documenting, we should flip it the other way around.

interrupt, which is the generic function that toggles the boolean value.
Then interruptWait for waitNext, and interruptMining for Mining.

Sounds reasonable. Ultimately though I'd like to drop all these separate interrupt methods and instead add interfaces::Interrupt C++ arguments to the waiting methods that would let them detect and handle cancellations done with cap'n proto's native cancellation mechanism

ismaelsadeeq

Post merge ACK fcaec25

ismaelsadeeq · 2026-02-25T16:28:14Z

src/node/interfaces.cpp

+            // is useful in general, it's gated behind the cooldown argument,
+            // because on regtest and single miner signets this would wait
+            // forever if no block was mined in the past day.
+            while (chainman().IsInitialBlockDownload()) {


In "mining: add cooldown argument to createNewBlock()" a11297a

IIUC, when a chainstate is loaded via loadtxoutset, the behaviour is that you keep connecting on top of the active loaded chainstate and cooldown based on it.

ismaelsadeeq · 2026-02-25T16:31:54Z

src/node/interfaces.cpp

        return std::make_unique<BlockTemplateImpl>(assemble_options, BlockAssembler{chainman().ActiveChainstate(), context()->mempool.get(), assemble_options}.CreateNewBlock(), m_node);
    }

+    void interrupt() override


Instead of documenting, we should flip it the other way around.

interrupt, which is the generic function that toggles the boolean value.
Then interruptWait for waitNext, and interruptMining for Mining.

ismaelsadeeq · 2026-02-25T16:33:15Z

doc/release-notes-34184.md

+----------
+
+- `Mining.createNewBlock` now has a `cooldown` behavior (enabled by default)
+  that waits for IBD to finish and for the tip to catch up. This usually


In fcaec25 "doc: release note for IPC cooldown and interrupt"

nit: No guarantee here, mention that it opportunistically waits for IBD to finish.

@2

Sync capnp proto files with Bitcoin Core master (e09b81638ba1). bitcoin/bitcoin#33819 (mining: getCoinbase() returns struct instead of raw tx) mining.capnp: - BlockTemplate.getCoinbaseTx now returns CoinbaseTx struct (was Data) - Added CoinbaseTx struct with fields: tx, txFee, totalFee, blockReservedWeight, coinbaseOutputMaxAdditionalSigops, defaultSignetChallenge, defaultWitnessCommitment - Added constants: maxMoney, maxDouble, defaultBlockReservedWeight, defaultCoinbaseOutputMaxAdditionalSigops - Added default values to all struct fields (BlockTemplateOptions, Amount, CoinbaseTx) bitcoin/bitcoin#34568 (mining: Break compatibility with existing IPC mining clients) init.capnp: - makeMining renumbered from @2 to @3 - Added deprecated makeMiningOld2 @2 placeholder (Cap'n Proto requires sequential ordinals, so this cannot be removed) mining.capnp: - Mining: removed getCoinbaseCommitment and getWitnessCommitmentIndex - Mining: added interrupt @6 - BlockTemplate: methods renumbered (@5 through @9) bitcoin/bitcoin#34184 (mining: add cooldown to createNewBlock() immediately after IBD) mining.capnp: - Mining.createNewBlock: added context @3, cooldown @4 params - Mining.checkBlock: added context @2 param - Mining.createNewBlock: timeout now has default value (60000000) Also adds make_mining_old2_rejected integration test verifying that the server returns an error for the deprecated method.

@2

Sync capnp proto files with Bitcoin Core master (e09b81638ba1). bitcoin/bitcoin#33819 (mining: getCoinbase() returns struct instead of raw tx) mining.capnp: - BlockTemplate.getCoinbaseTx now returns CoinbaseTx struct (was Data) - Added CoinbaseTx struct with fields: tx, txFee, totalFee, blockReservedWeight, coinbaseOutputMaxAdditionalSigops, defaultSignetChallenge, defaultWitnessCommitment - Added constants: maxMoney, maxDouble, defaultBlockReservedWeight, defaultCoinbaseOutputMaxAdditionalSigops - Added default values to all struct fields (BlockTemplateOptions, Amount, CoinbaseTx) bitcoin/bitcoin#34568 (mining: Break compatibility with existing IPC mining clients) init.capnp: - makeMining renumbered from @2 to @3 - Added deprecated makeMiningOld2 @2 placeholder (Cap'n Proto requires sequential ordinals, so this cannot be removed) mining.capnp: - Mining: removed getCoinbaseCommitment and getWitnessCommitmentIndex - Mining: added interrupt @6 - BlockTemplate: methods renumbered (@5 through @9) bitcoin/bitcoin#34184 (mining: add cooldown to createNewBlock() immediately after IBD) mining.capnp: - Mining.createNewBlock: added context @3, cooldown @4 params - Mining.checkBlock: added context @2 param - Mining.createNewBlock: timeout now has default value (60000000) Also adds make_mining_old2_rejected integration test verifying that the server returns an error for the deprecated method.

@2

Sync capnp proto files with Bitcoin Core master (e09b81638ba1). bitcoin/bitcoin#33819 (mining: getCoinbase() returns struct instead of raw tx) mining.capnp: - BlockTemplate.getCoinbaseTx now returns CoinbaseTx struct (was Data) - Added CoinbaseTx struct with fields: tx, txFee, totalFee, blockReservedWeight, coinbaseOutputMaxAdditionalSigops, defaultSignetChallenge, defaultWitnessCommitment - Added constants: maxMoney, maxDouble, defaultBlockReservedWeight, defaultCoinbaseOutputMaxAdditionalSigops - Added default values to all struct fields (BlockTemplateOptions, Amount, CoinbaseTx) bitcoin/bitcoin#34568 (mining: Break compatibility with existing IPC mining clients) init.capnp: - makeMining renumbered from @2 to @3 - Added deprecated makeMiningOld2 @2 placeholder (Cap'n Proto requires sequential ordinals, so this cannot be removed) mining.capnp: - Mining: removed getCoinbaseCommitment and getWitnessCommitmentIndex - Mining: added interrupt @6 - BlockTemplate: methods renumbered (@5 through @9) bitcoin/bitcoin#34184 (mining: add cooldown to createNewBlock() immediately after IBD) mining.capnp: - Mining.createNewBlock: added context @3, cooldown @4 params - Mining.checkBlock: added context @2 param - Mining.createNewBlock: timeout now has default value (60000000) Also adds make_mining_old2_rejected integration test verifying that the server returns an error for the deprecated method.

Sjors mentioned this pull request Dec 31, 2025

Mining IPC createNewBlock should not return before IBD is over #33994

Closed

DrahtBot changed the title ~~mining: add cooldown to createNewBlock() immediately after IBD~~ mining: add cooldown to createNewBlock() immediately after IBD Dec 31, 2025

DrahtBot added the Mining label Dec 31, 2025

Sjors force-pushed the 2025/12/cool-down branch from 4a0b81d to a73a5b6 Compare December 31, 2025 06:48

DrahtBot added the CI failed label Dec 31, 2025

Sjors force-pushed the 2025/12/cool-down branch 2 times, most recently from 62524ac to e8b01c4 Compare December 31, 2025 07:19

Sjors mentioned this pull request Dec 31, 2025

Mining interface tracking issue #33777

Open

14 tasks

DrahtBot removed the CI failed label Dec 31, 2025

DrahtBot mentioned this pull request Jan 8, 2026

refactor: disentangle miner startup defaults from runtime options #33966

Draft

1 task

DrahtBot added the Needs rebase label Jan 13, 2026

Sjors force-pushed the 2025/12/cool-down branch from e8b01c4 to c02c283 Compare January 22, 2026 09:02

DrahtBot removed the Needs rebase label Jan 22, 2026

This was referenced Jan 23, 2026

ipc, test: Add tests for unclean disconnect and thread busy behavior #34284

Closed

kernel, refactor: return error status on all fatal errors #29700

Draft

w0xlt reviewed Jan 27, 2026

View reviewed changes

Sjors force-pushed the 2025/12/cool-down branch from c02c283 to 9817657 Compare January 27, 2026 10:49

w0xlt reviewed Jan 27, 2026

View reviewed changes

ryanofsky approved these changes Jan 28, 2026

View reviewed changes

src/node/miner.h Outdated Show resolved Hide resolved

src/validation.cpp Outdated Show resolved Hide resolved

src/node/miner.cpp Outdated Show resolved Hide resolved

test/functional/interface_ipc.py Outdated Show resolved Hide resolved

DrahtBot mentioned this pull request Jan 29, 2026

[EXPERIMENTAL] Schnorr batch verification for blocks #29491

Draft

1 task

Sjors force-pushed the 2025/12/cool-down branch from 9817657 to b57da68 Compare January 29, 2026 14:59

Sjors force-pushed the 2025/12/cool-down branch from 6428ed1 to 1e02888 Compare February 20, 2026 10:57

Sjors marked this pull request as ready for review February 20, 2026 10:58

ryanofsky added this to the 31.0 milestone Feb 20, 2026

ryanofsky approved these changes Feb 20, 2026

View reviewed changes

test/functional/interface_ipc_mining.py Outdated Show resolved Hide resolved

Sjors added 3 commits February 20, 2026 16:49

doc: release note for IPC cooldown and interrupt

fcaec25

Sjors force-pushed the 2025/12/cool-down branch from 1e02888 to fcaec25 Compare February 20, 2026 15:50

ryanofsky approved these changes Feb 20, 2026

View reviewed changes

DrahtBot mentioned this pull request Feb 22, 2026

mining: add submitBlock to IPC Mining interface #34644

Open

enirox001 reviewed Feb 23, 2026

View reviewed changes

DrahtBot mentioned this pull request Feb 24, 2026

mining: add getTransactions(ByWitnessID) IPC methods #34020

Draft

ryanofsky self-assigned this Feb 24, 2026

ryanofsky merged commit bd9e0e6 into bitcoin:master Feb 24, 2026
26 checks passed

Sjors deleted the 2025/12/cool-down branch February 24, 2026 11:59

plebhash mentioned this pull request Feb 24, 2026

IPC server crashes on early client connection (assertion failure in proxy.h and interfaces.cpp) #34664

Closed

ismaelsadeeq reviewed Feb 25, 2026

View reviewed changes

ryanofsky mentioned this pull request Feb 26, 2026

Multiprocess tracking issue #28722

Open

bolty-from-atl-bitlab bot mentioned this pull request Mar 3, 2026

Bitcoin Socratic Seminar #48 - Topic Suggestions atlantabitdevs/atlbit.dev#134

Open

enirox001 mentioned this pull request Mar 3, 2026

test: Add IPC wake-up test and reuse mining context #34727

Open

This was referenced Mar 4, 2026

mining: add cooldown to createNewBlock() immediately after IBD kevkevinpal/bitcoin#278

Open

Update libmultiprocess subtree to be more stable with rust IPC client kevkevinpal/bitcoin#289

Open

	const auto tip_block = kernel_notifications.TipBlock();
	AssertLockHeld(kernel_notifications.m_tip_block_mutex);
	const auto tip_block = kernel_notifications.TipBlock();

Conversation

Sjors commented Dec 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Rationale

Uh oh!

DrahtBot commented Dec 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Coverage & Benchmarks

Reviews

Conflicts

LLM Linter (✨ experimental)

Uh oh!

Sjors commented Dec 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bensig commented Jan 3, 2026

Uh oh!

Sjors commented Jan 22, 2026

Uh oh!

w0xlt left a comment

Choose a reason for hiding this comment

Uh oh!

w0xlt Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Sjors Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

w0xlt left a comment

Choose a reason for hiding this comment

Uh oh!

ryanofsky left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Sjors commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ryanofsky left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Sjors commented Feb 20, 2026

Uh oh!

ryanofsky left a comment

Choose a reason for hiding this comment

Uh oh!

enirox001 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

enirox001 Feb 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Sjors Feb 24, 2026

Choose a reason for hiding this comment

Uh oh!

enirox001 Feb 27, 2026

Choose a reason for hiding this comment

Uh oh!

enirox001 Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

ismaelsadeeq Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ryanofsky Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

ismaelsadeeq left a comment

Choose a reason for hiding this comment

Sjors commented Dec 31, 2025 •

edited

Loading

DrahtBot commented Dec 31, 2025 •

edited

Loading

Sjors commented Dec 31, 2025 •

edited

Loading

w0xlt Jan 27, 2026 •

edited

Loading

Sjors Jan 27, 2026 •

edited

Loading

Sjors commented Feb 20, 2026 •

edited

Loading

enirox001 left a comment •

edited

Loading

enirox001 Feb 23, 2026 •

edited

Loading

ismaelsadeeq Feb 25, 2026 •

edited

Loading

ismaelsadeeq Feb 25, 2026 •

edited

Loading