Damus doesn't work offline.
Do you want Damus to be the "new client" that publish events on behalf of another keypair?
You mean what nostr clients allow you to generate NIP-26 tokens while being offline right now?
None that I knew of, tbh.
Ok, let's see it with an example:
Initial situation:
- you have a nostr client using a keypair.
- you want to use another nostr client but you don't want to assume the risk of introducing the privkey in the new client.
Here comes NIP-26 to help:
- you log in the new client with a brand new keypair (ideally the new client guides you to create this new keypair automatically)
- you create a token in the first nostr client, signed by the original privkey, that allows the new privkey to publish events on behalf of the original privkey (with some limits: event kinds, time, etc)
- you configure the delegation in the new client introducing the token.
- you can now publish from the new client signing with the new keypair, on behalf of the original keypair (the published event includes the token so that everybody can check that it's allowed)
Does it make sense?
You don't expose it.
You sign the delegation token with the original client where it's installed.
Using Phoenix Wallet
---------------
Easily Send and Receive Bitcoin Using Lightning on Your Phone
---------------
Lightning network payments are a faster and often cheaper way to spend and receive bitcoin. This guide will walk you through the easiest way to get started.
1. Install Phoenix Wallet on Android or iPhone.
2. Run Phoenix and click create new wallet.
3. Click the Receive button to receive bitcoin using the lightning network.
- Click show bitcoin address if sender does not have a lightning wallet.
4. Once you have bitcoin in the wallet you can pay any lightning invoice by clicking the send button.
Full Guide: https://werunbtc.com/phoenix
I miss Phoenix and Eclair here in #nostr.
Anybody knows if they are here somewhere?
π
Lightning Wallets won't be able to read private zaps... until the became nostr clients by themselves!
#[3]
Right. So how do we generate our own keys to use on Nostrgram for example without exposing the nsec?
A new keypair is generated to be used in nostrgram.
Via NIP-26 a delegation token is signed by the original privkey.
That token allows the new privkey to sign certain events during certain time on behalf of the original privkey.
In regions where the internet is slow or unstable, using Bitcoinβs Lightning Network with self-custodial wallets can be a challenge.
That's why I did a review of the best Bitcoin Lightning wallets in rural #Zimbabwe for @BitcoinMagazine
I hear and read statements saying that newbies need convenient, easy-to-use tools, otherwise they would be overwhelmed and wonβt use Bitcoin. I think this is wrong.
People who are being onboarded onto custodial services are harder to convince to step up their game toward financial sovereignty and start using non-custodial tools. There is a big resistance to change habits.
If a person starts using a custodial wallet, they very, very often believe that they are using Bitcoin already. They will tell you that they never faced any problems and that they, therefore, donβt see a need to change their setup.
As a Bitcoin educator, it is my first duty to teach people about self custody, why it is important and to make them aware of the risks they are taking. They need to understand the difference between custodial and non-custodial services.
Only then do I present different tools and make them familiar with the pros and cons of each one. Afterwards, they need to decide for themselves which route they want to take.
That is the only way that people wonβt consider me responsible for any losses they might incur and itβs the only way that they will understand that Bitcoin is all about ownership.
I was unsure, though, if Phoenix or Breez would work in a setting with bad internet connectivity. Thatβs why I set out to do a test in the area of Great Zimbabwe, about 300 kilometers south of the Zimbabwean capital of Harare.
In my review I included @Machankura8333 @MuunWallet @WalletofSatoshi @Breez_tech @ZeusLN @BlueWalletio @PhoenixWallet @ln_zap
I tested @Breez_tech, @ZeusLN and @BlueWalletio on an iPhone and @PhoenixWallet and @ln_zap on an Android device.
For the results please read my article ππ»
https://bitcoinmagazine.com/culture/top-bitcoin-lightning-wallets-in-slow-internet
#[10] made an article recently about the experience of using Lightning Wallets on countries with slow mobile networks, mostly in Africa, were she's living lately.
I think we have to work harder to excel both LN UX and #nostr UX on those places with slow and/or expensive mobile networks.
We (westerns) use to forget the big difference in connectivity in different places of the world.
Lots of work to do!
π«
#[3]
Precisely today #[7] from #[8] was asking for ideas to implement next.
cc.'ing them in this thread.
That could actually make people to be more aware of their financial privacy, I think.
Oh!
That exactly was the vision on Rusty's first vision of Lightning Offers / bolt12!
But recurring payments function was discarded for now, afaict.
They can be implemented in higher layers in wallets of course! π
#[2] . He's one of the early nostr developers. He's not very active on nostr right now, but he could add his early vision on developing the protocol.
What about getting the zaps information from the nostr events to enrich the transactions history screen?
(Sender/receicer's name & pfp)
#[1]
Why does it need to verify a new identity?
Why doesn't it work with nostr identities/keypairs?
This is something that I also don't understand, why doesn't it use nostr pubkeys?
While waiting for #[3] to publish the final version, here's the not-final one:
**New Nostros Release [v0.3.0.9-alpha] Private Bookmarks**
**What's Changed**
- Private Bookmarks
Now users can decide to add notes to a public or private list of bookmarks
)
)
- User public bookmarks
User's public bookmarks are available in the profile view.
)
**Changelog**
* Private bookmarks by @KoalaSat in https://github.com/KoalaSat/nostros/pull/382
**Full Changelog**: https://github.com/KoalaSat/nostros/compare/v0.3.0.8-alpha...v0.3.0.9-alpha
https://github.com/KoalaSat/nostros/releases/v0.3.0.9-alpha
**Download**
Markdown... ππ
usernames > display names
Either way, I agree that something has to be done.
That doesn't make sense:
