Lol but it requires an account

it does?

The inventor says otherwise: View quoted note →

Doesn't it require that you sign the nostr messages?

excellent work. this 🧡 "The current implementation in publsp is just a beginning. The future for an open liquidity marketplace over Nostr is bright. Here are just a few things I can envision happening in the near future" -- agree and something needed...right now there are too many closed markets.

yes, but I think it just generates a keypair for that and then autosigns whatever messages it creates, so the user experiences no friction -- they don't have to copy/paste anything to and from their node, for example

I am aware of 7 accountless markets and 3 additional ones that require an account. I list them here:

List of channel sellers

The more the merrier! The next best thing to a decentralized protocol is a coordinated one without as many independent coordinators as possible

Oops, I meant "with" not without

That's correct. Also nothing stopping either party from using their own keys if they prefer.

I'm just being a bit pedantic because a signed nostr message is essentially the same thing as a signed message from your node. Only the UX is different; it's not about there being an "account" from a technical or privacy perspective. it's that there's user friction in signing messages.

I think signing in with a node is essentially different from communicating via a randomly generated one-time-use nostr key By signing in with a node, you can send notifications to my account with confidence that I will see them the next time I log in, and you can log my sessions With a one-time-use nostr key, if you try to message me, I won't see the messages because I never sign in with that key again, and if you try to log my sessions, you'll only see one session

But you have to specify the node destination that you're purchasing for, plus another separate identity (which is often not one-time use) so really you're giving up more pieces of information.

I haven't tested lspub yet but if it's nostr keys are not one time use then that ought to be fixed imo There's no reason to use your real identity to purchase a channel -- spin up a a fake one for every purchase Your point about needing a node pubkey anyway is a good one, I will start brainstorming a way to easily use a new node pubkey for every channel too

The current implementation of publsp autogenerates new keys at startup if none are found, then saves those to file. Each subsequent startup will try reading that file to see if keys are there to use. I figured that was a reasonable trade-off to reduce friction, and to avoid potential confusion if the tool automatically regenerates new keys each time. But you bring up a good point. This could just be a new option the user sets to deliberately create new keys each time, or the opposite, to keep the existing keys each time. I guess either opt-in or opt-out but the user is made aware. On the receiving LN node privacy issue, I think that's a separate problem to tackle. In the end, the LSP needs to know where to open the channel so it can't be avoided, but there's no reason that the receiving nodes can't be one-offs, for example.

I wonder if it'd be possible to obfuscate the receiving node pubkey similar to how NIP-17 private messages obfuscate the receiver key?

That's what I'm thinking. I believe mutiny wallet creates a new pubkey for every channel it requests, and the transLND project shows that you can spin up new pubkeys on LND and pretend those belong to your node, so I think its possible, at least on lnd

Love it. I wasn't aware of those options.

Just pushed an update to expose an option on the cli to reuse keys

GitHub

added cli option to reuse nostr keys, default is auto key rotation · smallworlnd/publsp@21cdce8

LN liquidity offers/purchases over Nostr. Contribute to smallworlnd/publsp development by creating an account on GitHub.

Default behavior is to auto rotate keys on startup, so users have to opt-in to reuse. Thanks for the idea!