What app did you use?
Mined on the phone, or you delegated the mining to another device but signed from the phone?
Try Oak Node on Umbrel. You can view and re-view the NWC QR as many times as you want.
AFAIK Alby shows only once the NWC secret (and QR code), when you create it.
We just need a way to let clients easily buy some of this cheap computing power to add PoW to their notes.
Mobile clients are limited in how much PoW they can mine.
No simple solution yet for them to delegate PoW to 3rd party.
I'm working on a solution for that. Tentative spec: https://oak-node.net/file?name=doc/ons/ons-2.md&ci=trunk
nostr:npub1zg69v7z7u7q4w5wzsqzwdnh58x8py4hef2fm750eqqvw9zkvh76q4yjdwv
não estou a conseguir enviar-te sats em vários clientes nostr.
"Error: failed to retrieve zap endpoint :("
Corrigido! Obrigado
True. But they need extra logic that checks if a relay is misbehaving in the first place.
I think he means relays who don't play by the rules.
A malicious relay coud:
- send the same message(s) multiple times
- send extra messages that don't match the filters
- do this both for stored events (pre EOSE) and for streamed events (post EOSE)
IMO its a viable attack vector, because clients have less resources so by doing the above, a relay could DoS a client.
Even if unexpected events are "filtered out" by the client before showing them to the user, the client still presumably verifies they're valid events, and signature verification is quite intense. So unexpected large events are also an attack vector, they can hit the client CPU hard.
Nostr SDKs used in clients could defend against most of this by
- only returning events that match the subscription filters
- only validating if an event is valid (signature) if the above is true
- not processing and returning events that have already been seen before (much harder to do)
cc nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet
Probably not a concern now, because Nostr is small.
(Another defence for clients is to use a semi-trusted relay aggregator like Wine or caching service like Primal)
I think he means relays who don't play by the rules.
A malicious relay coud:
- send the same message(s) multiple times
- send extra messages that don't match the filters
- do this both for stored events (pre EOSE) and for streamed events (post EOSE)
IMO its a viable attack vector, because clients have less resources so by doing the above, a relay could DoS a client.
Even if unexpected events are "filtered out" by the client before showing them to the user, the client still presumably verifies they're valid events, and signature verification is quite intense. So unexpected large events are also an attack vector, they can hit the client CPU hard.
Nostr SDKs used in clients could defend against most of this by
- only returning events that match the subscription filters
- only validating if an event is valid (signature) if the above is true
- not processing and returning events that have already been seen before (much harder to do)
cc nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet
Probably not a concern now, because Nostr is small.
(Another defence for clients is to use a semi-trusted relay aggregator like Wine or caching service like Primal)
Check out NIP-10, it's written exactly to explain this.
cashu-lnurl looks like a quick and simple way to do offline receive. Though you have to trust the provider. And you get the sats as cashus.
Am I right?
The Gossip client is shaping up!
Just started using it again after a couple of months and:
- now it has proper support for DMs
- UI is much faster, almost instant
- UI is much slicker
It may just be the best desktop Nostr client yet 🤔
What hardware specs? Looking into CLN too.
40 bits, that's awesome!
Those gaming PCs are starting to look quite appealing now :)
Would you be interested to help me test something out? It involves nostr, PoW, Rust and generally many CPU cores.
I haven't tried Mutiny Wallet yet. I do use Phoenix, but not for zapping, mostly just for collecting DCA funds. I am still using the custodial Alby + Zeus combo for zapping, similar to what you have. Just looking around I think there will be a lot more solutions soon, I'm looking forward to Green from nostr:npub1jg552aulj07skd6e7y2hu0vl5g8nl5jvfw8jhn6jpjk0vjd0waksvl6n8n adding lightning support, that will finally push me over the edge to buy a Jade 😂
Mutiny is better for zaps 💯 It supports NWC https://github.com/getAlby/nostr-wallet-connect It is also beta, so beware dragons 🐉 Follow nostr:npub1t0nyg64g5vwprva52wlcmt7fkdr07v5dr7s35raq9g0xgc0k4xcsedjgqv to stay up to date!
Phoenix is not good for zaps, no NWC. As a self custody wallet for any other use, I think it is great! I use it to collect DCA payments, and have processed a lot of other transactions, seems quite reliable.
nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 wen NWC?
A bunch of nostriches are already making noise about it:
nostr:note1vt0huymywhlwwl08y3rn8xta95cjlxgd5u6eatqup5x54ncd2t3s40ps77
nostr:note1s6shzsna6m2yrr6rgvldz88erx004zytn2gnayccv45vedj6ntrq5k5yjn
nostr:note1vc4mctnprancd4surtmp0pg0qcwh3ggd7kaxl038aw8lz4ml9uesrdxp8n
See nostr:npub1wxl6njlcgygduct7jkgzrvyvd9fylj4pqvll6p32h59wyetm5fxqjchcan and nostr:note1qqq8pgp23k394cukg4w9mgfjh54z9jhyjukqan582rkks36rhs5s620vev
Quick, get the Nostr CEO on the line!
nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz nostr:npub1wxl6njlcgygduct7jkgzrvyvd9fylj4pqvll6p32h59wyetm5fxqjchcan
Great minds think alike ;)
nostr:note1qqq8pgp23k394cukg4w9mgfjh54z9jhyjukqan582rkks36rhs5s620vev