Nostr Web Client

Hm... Tried to zap @vpnrc but this shows up...

Found this in my logs. (tangent: Nostr clients need some Markdown imho)

```

2023-07-27T11:06:26.275Z INFO plugin-pay: cmd 34 partid 0: Payment fee constraint 250msat is below exemption threshold, allowing a maximum fee of 5000msat

2023-07-27T11:06:26.656Z INFO plugin-pay: cmd 34 partid 0: Destination 030a58b8653d32b99200a2334cfe913e51dc7d155aa0116c176657a4f1722677a3 is not reachable directly and all routehints were unusable.

```

So it appears I can't just zap 50 sats - I must at least use 250?... But, it says msat, so it *should* have worked.

Ideas? nostr:npub16vzjeglr653mrmyqvu0trwaq29az753wr9th3hyrm5p63kz2zu8qzumhgd

Reply to this note

Please Login to reply.

Discussion

The Fishcake (nostr.build) 2y ago

Your only channel that is from me still didn’t reach sufficient liquidity on your side to satisfy reserve capacity. Unless you receive at least 10k sats, you will not be able to zap anyone 🐶🐾🫡

InBoston 2y ago

Didn’t realize that. Have an idea not sure how doable is it. What if there was a way to ‘zap’ that would lead to add new a inbound connection of that amount without actually sending the sats to the receivers lightening address. What would be the upsides and downsides of that?

The Fishcake (nostr.build) 2y ago

There is none, but side channels. It’s all a big balancing act. Node cannot send more than it actually has🐶🐾🫡

InBoston 2y ago

Just for my understanding- say I ‘new-type-zap’ you but this would connect to your inbound address and add 10 sats to liquidity. That’s all it would do. Would it still be bound by the constraints you listed above?

The Fishcake (nostr.build) 2y ago

Will not work. It’s all rooted in bitcoin, and once it is lifted to L2 (lightning) it is balanced in channels. You can’t spend what you don’t have. 🐶🐾🫡

vnprc 2y ago