@Bridgoro,I appreciate your prompt responses and bug fixes on your platform. Earlier users reported issues with the reCAPTCHA, but I didn't encounter any problems when creating my account. This suggests a dedicated team behind the platform. If I notice any bugs, I'll be sure to report them, but so far, everything seems smooth.
We are fixing frontend bugs as quickly as possible so that users can continue testing comfortably. The backend naturally requires more time, but work is ongoing.
Thanks again for your continued support of the project.
First off that beta test guide was well written to the tee , hats off to you guys!
Secondly I had a tough time getting my account signed up and thought perhaps it's an issue of geofencing and jumping onto my VPN, boom email came through faster than lightening which makes me want to ask if geo fencing is a thing here ?
Also even after getting my account setup still can't login from my PC but on mobile I get to enjoy full access??
Thirdly having opted to use a VPN I realized that for countries in the EU that follow the cookie law 🍪, the platform doesn't prompt for this consent. Will you consider adding this ?
Very active support staff when it comes to tackling these bottlenecks and all reported bugs and suggestions...
Just out of curiosity @Bridgoro, how big is the team ?
Please keep in mind that the GitBook page is still a work in progress.
We will continue improving and expanding the content.
We don't have any IP or country-based restrictions.
If you experienced signup delays, the issue was most likely related to your local network or country limitations, not our system.
If you face login issues:1. Please log out and log in again.
2. If it doesn’t work, try registering again with the same email and re-entering the activation code.
This bug has already been added to our backlog, and we will fix it soon so that future users don't encounter it.
We would also be grateful if you could test the mobile version and share feedback, improvement ideas, and bug reports.
The cookies popup is currently disabled during Beta, but it will be included for the final release.
In the meantime, you can review our
Terms & Conditions and
Privacy Policy for details.
What could be the issue?I thought @Bridgoro had resolved the sign-in/sign-up problem.Being able to access the site on mobile seems to allow full functionality.When @Bridgoro is online,they may respond and work on fixing the bug to enable seamless access on PCs.
We are actively working on reported issues. Don't worry, we will update you as soon as the next fixes are rolled out.
Part 3: Beta Test Post
11. My last bug post covered issues on the reward page, I am glad the suggestions and bugs I found are no more, but new bugs have taken place, before when I claimed my rewards, the task automatically removed from the "claim" page and added into the "claimed" page but now when I opened site today to claim the daily claim task's status changed to claimed as shown in the picture but it did not moved from that page to the claimed page.
Thank you for testing the Earnings section.
The Tasks section will be reworked soon, especially the handling of Claim-type tasks.
Status: [Added to backlog]
12. Now I am confused because the compeletion date of this task is 22, so that mean I did not claimed today, and if that's the case, that mean daily claim option is not daily, but one time? So to test this I created another account with my referral link, and I found one more error, will mention it later but first this, so I created a new account, went straight to earnings section and claim the daily reward and it successfuly moved from its page to "Claimed Page" So, why I am seeing this on my main account. I hope you are getting the issue, Now the reward completion date on my main account is 22 august, and when I tried to claim it again today (for the first time) it gave the following error.
(August 24, 2025, 06:23:50 AM edited: I am editing it again from here, because I opened my profile again to the balance history, I saw the tx there of the claim I did today, so I think brgx and xp added to my account, but the following error in the image is something else, it is also not moving the task claimed, to its tab. )
Please tell me the Uuid mentioned in the error is nothing personal of mine.
This is a bug, and we’re already working on fixing it.
Just to clarify:- UUID is the account's unique identification number.
- Since our exchange doesn't store any personal user information, the system uses a UUID for account identification.
- As you can see, the system doesn't use a user's email for identification purposes.
13. Coming to the error I found while getting the referral, so I pasted the referral link to another browser and hit enter as you know we have to hit enter haha, so it took me to the sign up page and I was waiting for the referral code to be entered automatically in the referral text box, as it should be, but it did not so I closed the tab and entered again now the second time it was automatically there. So I thought why not the first time, so I tested this on a separate mobile device, sent the link, opened it, and the first time referral code was not there in the referral text box, but when I clicked the referral link again without closing that tab, keep it opened and second time the code was there. So why not the first time, code is entering automatically like the way it should be. I hope I was able to convey it properly. If you want you can try to create a new account from referral link on a new browser where you did not opened the site before and see it for yourself.
We will investigate this Invite Code link bug.
Status: [Under investigation]
14. When you will be doing that, like creating new account and when you try to sign up, you will see in the password tex box an eye icon obviously too see the password and to hide it, but there were two, but when I clicked on one, the other vanished.
We will check this bug as well.
Status: [Under investigation]
This was my 3rd part as I was trying to make some tx here, but I thought I should claim reward again today but it was showing error, and found the above errors. Hope these are real and will be solved. I have made a video for the 13th number error, but I have to edit it because of some personal data visible in it. But I hope you won't need it, because you can test it by yourself.
Thanks for your reports.
It will be a great idea if you guys are launching your own Discord servers in the coming days. Hopefully we will see it as soon as possible, as smooth communication mediums are the best representations of reputable projects where no one faces any kind of trouble/problem while contacting the projects' representatives.
Other than this, I really appreciate you guys for this project because I can see your teamwork and dedication towards this project. Keep it up.

We will post an update on both the ANN and BOUNTY threads once the Discord server is launched.
Thank you for your support!
I was just completing the recent task given there; most of them were checked as completed or claimed status. But when I tried to submit the "comments base bugs reports" task, it was cleared in the "in progress section". But when I click the "Done" section, it shows me that the tasks are still loading to submit and not submitted even in the "Done" section. There must be some kind of gap/error/bug in its back-end process that makes its delay that long.
Other than this, other small tasks were completed and claimed smoothly. I have even received their completion mail on my Gmail account.
As we mentioned earlier, the Tasks module is currently being reworked. We will post an update as soon as the bug fixes are completed.
Status: [Already added to backlog]
I'm surprised to hear that there are only two of you handling this team. Despite the small team size, you're both doing an excellent job fixing bugs and identifying new ones from testers. Keep up the great work, and I'm confident you'll make this team shine.
All of this has been possible thanks to you - the Bitcointalk community.
I wonder how I ended up writing Unconfirmed instead of Unexpected Error. I think this issue has been raised before and you gave possible reasons for it. Sorry for the mixup though it's still showing in all browsers I tested. Chrome for instance:
No problem, mistyping happens.
As we mentioned earlier, we were able to reproduce this bug and are already working on fixing it.
Status: [Already added to backlog]
New week, new heights to conquer!After a short rest, we're diving headfirst back into development and bug fixing.
Today, we've already managed to fix several issues, with one of the most important being the requests from Cloudflare. We successfully removed the need for Cloudflare requests to users (
unpkg third-party requests).
Currently, only requests related to CAPTCHA, fonts, and icons remain, and we will resolve those soon as well (
except CAPTCHA, which will stay for security reasons).