by "built on bitcoin" I do not exclusively mean "built on L1"
I'm asking for apps or protocols people want to see on *any* bitcoin layer but aren't sure it's possible
I'll also expand it in this way: also post if there's something you want to see and you are unsure why no one's currently doing it, or if you *do* know someone who's doing it but you don't like their approach
I wonder what feature of bitcoin a dating site could use? zaps instead of pokes? idk
one of the things I like about cashu is that it's really easy to self host, and if you do that, it's *not* custodial
every feature someone builds for cashu is a feature you can use self-custodially by running your own mint (which is easy to do because they are lightweight)
but you can *also* use it on someone else's mint if you accept the trust assumptions
so no, I don't think it's unwise, I think it gives people options
If there's any app or protocol you want to see built on bitcoin, but you're not sure it's possible due to bitcoin's limitations, post it in this thread
Cashu is an awesome project, I especially recommend it for developers new to the bitcoin space who want to do something meaningful and fun with a small learning curve https://github.com/cashubtc/awesome-cashu
Someone told me a government shutdown means they stop providing non-essential services. So why don't we just "always" do that? Sounds like a huge cost savings!
Turns out, they somehow manage to spend more money "not" providing those services than they spend "providing" them 
miners be hashing
5 blocks in 8 minutes seems pretty fast 
I don't think you need fast read access to the utxo set after IBD, because you have an average of 10 minutes to validate new blocks and that's enough time to do it with slow read access
*during* IBD, I think it's a different story. But even there, MergeSync looks promising. It lets users download the blockchain first, without validating changes to the utxo set, and then *afterwards* efficiently extract the utxo set by creating an array representing all tx inputs ever used in any transaction in any block (in the format txid:vout) and injecting into that same array all tx outputs ever created (in the same format), and then removing all duplicates. What you're left with is the utxo set, without needing to update it *during* IBD.
combining these two ideas, I think you can run a fully validating node without fast read access to the utxo set, i.e. with low ram requirements. Just use MergeSync to do IBD, and after that, slow read access suffices
> or apply filter parameters blindly from a centralized platform
yeah, that sure sounds like knotsis
your typical knotsi would never willingly stop using the default software and run something nonstandard instead -- definitely not
> sounds like you do indeed think that having a wild west type situation where people could apply different filters to their mempool is the preferable condition
You act like that's an unusual opinion. Boy, are you in for a surprise if you ever read bitcoin core's policy.cpp file
https://github.com/bitcoin/bitcoin/blob/master/src/policy/policy.cpp
I'll give you a hint:

> the end user isnt figuring out what the necessary parameters are to filter
Wow, you sure know a lot about people you don't know
> they are getting them from somewhere and calle is totally correct they must be updated regularly
Calle said they must be updated "every single day" AND users have to download them daily. And this is an obviously absurd position, do you have to download adblock every single day? No, only when it stops working.
I don't know what you mean by centralized authorities with custom filters
do you think everyone who writes a piece of software is a central authority? if someone makes a thing and puts it online for free, and users say "hey, that does a thing I want, I will run that" or "nah, I don't like it, I won't run it" <-- there's no central authority involved
The post's central thesis is that updating your filters cannot be done in a decentralized way, and he cites adblockers as an example
This thesis is wrong and adblockers prove it. Adblockers that don't do what users want are ignored and their usage quickly drops to nil
His post also contains several other blunders, like "The goal of this change is not to help transactions to slip through more easily" -- it literally is. The motivation for the change is to invite spammers to use op_returns. Most of whom explicitly say they don't want to use op_returns.
He also presents a false dichotomy at the end of the post, asking why his opponents even care about bitcoin if they think spam can kill it. As if somehow the people who welcome spam care about bitcoin and the people who fight it don't. You can like bitcoin *and* fight spam on it via filters.
Sounds like you're in danger of falling for the "just use monero" meme. Your post acts like it is far easier to use monero privately than lightning, but you may not have considered the following difficulties:
- You're supposed to run a monero node (not a phone wallet)
- You're supposed to hide the ip address of your node or wallet by running that software behind tor/i2p/vpns
- You're supposed to avoid reusing monero addresses, or even reusing a monero *wallet*
See these quotes from getmonero.org:
"To prevent the payer from linking your payouts together [you must] generate a new subaddress for each payout. ... If you need perfect unlinkability of your receivables, the only solution remains to use a separate seed (separate Monero wallet)." source: https://docs.getmonero.org/public-address/subaddress/
“It's always advisable, especially for privacy-conscious users, to use a personal node when transacting on the network to achieve the highest rate of privacy.” source: https://www.getmonero.org/get-started/faq/
“Some dangers can be mitigated by using remote nodes on the Tor or I2P networks or using a VPN.” source: https://www.getmonero.org/get-started/faq/
By contrast, you've said you can just post a monero address on stacker news and be protected. But where did you *get* that monero address? Did you set up a node first? Did you just download Cake Wallet and hope their software isn't logging your monero address and mapping it to your IP? Did you turn on tor first? Are you doing anything to avoid address reuse? Are you creating a new wallet for each payment?
Privacy is very hard, and it's a trap to fall into thinking "Oh, as long as I just post a monero address somewhere, my privacy is protected by default." No it isn't.
By value I mean the value field in bitcoin transaction outputs. So nfts don't qualify
