pull down to refresh

The biggest barrier to bitcoin adoption is time, and there's not much we can do to speed it up.
Here's my theory. In any given generation, there's a small, roughly fixed percentage of people whose brains are wired to "get it" on contact. Bitcoin spread like wildfire from 2012 to 2017 because we were burning through that pool fast. Ever since, growth has looked more organic. Not because bitcoin got worse at convincing people, but because the easy converts were already converted.
The good news is that this pool refills with every new generational cohort. Combine that with the economic darwinism of having to choose where to store your value over decades, and we win by default. Fiat doesn't have to lose dramatically. It just has to keep doing what it's doing.
So the barrier isn't education, regulation, or UX. It's just time.
What about the "alerts" feature? does anyone think it would be a good idea? and if so, I was thinking on how to do it, two options I've been considering are:
- Email based, you enter an email, get sent a confirmation email and then are allowed to add alerts
- Nostr based, you sign in with NIP-07 and then place your alerts, which would be delivered as whatever messaging format nostr clients prefer these days (gift wraps?)
Thanks for the advice. But for now this is client-only, so if an event gets dropped by relays the order will just not show up and there's nothing I can do. I am thinking of adding a server-side component to this though, so that might be tackled there.
The problem I noticed just now however is the opposite, hodlhodl events seem to remain stale there.
Thanks for the reply, interesting points! I think to scale past the current 1-to-1 architecture I'd need to set up a video streaming server. The payments can still remain something peers exchange directly.
Right now the mint is hard-coded. I wanted to get it out there as fast as possible, so certain features had to wait. The next thing I plan to add is support for users to chose their mint from a list of curated ones.
No, it's loading here.