Show thread history
jb55
2mo ago
bizarre it would need to do this, I thought signing stayed on device? why does it need to go to the internet and back just to sign?
See translation
0
0
0
0
0
Replies
npub1kun56
@npub1kun56
2mo ago
Amber can do entirely local signing using NIP-55, but it also supports remote signing via NIP-46. It uses relays to transfer the unsigned data to Amber, then the data is signed locally and transferred back to the client via relays. The relays used can be selected by the user and can even use a local relay, such as Citrine.
That said, even using Amber for NIP-46 signing has been spotty for me. Not sure why. It is using a similar concept as Nostr Wallet Connect, which has always worked quite well, but remote signing often just fails for some reason.
That said, even using Amber for NIP-46 signing has been spotty for me. Not sure why. It is using a similar concept as Nostr Wallet Connect, which has always worked quite well, but remote signing often just fails for some reason.
See translation
0
0
0
0
0
npub19ma2w
@npub19ma2w
2mo ago
Maybe just to provide another option for apps that expect this kind of signing?
See translation
0
0
0
0
0
npub1d0ena
@npub1d0ena
2mo ago
npub1l2vyh
@npub1l2vyh
2mo ago
amber supports nip-46 and nip-55
you can use nip-46 with amber via a localhost relay too
you can use nip-46 with amber via a localhost relay too
See translation
0
0
0
0
0
npub1gcxzt
@npub1gcxzt
2mo ago
NIP55 is local. NIP-46 can use a local relay when the app doesn't implement NIP-55 or a remote relay when using a desktop client with Amber as the signer.
See translation
0
0
0
0
0