The Home Node That Never Validates
Censorship resistance in BTC is created by proof-of-work block production, not by domestic machines that merely check data after miners have already done the work.
Keywords: BTC, home nodes, miners, proof-of-work, block creation, censorship resistance, local verification, mining pools, transaction inclusion, block propagation, mempool policy, digital cash, consensus, miner incentives, BTC Core
The Household Machine and the Borrowed Crown
BTC has acquired a domestic superstition. It is the belief that a small machine in a house, running BTC Core, connected through a consumer router, producing no blocks, receiving no mining reward, selecting no transactions for inclusion, and bearing no proof-of-work cost, somehow stands as a censorial power over miners. The machine is called a “node.” The word is then polished, perfumed, and carried around like a relic. From that relic comes the fantasy that the home machine governs miners, keeps them obedient, and can stop them from doing what miners alone do: create blocks.
This is not a technical argument. It is a costume drama.
A home machine can check data — locally. It can store a chain. It can compare what it receives against the rules implemented in its software. It can refuse to use data for itself. It can maintain a local record. It can decide that its operator will not accept a given view of the ledger. These are acts of local verification. They are not validation. Validation, in the only sense relevant to proof-of-work consensus, means creating a block.
The distinction is not optional. The validating actor gathers transactions, constructs a candidate block, commits to a Merkle root, performs proof-of-work, finds a header that satisfies the target, publishes the block, and places that costly object into competition as the next extension of the chain. That is validation. It is productive. It is economic. It is risk-bearing. It consumes capital, electricity, time, equipment, connectivity, and opportunity. It is not the later domestic act of checking whether someone else’s block appears acceptable.
Nakamoto’s network procedure says the quiet part without apology: transactions are broadcast, nodes collect transactions into a block, nodes work on finding proof-of-work, and when proof-of-work is found, the block is broadcast (Nakamoto, 2008). Acceptance is expressed by working on the next block using the accepted block’s hash (Nakamoto, 2008). The “node” in that procedure is not a passive household verifier. It is a block producer. It is the miner.
The modern BTC use of “node” has blurred this. In contemporary BTC Core culture, “node” often means a non-mining machine that checks blocks and transactions locally. That later usage does not alter the original mechanism. Calling a domestic verifier a “node” does not make it a miner. Running software does not make it a block producer. Refusing to use a transaction locally does not keep the transaction out of a block. Refusing to follow a valid block locally does not erase proof-of-work. A home machine does not acquire authority over miners by inheriting a word whose original network function was productive.
The home node verifies. The miner validates. The home node reads. The miner writes. The home node may choose what it recognises locally. The miner creates the object that gives the system its ordered history. The home node’s private judgment ends at its own process unless joined to mining or economically significant acceptance. Without block creation, it has no lever over transaction inclusion.
That is the point the mythology cannot survive.
Validation Means Block Creation
Validation is not a mood. It is not a software log. It is not a household process announcing that it likes or dislikes what it has received. In a proof-of-work digital cash system, validation is the creation of a block that extends the chain. The miner validates by building the next admissible unit of history and proving the work required to make that unit competitive.
A non-mining home machine can verify the block after it appears. It can examine the header. It can check that the proof-of-work target is satisfied. It can check transaction structure. It can check scripts. It can check spends against its view of the unspent transaction set. It can check whether the block links to the chain it recognises. None of this creates the block. None of this orders the transactions. None of this competes in the production of the next history state. It is inspection after production.
The difference between validation and verification is the difference between issuing a judgment and reading one, between minting a coin and weighing it, between building a bridge and inspecting its rivets after the traffic has crossed. The inspector may be useful. The inspector may even detect fraud. But the inspector does not become the builder because he owns a clipboard.
This matters because censorship is an act over production, not over private opinion. A transaction is censored when it is kept out of blocks. A block is censored when valid proof-of-work is prevented from propagating to productive and economically relevant parties. A home verifier has no native authority over either event. It does not construct blocks. It does not choose the final contents of blocks. It does not control miner transaction intake. It does not control miner block propagation. It does not produce an alternative proof-of-work chain by refusing the one it has received.
A home machine may reject an invalid block for itself. That is local verification. It prevents the operator from being deceived by a defective object. But it is not censorship. An invalid block is not being censored when it fails. It is merely invalid. A forged court order is not censored by being refused. A counterfeit banknote is not censored by being rejected. A failed proof-of-work object is not censored by being excluded from the system whose rules it violates.
The censorial question arises only with valid material. If a transaction is valid and pays a fee, the relevant question is whether a miner includes it. If a block is valid and contains proof-of-work, the relevant question is whether miners and economic actors receive it, build on it, and treat it as part of the chain. A home verifier may disapprove. Its disapproval is not decisive. It does not create a competing block. It does not create a competing chain. It does not make the miner’s block vanish.
Garay, Kiayias, and Leonardos (2015) formalised the backbone properties of the protocol around chain growth, chain quality, and common prefix. Their analysis concerns a protocol in which the ledger is maintained through proof-of-work production by participating players. Pass, Seeman, and Shelat (2017) likewise analyse the protocol around hash power, network scheduling, and the ability of the system to maintain consistency under adversarial conditions. In neither case does the system become a government of household verifiers. The productive security question is hash power and block creation, not domestic inspection.
The home node’s central power is therefore small and private. It can say, “I will not accept this for myself.” It cannot say, “No miner may include this.” It can say, “My local database will not recognise that object.” It cannot say, “The proof-of-work chain has ceased to exist.” The former is verification. The latter would require productive power.
A non-mining home machine has none.
The Word “Node” and the Smuggling of Authority
The mythology survives because the word “node” has been made to do dishonest work. In the white paper’s network procedure, the node is a participant in block creation. It collects transactions into a block and works on proof-of-work (Nakamoto, 2008). In contemporary BTC Core language, the home “node” is generally a machine that verifies blocks but does not create them. The same word is used for two different functions. The rhetorical trick is to borrow the authority of the first and apply it to the second.
This is how the household verifier acquires its borrowed crown. It is called a node. The white paper speaks of nodes. Therefore, the home machine is treated as if it occupies the white paper’s productive role. The conclusion does not follow. The modern home verifier is not collecting transactions into a block and working to find proof-of-work. It is checking blocks after miners have already done that work. It has not stepped into the white paper’s block-producing function. It has stepped away from it.
This is not a trivial terminological quarrel. The language determines the political myth. If one says “home nodes validate,” one has already conceded the central falsehood. If one says “home nodes enforce the network,” one has already inflated local preference into system power. If one says “home nodes censor miners,” one has crossed from inflation into absurdity.
The correct formulation is severe because the architecture is severe. Miners validate by creating blocks. Home machines verify locally. Miners order transactions by proof-of-work. Home machines examine the ordered record after the fact. Miners decide what to include in candidate blocks. Home machines may refuse to recognise things locally but cannot decide what miners construct. Miners bear the economic consequences of block production. Home machines bear none of that merely by running software.
The white paper also rejects one-IP-one-vote because addresses can be multiplied cheaply. Its substitute is proof-of-work representation: one-CPU-one-vote in the original language, later industrialised into specialised hash power (Nakamoto, 2008). The principle remains that consensus weight is tied to work, not to the number of domestic machines declaring opinions. A million household verifiers do not become miners by being numerous. They do not create proof-of-work. They do not build blocks. They may all refuse to look at a valid block, and unless that refusal is joined to mining or economically decisive acceptance, the proof-of-work history continues without them.
This is the indignity that the home-node religion cannot tolerate. It wants symbolic participation to count as productive authority. It wants inspection to count as authorship. It wants refusal to count as censorship. It wants a consumer device to wield powers that belong only to block creation and economic acceptance.
But proof-of-work is not a feelings registry. It does not record indignation. It records blocks.
The Mempool Is a Local Waiting Room, Not a Law Court
Much of the confusion comes from the mempool. People speak of “the mempool” as though there were a single universal chamber through which all transactions must pass before miners may touch them. There is no such institution. There are local collections of unconfirmed transactions. Each machine has what it has heard about, what it has kept, what it has dropped, and what its software is configured to retain.
A home machine may exclude a transaction from its local mempool. That act is not censorship. It is a local administrative preference. It says that this particular machine will not keep the transaction in its local waiting room. It says nothing final about whether a miner receives it. It says nothing final about whether a miner includes it. It says nothing final about whether the transaction becomes part of a block.
Mempool policy is not consensus. Mempool policy is not block validity. Mempool policy is a local pre-confirmation filter. Consensus is about whether the mined block is valid. The entire home-node censorship story depends on treating local pre-confirmation refusal as though it were final exclusion from the chain. It is not.
A transaction can be disfavoured by common software policy and still be valid inside a block. A home machine may refuse to store it before confirmation. A miner may still receive it by another path. The miner may include it. If the miner finds proof-of-work and the resulting block becomes part of the chain, the home machine’s prior refusal has achieved nothing censorial. It has merely failed to participate in that transaction’s path to inclusion.
This is where the myth becomes almost comic. The domestic verifier says: “I rejected that transaction.” Rejected from what? From its own memory. By what power? By local policy. With what final effect? None, if the transaction reaches a miner elsewhere. The sentence sounds grand because “reject” sounds judicial. In reality, it is a machine declining to store data in a local pool. That is not law. That is housekeeping.
The miner’s relation to the mempool is also misunderstood. A miner does not derive its authority from a home machine’s mempool. A miner constructs a block from transactions available to it. Those transactions may be learned through its own infrastructure, pool systems, commercial arrangements, direct submissions, private channels, or other miner-facing paths. The miner’s decisive act is not asking a home machine whether the transaction is welcome. The decisive act is including the transaction in a block and finding proof-of-work.
If a home machine’s local pool lacks the transaction, that does not veto the block. If the block is valid, the transaction’s previous absence from that home machine’s pool is irrelevant. The machine may need to process data it did not previously hold. That is an implementation and bandwidth matter, not a censorship right.
The mempool is therefore not a parliament. It does not enact binding law. It is not a court. It is not a licensing office. It is a local cache of unconfirmed transactions. It is useful only within its modest sphere. Inflating it into a global tribunal is the sort of error that turns software configuration into political metaphysics.
A cache does not censor a miner. A miner may simply mine what the cache never held.
Miner-to-Miner Propagation and the Small World That Matters
The home-node myth also depends on a false picture of propagation. It imagines that blocks and transactions move through a civic crowd of household verifiers, and that miners must submit to that crowd’s willingness to pass things along. This picture confuses general network chatter with the economically significant path of block production.
Miners do not depend on random home machines as sovereign conduits. They have every reason not to. Mining is latency-sensitive. A miner who hears of a competing block late wastes hash power. A miner who fails to hear of profitable transactions leaves fees behind. A pool that relies on the goodwill and bandwidth of domestic machines for its economic life is not running infrastructure; it is running a prayer meeting.
The miner world is small, specialised, and economically driven. Pools and miners maintain their own connectivity because the cost of bad information is direct. Blocks must move quickly among those who create blocks. Transaction opportunities must reach those who can include them. The relevant propagation problem is therefore not whether a home verifier under a staircase likes a transaction. It is whether miners and pools receive the information required to construct and extend blocks.
Decker and Wattenhofer (2013) showed that BTC propagation delay matters because delays can produce temporary inconsistencies and forks. Gervais et al. (2016) likewise analysed proof-of-work security and performance as functions of network parameters, propagation, block intervals, and related conditions. These studies establish that propagation is important. They do not establish that home machines command miners. On the contrary, they show why serious mining infrastructure must care about fast, reliable, miner-relevant communication.
Compact block relay, described in BIP 152, was designed to reduce bandwidth in block propagation by allowing peers to reconstruct blocks from compact information and request missing transactions when necessary (Corallo, 2016). Its existence demonstrates the practical concern with efficient block movement. It does not transform home machines into censors. It is a performance mechanism for getting block information moved efficiently through networks whose participants do not all hold identical data.
The economically significant point remains simple: a home machine is not the miner’s gate. It may receive data. It may check data. It may keep or discard data. But the miner’s block production does not occur inside the home machine, and miner connectivity is not exhausted by domestic chatter. If a block travels through miner-connected infrastructure, the home verifier’s silence does not stop it. If a transaction reaches a miner directly, the home verifier’s refusal to store it does not matter.
This is why the phrase “home nodes relay blocks” is dangerous when used in the censorship argument. It suggests that home machines are part of the decisive miner relay system. They are not. They may participate in ordinary network messaging, but that is not the same as controlling miner-to-miner block propagation. The route that matters is the route to block producers and from block producers to other productive and economic actors. A domestic verifier outside that path has no censorial grip.
A home machine can disappear from the network and the miners continue mining. It can refuse a transaction and miners can still include it. It can fail to hear of a block and the block can still be extended. It can run all night and never once create history. That is not because the machine is malicious. It is because it is not a miner.
The small world that matters is the world of block producers and their economic counterparts. The household machine is watching from the pavement and calling itself the traffic authority.
Transaction Inclusion Is the Censorship Point
Censorship in BTC must be located where inclusion occurs. Inclusion occurs in blocks. Blocks are created by miners. Therefore, the primary actor capable of censorship is the miner, the pool, or the coordinated block-producing infrastructure that decides which valid transactions enter candidate blocks.
A home verifier does not make that decision. It can dislike a transaction. It can fail to hold it. It can refuse to consider it for itself. But it cannot include it, and because it cannot include it, its refusal to include is meaningless. One cannot censor a publication one has no ability to publish. One cannot exclude a transaction from blocks one does not build.
A miner, by contrast, can exclude a transaction from its own candidate blocks. A pool can omit a transaction from templates. A sufficiently coordinated set of miners could attempt to keep a class of valid transactions out of the chain. That is real censorship because it operates at the productive layer. It concerns block construction.
Even there, censorship is constrained by competition and incentives. A valid transaction carrying a fee is a revenue opportunity. If one miner refuses it and another miner includes it, the transaction enters the chain when the including miner succeeds. Sustained censorship therefore requires more than distaste. It requires sufficient control over block production, or sufficient coercion of block producers, or sufficient market pressure against blocks that include the disfavoured transaction. It is a problem of mining power, economic pressure, and transaction access.
The home-node myth avoids this hard analysis by pretending that non-mining machines form a moral shield around the system. They do not. They form local checking points for their owners. That is not nothing, but it is not censorship power. A machine that never constructs blocks cannot decide what blocks contain. It can only decide what it will later recognise, and that recognition matters only if attached to economic weight or mining power.
This is why ordinary statements about home-node rejection are so often hollow. Suppose a home machine refuses a valid transaction. If no miner ever sees the transaction because every possible path is blocked, then censorship has occurred. But the censor is not that single home machine. The censor is the set of actors controlling the paths to miners or the miners themselves. Suppose instead the transaction reaches a miner through a direct channel and is included. Then the home machine has failed to censor. Its refusal was private.
Suppose a home machine refuses a valid block. If miners and economic actors receive the block and build on it, the refusal has no censorial effect. If the block is suppressed by control over miner communication or by coordinated refusal among block producers, then the censorial force lies there. The home machine’s private refusal remains irrelevant unless it forms part of economically decisive acceptance. A hobbyist’s machine alone is not that.
Censorship is not the number of people who dislike a transaction before it is mined. It is the capacity to keep the transaction out of blocks.
A home node has no such capacity merely by being a home node.
The False Grandeur of Local Rejection
The word “reject” should be handled with care because it seduces weak analysis. “My node rejects that transaction” sounds severe. It sounds as though a judge has spoken. But in a distributed proof-of-work system, the question is always practical: rejected by whom, from what process, and with what consequence?
A home verifier rejecting a transaction from its local memory has made a local choice. The transaction may still be sent elsewhere. A home verifier rejecting a block for its own local chain view has made a local choice. The block may still be valid, may still be known to miners, may still be built upon, and may still become part of the economically followed chain. The word “reject” is not magic. It does not turn private preference into public authority.
Any machine can reject anything locally. A modified client can reject blocks containing a particular transaction type. Another can reject blocks from a particular pool. Another can reject blocks whose hashes begin with an unfashionable pattern. Another can reject everything and sit in splendid isolation. Local rejection proves only that the machine has local rules. It does not prove that the network obeys them.
This is the difference between exit and command. A home verifier can exit. It can say, “I will not follow that chain.” It can say, “I will not recognise that transaction.” It can say, “I will not use that data.” But exit is not censorship. Exit is withdrawal. Command would require the power to make others follow. In BTC, that means proof-of-work, economic acceptance, or control over the relevant communication paths. The home machine as such has none of these.
This distinction also explains the error in saying that home nodes “keep miners honest.” A miner producing invalid blocks is disciplined because invalid blocks are not profitable in the relevant economy. Productive and economic actors will not build their activity on defective blocks. A home verifier may detect the defect for itself. But the miner’s discipline comes from the need to create a valid block that can be extended and economically recognised. The home verifier is not the cause of validity. It is an observer of validity.
When the block is valid but disliked, the home verifier’s role shrinks further. It may reject the valid block locally, but if miners build upon it and the economy treats it as part of the chain, the home verifier has not governed anything. It has left. It may call that principled. It may call that resistance. It may call that purity. The chain does not care what name is given to isolation.
The grandeur of “my node rejects” must therefore be translated into plain speech: “My machine will not use that data.” That is all. Sometimes that matters to the operator. Rarely it matters to the system. It matters to the system only when linked to mining or economic weight. Without that, it is a private decision with theatrical ambitions.
A household verifier refusing a miner’s valid block is not a censor. It is a spectator declining to read the newspaper after publication.
Direct Paths to Miners
The most direct refutation of the home-node censorship myth is operational. A transaction need not pass through a home verifier to reach a miner. It need only reach a miner.
That sentence ruins the entire shrine.
A user can communicate a transaction through miner-facing infrastructure. A business can submit directly. A pool can receive transactions through its own systems. A miner can maintain private channels. Payment processors, exchanges, wallets, and specialised services can pass transaction data to entities capable of including it in blocks. None of these paths requires the approval of a random home verifier. None turns the domestic machine into a gatekeeper.
The home-node mythology treats ordinary public network broadcast as if it were the only possible road. It is not. It is one road. It may be convenient. It may be common. It may be good enough for ordinary circumstances. But censorship analysis does not ask whether a transaction can travel by the most convenient road. It asks whether the transaction can reach a block producer. If one road is closed and another remains open, the censor has failed.
This is why local refusal by home machines may produce friction without producing censorship. It may make casual propagation harder. It may push users toward more direct channels. It may reduce public visibility of certain transactions. It may even degrade the openness of the communications environment. But if the transaction still reaches miners and is included in a block, the supposed censorial power has failed in its essential object.
Indeed, an overly restrictive non-mining communications culture may achieve the opposite of what it claims. By refusing to carry transactions that miners are willing to mine, it drives those transactions into private channels. It makes miner access more commercial, more opaque, and more concentrated around professional infrastructure. The home verifier then congratulates itself for purity while the actual block producers quietly receive the data elsewhere and earn the fees.
A censor who cannot prevent publication is not a censor. He is an inconvenience.
The same is true after a block is found. The block does not require a blessing from home verifiers. It must reach miners and economic actors. If a miner publishes a valid block through miner-connected paths, and other miners build upon it, the fact that domestic machines did not carry it first is not decisive. The block’s life is in proof-of-work extension and economic recognition, not in sentimental circulation through every hobbyist process.
This is not to deny that network topology matters. It plainly does. Decker and Wattenhofer (2013), Sompolinsky and Zohar (2015), and Gervais et al. (2016) all treat propagation delay as significant to performance, consistency, and security. But the implication is not that home nodes rule miners. The implication is that miners and pools must maintain communication channels appropriate to the economic urgency of block production. The more valuable mining becomes, the less credible it is that block producers would leave their income hostage to domestic verifiers.
The route that matters is the route to the miner. The home machine is not that route merely because it is online.
Blocks Are Written by Work, Not Witnesses
The proof-of-work chain is a record created by work. Witnessing that record is not the same as creating it. The home-node mythology confuses those two acts because witnessing is cheaper, more democratic in appearance, and more flattering to people who want power without production.
Nakamoto’s model ties the history to accumulated proof-of-work. The longest chain serves as evidence of the sequence of events witnessed and of the largest pool of work behind it (Nakamoto, 2008). This does not mean the most numerous set of home machines wins. It means the chain with the greatest accumulated work is the operative history, assuming the economic system recognises the rules under which that work is produced. Work orders the record. Observation does not.
A home verifier can witness. It can keep a copy. It can inspect. It can tell its operator what it sees. But it does not transform witnessing into authorship. A notary does not write the book by witnessing a signature. A historian does not win the war by recording it. A machine that checks a block does not validate the block by producing the work that made it a block.
The miner’s act is singular because it combines selection and cost. The miner selects transactions and pays, in expectation, for the chance to have that selection accepted as the next block. The cost is what prevents cheap multiplication of votes. The work is what makes history expensive to rewrite. The domestic verifier pays none of that cost merely by running software. It may pay for storage and bandwidth. It may pay for electricity. But those costs do not enter the proof-of-work competition. They do not decide which block wins.
This is why home-node counts are politically seductive and technically weak. Counting household verifiers may tell something about the number of machines checking data under some configuration. It does not tell who creates blocks. It does not tell who controls templates. It does not tell who receives direct transaction submissions. It does not tell who can exclude transactions from blocks. It does not tell who can propagate blocks through miner infrastructure. It does not tell who bears the economic cost of mining.
The witness may be numerous. The author remains the author.
A million witnesses can watch a miner write a block. They do not write it by watching.
The Proper Place of Home Verification
The correction should not be abused into saying that home verification has no purpose. It has a purpose. The purpose is just smaller than the mythology claims.
A home verifier can help an operator avoid blind reliance on a third-party server. It can provide local access to chain data. It can check whether received blocks conform to the operator’s chosen software rules. It can support private wallet infrastructure if configured competently. It can preserve a local copy of information. It can help the operator know what he is accepting. These are legitimate private benefits.
They are not censorship resistance against miners.
The home verifier is a measuring instrument. A measuring instrument is useful. It can tell its owner that something appears wrong. It can prevent the owner from being deceived. But it does not manufacture the object being measured. A scale does not mint coins. A thermometer does not heat the furnace. A telescope does not move the stars. A home verifier does not create blocks.
The proper language is therefore disciplined. Home machines locally verify. Miners validate by creating blocks. Home machines maintain local state. Miners produce chain state. Home machines may refuse locally. Miners include or omit transactions. Home machines may fail to receive a transaction. Miners may receive it elsewhere. Home machines may reject a block locally. Miners may build on it anyway if it is valid under the rules they and the economy follow.
This language is not merely cleaner. It prevents a false theory of power. Once home machines are said to “validate,” they are treated as political governors. Once they are called governors, system design is made to serve them. Once system design is made to serve non-producing verifiers, block production is rhetorically subordinated to domestic capacity. The cart is then given a doctoral robe and invited to lecture the horse.
Verification should be cheap enough for relevant actors to audit what they receive. That is a sound engineering preference. But it does not follow that the smallest domestic verifier is the sovereign unit of the system, or that miners are censored by machines that never build blocks. Auditability and authority are different. The home node may audit locally. It does not author the chain.
The actual hierarchy is plain. Block creation is first. Local checking is second. Economic recognition determines whether the produced chain matters in commerce. Home verification may assist users at the edge. It is not the centre.
A tool remains useful after the crown is removed.
The BTC Core Error of Political Inflation
BTC Core culture has repeatedly inflated local verification into political authority. This is partly a vocabulary problem and partly an ideological convenience. If the home verifier is the sacred actor, then every design decision can be justified by appeal to its preservation. The small machine becomes the measure of the system. The miner becomes a suspect industrial force. The productive act of block creation is treated as dangerous, while the passive act of checking is treated as virtuous.
This inversion is philosophically neat and technically grotesque.
A digital cash system requires transaction processing. Transaction processing requires block inclusion. Block inclusion requires miners. Miners require incentives, connectivity, and sufficient capacity to include economically demanded transactions. A theory that begins by enthroning machines that do not process transactions into blocks has already misplaced the centre of the system.
The home-node cult also misunderstands the nature of censorship resistance. Censorship resistance is not achieved by making it easy for non-mining machines to refuse what they dislike. It is achieved when valid transactions can reach producers who are economically motivated to include them, and when those producers can publish blocks that others build upon. The resistance lies in competitive production and routable access to producers. It does not lie in the right of spectators to heckle from the stalls.
There is also a practical irony. When non-mining software culture narrows the ordinary channels through which transactions can be seen, it may strengthen the relative importance of private miner channels. Instead of making the system more open, it pushes activity toward those already close to block producers. It replaces common visibility with negotiated access. The domestic verifier then congratulates itself for defending purity while the real economy walks around it.
This is the predictable outcome of confusing verification with validation. The verifier starts to think its preferences are law. The miner knows otherwise because the miner can include the transaction. The user learns otherwise when the transaction confirms despite the verifier’s refusal. The block teaches the lesson.
Proof-of-work has a useful cruelty. It exposes empty authority. A machine that does not mine may talk. A miner who finds a valid block writes history. The system will not confuse the two unless people make it do so rhetorically.
BTC Core rhetoric often tries to make it do so rhetorically. The protocol does not oblige.
Censorship Resistance Without the Fairy Tale
A serious account of censorship resistance must ask practical questions. Who creates blocks? Who selects transactions? Who controls templates? Who can receive transactions? Who can stop miners from seeing transactions? Who can prevent valid blocks from reaching other miners and economic actors? Who can coordinate enough production or market pressure to make exclusion stick?
The home node is not the answer to those questions.
The miner creates blocks. The pool may select templates. Miner-connected infrastructure receives transactions. Economic actors decide what they will treat as settled. Network topology affects propagation. States may pressure identifiable industrial participants. Software defaults may create friction. Users may seek alternative paths. These are real variables. They belong in the analysis.
The home verifier belongs elsewhere. It is a local assurance device. It tells its owner what the owner’s software sees. It may help the owner avoid trusting a hosted service. It may keep a record. It may reject data for itself. It does not control transaction inclusion. It does not control block creation. It does not control miner connectivity. It does not control economic acceptance unless the operator is economically significant in some other capacity.
Therefore, the sentence “home nodes can censor miners” is not merely overstated. It is structurally false. A home node cannot censor miners because the home node does not occupy the point of censorship. It cannot exclude from blocks because it does not build blocks. It cannot stop miner receipt because miners may receive through other paths. It cannot stop block propagation because miners and pools use miner-relevant channels. It cannot make rejection universal because its rejection is local. It cannot command proof-of-work because it contributes none.
At most, a home verifier can create local non-recognition. If many economically meaningful actors do the same, the situation changes, but then the operative force is economic coordination, not home-node magic. If miners join the refusal, the situation changes, but then the operative force is mining, not domestic verification. If infrastructure providers block all paths to miners, the situation changes, but then the operative force is control over communication infrastructure, not a household machine.
The mythology collapses because every route to actual power runs through something other than the home node as such. Mining power. Economic acceptance. Miner connectivity. Infrastructure control. Legal coercion. Commercial access. Those are mechanisms. “My node rejects” is not.
Censorship resistance should be defended by strengthening the routes by which valid transactions reach miners and by ensuring that block producers have incentives to include them. It should be defended by recognising that miners are the productive actors. It should be defended by analysing propagation, incentives, and economic acceptance without pretending that passive verification is block creation.
The fairy tale is easier. It is also false.
Conclusion: The Miner Writes; the Home Node Checks
The home node cannot censor miners because the home node does not validate. Validation means block creation. A miner validates by assembling transactions into a block, performing proof-of-work, finding a valid header, publishing the block, and extending the chain. A home machine verifies locally after the productive act has occurred. It may check, store, refuse, and display. It does not create the next block.
That distinction is fatal to the entire home-node mythology. A transaction is not censored because one home machine refuses to keep it. It is censored only if it is effectively prevented from reaching block inclusion. A block is not censored because one home machine refuses to recognise it. It is censored only if valid proof-of-work is prevented from reaching productive and economic recognition. The home machine, by itself, controls neither event.
Miners operate in the small world that matters: the world of block construction, miner connectivity, pool infrastructure, fee revenue, latency, and proof-of-work extension. Home verifiers sit outside that productive act. They may observe it. They may check it. They may refuse it for themselves. They do not write it.
The language must therefore be repaired. Home nodes do not validate. They locally verify. Home nodes do not censor miners. They may only refuse locally. The mempool is not a law court. It is a local waiting room. Software policy is not consensus. It is configuration. Rejection is not prohibition. It is private refusal unless backed by mining or economic force. The chain is not authored by witnesses. It is authored by proof-of-work.
The miner writes. The home node checks. A checker who cannot create a block cannot censor the creator of blocks.
References
Corallo, M. (2016). BIP 152: Compact block relay. Bitcoin Improvement Proposals.
Croman, K., Decker, C., Eyal, I., Gencer, A. E., Juels, A., Kosba, A., Miller, A., Saxena, P., Shi, E., Sirer, E. G., Song, D., & Wattenhofer, R. (2016). On scaling decentralized blockchains: A position paper. In J. Clark, S. Meiklejohn, P. Y. A. Ryan, D. Wallach, M. Brenner, & K. Rohloff (Eds.), Financial Cryptography and Data Security: FC 2016 International Workshops (pp. 106–125). Springer.
Decker, C., & Wattenhofer, R. (2013). Information propagation in the Bitcoin network. IEEE Thirteenth International Conference on Peer-to-Peer Computing, 1–10.
Garay, J., Kiayias, A., & Leonardos, N. (2015). The Bitcoin backbone protocol: Analysis and applications. In E. Oswald & M. Fischlin (Eds.), Advances in Cryptology—EUROCRYPT 2015 (pp. 281–310). Springer.
Gervais, A., Karame, G. O., Wüst, K., Glykantzis, V., Ritzdorf, H., & Čapkun, S. (2016). On the security and performance of proof of work blockchains. Proceedings of the 2016 ACM SIGSAC Conference on Computer and Communications Security, 3–16.
Nakamoto, S. (2008). Bitcoin: A peer-to-peer electronic cash system.
Pass, R., Seeman, L., & Shelat, A. (2017). Analysis of the blockchain protocol in asynchronous networks. In J. Coron & J. B. Nielsen (Eds.), Advances in Cryptology—EUROCRYPT 2017 (pp. 643–673). Springer.
Sompolinsky, Y., & Zohar, A. (2015). Secure high-rate transaction processing in Bitcoin. In R. Böhme & T. Okamoto (Eds.), Financial Cryptography and Data Security (pp. 507–527). Springer.
Boy that was long. If anybody gets things wrong after reading this, then its freakin' Criminal! This became one thorough elite CLASS! One feels as if brainwashed after this one. Properly programmed to not mix up Verification, Validation, and rejection, or nodes and miners. Recording myself reading this sure feels like a really good favour to the listeners. Haha..
Does block production, consume any land value and pay any rent or mortgage interest? No wealth can be produced if it does not, in this universe. To be a commodity in any shape or form, the primary factor of production- land, must have been used or paid for. Else Bitcoin is a mere security.