-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message delivery issues not being sent or confirmed by receiver #778
Comments
One proposal I had was to use checksums on the messageIds array. That way the client and server can easily "ping" each other with a value to determine if a resync is needed with relatively low overhead. What do you think @kevkevinpal? |
Nice idea... the bigger problem though is that messages might never make it to your relay because of lightning liquidity issues, or MQTT issues |
Just so we're clear the chain of custody looks something like (sender client) --(1)---> (sender relay) ---(2)---> (recipient relay) ----(3)---->(recipient client) It seems you're mostly concerned about step 2 which seems to be the problem here? |
Right. Latest relay master waits for step 2 before returning a success or error message to the sender, so that should help a lot with "silent" failed msgs |
So are these current failures silent because the relay isn't update to latest master? One thought for how we can help on the client side is to detect a pattern of frequent failures and make recommendations such as adding more liquidity and alert the user? |
As per this ticket here some messages are not going through or there is an issue with the confirmation back from the receiver.
Andrew has experienced this with two different lite users.
The text was updated successfully, but these errors were encountered: