Came here to make the same comment. I love the videos and watch every one of them. I also switched to Knots…even before this op_return nonsense. However, if the transaction is confirmed, your Knots node is going to download and store it whether you chose to relay it or not.

With regard to the ‘attack’, is there some sort of legal distinction between ‘transmitting’ and ‘storing’ this horrific data nostr:nprofile1qqsggcc8dz9qnmq399n7kp2yu79fazxy3ag8ztpea4y3lu4klgqe46qpz3mhxue69uhkummnw3ezum3dw35jumt99uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59up0zady ?

Reply to this note

Please Login to reply.

Discussion

The idea is that Knots filters will deter most spam. Spam would be more common without the filtering. If the spam makes it to a confirmed block, Knots respects the consensus rules and downloads the block, and will relay it when necessary.

(Ligit, non-snarky) Question(s):

In Core 30 are the settings to adjust OP_RETURN size being removed? Are these settings in Core 30 set at max size for OP_RETURN by default with no way to dial them down?

It’s my understanding that the setting is still ‘tunable’ for now, but the plan going forward is to deprecate even that functionality.

Thanks nostr:nprofile1qqsggcc8dz9qnmq399n7kp2yu79fazxy3ag8ztpea4y3lu4klgqe46qppamhxue69uhku6n4d4czumt99uq3gamnwvaz7tmjv4kxz7tpvfkx2tn0wfnj7ru4snc for making this clear in the most recent videos. Relaying this garbage IS the attack. It’s got nothing to do with the nodes ultimately having to download and store it in their copies of the time chain…it’s about distribution. I totally missed this.