There is a reason to tolerate spam in the blockchain: ejecting it requires a large amount of hashrate, and the cost is too high But the same reason does not apply to your mempool: ejecting most of it is easy, and the cost is low

"The law meant to prevent drinking in the parks does not prevent drinking in the bars. Therefore, remove it!" "The ordinance meant to prevent loud music in the library does not prevent loud music in the nightclub. Therefore, remove it!"

"The filter meant to eject spam from your mempool does not eject spam from the blockchain. Therefore, remove it!" "The policy meant to eject students from the staff lounge does not eject them from the school. Therefore, remove it!" Same energy

If you want your coffee maker to stop coffee grains from entering your coffee, and it doesn't, that's a technical problem. Coffee filters help. If you want your mempool policy to stop spam from entering your mempool, and it doesn't, that's a technical problem. Spam filters help.

Future me: you want to run a node? Great! There are 2 main kinds: Core and Knots. The main difference between them is how they approach spam. Core takes a welcoming stance toward spam transactions, whereas Knots filters them out as much as possible. Which one do you want to run?

Click here to try them:

My latest invention is the Bip157 Playground. Learn what bip157 filters are, play with them, and consider using them in your next bitcoin privacy project -- all from the comfort of your web browser.

Yesterday, on Rearden Code's podcast, we had a productive discussion about the Spam Wars My favorite clip is this, where he concedes that filtering spam would be a good idea *if* a user wants their node to help relay txs as a public service Full episode: https://t.co/plQdDBZ3HB

In case this is confusing, I've written up an explainer here:

I've made lots of progress in my quest to make a bip157 browser wallet! Thanks @guggero for serving bip158 filters in a web-friendly way at https://t.co/LXKhtFZEMl, and thanks https://t.co/vrA8QE0deH for providing libraries that let me parse them. Most of the hard parts work now!

I'm very happy to say: It looks like one of the Ark teams has finally launched a publicly available wallet! https://t.co/bL7OPxj1v2

Finally, the uint8array format in javascript natively supports hex encoding

Join me and @SuperTestnet to talk about bitcoin in 2.5 hours! https://t.co/9VzE1bpUFq

TIL bitcoin has a native REST interface for public blockchain data. Sadly, I don't think anyone enables the rest interface AND exposes it to the public internet AND sets a browser-friendly CORS policy If you know someone who does, share their node's ip address and REST port here

Hey @blyssdev any thoughts?

This block explorer used to use a variant of Oblivious Transfer to stop the server from learning user ip addresses while still allowing them to query about the balance and tx history of any address It doesn't seem to work anymore Is there a github? Could someone relaunch it?

I'm on a quest to build a browser wallet based on Bip157, Compact Block Filters. And I hit my first roadblock: I can't find any servers that serve compact block filters with a web-friendly interface So I've opened an issue on electrumx. Please support it!

The privacy section of bitcoin's white paper applies to lightspark If you avoid linking your identity to your pubkeys, then you have pseudonymous privacy It is also wise to avoid sending to the same pubkey twice, and if you do so, you still should take steps to manage cospends

Folks like Rearden should understand they don't get to define what your node is for You signed no agreement saying you would relay other people's transactions If you want to relay some of them and not others (e.g. spam), that's your prerogative Even if some folks don't like it

비트코인 셀프 커스터디와 관련한 엄청 흥미로운 아이디어. 비트코인 보안 서명 레이어, B-SSL. 백서 내용 llm 요약. 백서는 글타래에 있는 깃허브 링크에 있음. --- 이 문서는 B-SSL(Bitcoin Secure Signing Layer)이라는 새로운 비트코인 보관 구조를 소개하는 기술 백서입니다. B-SSL은