pull down to refresh

1163 sats \ 6 replies \ @adam_coinos_io OP 19 Sep \ parent \ on: Coinos adds Nostr Wallet Connect (NWC) nostr
I think the issue was that our load balancer wasn't passing the user's IP to the relay properly so it thought all users had the same IP. Should be resolved now.
Also yes we are open source and our NWC implementation is here: https://github.com/coinos/coinos-server/blob/master/lib/nwc.ts
write
preview
20 sats \ 5 replies \ @ek 19 Sep
Cool, thanks for the info!
I assume rate limit errors are communicated by the relay as defined in NIP-01 like this:
["OK", "b1a649ebe8...", false, "rate-limited: slow down there chief"]
and not per wallet as a NWC error as defined in NIP-47 like this:
{
    "result_type": "get_info",
    "error": {
        "code": "RATE_LIMITED",
        "message": "rate-limited: slow down there chief"
    },
    "result": null
}
Communicating it via the relay (if you control the relay) makes more sense imo.
I also found a potential issue on our side that would still explain @grayruby's issue with rate limits + missing error handling on the relay layer on our side. Our code currently only expects NWC errors when dealing with NWC, not relay errors.
reply
0 sats \ 4 replies \ @grayruby 19 Sep
Tried to detach wallet and the attach again but cannot. Still getting the same error message.
reply
1071 sats \ 2 replies \ @adam_coinos_io OP 19 Sep
Can you try one more time please? I just fixed a bug with our NWC responses
reply
100 sats \ 1 reply \ @grayruby 19 Sep
Thanks. I need to run and do some errands but I will be back in about an hour and give it another shot. Keep you posted.
reply
100 sats \ 0 replies \ @grayruby 20 Sep
Everything working again now.
Thanks @adam_coinos_io @ek @k00b
reply
1020 sats \ 0 replies \ @ek 19 Sep
:(
Just signed up on Coinos myself. Attaching for payments works fine but when I attach it for receives, I get this error:
failed to create test invoice: failed to connect to wss://relay.coinos.io: null
which doesn't make sense since I can connect fine to it on the client. So sounds like something is wrong on our side.
To confirm: you get Cannot read properties of undefined (reading 'includes') no matter if you try to attach for sending or receiving, right?
reply