I'll have to try this this week π
Google is removing self-custodial wallets from app stores worldwide.
We anticipated this and began building a self-custodial web wallet you can access anywhere β no app store required.
Now with light & dark mode for your viewing comfort.
Weβre still early in developing our self-custodial web wallet, and we want your feedback.
Try it out, break it, and tell us what you think. Every click helps us make it better.
https://wallet.blitz-wallet.com
#Bitcoin #SelfCustody #BlitzWallet
Just tried downloading from Zap Store, bundle is 290MB vs 40MB on Play Store. What's the difference?
"If you've been in bitcoin for 9 years, why are you still working?"
https://blossom.primal.net/65caee592a467e437319e603aa88637a37455c0f71f7fe39896f4ef3f35e2d28.mp4
What's the minimum stack size for someone to stop in your opinion?
Lol here you go, nostr:nprofile1qqsy67zzq5tc9cxnl6crf52s4hptdwhyaca5j7r8jwll535tdadedvcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wd3skueqpzpmhxue69uhkummnw3ezuamfdejs2sh6m6 was really unhelpful with the source for this one π
Ok one step closer, deleted X from my phone, can only reach it via browser now, and I rarely ever bother to log into things in the browser π
Are nostr:nprofile1qqswq087qywczsjtkc9p960tpjcvn35gcdr39smefsr49cr33vmfausppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgdwaehxw309a38yc3wd9hj734nsuz fedimints a thing as yet? It seems like cashu style ecash is so much further along user-wise now
Maybe we don't actually need a bunch of little federations for every community. Just one or two well-resourced Liquid Federation style mints that are widely available
It's sort of what we learned with nostr:nprofile1qqsglefmxagcu0d7nw4jdkgj9ysqrk9cst0fg44hkz9kzhu39hyt7jspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp06t72j0 where our original vision was trying to help communities setup their own wallets. No-one really wanted that though, everyone just wanted to use the Blink instance, and in the end we mostly ended up working less in stack re-deployability and more on in-instance end-user-facing features
Curacao has a really active community on https://btcmap.org/community/btc-curacao
> fee is not calculated based on what you have on your mempool that's not correct. even core is using more advanced methods to estimate fee. its just an argument
I'm sorry, you must be joking
In core, fee estimates are calculated entirely from the mempool. This isn't even up for debate, it's literally in the code.
- The `TxConfirmStats` class ([here](https://github.com/bitcoin/bitcoin/blob/8309a9747a8df96517970841b3648937d05939a3/src/policy/fees.cpp#L77)) builds buckets of mempool transactions based on fee rates and then analyzes how long they take to be mined.
- If you unravel `TxConfirmStats::EstimateMedianVal` ([here](https://github.com/bitcoin/bitcoin/blob/8309a9747a8df96517970841b3648937d05939a3/src/policy/fees.cpp#L244)), the code scans buckets of stored feerates built **from the mempool** and gives you the median feerate for the bucket that most closely matches your confirmation criterion.
It's the same for other estimators as well. We rely primarily on the mempool.space estimator in the `bria` engine we use for Blink ([here](https://github.com/GaloyMoney/bria/blob/018f25b52f991886f1c6ee9713cee4ee641e8187/src/fees/client.rs#L23)) as it's the most reliable we've found from years of observed transaction activity. And if you go to the mempool.space repo and look at how they do fees, `getRecommendedFee` is called ([here](https://github.com/mempool/mempool/blob/cba4308447341725587c232f77c102efc834d488/backend/src/api/fee-api.ts#L22])) which if you follow the code uses mempool transactions and projected mempool blocks to estimate fees.
I think this is the issue lots of us are having with this "debate". Lots of things are being said that aren't even subjective, just objectively wrong.
Big miners have been and are going to do this anyway regardless of what nodes want, because nodes already accept much larger OP_RETURN sizes in mined blocks
... nodes already accept much larger OP_RETURN sizes in *mined blocks* ...
This change *is not* about changing about what nodes accept in blocks (consensus)
It's changing what nodes gossip about pre-block
It's saying that if nodes ignored the gossip, then folks will just tell the miners directly at a higher cost that they are so far happy to pay (shitcoin economics, see BRC20 vs. Runes)
"Core" is saying that pretending to not listen to gossip when you're going to accept the block anyway does not meaningfully stop spam, but it does affect miner centralization
Ironically, the only thing "Core" is forcing is a change that would actually hurt miners by reducing preferential miner fees and opportunities for miner centralization through degraded block relay
Ironically, the thing they are forcing is better for decentralization (accurate mempools, predictable fee estimates, less miner centralization pressure)
____
These are the arguments as I understand them so far, but I do agree that communication was handled poorly and that they should never the option to configure in and not force a single setting on nodes
But I also agree that the default should help decentralization and network health. So I agree that raising the default size of OP_RETURNs that nodes *gossip* about with an option to configure is good, given that there is already a much larger limit nodes will already accept in mined blocks today
None of these are consensus changes that can result in any sort of fork though. Nothing here changes what a valid mined transaction is. So comparisons to blocksize war don't really make sense to me because it's not the same game theory at all
More of this sort of conversation/clarification, and less of the X-style screeching past each other ππ½
Same, because otherwise make it make sense π
Android, would to check that out
Is this possible from any clients today? Who supports ecash zaps? (cc nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5)
Can zap as little as 1 sat, there's no-one on nostr who can't afford that... it's not all about money, it's about sending a message
Iβm getting really excited about all the possibilities that Nostr brings. Just wrote a blog post on the topic here:
https://www.awhb.dev/blog/nostr-how-it-could-change-the-world
I'd love to zap this note
The vibe on here is so much more sane than everywhere else right now ππ½
Wouldn't mind seeing some of the insights from this if you end up sharing
nostr:nprofile1qqsrpl96thl42ve0gsah63ypz75uunzpgfrd0g2x8nry4ggtef6crdgpzfmhxue69uhhqatjwpkx2urpvuhx2ucpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgawaehxw309ahx7um5wghx67t0wahxgctddehx7er99e3k7mgljk58c *finally* on here, and for all the expected reasons π
I did not realize Danny continued with WBD π₯
There's also this perspective, which if valid would have had me ignoring these questions too
https://www.politico.com/news/2025/01/08/wildfire-threatens-karen-bass-extended-honeymoon-00197228


