Request for xlm to keybase username shows not satisfied on their end after they've paid.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- PR merge metrics
- PR metrics pending
Description
I just did a keybase log send regarding a request from the cli on my hammer device (v2.13.xxx SlackBuild).
The keybase user paid the request for 0.042xlm, but it did not resolve in his gui chat view, so he satisfied the request again. In both chat messages on my device satan it showed two payments from the user I sent the request to, yet it still shows as unsatisfied on his end.
I've asked him to check his wallet to see if it shows both payments to me.
Let me know if there's anything else in the form of info from me that might help.
my log id: 108fa970eaed8686febb061c
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the payment request from the CLI and checking its status in the GUI chat view. Use the provided log id, 108fa970eaed8686febb061c, to trace the two reported payments and compare what each side displays. Done means the recipient sees the request as satisfied after a single payment, or the failure is precisely documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cli
- Domain
- cli, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100