Skip to content

Conversation

@Sjors
Copy link
Collaborator

@Sjors Sjors commented Nov 24, 2025

This was broken by #58 resulting in spurious "Tip changed" messages.

Worse however is that that this caused m_last_block_time to update too often. When -sv2interval is set to 10 seconds or less, this results in PruneBlockTemplateCache never running.

This was broken by stratum-mining#58 resulting in spurious "Tip changed" messages.

Worse however is that that this caused m_last_block_time to update too often. When -sv2interval is set to 10 seconds or less, this results in PruneBlockTemplateCache never running.
@Sjors Sjors merged commit fbe0984 into stratum-mining:master Nov 24, 2025
19 checks passed
@Sjors Sjors mentioned this pull request Nov 24, 2025
@Sjors
Copy link
Collaborator Author

Sjors commented Nov 24, 2025

2025-11-24T14:25:58Z [sv2:trace] Ignore fee changes for 1 seconds (-sv2interval), wait for a new tip, client id=0
2025-11-24T14:25:59Z [sv2:trace] Tip changed, client id=0
...
(10 seconds later)
...
2025-11-24T14:26:09Z [sv2:trace] Prune stale template id=69 (10s after new tip)
2025-11-24T14:26:09Z [ipc:info] {sv2-tp-42890/b-sv2-13677769} IPC client destroy N2mp11ProxyClientIN3ipc5capnp8messages13BlockTemplateEEE
2025-11-24T14:26:09Z [sv2:trace] Prune stale template id=70 (10s after new tip)
2025-11-24T14:26:09Z [ipc:info] {sv2-tp-42890/b-sv2-13677769} IPC client destroy N2mp11ProxyClientIN3ipc5capnp8messages13BlockTemplateEEE
...

Before this PR the "Prune stale template" didn't show, though this bug only shows up if you set -sv2interval to something < 10s, which I did in order to test #63.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant