🌐 Bridgoro.com - BETA TEST! Active until December 7th!!

[btcnbegun]

1st: Important, Severity (High)

Referred user doesn't show up in the referrals page/tab after user signed up with the referral link.
Is the referral program working?

Screen of the other user:

Referrals tab :


2nd:

Submitted button is spinning that is not stopping:




3rd:



Under Task manager

Time to complete tab is 24:00. Should be 00:00 once submitted as per as Claims tab. This is for Tell parents that You love them


4th:

Submit 5 Bug Reports task page.

Completion timer is in static mode and not in the countdown mode.


5th:

Chrome Version 139.0.7258.129 and Opera One(version: 120.0.5543.161)



Mail daemon is blocking Protonmail IMAP/POP3 mail server
(Reason): With two Protonmail emails there is a need of a signup fix ' User not assigned'

[Faisal2202]

Part 2: Beta Test Post

7. I was visiting the earning section, and I was filling in the task by providing the proof in that text box, and when I entered the link and it successfully submitted but when I clicked on the second task and saw the previous link still lying there resting, I first completed the task of a meaningful reply to another user's report and when I went for the second task of ann, the previous link was not removed, I had to cut it or after reloading the page it removes, but I think it will be best when we click on the "submit proof" button of a new task the text box should be empty, here is the proof, for better understanding, I did the same with third task and the 2nd task's link that I pasted was still there. Although nothing big but it can create problem later if someone thought they have pasted the correct link and submit, and there is no option of editing it as well.

8. In this picture, you can see I am on the Done page, and it shows the tasks I have already submitted, then why I am seeing a loading icon (animation) besides the submitted button? I have marked it as well with a red rectangle. It should be a green tick here? If it were to show that the task is submitted, but it will turn green when it is approved, then I don't think this is a seamless way. The seamless way would be like, it changes to claimable and then I go to the claims tab to claim the reward of this task (If it is already like this, which I think it is, then still those loading icons should not be there). And one more thing when I click on the submit button the information window right next to it, shows up, where the details are written, as you can see I have submitted the task but the status is still showing available, it should also change to submitted.

9. Although the claim status changes smoothly. And one more thing, is it possible if you guy consider changing the name to Rewards or My rewards, instead of My task, because "rewards" is better than "my task" from CTA point of view. I mean I did no notices it at first glance after I signed in, but today I click on earn which was at a good place obviously and a good CTA button too, but the one on the top is not that good, you can also change it to "Earnings".

10. Where can I see the total balance of brgx I have earned, it will be easy if users don't have to calculate it manually, I know we can see balance in profile but a small balance option visible here or at besides the profile icon all the time will be awesome and, a small balance option somewhere here, will be best for this page but if not here, then the same option in the top right corner somehwere in between our user id and profile icon.

This was my second part and I hope this will help. I will cover more.

you can say this was part 1.

[Bridgoro]

Tested with Firefox. Error message "Unconfirmed Error" pops up even before logging in and also appeared during deal creating. I'll be updating this as i test more browsers.
The unexpected error message also showed up in Tor browser before I logged in. Tor connection is usually slow and signing in took even longer time than other browsers. I also noticed a pop-up message at the Bridgoro homepage when I landed. It must be a new addition I suppose? The error message doesn't seem to be present after logging in on Tor, just before login.

This error message looks unusual, and we haven't been able to identify it yet.
To help us narrow it down, could you please follow these steps?

1. Log out of your Bridgoro account.
2. Clear your browser cache in the settings.
3. Open the exchange page and press Shift+F5 (Windows) or CMD+Shift+R (Mac).
4. Log back into your account and check all pages for the Unconfirmed Error message.
5. If possible, also test with different browsers: Opera, Chrome, Vivaldi, or even Edge  .

If the error appears again, kindly send us a full-screen screenshot showing the entire page of the website.
Sorry for asking you to go through these steps, but without this, it's difficult for us to identify the root cause of the issue.
Status: [Under investigation]

