And it will be in mine... Do you get it?
What do you mean now I get it. I don't think you get it at all. What do you think I just said?
So it's both. Idk man I didn't have recipts on my server but I sure felt like I was getting zapped when people sent me Bitcoin using the address on my nostr profile.
Again... Completely out of your depth. The mempool is informed by YOUR NODE not anyone else's...
Is a zap a receipt or a payment?
I just think the payment part is the zap. A receipt didn't feel like a zap.
Not my node. I want an accurate picture of the mempool when I make a regular transaction.
What are you not understanding... OP RETURN data is more expensive than witness data. Doesn't matter how many bytes...
I don't spam Bitcoin.
Yes... They can. It's more expensive. And not because of filters. It's because witnesses data gets a discount.
You are the one looking more silly sir.
So the receipt is the zap and not the payment.
Interesting.
If I use someones nostr lightning address to fetch an invoice and pay it, is that a zap? Or is it only a zap if the LNURL server provides nostr support and receipts? Because in my mind if I make a successful lightning payment to a nostr user, that's a zap regardless of a receipt. But correct me if I'm wrong.
firstly, They DIDN'T remove them. The default limit was changed to like a million bytes or something. Basically no limit. You can still set a limit just fine with core. Even when 30 comes out.
secondly, if and when they DO remove OP_RETUN limit it's just the OP_Return limit. All other policies remain. policies generally exist to make sure the user doesn't fuck something up and make a bad tx. It's not for making sure the network doesn't get the transactions.
I actually don't run core or knots, but I do run a node. I'll let you guess the flavor. It's one that doesn't have any policy restrictions for anything. I can make whatever transaction I want to with my node.
no... I just told you why. It's not filters at all. OP_RETURN doesn't get a discount, witness data does. So rather than putting arb data in OP_RETURN, you stuff the witness with it. This makes more unspendable UTXOs (bad for Bitcoin). Removing the limit does not stop this either. I don't have any ego man. I'm just arguing facts and you rebut with arguments that fall flat or don't make any sense.
What? You can set policy however you want to in core? WTF are you talking about. Every node, no matter what flavor, further decentralizes the network...
You are really confused my guy.
Because it's cheaper to stuff the witness with arbitrary data.... You are arguing out of your depth with extreme conviction...
Strong Mac vibes.
Email is extraordinarily centralized. You want that for Bitcoin?
Email is not Bitcoin. I won't entertain the argument. They're not even close.
Core has not made a new release yet... 29 is still the current. Removing the limit will not increase spam because the limit never stopped "spam" to begin with.
The limit is still there on all nodes currently by default, yet, I can still make a tx with one beyond the limit...
You want to "fix" it, then roll back to 2014 and remove OPRETURN and the Segwit discount. That's a hard fork. It's not happening. Running knots is just a virtue signal, not a solution. It does nothing.
your second point is wrong... again...