Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 3
Generated: 18:11:51
I have this setup but use nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wfjkccte9ekkjmnfvf5hguewvdshx6p0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0wsvavr for my wallet... It all works so well together.
2025-05-25 03:30:02 from 1 relay(s) 1 replies ↓
Login to reply

Replies (3)

Reason for some latency compared to server-side custodial wallets is that if you want to zap using NWC (not deeplink), incoming NWC command must be routed to the device push message, wake it up in the background and process ecash payment - because ecash lives directly on device. After some optimization this is now faster then it used to be.
2025-05-25 11:41:02 from 1 relay(s) ↑ Parent 1 replies ↓ Reply