1st: Important, Severity (High)
Referred user doesn't show up in the referrals page/tab after user signed up with the referral link.
Is the referral program working?

Yes, the referral program is working.
It's possible that the Invite Code didn't pass correctly during the registration of your test referral account, especially since we are running frequent server updates during bug fixes.
For such cases, you can add the Invite Code once after registration:
1. Log in to your referral account
2. Go to Profile -> Referrals (tab)
3. On the right side, find the section Have an Invite Code?
4. Paste your code and click Apply Code
5. Once the code is applied, the button will change to Code was already applied

If your referral count (on the referral account) doesn't update after this, please send us both your referrer's username and the referral's username so we can check the issue internally.
Don't forget to refresh the page on your referrer and referral accounts.
Status: [Under investigation]

Submitted button is spinning that is not stopping:

This isn't a bug.
The spinning icon simply indicates that your submitted task has been sent and is waiting to be reviewed by our team.
That said, we understand it may be confusing, so we will consider deleting the icon to make it clearer for users.
Status: [Added to backlog]

Under Task manager
Time to complete tab is 24:00. Should be 00:00 once submitted as per as Claims tab. This is for Tell parents that You love them

The timer shows the total time available to complete the task, but once you submit, the timer stops.
For a better user experience, we will update this so that after submission, it displays 00:00 along with the status Pending Review.
Status: [Added to backlog]

Submit 5 Bug Reports task page.
Completion timer is in static mode and not in the countdown mode.

It looks like the timer got stuck and isn't counting down properly.
We've logged this as a bug and will review it to provide a fix soon.
Status: [Added to backlog]

5th:
Chrome Version 139.0.7258.129 and Opera One(version: 120.0.5543.161)
Mail daemon is blocking Protonmail IMAP/POP3 mail server
(Reason): With two Protonmail emails there is a need of a signup fix ' User not assigned'

We have already encountered this bug earlier and identified the cause.
Could you please:
1. Try registering the account again using the same email
2. Get the activation code from your email.
3. Enter it and log in again.
Let us know if the error message appears again.
[P.S.] Sorry, I didn't quite understand the part about the Mail Daemon block. Could you please describe it in more detail?
Status: [Needs more data]

7. I was visiting the earning section, and I was filling in the task by providing the proof in that text box, and when I entered the link and it successfully submitted but when I clicked on the second task and saw the previous link still lying there resting, I first completed the task of a meaningful reply to another user's report and when I went for the second task of ann, the previous link was not removed, I had to cut it or after reloading the page it removes, but I think it will be best when we click on the "submit proof" button of a new task the text box should be empty, here is the proof, for better understanding, I did the same with third task and the 2nd task's link that I pasted was still there. Although nothing big but it can create problem later if someone thought they have pasted the correct link and submit, and there is no option of editing it as well.

We see the issue, and you are absolutely right.
The bug will be fixed soon.
Status: [Added to backlog]

8. In this picture, you can see I am on the Done page, and it shows the tasks I have already submitted, then why I am seeing a loading icon (animation) besides the submitted button? I have marked it as well with a red rectangle. It should be a green tick here? If it were to show that the task is submitted, but it will turn green when it is approved, then I don't think this is a seamless way. The seamless way would be like, it changes to claimable and then I go to the claims tab to claim the reward of this task (If it is already like this, which I think it is, then still those loading icons should not be there). And one more thing when I click on the submit button the information window right next to it, shows up, where the details are written, as you can see I have submitted the task but the status is still showing available, it should also change to submitted.

Thank you for helping us improve the UX/UI of the platform!
As we mentioned earlier, we invested a lot of time into backend processes but admittedly overlooked parts of the frontend. Thanks to your feedback, we are now improving it so users can feel more comfortable while using our exchange.

Regarding your suggested fixes: we completely agree.
The original loading icon was meant to show that tasks were in a pending state, but we realized that it looked confusing, so we will remove it (one of the users already sent a report about it).
Status: [Already added to backlog]

