I was watching one of your videos and was blown away by how many people saw it already!
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn I finally got around to syncing your notes. Pulled in quite a bit from Primal! I don't think @damus has upgraded negentropy though. 
I figured it out. It looks like some of the tokens you received are malformed. Not sure where they came from but I'm pushing out a fix so it moves on gracefully if it can't decrypt the event. Should be ready in 5 minutes.
You can set up a nostr wallet with https://westernbtc.com. I’m still building out most of the functionality. But I have a unique feature where you can receive zaps to your nostr wallet via [username]@westernbtc.com. For example what I have mine set to.
I think this is a perfect way for nostr adoption. Release it on nostr first for a day or two. Release it everywhere else after that if you want.
Right, not powerful enough yet. One day though.
Unimpressive stat: 99.9% uptime.
Impressive stat: longest downtime: 1 hour.
Is the issue you're running into that it's spinning and never finishes when you click decrypt on your extension? I've run into this issue with Gooti where I have to click the arrow next to Allow to Allow Once.
nostr:npub1tgyjshvelwj73t3jy0n3xllgt03elkapfl3k3n0x2wkunegkgrwssfp0u4
My futuristic prediction: our laptops will be replaced by our phones.
We’ll plug our phones into a docking station that hooks up an external monitor, keyboard, etc., when we want the desktop experience.
This will take some digging because I can’t reproduce it yet. I’ll keep you posted.
You're still running into this error even though you have the new extension? Even after you created a new wallet?
If you join https://westernbtc.com, one of the services we offer is a blossom (media) server. Here it is in action 
You won't be able to use any wallet functionality if if you can't decrypt the messages.
It looks like your extension is still having problems decrypting. Are you still using nos2x-fox? I would switch to https://getgooti.com
It should now be scrollable and, in general, better suited for mobile.
I actually just pushed out a change that allows you to bypass the wallet creation part. Let me know if you run into any more issues.
I’ll take a look at it tomorrow morning. I’ve been making substantial changes and adding new features. Still working out the kinks. Thanks for the patience!
I believe nostr:npub194dkgpxl2vk7pqkeualh7sjh5m6rldumh80gm5av0h67d494qzcqum2u20 was trying to do a nip44 decrypt that contained a “+” character.
If they use a credit card in any form, they probably already know.
Discouraging nostr:note1qqqqwp6d8u52qp39ec60m59262zrhvnnftzvl4xmr20umnp92w6svvehth
Oh? What’s the site?
That’s awesome! It’s a paid relay though so you won’t be able to post to it.
Do we need two separate kinds (17375, 10019) for the wallet and mint information? Couldn't we have one event / kind where the content is encrypted and contains the priv key, the tags contain the mints, relays, and pub key?
That way anyone could retrieve the public information from the event, but only the wallet creator could decrypt the priv key from the content.
Never seen this chart before. Block subsidy reward in USD.
nostr:nprofile1qyghwumn8ghj7vf5xqhxvdm69e5k7tcpzpmhxue69uhkummnw3ezumt0d5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5gapjsj nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcqyprqcf0xst760qet2tglytfay2e3wmvh9asdehpjztkceyh0s5r9cpvx58v NIP-17 obviously doesn't work with whitelisted relays because you have to create a random pubkey to send the message.
Could you instead, at some point (maybe when you first follow someone as it's a public event anyways), send a single encrypted message to the recipient intended for the transfer of a symmetric key? That way you could:
1. Encrypt a message using the symmetric key
2. Send it to the relay the pubkey is whitelisted on
3. The recipient's client, probably only checking for that event kind and narrowed to pubkeys they follow) would then attempt to decrypt it using the symmetric keys it's holding
4. The recipient's client would then store the message appropriately
nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzemhxue69uhks6tnwshxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshszyrhwden5te0dehhxarj9ekk7mf0qy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz7qghwaehxw309aex2mrp0yhrq7rrdpshgtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uq3samnwvaz7tmjv4kxz7fwwd5kzmtnw3ezucm0d5hszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcppemhxue69uhhjctzw5hx6ef0qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6cczutgzr is there anything built into the wallet.cashu.me wallet where you can specify a receiving server and check for available "PAID" quotes locked to a specified P2PK? I'm not sure if there's a protocol for that or not. I know you're doing a hardcoded example with npub.cash. Maybe I can implement this feature if that's something you feel should be included. Thoughts?
If you're not already watching, get in here. This is a GREAT live stream with nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qg4waehxw309aex2mrp0yhx6mmnw3ezuur4vgq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qqsgydql3q4ka27d9wnlrmus4tvkrnc8ftc4h8h5fgyln54gl0a7dgsyrcvv9 and nostr:nprofile1qyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qyvhwumn8ghj7um9dejxjapwdehhxenvv9ex2tnrdaksqgqyey2a4mlw8qchlfe5g39vacus4qnflevppv3yre0xm56rm7lveyr9lldz .
Correct! What's easier to do is to not mint the tokens on the server though but to create a mint quote that the user can then mint when they come online. That way the server wouldn't have to store any proofs.
You can use NUT-20 to lock a mint quote to a user key so the server can't rug it: https://cashubtc.github.io/nuts/20/
Another question. If they want to use LUD16 with https://westernbtc.com, I would still need a static public key from them. Would they just update this whenever they don't want mints to be linked together? And as far as not being able to rug them with the quote id for the mint, is there information in the memo of the lightning invoice the payer would need to verify? Or am I supposed to send back more information for that purpose?
Correct! What's easier to do is to not mint the tokens on the server though but to create a mint quote that the user can then mint when they come online. That way the server wouldn't have to store any proofs.
You can use NUT-20 to lock a mint quote to a user key so the server can't rug it: https://cashubtc.github.io/nuts/20/
> lock a mint quote to a user key so the server can't rug it
That was something I felt uneasy about when I was following this process. Glad to hear this is changing.
- 40% chance
- “when I am right”
😂
This is built in to the WesternBtc relay. Negentropy.
Zappy New Years!
I’m out for a bike ride and I realized something.
I think what’s coming for bitcoin is going to be a huge “bitcoin bubble”. Any company adopting the MicroStrategy playbook is going to skyrocket in share price.
I think next year or the year after, we see a blowoff top similar to 2017. Queue the next “Bitcoin is dead” articles. Bitcoin is still the innovation, like the internet was in the dotcom boom.
Wish I could offer some advice but I own no gold.
Yes sorry that’s a bug. Shouldn’t need to put in a referrer haha.