I did both this and increasing counters. I think it was the counters because "remove spent" reported zero removed.

Thanks!

Because I use one cellphone, it might be closed when I move to open the Zeus wallet.

I'll try again, by sending sats to the free Lnurl address used in my current minibits wallet

What's going on with my #minibits wallet...? Is mint.minibits.cash fucked?

I've got 0xchat, add me!

That’s really great to hear. Thanks so much for testing. Keep the amounts small as I’m sure there will be bugs and hiccups.

I plan to add some of the debugging functionality found in other wallets as soon as I can (e.g. exporting data, checking proofs, etc.) — you know, in case it’s needed.

Just tried sending lightning sats to myself as ecash and back again. Instant and none of the buggy delays in processing the tx I have seen in some other wallets.

NWS works with and without encrypted transport. There are lots of different flavors to explore.

When used without encryption, the entry node must be run by the user themselves because public entry nodes would be able to listen in otherwise. Two options in those cases: run the entry node locally in tandem with your (unmodified) client, or skip the entry node and modify the client so that data is sent through nostr to the exit node directly (the client is the entry node).

When used with encryption, the entry node can also be public. If the encryption doesn't rely on certificate authorities, it just works. You have to make sure you're talking to the right person, but that problem is as old as computer science. For example, ssh will ask you to confirm the fingerprint of the server when you connect.

If the encryption is https and the certificate was issued for a normal domain, your browser will complain (do you trust this website?) and the user will have to say "let me pass, even if insecure". Without ugly hacks (issuing your own root cert for example), I don't know ways to circumvent this. Note that Tor services doen't support https and they don't have to since transport is always Sphinx-encrypted (even hidden from the entry node).

How do you make sure you're talking to the right server if you use https? Couldn't the entry node just send your traffic somewhete else? We can actually do something that is unique to Nostr here: the exit node can publish its own TLS certificate on nostr and sign it. That's right, you don't need an authority to do that for you if you remain within the NWS system. Clients can fetch the cert from nostr before talking to the entry node and verify against that cert.

Here is another cool part that we haven't talked about yet: the exit node can also be configured to reach the global Internet and not only a local service (we call this NWS v2). In those cases, NWS can be used a bit like a VPN. You can type "https google dot com" in your browser and your encrypted traffic would flow from your machine to the entry node, to the exit node, then to Google and back to you. on those cases, nobody complains about the certificate because everything is fine.

Exciting shit. Gm.

Awesome! Do you have a GitHub link?

You’re welcome! Any tips on recovering the sats that were sent out as an invoice payment? Or would that be an issue on the wallet side (e.g. 0xchat)?

Thanks for pinging me!