The same adjustment applies to the status display on the right section of the Tasks page.
From now on, task statuses will be shown more clearly with the following labels:
Available - Task is available for acceptance.
In Progress - Task has been accepted but not yet submitted for review.
Pending Review - Task has been submitted but not yet reviewed by the team.
Approved - Submitted task has been reviewed and approved.
Declined - Submitted task has been reviewed and declined.
Status: [Added to backlog]

9. Although the claim status changes smoothly. And one more thing, is it possible if you guy consider changing the name to Rewards or My rewards, instead of My task, because "rewards" is better than "my task" from CTA point of view. I mean I did no notices it at first glance after I signed in, but today I click on earn which was at a good place obviously and a good CTA button too, but the one on the top is not that good, you can also change it to "Earnings".

Thank you for the UX improvement feedback!
We will consider renaming My Tasks in the navigation menu to Earnings for better clarity.
However, inside the task page itself, we will keep the tab name as Tasks to avoid confusing users.
Status: [Added to backlog]
Updated status: [Fixed to Earnings]

10. Where can I see the total balance of brgx I have earned, it will be easy if users don't have to calculate it manually, I know we can see balance in profile but a small balance option visible here or at besides the profile icon all the time will be awesome and, a small balance option somewhere here, will be best for this page but if not here, then the same option in the top right corner somehwere in between our user id and profile icon.

