Why did my Knots node follow the BIP-110 soft-fork? How do I make it follow the longer chain?

Why did my Knots node follow the BIP-110 soft-fork? How do I make it follow the longer chain?

Manage alerts

Loading saved threads...

Geremia · External communityPost link
External question — Bitcoin Stack Exchange Author: Geremia Original post: https://bitcoin.stackexchange.com/questions/130980 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. My Knots full node seems to have stopped receiving blocks after 961636, which seems to indicate it followed the BIP-110 * soft-fork: bitcoin-cli getchainstates returns: { "headers": 961636, "chainstates": [ { "blocks": 961636, "bestblockhash": "0000000000000000000216a2691f8b2b7b2275b0ce6131cf4e8c0fe5361fb9c0", "bits": "1702353d", "target": "00000000000000000002353d0000000000000000000000000000000000000000", "difficulty": 127479855693691.4, "verificationprogress": 0.9999767532445456, "coins_db_cache_bytes": 8388608, "coins_tip_cache_bytes": 17169383424, "validated": true } ] } (Why does verificationprogress ≠ 1, anyway?) " BIP110 Situation Monitor: Live " shows this: What about Bitcoin Knots made it follow the BIP-110 fork? Is there a way I can make Knots follow the main chain? Knots's website has a headline: [The Bitcoin network is under attack] --- block production has slowed significantly. [Read the announcement] The community is preparing mitigations to resolve the situation. In the meantime, attackers are spreading misinformation and advising users to downgrade or switch to insecure node software. Users are strongly advised not to downgrade or switch to software that weakens Bitcoin's consensus protections. Doing so may compromise your security and expose you to false confirmations from blocks that are invalid under Bitcoin's consensus rules. If you have already downgraded, upgrade to the latest version of Bitcoin Knots. Knots will attempt to repair the resulting chain state and return your node to the valid chain. Miners who restart their nodes may need to add the following to bitcoin.conf: maxtipage=2592000 Another announcement will be published as soon as a mitigation is ready. If you would like to participate in the ongoing mitigation strategy, join the #strategic channel on the Bitcoin Knots Discord . Why does it advise miners should set maxtipage=2592000 ? *See these 9 August 2026 stories:Coindesk: "Controversial Bitcoin fork BIP-110 mines two blocks, then stops"PrimXBT: "Bitcoin’s BIP-110 Fork Falls 48 Blocks Behind Main Chain"
Quote
Report
Pieter Wuille · External communityPost link
External answer — Bitcoin Stack Exchange Author: Pieter Wuille Original post: https://bitcoin.stackexchange.com/a/130981 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. What about Bitcoin Knots made it follow the BIP-110 fork? Recent Knots clients implement BIP-110, while Bitcoin clients did not. BIP-110 says that the chain considered by Bitcoin clients is invalid, so Knots, following BIP-110, rejects it. Thus, from that perspective, Knots is simply not a Bitcoin client anymore, but a client for its own chain, which has (very) little blocks since the fork point. Is there a way I can make Knots follow the main chain? Revert to an older version that still followed Bitcoin's rules, or another Bitcoin client.
Quote
Report

Post Reply

Checking account access…