{
  "schema_version": 1,
  "state": "Archived authored position; read the guide for current qualifications",
  "canonical_guide": "https://bsv.place/guides/mining-incentives-and-economic-acceptance/",
  "url": "https://x.com/ProjectBabbage/status/2107167307097342049",
  "author": "Project Babbage",
  "published_at": "2026-10-05T17:53:29Z",
  "capture_date": "2026-10-05",
  "parent_url": "https://x.com/jionny112/status/2107129424135225455",
  "text": "You don’t have to mine blocks to decide what you accept as payment. Producing blocks, verifying them and accepting them are different jobs.\n\nA machine that validates without mining can provide independent verification. It does not contribute hashpower or win the next block. Saying it has no mining vote does not mean its operator has no useful role or economic choice.\n\nYou also don’t have to run a full node to choose which payments your business accepts. You can use a wallet or service to perform checks, with the corresponding reliance on that provider.\n\nSo let me be precise about “we ignore their blocks”: participating miners and infrastructure operators enforce an acceptance policy in software. SV Node documents a mechanism for rejecting an identified withholding-attack branch locally. That excludes it from that operator’s chain selection even if it has more accumulated work. Miners applying that decision continue on the accepted branch. Payment services and businesses need compatible policies for settlement to agree.\n\nOne person refusing a branch cannot make everyone else refuse it. Continued operation requires miners to keep producing accepted blocks, and effective coordination among the participants relying on them. Disagreement can produce a split or disruption. But we have the alert system for helping humans decide what’s an attack and how they may want to respond.\n\nOrdinary transaction validation also does not settle every disputed reorganization. BSV has additional governance arrangements, including Association directives to invalidate specified blocks under its published Network Access Rules. Those responsibilities should be judged against identifiable rules and evidence. We think “honest” must describe conduct under those or similar rules, not simply agreement with us.\n\nNow consider the attacker’s economics.\n\nThe objective of a profit-seeking double-spend attack is to walk away with more value than it costs. Producing a longer branch is only useful if the intended victims accept it and the attacker can realize the payoff.\n\nIf coordinated rejection prevents that payoff and the attack branch’s mining rewards are not recognized by the economy being targeted, the attacker is left with the costs without the intended return. Mining accepted blocks offers an alternative way to earn revenue.\n\nMaking that response credible and known in advance changes the calculation before the attack begins. The purpose of enforcement is therefore also deterrence: remove the expected profit and fewer people have a reason to attempt the attack.\n\nThat is why we expect profit-seeking attacks of this kind to be rare when this response is credible and consistently applied. It is an economic expectation, not a guarantee that attacks are impossible. Sabotage, outside incentives and coordination failures still matter.\n\nOur argument is that proof of work, rule enforcement and economic acceptance operate together. Hashpower remains essential. Its owner still needs other participants to accept the result.\n\nSV Node’s rejection mechanism:\nhttps://docs.bsvblockchain.org/network-topology/nodes/sv-node/frequently-asked-questions/safe-mode\n\nPublished enforcement rules:\nhttps://docs.bsvblockchain.org/network-access-rules/network-access-rules/part-iii-enforcement-rules",
  "limits": "Publication establishes the authored argument, not measured attack frequency, universal convergence or deployment evidence. The guide explicitly states those conditions."
}