My wife and I are expecting our second child.
I just felt the baby moving for the first time (my wife’s been feeling movement for a few days) and tomorrow we find out the gender 🎉🧡👶
Daniel aka Bitcoin Gandalf
gandalf@btcgandalf.com
npub1ac8q...657s
I tell epic stories about the revolutionary people and events in #bitcoin | Follow me to explore bitcoin's past so you can understand its future.
Zap zappidy zap zap zap 

I'm running 3–4 NOSTR clients between web and phone at any one time.
Anyone else like this?
Am I showing up as verified with the btcgandalf.com domain for you guys?
We have to be aware of the danger for NOSTR to go the way of email.
Whoever is best funded will likely build the best client and everyone will end up on that. If they choose the advertising route to monetise you could end up with a Twitter like experience.
Curious to hear your thoughts on this. 👇🏼
What am I doing wrong here?
Trying to get NIP-05 verified with my own domain.
I've got the domain hosted.
I've got a .well-known/nostr.json file inside my public_html folder at my domain host. The nPub has been converted to HEX format using damus.io/key. The "name" I am using in the json file is GANDALF and then I am inputting gandalf@btcgandalf.com in the NIP-05 identifier field in my nostr profile.
I have followed the instructions to enable CORS by creating a .htaccess file.
But still no verification.
Any ideas where I am going wrong?
I still don't have the verification badge for BTCGandalf.com, do i? 

Still can't believe I tweeted out my NOSTR private key lol
Reminder my old account is now in the public domain.


This is all catching me as I was finishing work and gotta drive now so all rushed but some great memes to come of the situation🤣
Yup, it happened.
I accidentally pasted my private key into a scheduled Twitter post.
I’m logged of Twitter this week so didn’t realise for +45 minutes. RIP my old NOSTR account.