What clients have nip-46 implemented now? We are very interested in this, but the development schedule is very heavy at the moment.

Reply to this note

Please Login to reply.

Discussion

Ideally it would be universal so any mobile client can sign into any desktop client.

I’d start with nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z, he implements all the NIPs!

People are working on dedicated native mobile signer apps as we speak.

nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 just released NIP-46 support on Amber, an Android signer.

nostr:note17dlrejdnn878zllmwjajzun3wldwsxdkqht8dzw4dusarvee96vqq3e3vw

nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 and nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac also are working on this.

I have iOS on my aspirational backlog, but I’m pretty backlogged.

🔥🔥🔥

Yep, this is probably a feature of Signers, not the clients themselves.

The ones I know support bunker style URLs https://github.com/nostr-protocol/nips/blob/master/46.md#direct-connection-initiated-by-remote-signer but we need nostrconnect URL https://github.com/nostr-protocol/nips/blob/master/46.md#direct-connection-initiated-by-the-client support in clients so mobile apps can scan a QR and establish the connection.

Ok, thank you, https://nsec.app/ has done a great job. We've always wanted to do something like this. I added it to the Freerse development plan.