>Arbitrary is different to illegal. I see you recognise that. How the data is viewable on chain is important, right? Is it easily extracted/viewed? Or does it require special tools to decrypt/compile?

why is that relevant? let's take the CP argument. do you really think that an argument would make sense in law where someone says "no your honor, you see, the data is actually rot13'd, there's no raw CP"... like come on haha

> Just because something has been done in the past doesn’t mean we have to accept it moving forward.

it actually kind of does. actually removing the ways to achieve this would make bitcoin literally unusable. Even if bitcoin got limited to only a simple database where you can send and receive money to addresses, you could still encode that data in the address.

This may look like an npub, but it's actually a rickroll: npub1dejhvetjypnk7mnwvysxw6tkv5s8jmm4yp6hqtpqdejhvetjypns3hyxs3, filter this please.

> sentiment out there is that there are changes possible that can, as a minimum, restrict CP. Can’t imagine there are any arguments against that being persued.

of course, nobody wants CP, not knots and not core. But how do you restrict it without also limiting REAL spending transactions?

> And whilst you’re there, discuss winding back those other changes that the community has since determined detrimental to the MONEY use case.

datacarriersize doesn't impact money use cases, in any way. if anything it HELPS WITH MONEY, because your node can go by with less data actually stored in its UTXO set. putting data into OP_RETURN instead of UTXOs literally makes YOUR NODE FASTER.

damn I missed an opportunity! pretend the npub was npub1yqsxsar5wpen5te009hh2ar49e3x2tmy29mngaee2an4sc63yqsqmgmsk0 much funnier!

Reply to this note

Please Login to reply.

Discussion

No replies yet.