pull down to refresh

0 sats \ 7 replies \ @optimism 9 Oct \ parent \ on: List of technical people against relaxing the OP_RETURN filter bitcoin
It must suck to so desperately need a tree to bark up on, that you have to resort to this tree. lol
I'm supporting code review. Have you done code review, brother? Have you at the very least read the release notes? What's the non-configurable change and how is it controversial?
write
preview
0 sats \ 6 replies \ @sudonaka 9 Oct
Make sure you mention all that to the jury for the cp distribution trial, Iā€™m sure they will understand.
reply
0 sats \ 5 replies \ @optimism 9 Oct
Oh I'll be on trial? For something I didn't do? Imma be one rich mf!
reply
0 sats \ 4 replies \ @sudonaka 9 Oct
If you relay CP to other nodes then you would be doing something. Keep laughing buddy!
reply
0 sats \ 3 replies \ @optimism 10 Oct
How does whatever you run right now protect you from this?
reply
200 sats \ 1 reply \ @standardcrypto 11 Oct
don't feed the trolls šŸ™„
reply
0 sats \ 0 replies \ @sudonaka 11 Oct outlawed
stackers have outlawed this. turn on wild west mode in your /settings to see outlawed content.
0 sats \ 0 replies \ @sudonaka 11 Oct
We dont relay (before confirmation) op_returns larger than the filter we set.
If you update to v30 then you will relay any op_return that fits in the block.
It might never be mined, just circle around mempool until expire, then they could send it again
reply