pull down to refresh

500 sats \ 4 replies \ @lightcoin 27 Oct \ parent \ on: "Running a Bitcoin Full Node Requires Storing Child Porn" -- Nope. bitcoin
Now
always has been
write
preview
0 sats \ 3 replies \ @fourrules 27 Oct
You're just ignoring the responses to that thread. I've heard all of the arguments that responded to that, so I know you have.
reply
0 sats \ 2 replies \ @lightcoin 31 Oct
I didn't ignore any responses to that thread. Quite the opposite, I actually responded to every critical or questioning reply, because the goal of the thread was to educate. If you see a reply you think I missed, please link to it and I will respond to it.
Now I have some questions for you:
Has it, or has it not, always been consensus-valid to embed up to ~1 MB of data using OP_RETURN?
Has it, or has it not, always been consensus-valid to embed up to ~4 MB of data using witness envelopes?
c52f39725a1c62b36a1a47ebdbeabf2b7ce84d381c600fab9241ca437d51fc32
reply
0 sats \ 1 reply \ @fourrules 31 Oct
Policy matters
reply
0 sats \ 0 replies \ @lightcoin 31 Oct
Has it, or has it not, always been standard to embed up to 10,000 bytes of data using segwit witness envelopes and up to 400,000 bytes of data using taproot witness envelopes?
reply