Could Nostr Wallet Connect be used for things which weren’t lightning?

I’m agnostic about chains, but it seems to me being able to support ethereum would make the nostr tent bigger.

Looking at the code and spec, the only ln specific thing is the lightning address which is optional.

https://github.com/nostr-protocol/nips/blob/master/47.md

Reply to this note

Please Login to reply.

Discussion

🤮

I am sure I’ll get lots of folks saying it’s a terrible idea to support anything but bitcoin and lightning… ;-D

I always knew someone would try it but didn’t think it would be you!

Probably will backfire though as it’s expensive to send meTh transfers

So, you get it and I don't have to comment then? Great! 🤣

In all seriousness, I hate it and wouldn't support it, but Nostr is open, so anyone can build what they want, and this includes non-Bitcoin things.

That said, the STX fueled NIP didn't last very long and was rejected by most of Nostr instantly.

There’s a few Ethereum layer 2 implementations that may work alongside lightning, although I’m not sure how mature they are

Id rather we focus on bribing Nostr functions to regular apps and not expand the crypto sphere here. Bad enough as it is.

Bringing * 😆

There isn't even really anything about lightning itself that requires the L1 to be Bitcoin 🤷‍♂️

Lightning works just fine with Litecoin 😜

Does it make me want to gag? Yea, absolutely. But technically works 😁

I think it is difficult enough for a normie to backup private key, add lightning wallet. Don't want to confuse them!

I mean I just had to explain to somebody how nsec keys work and browser extensions for logins… We need it to be a lot easier.

Could you use the system keychain api to automatically keep the private key safe for the user? Then let them retrieve it when they need to? https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys/storing_keys_in_the_keychain

Yes and that doesn’t work with the web. As I said. We implemented this using apple keychain for key storage in nos.social. The problem is that most people use the web for most things. And we understand a system of accounts which exist on servers.

Honestly the compromise bluesky made isn’t terrible for this.

It is terrible because:

1- users don't hold the keys to migrate without the current pds's consent

2- even when they migrate, they also need the continuous consent of the centralized (and always will be) identity registry.

That being said, there is a movement in Nostr to give custody of keys to servers, without any path for redemption other than reboot with another key, so Nostr isn't really doing much better.

But you are right, the web is currently doomed to feel like visiting something that isn't yours, so it doesn't lend itself to key holding.

Native apps are much more appropriate for that psychologically not just technically.

The solution (I bet) is that we will have to reinvent browsers, to be more like the original vision that has authoring as a first class experience and tooling.

Oh I thought Nos was just an iOS app.

GunDB had a pretty clever user/pass api that was an abstraction over the keypair. Worked nicely but I think ultimately people just favored the keys because it was one less thing to worry about.

People understand keys to houses. They can be taught about the digital equivalent of that