pull down to refresh

mmm interesting, from my end I can see the initial user id is 4265<redacted>.questforsats and then you used 1853<redacted>.questforsats to checkin which has the 21 sats. You can look at storage/cookies in dev console to check which id the browser is using. I pluged in 1853<redacted>.questforsats and checked the withdraw page which showed me the 21sats.
Thanks for testing this out btw, I'm sure it's full of bugs!
Sat در اینجا به چه معنی است وچند ست یک بیت کوین یا دلار می شود
reply
0 sats \ 1 reply \ @Wumbo 20 Feb
So Microsoft Edge (the browser where I claimed waypoint) has two different cookies saved:
{"userId":"1853<redacted>.questforsats"} {"userId":"2578<redacted>.questforsats"}
I am guessing the 2578 cookie is getting used when I goto withdraw page and 1853 is being used on the waypoint page.
How and why this is happening I don't know.
Firefox (browser where I created waypoint) only has one cookie 4265
Surprise! Surprise! Edge is the problem child.
reply
wow thats weird, I defo need to test edge now! I got everything to work on firefox and just yoloed the release
reply