I don't understand why we give everyone a wall by default. This still allows for everyone to build their own wall as high as they want to. It just makes the default no wall. Making the repo more maintainable and putting the whole debate over how high the default wall should be.

Reply to this note

Please Login to reply.

Discussion

Thanks for your summary. So, how does one go about re-adding the filters? Is it easy?

Not particularly. But it is easy to run a concensous forks like knots that has the filters in it. So if you would like to filter your mempool, then you can easily run knots.

So in the current bitcoin software, these filters are available, but not turned on?

They are available and some are turned on as we speak

Some, but not others?

No they are all on, it's just a matter of the thresholds. By default the OP RETURN data can hold 80bytes of data. You can raise or lower this limit. The PR is to remove it entirely. If they do, you can still run a node with whatever limit you want and you would still be in concensous.

Thanks. Does pruning remove this data by default?

No. Pruning just removes txins up to a certain checkpoint that you define. It doesn't care what's in them. But also this is for mempool policy. ie transactions that have not yet been confirmed. Once a txt is confirmed, every node will store it. No matter what their mempool policy is