Your request will be discussed with my teammate, and we will get back to you once we've reviewed it.
Status: [Added to backlog]
Updated status: [We've added the XP/BRGX data as per your request.]


Thank you for continuing to test the Bridgoro exchange for sending us your bug reports.
What makes this even more exciting is that many of you aren't only reporting bugs but also sharing ideas on how to improve the platform, and that's truly awesome.

When all the bugs are fixed, your improvement suggestions applied, and the exchange officially released, each of you will be able to proudly say:
"I was part of building this exchange."


We would also like to share an important note from the devs' perspective:
Yes, there have been many bug reports, but the majority are related to the frontend and UX/UI improvements. The backend remains strong and stable, which is the foundation of the exchange.
Of course, we did identify a few backend issues as well, mainly related to Dust Transactions and the Dead Wallet Amount value, but these are already in progress and will be fixed soon.
So please don't think of Bridgoro as a "buggy" project. What you are seeing now is the natural polishing stage of Beta, while the core system continues to hold strong.

[LoyceV]

We would also be grateful if other users could test the Support button in the footer and let us know if it works or shows any errors.

I'd prefer a Support system that doesn't need Telegram. Clicking the link in Tor browser doesn't work.
For privacy: using Protonmail would be convenient. Bitcointalk PM would work too, but those aren't encrypted (and Cloudflare can read them).

Deposit TX:

Code:

f0c2a706bb17ae8bac54f292a74ac5ca1ef28f85a67430501f07de6625a9843d

We've identified the cause of the stuck Release Ready transaction. It was due to a Dust Transaction issue.
Even though there will be no Service Fee on mainnet for the first 6 months, during the Beta Test, we added a Service Fee % to each transaction (applied only to testnet tokens) for testing purposes.
In this case, because the exchange amount was very small, the Service Fee amount ended up being too tiny to be processed on the Bitcoin network. As a result, the transaction got stuck.

Can you still recover those (testnet) funds? The amount is small, but if it would get stuck forever, that would be bad. It's also a good test to see if "buffer wallets" can be accessed.

[Bridgoro]

I'd prefer a Support system that doesn't need Telegram. Clicking the link in Tor browser doesn't work.
For privacy: using Protonmail would be convenient. Bitcointalk PM would work too, but those aren't encrypted (and Cloudflare can read them).

For users who prefer not to use Telegram, there is a built-in Contact Form available on the homepage.
In September, we plan to launch a Discord server. Additionally, we will consider creating a separate Bitcointalk Support account with email notifications enabled so we can track incoming messages more efficiently.

Can you still recover those (testnet) funds? The amount is small, but if it would get stuck forever, that would be bad. It's also a good test to see if "buffer wallets" can be accessed.

We will do our best to retrieve the funds using Collector Module from the stuck exchange. We will update you next week with the results.

[ContentWriter]

Bug Report

Microsoft browser Edge reports unknown error before and after logging in. The browser also flags Bridgoro as not secure. With potentially a browser market war brewing with Google, you my have to sort this out.

[Faisal2202]

Thank you for helping us improve the UX/UI of the platform!
As we mentioned earlier, we invested a lot of time into backend processes but admittedly overlooked parts of the frontend. Thanks to your feedback, we are now improving it so users can feel more comfortable while using our exchange.

I can understand the frontend can will imporved on the way, and you know what, perfect UI is usually invisible haha, I mean nothing can be perfect, every single platform can have UI or other problems, the main important thing should be the backend if it is working smoothly no one talks or find such UI errors, I am finding because it is the job here haha.

Thank you for the UX improvement feedback!
We will consider renaming My Tasks in the navigation menu to Earnings for better clarity.

Thank you, I will love to say someone here on the forum about my contributions. That's the part I love most.

Your request will be discussed with my teammate, and we will get back to you once we've reviewed it.
Status: [Added to backlog]
Updated status: [We've added the XP/BRGX data as per your request.]

This is great, thanks for the approval.

Thank you for continuing to test the Bridgoro exchange for sending us your bug reports.
What makes this even more exciting is that many of you aren't only reporting bugs but also sharing ideas on how to improve the platform, and that's truly awesome.

When all the bugs are fixed, your improvement suggestions applied, and the exchange officially released, each of you will be able to proudly say:
"I was part of building this exchange."

I am already proud to say I am helping in a project, I have wrote many reviews before but review and bug post are quite different. Wish you best of luck.

[LoyceV]

We've identified the cause of the stuck Release Ready transaction. It was due to a Dust Transaction issue.
Even though there will be no Service Fee on mainnet for the first 6 months, during the Beta Test, we added a Service Fee % to each transaction (applied only to testnet tokens) for testing purposes.
In this case, because the exchange amount was very small, the Service Fee amount ended up being too tiny to be processed on the Bitcoin network. As a result, the transaction got stuck.

The 0.3% Service Fee isn't enough to explain why 11.xx USD became less than 10 USD (which is the limit for this test).

Yesterday (8/22/2025, 7:15:07 PM), I tried again: deposit 85132ca6fbd1f6b2392a5622b50fd23f7df78232c6d909997cde8464ffc8378c to accept Offer ID: a44e20c6-15ad-4b00-8f2e-019080abc3e9:
0.00061747 BTC > 0.2694231 XMR

It gives the same result: RELEASE READY, and nothing happens despite being more than $60. So I don't think the "dust limit" causes this.

I only now noticed XMR should be on Stagenet, not Testnet (which is what I used). Could that be the cause of not sending my transaction?
One of your faucet-links on gitbook points to a Testnet faucet, not Stagenet.


With 4 confirmations, my Bitcoin deposit status was still "Partially confirmed". It would be nice to show how many confirmations are needed (and 4+ is excessive for Bitcoin). I didn't see exactly how many deposits it takes.

[Bridgoro]

Bug Report
Microsoft browser Edge reports unknown error before and after logging in.

"User is not assigned" and "Unknown error": both are already in our backlog.
The root cause seems to be a frontend conflict. We are investigating and expect to deliver a fix next week, followed by a detailed report.
Status: [Already added to backlog]

The browser also flags Bridgoro as not secure. With potentially a browser market war brewing with Google, you my have to sort this out.

If you see the "Not Secure Connection" flag, it usually means the site is being accessed via HTTP instead of HTTPS. Please use HTTPS as our SSL certificate is active.

Third-party requests we use:
google.com -> CAPTCHA
gstatic.com -> Google Fonts
unpkg.com -> Cloudflare CDN

For security reasons, Cloudflare (unpkg) can’t be removed at this stage.
In the future, we may replace Google Fonts and possibly build our own CAPTCHA system to get rid of these two requests.
Status: [Not a bug]

I can understand the frontend can will imporved on the way, and you know what, perfect UI is usually invisible haha, I mean nothing can be perfect, every single platform can have UI or other problems, the main important thing should be the backend if it is working smoothly no one talks or find such UI errors, I am finding because it is the job here haha.

The Beta Test is essential for polishing all parts, especially the frontend. Massive testing has already uncovered several bugs in the backend as well. We won't move to release until the backend is fully stable. If any issue happens with a transaction during mainnet, we will restore funds from our own side, but we want to eliminate backend risks before going live.

Thank you, I will love to say someone here on the forum about my contributions. That's the part I love most.

Who doesn't love  

This is great, thanks for the approval.

Thanks for your idea, which helps us improve the project.

I am already proud to say I am helping in a project, I have wrote many reviews before but review and bug post are quite different.
Wish you best of luck.

Thanks a lot. Doing our best.

The 0.3% Service Fee isn't enough to explain why 11.xx USD became less than 10 USD (which is the limit for this test).

When accepting a Deal, remember that the Buyer covers not only their own Network Fee but also the Seller's Network Fee (Compensation Fee).
Status: [Not a bug]

Yesterday (8/22/2025, 7:15:07 PM), I tried again: deposit 85132ca6fbd1f6b2392a5622b50fd23f7df78232c6d909997cde8464ffc8378c to accept Offer ID: a44e20c6-15ad-4b00-8f2e-019080abc3e9:
0.00061747 BTC > 0.2694231 XMR
It gives the same result: RELEASE READY, and nothing happens despite being more than $60. So I don't think the "dust limit" causes this.
I only now noticed XMR should be on Stagenet, not Testnet (which is what I used). Could that be the cause of not sending my transaction?

I know about a stuck transaction, as this is our Exchange Offer from one of the test accounts.
This isn't related to Dust Transactions. We are still investigating, as it may be linked to testnet XMR being sent instead of stagenet XMR. Backend bugs are critical for us, so this needs deep analysis.
Please expect a detailed report next week.
Status: [Under investigation]

One of your faucet-links on gitbook points to a Testnet faucet, not Stagenet.

Thanks for pointing it out.
I mistakenly added a testnet faucet link instead of a stagenet faucet link earlier (just CypherFaucet provides both faucets: for testnet and stagenet).
The link is correct now.
Status: [Fixed]

With 4 confirmations, my Bitcoin deposit status was still "Partially confirmed". It would be nice to show how many confirmations are needed (and 4+ is excessive for Bitcoin). I didn't see exactly how many deposits it takes.

For BTC, 6 confirmations are currently required.
Next week, we will experiment with reducing the number of confirmations across all blockchains to find a balance between speed and security.


Important note for our Beta Test community:
We will pause bug reviews and development work until Monday.
After weeks of intense work, my teammate and I need a short rest to "clear the cache in our heads."

But please keep sending us your reports if you find any issues.
Rest assured, every single report will be reviewed carefully.

[Fiasem20]

@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.

[Woodie]

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 ?

@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.

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 ?

[Fiasem20]

Also even after getting my account setup still can't login from my PC but on mobile I get to enjoy full access??

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.

[Faisal2202]

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.

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.

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.

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.


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.

This was my second part and I hope this will help. I will cover more.

[snowpega]

We are sorry to hear that Telegram is blocked in your country.
For now, you can still reach us through the Contact Form on our platform.
In addition, we are planning to launch a Discord server around September to make communication easier.

We also apologize if some updates feel slower than expected.
Please keep in mind that we are a small team of just two people handling everything: development, bug fixing, Bitcointalk management, and the Beta Test.

We are doing our best to move things forward step by step.

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. 

Another Report of the day

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.

[Fiasem20]

Please keep in mind that we are a small team of just two people handling everything: development, bug fixing, Bitcointalk management, and the Beta Test.

We are doing our best to move things forward step by step.

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.

[ContentWriter]

Tested with Firefox. Error message "Unconfirmed Error" pops up even before logging in and also appeared during deal creating. I'll be updating this as i test more browsers.
The unexpected error message also showed up in Tor browser before I logged in. Tor connection is usually slow and signing in took even longer time than other browsers. I also noticed a pop-up message at the Bridgoro homepage when I landed. It must be a new addition I suppose? The error message doesn't seem to be present after logging in on Tor, just before login.

This error message looks unusual, and we haven't been able to identify it yet.
To help us narrow it down, could you please follow these steps?

1. Log out of your Bridgoro account.
2. Clear your browser cache in the settings.
3. Open the exchange page and press Shift+F5 (Windows) or CMD+Shift+R (Mac).
4. Log back into your account and check all pages for the Unconfirmed Error message.
5. If possible, also test with different browsers: Opera, Chrome, Vivaldi, or even Edge  .

If the error appears again, kindly send us a full-screen screenshot showing the entire page of the website.
Sorry for asking you to go through these steps, but without this, it's difficult for us to identify the root cause of the issue.
Status: [Under investigation]

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:

[Bridgoro]

@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).

[btcnbegun]

[P.S.] Sorry, I didn't quite understand the part about the Mail Daemon block. Could you please describe it in more detail?
Status: [Needs more data]


6.



Notification bug

Unable to get notifications for offers, deposits and rest of all the notifications except the system borne ones with the subscription button is on. This is for both email and telegram notifications.


7.

Floating error bug



Testing to discover that the withdrawal is possible with 49.9999999999 given that 50.00000000 BRGX is the minimum value for withdrawals. With the absence of network fee this seems to be a floating number error.

[Faisal2202]

The Beta Test is essential for polishing all parts, especially the frontend. Massive testing has already uncovered several bugs in the backend as well. We won't move to release until the backend is fully stable. If any issue happens with a transaction during mainnet, we will restore funds from our own side, but we want to eliminate backend risks before going live.

Love the transparency, the backend should be smooth like butter, and I tested ETH to other tokens yesterday. It was very smooth, and I tested other things as well, but I have not made any XMR deals yet, so once I do, I will be sharing my fourth report soon. Although I have one question. The buffer wallet in which we send our funds, like I send ETH to receive some other token, and if on the other hand, the buyer made the deal with me, will he receive funds from the same buffer wallet or funds move from buffer wallet to another wallet first, as I tried to follow the money, and I think it moves to another wallet from buffer wallet CMIIW. Although this does not change anything, just a silly qestion.

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.

Ok ok, thanks for the clarification. As I thought, it is better to ask about it.

And the invite code bug is real because I have tested it, two times. 

[Bridgoro]

Notification bug
Unable to get notifications for offers, deposits and rest of all the notifications except the system borne ones with the subscription button is on. This is for both email and telegram notifications.

About Email Notifications:
Could you please share more details along with a screenshot?
Also, could you clarify what you mean by the Mail Daemon block: do you mean that ProtonMail isn't receiving notification emails from Bridgoro due to certain restrictions or filtering?

About Telegram Notifications:
We are currently working on Telegram Notification Bot and applying some fixes. It will be back online soon.
We will notify everyone here once Telegram notifications are available again.

Floating error bug
Testing to discover that the withdrawal is possible with 49.9999999999 given that 50.00000000 BRGX is the minimum value for withdrawals. With the absence of network fee this seems to be a floating number error.

Yeah we see the bug. Thank for checking this type of possible bug.
We will fix it soon.
Status: [Added to backlog]

Ok ok, thanks for the clarification. As I thought, it is better to ask about it.
And the invite code bug is real because I have tested it, two times. 

We are aware of this issue and have already added it to our backlog for future fixing.
Status: [Already added to backlog]