Filters didn't make it cost more...
I don't even own a suit. And my watches are all really cheap casios and all my cars have utility. Except the Prelude. I have that for fun. Tbf I bought it for only $2700 and it was my daily for years before getting the truck. Got the truck for only $2800 😉
Proud of that.
98 Honda Prelude
98 Chevy K1500
I've put more money in them now than what I spent on them, but all of it combined is still twice as cheap as most people be spending on their cars now. Cars are fucking ridiculous. The biggest wealth killer in this country hands down.
Look into grain please!
It's the only thing I use daily besides nostr...
It's time grain relays got their own keys.
NIP29 on grain?
Yea. I figured that.
Ask all the people that stopped using nostr because they thought primal was nostr. I swear everytime I hear a detractor it's something about signing up with primal and being confused as of that's all nostr is.
Nostr itself can't implode. Primal might one day though. I don't see how they're profitable but maybe I'm wrong.
GM ☀️
Dew on the Bermuda sounds like a good name for a country album
So for grains client I have client relays separate from user relay lists (nip65) much like nostrudel HT nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr but on login the client relays are auto set from the users nip65 list. From there the user can pick and choose relays to interact with the client and it's separate from their actual list. Would it be a good idea to limit the client relay list to 5 relays max? and a notice to the user that they should consider taking some relays off their mailboxes if they have a bunch? or should I let them have a bad experience when they have a million relays in their list?
Filters don't matter. Economics does.
https://mempool.happytavern.co/tx/58ae7a318f19c580b14d3547d6c65d1a417bbe8980189d34c61b2d4161741dfb
nostr:npub1zsyt45zfh2u28zuhvp66lljp8s6jrwlw7ckvfn34255e7jt37t9qx0xwsm but muh filters
This was not out of band. I sent from my node directly to the network. I didn't "pay extra" I simply paid more than anyone else was paying at the time it was confirmed.
Dust tx in the OP_RETURN is also filtered by like almost all nodes. yet it was still confirmed at 1s/vb...
I HAVE NO INTEREST IN PUTTING DATA ON BITCOIN. I MAKE THIS TRANSACTION AS AN EXAMPLE ONLY. My reasons for removing filters is not to be able to put more data on chain, because as demonstrated, I can already do that. I have no interest in inscriptions. I have no interest in all the motives detractors will try to apply to me. My motivation is to remove paternal aspects from Bitcoins codebase and make it more maintainable. Filter exists to ensure users don't make unintended transactions, not to stop consensus transactions from getting confirmed. In that sense, things like the dust filter are probably good. And again, if we can fix witness stuffing, I'm all for it.
I'm saying my statement shows why filters don't work and are unnecessary.
proof: https://mempool.happytavern.co/tx/58ae7a318f19c580b14d3547d6c65d1a417bbe8980189d34c61b2d4161741dfb
It may be the glue that binds everything together but it certainly not for plebs to self-custody cheap bitcoin payments
No man I'm a bit technical and I got to say I think lightning is kind of broken
It's for corpos to make money routing Bitcoin payments for plebs.
I might would buy one.
How well connected is your node? Or what custodian?
Okay zigbee or matter? #asknostr
Also ALL versions of core currently have the default filters still. Including OP_RETURN limit at 80 bytes
There is no version of core that's released that has a higher limit.
yea but... they don't....
GM 😚 ☀️
"Firey but mostly peaceful" has got to be in the top 10 phrases that eximplify this clown world to come out in the last decade. What are some others?
#asknostr
I have viewpoints on abortion I would also impose. I'm sure you hold viewpoints that you think should be imposed.
Public shame for bad things is good. You don't have a problem with imposing that you can not murder and rape... How does society look at pedophiles? They're pretty publicly shamed as they should be. Right? Now I'm not saying parents of obese children are equivalent obviously. I'm just providing and example of public shame and a viewpoint you would also impose.
My nuanced take:
I'm in favor of removing mempool filters from Bitcoins code base.
I'm also in favor of a fix for witness stuffing if possible.
Arbitrary data should go in OP return where it is meant to go. And people should pay the normal fee based on the weight of that transaction.
Now that grain 0.4.1 is released, should I switch gears back to nostr hero? Or should I add blossom to grain, so that it's a relay and a blossom server?
Negatives also include appetite suppression. At least for me since I only weigh 115 anyways. I guess it's a positive if you're trying to lose weight.
They did leave them. Core 30 is not out yet but when it dies come out it will still have all filters. Todd's PR was not merged. Default limit for opreturn will be raised to make it basically unlimited. You can still set your own limit in your bitcoin.conf to whatever you want. Also opreturn is the only filter in question here. All others Policies remain the same by default I believe. Policies and defaults exist for making sure users don't submit unintended transactions. They don't exist to stop anything from being relayed.
Because it doesn't matter... That's the whole point. We don't need code in the code base that doesn't do anything.
There are very few because they don't make any sense financially. Do you want me to submit one now to prove you wrong send me 5K and I will just like I started this conversation with.
You started at 70 now it's at 90? Tell me the magic number where the filter start to "work"
How are you not understanding that filters only affect your node and not the network.
Yes, they blocked them. On THEIR NODE. They did nothing to prevent it from being mined. They are concensous, non standard transactions.
again... you can make a a tx with less than 1s/vb fee already and always have been able to...
You are incorrectly attributing the blockchain's transaction patterns to Bitcoin Core's default mempool policies. They think the blockchain 'reflects' these filters because the filters are actively preventing bad transactions from being included.
This is backwards causation. The mempool policies are purely local settings that only affect what transactions your individual node will relay or store in its mempool - they don't control what gets mined into blocks. Miners can set these filters to whatever they want, or ignore them entirely.
The real reason the blockchain resembles the default policy settings is much simpler: most people naturally create valid, reasonable transactions anyway. The blockchain looks 'clean' not because the filters are working to keep it clean, but because there wasn't much junk to filter out in the first place. The filters are largely redundant - they're rejecting transactions that most users wouldn't create anyway.
No... Witness data gets a discount on its weight. OP RETURN doesn't. That's not a filter thing, that's not a policy. That's just how Bitcoin works. Filters have nothing to do with it.