Chainspam is any data in blockchain txs not there solely to transfer, reclaim or privatize value securely. Transfer = reduce the senders' amount & increase the recipients'. Reclaim = restore part/all the senders' amount after a failed payment. Privatize = do a coinjoin or similar

My favorite part of today: I observed that in the Knots v Core debate, the Core side leans on emotion and the Knots side leans on technical/logical arguments Immediately, Core supporters responded with ridicule and ad hominem -- i.e. appeals to emotion View quoted note →

Plebs lately: "Wow you listen to @mattkratter too?"

Part of the reason why the Core side is a loser in the spam debate is that they generally prefer arguing from feelings and emotion, whereas the Knots side relies more on technical arguments View quoted note →

Syllogistic logic supports mempool filters: (1) If the filters clean your mempool, then they work (2) They do clean your mempool; witness: your eyes (3) Therefore, the filters work

A guy at btc++ Istanbul had an interesting project. He downloads the blockchain without checking for doublespending. After he has all the data, he does a doublespend check by running an efficient sorting algorithm called MergeSort, which, in his implementation, takes all "input" utxos and "output" utxos, sorts them alphabetically via txid_vout, and removes duplicates. Those are always outputs created in one tx and spent in another The result is a list only containing unspent outputs, i.e. the result is the utxo set, and this procedure gives him a sync speedup of slightly over 50%. It also does not seem to require storing an "intermediate" utxo set *during* ibd I wonder if is wise to do ibd with that method, and then apply the utreexo accumulator procedure to the utxo set once it gets created at the end of ibd. The result would be, you only need the full utxo set once during the lifetime of your node: you need it at the end of ibd, and only to construct the utreexo accumulator. After that, you don't need the utxo set, unless you want to help others sync the same way

My phone screen cracked but I can't share a screenshot because it's on the surface so the screenshotter doesn't see it Can phone devs do something

Bart, wake up! They're coming to spam your mempool!

More knotzis should give Floresta a try It's all about filters! ;)

Current state of Bitcoin Core