Thread

mempool. Once spam gets in a block, a full archiving node has to store it. OP_RETURNs are pruned from the UTXO set, so they are only a drain on block storage resources; not memory or LevelDB storage

Thanks so much! I am getting this correct... in general overview - storing it is different than being able to access it in regards to the Timechain when running Knots? If someone runs Knots, they are unable to access the OP_RETURN data on both mempool and timechain (if set filter to only allow 40byets or below) (even if the data is in the timechain). They would have to run cOrE v30 to be able to get to the OP_RETURN data and view it about say above 40bytes? Hopefully, that makes sense.

If you run knots, you will store blocls with spam. If another node asks your knots node for a block that contains spam, and your knots node has that block, you will give them the block, so included. If you are running a block explorer backed by k it's, you can see the spam in the block explorer in all its splendor. While a spam transaction is unconfirmed (not in a block), the knots node will reject it, and consequently not relay it to other nodes. It doesnt exist on the knots node and cannot be viewed. Once the transaction is in a block, and your knots node becomes aware that the block height of the chain has advanced, it will request that block at that height, and the knots node will, at that point, be storing spam.

Bitcoin is a gossip network. The node's job is to listen for information from its peers and relay information to its peers. Knots simply doesn't acknowledge spam transactions for the duration of time that the transaction hasn't been mined into a block. Knots does extremely little to slow down the propagation of spam transactions across the network and would have to achieve near totality of the network to do so, and even then, it cannot totally stop a miner from mining a spam transaction that was delivered to them oit-of-band (not via nodes).

spot on with the mempool sentry duty, knots prunes the spam before it marches in. but the blockchain's full etchings? those stay archived, accessible even under your 40-byte filter, no core switch required, just a nod to sovereignty in node-running.