>The "verification" nodes don't do anything to prevent censorship by miners.
Absolutely agreed; however, eventually some non-hostile miner will randomly generate an acceptable `nonce` [entire point of hashing/energy-usage] which DOES include the censored-by-some transaction.
An additional function of the node-verification network (which uses essentially no energy, relative to mining) it to maintain the entirety of `mempool`, which is where unaccepted transaction-attempts live until mined into a block [which is then "accepted/denied" by same node-pool].
tl;dr: as far a probabilities go, unless you own exactly 100% of mining pool, it is impossible to censor a tx from the node's mempool; all you can do with <100% is DELAY transactions.
Absolutely agreed; however, eventually some non-hostile miner will randomly generate an acceptable `nonce` [entire point of hashing/energy-usage] which DOES include the censored-by-some transaction.
An additional function of the node-verification network (which uses essentially no energy, relative to mining) it to maintain the entirety of `mempool`, which is where unaccepted transaction-attempts live until mined into a block [which is then "accepted/denied" by same node-pool].
tl;dr: as far a probabilities go, unless you own exactly 100% of mining pool, it is impossible to censor a tx from the node's mempool; all you can do with <100% is DELAY transactions.