Bitcoin Forum

---

 

This is your chance to test the platform, help improve it, and earn rewards for your contributions.

---

🔹 Brief Project Overview 

Bridgoro exchange is designed as a semi-decentralized escrow-based platform that combines automation with user privacy: 
• Automated escrow system powered by blockchain adapters and smart contracts 
• No custody by the team – funds are held in buffer wallets beyond our direct access, with recovery possible only via a transparent collector module 
• Semi-decentralized design: Registration is required, but the exchange runs without KYC/AML and ensures anonymity 
• We support Monero (XMR) for more privacy

Bridgoro's announcement post link [ANN] (https://bitcointalk.org/index.php?topic=5555402.msg65699760#msg65699760) 

---

🔹 Key Features 

✔ Supported assets at launch: BTC, ETH, SOL, TRX, XMR 
✔ No KYC / AML requirements 
✔ No transaction freezes 
✔ Automated and secure escrow system 
✔ Minimum exchange amount: ~$30 (USD equivalent) 
✔ Service fee-free for ~6 months after launch (only standard network fees apply) 
✔ Gamified rewards: complete tasks, earn BRGX tokens, withdraw into USDT anytime 

---

🔗 Project Links

🌐 Website: https://bridgoro.com (https://bridgoro.com)  
📖 Documentation (GitBook): https://bridgoro.gitbook.io/bridgoro-docs (https://bridgoro.gitbook.io/bridgoro-docs)  
📖 BETA TEST Guide (GitBook): https://bridgoro.gitbook.io/bridgoro-docs/bridgoro-beta-test (https://bridgoro.gitbook.io/bridgoro-docs/bridgoro-beta-test)  
💬 Telegram (Community Channel): https://t.me/bridgoro (https://t.me/bridgoro)  
📢 Telegram (Support): https://t.me/bridgoro_support (https://t.me/bridgoro_support)  

---

To ensure fairness, transparency, and smooth participation in the Beta Test, please read the following rules carefully:

---

1. Testnet-Only Environment  
• All testing will be performed exclusively on testnet networks with testnet coins that have no real-world value.  
• This approach eliminates any risk of financial loss during the Beta Test.  
• Detailed guidelines on how to download testnet wallets, connect to testnet networks, and obtain testnet coins are available on the project’s GitBook page (https://bridgoro.gitbook.io/bridgoro-docs/bridgoro-beta-test).  

---

2. Eligibility  
• Only Bitcointalk forum members are eligible to participate.  
• Accounts must have been created no later than July 31, 2025 to qualify.  

---

3. Registration for Participation  
• To participate, forum members must check in by posting in this thread stating their intent to join the Beta Test and reward program.  

---

4. Beta Test Duration  
• The Beta Test begins on Monday, August 18, 2025.  
• The test period will last two weeks end date August 31, 2025.  
• Participants can start publishing bug reports in this thread from the first day of the test.  

---

5. Bug Report Rules  
• Before posting, participants must check existing bug reports in this thread.  
• Duplicate reports will not be counted - only the first valid submission of an issue will be recognized.  
• Reports must be clear, reproducible, and related to UX/UI, exchange functionality, etc.  

---

6. Reward Distribution  
• At the end of the Beta Test, the Top 10 most active participants (based on the number and quality of bug reports) will be selected.  
• After the Beta Test period, the list of the Top 10 winners will be published in this thread. Each winner will then be required to provide their BTC or XMR address here in order to receive their payout.
• All reward payouts will be made publicly, and transaction hashes will be published here for transparency. Except XMR transactions as they can't be tracked..  

---

7. Reward Structure  

Rank	Reward
1st Place	$350
2nd Place	$250
3rd Place	$200
4th Place	$150
5th Place	$100
6th–10th Places	$50 each
Total Pool	$1300

 
Each winner can choose payout asset: BTC or XMR

---

8. Additional Information  
• Testnet tokens used during the Beta have no monetary value and can't be withdrawn.  
• Internal BRGX tokens have no value and can't be withdrawn during the Beta Test period.  
• After the Beta Test concludes, all accounts, balances, and transaction histories will be reset.  
• For detailed technical guidelines, please refer to the official GitBook documentation.  

---

I'm interested, but how do you reconcile this:

with this:

Do they refer to the same testnet bug hunting?

You may have to take a closer look at your website. I've made 3 attempts at signing up but it returned this error after filling email and checking captcha:

https://www.talkimg.com/images/2025/08/19/UZXyY8.png

Bug 2

I succeeded in registering after 5 trials. From my dashboard, the first bug I noticed is that the filter button isn't working. It opens briefly and jumps back to its default setting in a UI blink.

https://www.talkimg.com/images/2025/08/19/UZXcUa.png

Bug 3

Clicking my profile icon also resulted in no response. The only indication of an action on the website was a slight flicker in the browser and a fleeting view of the drop-down menu in the profile.

https://www.talkimg.com/images/2025/08/19/UZX4Wl.png

Bug 4

Only the Gitbook and Home pages are working properly. The other 3 pages, My Offers, My Deals and My Tasks exhibit UI blink errors.

https://www.talkimg.com/images/2025/08/19/UZdZyZ.png

Bug 5

This should be a discontinued session bug. Let me explain it this way. When I had an interruption in the internet network, I couldn't access my dashboard any longer. Instead, I met a blank homepage that refreshed automatically without loading up. I think the website's session management fails after network disruptions.

Bug 6

https://www.talkimg.com/images/2025/08/19/UZdDBw.png

The 'How it Works' page at the footer opens to the Bridgoro guide on using the platform. When I tried to close the cookies button, it led to this error page:

https://www.talkimg.com/images/2025/08/19/UZdWX9.png

Bug 6

The contact form link at the footer exhibits UI blink error. Clicking the link it shows the contact page briefly before it closes again.

https://www.talkimg.com/images/2025/08/19/UZuXZm.png

Thank you for your bug report and questions.
Please see our responses below:

General Notes:
- Minimum Exchange Amount: Currently set at around $30 USD equivalent due to network fee restrictions (fees scale with crypto volatility). During Beta Test, the minimum is reduced to $10 USD equivalent.
- Beta Test Mode: The Bridgoro platform is running exclusively on testnet networks for safe testing. After the Beta phase is complete and all critical bugs are fixed, we will switch to mainnet and enable full P2P exchange functionality.

Bug Reports:
1. Sign-Up Bug - [Fixed]
- Issue reproduced and resolved.
- Please clear your browser cache and verify the platform version displayed in the bottom-left corner: v0.1.4.

2. Endless Refresh Loop / UI Blink - [Fixed]
- Root Cause: The old sign-up flow auto-logged users in after code confirmation. With CAPTCHA introduced, this caused a duplicate challenge (at registration and login). To resolve this, we moved to the standard flow where login is required after registration.
- However, a legacy script still attempted fast login, generating unauthorized requests and blocking access to sections (MyOffers, MyDeals, MyTasks). After re-login, users were incorrectly redirected to the homepage.
- Resolution: Script removed, flow corrected. Please clear cache, log out, and log back in to confirm.

3. GitBook Guide Bug - [? Needs More Info ?]
- We couldn't reproduce this issue on our side. It may be client-specific.
- Please try to reproduce and provide detailed steps for further investigation.


Thank you again for testing.
You are our first bug reporter here on BOUNTY page, and since testers are limited, you currently have high chances to receive the main reward of $350 in BTC or XMR (your choice).

Bug 7

I clicked the "Trade" button for the BTC/ETH pair, the "Accept Offer" pop-up window showed instability and flicked on and off. Furthermore, the "close" button and "Accept Offer" buttons are frozen, only the "Cancel" button works.

https://www.talkimg.com/images/2025/08/19/UZuJF9.png

This is a great way to find bugs and errors. I will be participating and writing my bug-related post in a day or two. I like testing things and I read the whole instructions, I read the website and checked things, I would love to be a part of a beta test program, if you guys allow me, thanks.

Could you please provide more details, as we were unable to reproduce this bug?
- Browser: (e.g., Chrome, Firefox, Opera, etc.)
- Operating System: (Windows, macOS, Linux)

Cache Cleared: Please confirm whether you have cleared your browser cache.

If the issue persists, we kindly ask you to record a short video demonstrating the problem and share it with us via Telegram Support.

Thank you for your interest!
We appreciate your enthusiasm for testing and would be glad to have you participate in the Beta Test program.
Please feel free to submit your bug reports once you encounter any issues. Every valid report helps us improve the platform, and active testers will also be eligible for the Beta Test rewards.

Welcome aboard, and we look forward to your feedback!

hi, here are some of the bugs and/or problems that i found:

1. https://www.talkimg.com/images/2025/08/19/UZuWv5.th.png (https://www.talkimg.com/image/UZuWv5)

clicking edit profile but the save button is off screen, i tried to scroll down but it doesn't, im on chrome and my laptop screen resolution is 1366x768

i had to zoom out to find and click the save button. i don't know if u consider this a bug but it should either scroll or auto correct with screen resolution

2.https://www.talkimg.com/images/2025/08/19/UZwdOD.th.png (https://www.talkimg.com/image/UZwdOD)

this is on 'explore offers' page and i clicked 'trade' to try and exchange btc to solana but it doesn't have the option to enter rollback address for btc

as explained in the guide here: https://bridgoro.gitbook.io/bridgoro-docs/all-about-trading/how-to-accept-a-deal-offer

3. https://www.talkimg.com/images/2025/08/19/UZwAYZ.th.png (https://www.talkimg.com/image/UZwAYZ)

this is when i entered the solana address and tried to exchange 0.00008 tbtc

i aborted the exchange and tried again with 0.00005 tbtc for which the deal was created successfully, i don't know why it gave error for bigger amount

---

continued..

4.  https://www.talkimg.com/images/2025/08/19/UZwMRa.th.png (https://www.talkimg.com/image/UZwMRa)

this dialogue box should report how many confirmations are needed for the exchange to take place

also, it stayed the same even after 6 confirmations, it is only after closing it and reselecting the deal from: https://bridgoro.com/user/my-deals

that it changed to 'partially confirmed' and then to 'release ready' when it should do that without doing the above steps

also, now it is stuck on 'release ready' for last 10 minutes

5. also, on https://bridgoro.gitbook.io/bridgoro-docs

these pages are empty:

https://bridgoro.gitbook.io/bridgoro-docs/getting-started/notification-settings

https://bridgoro.gitbook.io/bridgoro-docs/all-about-trading/how-to-start-earning

guess this pages are just not made yet, so don't think it is a bug

6. https://www.talkimg.com/images/2025/08/19/UZwTY1.th.png (https://www.talkimg.com/image/UZwTY1)

same but again, when trying to exchange trx to solana

https://www.talkimg.com/images/2025/08/19/UZwt8m.th.png (https://www.talkimg.com/image/UZwt8m)

max was 177 trx, trying to exchange 150 and the above error popped up

7. https://www.talkimg.com/images/2025/08/19/UZwE5C.th.png (https://www.talkimg.com/image/UZwE5C) https://www.talkimg.com/images/2025/08/19/UZws2b.th.png (https://www.talkimg.com/image/UZws2b)

using filters on the 'explore offers' page

the first asset selection should show the pair you want to exchange and second field should what you want it to exchanged to

but see the screenshot above, when selecting the asset in first field it shows the pair u want to recieve

similarly the selecting the asset in the 2nd field shows what u want to exchange (send)

i think it should be other way around

First, I needed to clear cache to reassess the situation. By the way, I'm using Chrome on Window. Initially, I couldn't log out due to bug 3. After clearing cache, I noticed you've added images to the captcha, however, it seems to have created another bug (8 ) that froze the sign in button. I'm retrying it now. As soon as I log back in, I'll try and recreate it possibly with video.

https://www.talkimg.com/images/2025/08/19/UZwBKZ.png

Thank you for your BUG report
Please find our reply to your report below.

1. Screen Size Bug - [Added to Backlog]
Status: Identified
Details: A bug affecting screen size handling was reported.
Action Plan: Added to backlog. The fix will be implemented shortly, and an update will be posted in the next Bug Fixing Report.

2. Rollback for SOL - [Not a Bug]
Status: Closed (Not a Bug)
Details: Rollback Wallet Address is not required for Solana (SOL). Similar to BTC, ETH, and TRX, SOL transactions are fully traceable and sending addresses are visible on-chain.
Note: Rollback Wallet Address functionality is required only for Monero (XMR), due to its privacy features.

3. Dead Wallet Amount Bug - [Added to Backlog]
Status: Identified
Details: Root cause identified. Issue originated from test parameters used during Alpha testing.
Action Plan: Added to backlog. Fix will be deployed shortly.
Additional Fix: The Dead Wallet popup message will be updated to use more user-friendly language.

4. Deal Status Dialogue - [Not a Bug - UX Improvement Scheduled]
Status: Improvement Scheduled
Details: The current dialogue shows only the live status without auto-update. To refresh, users must close and reopen the popup, or monitor the My Deals page which does auto-update.
Action Plan: For improved user experience, auto-update functionality will be added directly to the popup dialogue.

4.1. Release Ready Status (Monero Specific) - [Not a Bug]
Status: Closed (Expected Behavior)
Details: Monero blockchain requires 10 confirmations ( about 20 minutes) before funds are marked as [Release Ready]. This is a protocol-level limitation, not a platform issue.

5. GitBook Disclaimer - [Not a Bug]
Status: Closed
Details: The main page of GitBook explicitly states:
Note: The guide is a work in progress and will be continuously updated and refined.

6. Dead Wallet Amount Bug - [bug duplicate]
Status: Duplicate (Merged with Issue No. 3)
Details: This is the same issue reported under point #3. Already tracked in backlog and currently in progress.

7. Filter Bug - [Added to Backlog]
Status: Identified
Details: Frontend filter functionality issue confirmed.
Action Plan: Added to backlog. Will be fixed in an upcoming release.

---

We would like to extend our sincere appreciation to all participants for contributing to the Beta Test.
Your feedback and reports are invaluable.
The appearance of bugs during this stage was anticipated, which is precisely why the testing environment was deployed on testnet networks. This allows us to identify and resolve issues without risk to user funds.

Thanks to your active involvement, in the near future (when we fix all bugs, of course ;)), we will be well-positioned to launch our semi-decentralized P2P exchange - a platform designed to provide crypto enthusiasts with a secure, transparent, and user-focused trading experience.

Please find our reply to your report below.

1. Sign-In Button Inactivity - [Unable to Reproduce]
Status: Investigation Ongoing
Details: A user reported that the Sign-In button becomes inactive.
Reproduction Attempts: Tested across multiple environments (MacOS, Windows) and browsers (Chrome, Firefox, Opera). The issue could not be reproduced — the button remained active in all test cases.
Action Plan: Awaiting additional input. To assist further troubleshooting, we kindly request a screen recording/video demonstrating the bug when it occurs.

2. CAPTCHA Image Prompt - [Not a Bug]
Status: Closed
Details: CAPTCHA image display is controlled automatically by the verification system. No manual configuration has been implemented to enforce when images appear. Depending on system checks, CAPTCHA may:
- Require image validation, or
- Pass the user without showing images.
Action Plan: No changes required. Behavior confirmed as intended.

---

P.S. Only reproducible bugs will be applicable for counting Beta Test participants' activity.

I just checked again. This is working just fine. I checked all the other pairs and it's resolved. I'll try making some test transctions to be certain every step works.

1. Account Creation Page is fixed and I am unable to scroll it, to view the content of that page, I have to zoom in and zoom out from the settings of my browser, I am on a desktop just to be clear, I think the viewpoint is fixed or there is problem in css overflow setting, I know a little css and html, so just guessing. You guys are dev, so you know better. As you can see in the image, there is no scrollbar and I am unable to see the last line clearly, where you wrote "already have an account? sign in", I know I can read it still, but It will be better with a scrollbar. A small part of the logo is also not visible on the top.


2. It is like a suggestion not some big error, but it worth the effort to change for a more sophisticated UI, in the image, question mark has been used, I think in place of this, an info icon should be used which looks like "i" or "ⓘ" I like the one with a circle around it.


3. The same scroll bar issue at the create deal window, as shown in the following image, same issue as shown in the image one. Although the switching option is very great and the options below of min, half and max is also a very useful.

4. After creating the deal from ETH to BTC, transaction status window came, I feel the lack of a QR code for the deposit address, because I have used many such exchanges and most of the time I have to make the tx from mobile and it is really handy to use QR code. Plus besides this QR code thing, don't know why after few second it was on loading, because the exchange rate was not changing at all if that's why that window was loading, as shown in the picture.


5. Time to confirm from blockchain is a bit time consuming, I mean 38 blockchain confirmation so far and the tx is still stuck at Deposit phase on Deal Details window. If it's possible please lower the blockchain confirmation number, or if you have already lowered it, then it is taking more time than the lower number. After 10 minutes I checked the btc wallet, I received the funds but the window is still loading on the deposit phase, it is not going to the next stage of processing or to the next phase, and the next page I saw was my offers after closing the deal window, and my deal was completed there in status, so clearly there are some flaw, it was stuck at deposit phase, not moving forward from there.

6. Same scroll issue on the create offer window, I think I don't have to add image, but one more thing after clicking the create offer button it take around 2 to 3 second then it shows the window, the delay is a bit laggy.

So far this was it, I will be testing it more for other conversion for now I have tested it for ETH to BTC, it worked well besides the one issue I explained, and I will test ETH to XMR, TRX, BTC and SOl and for all other assets I will do the conversion, in my next post, you can say this was part 1.

This wasn't a bug, I actually missed the verify button at the base of the images either because I didn't scroll down enough or the button didn't  render initially.

Thanks for explanation.

---

Doing our best in fast resolving bugs.
Good luck with the tests!

Same thing with mine, when I tried TRX-SOL order the first time, it popped the same kind of error, I did not think the amount was the issue… I refreshed the page and repeated the process again but it kept showing the same error, it was when i reduced the amount that it went through…

I faced the same issue but it was about the detail about amount, you guys should increase the amount, you must click the max button beneath the amount option when making this order this way the problem can be solved, it is not an error although when I faced this issue it was a bit hard for me to understand what is happening, so when I give it a try I understood the error but I hope the team will change the text into an easier one for easy understanding of a normal joe.

Check the offer detail before making the transaction and then do the rest to go beyond this point.

Thanks for the first part of your reports.
Looking forward to the second part.
Please find our reply to your report below.

1. Screen Size Bug - [bug duplicate]
Status: Fixing in Progress (Previously Reported)
Details: Adaptive UI issues identified.
Additional comment: During development, the two of us (yes, just two devs behind this whole project) were completely absorbed in building the semi-decentralized core: the cross-chain blockchain adapters and escrow buffer wallets. In that process, we overlooked one important thing: the adaptive layout.
That's on us, and we admit it openly. The good news is that we've already rolled up our sleeves and started fixing the adaptive design to make the user experience smooth on every screen size. This update is coming very soon.

2. Explore Offers Info Icon - [Added to Backlog]
Status: Scheduled for Fix
Details: Current implementation uses a ? icon. User suggestion to replace it with ⓘ provides clearer UX.
Action Plan: Icon replacement has been added to backlog and will be implemented by tomorrow.
Additional comment: We admit that your version of the icon is better than ours.

3. Scroll Issue (UI Adaptivity) - [bug duplicate]
Status: The  bug is the same as Screen Size Bug
Details: Scrolling inconsistencies are linked to the same adaptive design bug as mentioned in Issue 1.
Action Plan: A full review of all pages and popups will be conducted to ensure proper adaptivity across screen sizes.

4. QR Code Implementation - [Added to Backlog]
Status: Pending Implementation
Details: QR code functionality has not yet been integrated.
Action Plan: Feature request accepted. QR functionality will be added in upcoming updates as part of UX/UI improvements.
Additional comment: The loading status appears because the system is constantly checking the exchange rate and other status updates in the background.
Please note that this popup doesn't yet include an auto-update feature (we are already working on it and will be adding it soon).
In the meantime, you can track updates in two ways:
- Use the My Deals page, which already supports auto-updates, or
- Simply reopen the deal by clicking on it in the table.

5. Blockchain Confirmation Times - [Not a Bug]
Status: Closed
Details: The platform already uses the minimum possible confirmations for each blockchain to ensure stable escrow module operation.
ETH, SOL, TRX have fast confirmation times: Partially Confirmed within a few seconds. Confirmed | Release Ready within less than a minute.
BTC, XMR have longer confirmation times are inherent to blockchain design. For Monero (XMR) is 10 confirmations (around 20 minutes) are required due to protocol limitations.
Action Plan: No changes required. Behavior is blockchain-protocol dependent.
Additional comment: As mentioned earlier, the status section in the popup doesn't yet include an auto-update feature. We are already working on adding this functionality in an upcoming update.
In the meantime, we recommend checking the deal status on the My Deals page, where updates are reflected automatically.

6. Scroll Issue (Duplicate) - [Duplicate of Issue No.1 Screen Size Bug]
Status: Merged with Issue No. 1 and 3
Details: Same adaptive UI bug as reported above. Already in backlog for resolution.

6.1. Button Click Delay / Lag - [More Information Required]
Status: Pending Investigation
Details: Button click lag has not been reproduced during testing.
Action Plan: Request user to clear browser cache. If issue persists, please provide a video recording of the delayed click and forward it to our Telegram Support, referencing your Bitcointalk report.

Welcome aboard!
We are glad to have you as a new participant in our Beta Test! 🎉
The bug with the Dead Wallet Amount has already been logged in our backlog and will be fixed soon, but we truly appreciate you taking the time to report it.
As a quick reminder, during the Beta Test period, the minimum exchange amount is set at $10 (USD equivalent). You can easily verify this by checking the USD field on the right side of the interface.

Thank you for helping us explain the UI to other users, we really appreciate your support!

Just as a quick clarification: the exchange amount only needs to be entered for Flexible Offers (when the Fixed Offers toggle is off). This type of offer was designed specifically for users who want to create large-amount offers, allowing multiple participants to accept portions of it. This approach makes it easier to match demand, since very large offers typically attract fewer single buyers.

But we would like to admit that there is a bug with the Dead Wallet amount and we will fix it within tomorrow or a few days.
You can find more details about the Dead Wallet Amount part on our GitBook page (https://app.gitbook.com/o/OvGWurZu76ZIZG8StHJn/s/u2Dw921L0PDeSbvkxcPl/system-architecture/how-do-buffer-wallets-work#dead-wallet-prevention).

Will be trying this..

understood not a bug but maybe this functionality should be added.. ??

because often time people send from other exchanges/casinos

i did that just yesterday, cashed out usdt(bep20) to a cryto-swap site

and received btc in my wallet but still provided them with a bnb address

in-case something goes wrong during the swap and they need to send the usdt back

but whether this is required or not is totally up-to u :)

Quoting my posts from the other topic here as I was requested to post here to participate in the Beta Test Reward Program:

1. You guys are doing great, because 2 developers and managing the project and the thread, I noticed you guy are also managing the ann thread by yourself, giving long replies to everyone in detail and at the same time managing the project, bro I have to admit you guys are putting real effort. You deserve success. And sorry I did not noticed someone has already published the scrolbar issue as when I started testing and writing I only saw the contentcreation post, so maybe that's why.

5. I think I failed to share the actual problem here, You see the window that shows up to tell us the stage we are at, like in first we are at Created stage-->Deposite Stage-->Processing Stage-->Completed

So when I created the transaction and went on the next stage of deposit and confirmed the deposite, it kept loading there for more than 12 to 15 minutes until I thought maybe I have received the funds in btc wallet (testnet) but that window was still stuck at deposit stage, it was not continuing to the next stage of processing or completed, that's what I meant in the 5th point. I hope I have successfully conveyed my point.

6.1  I am using Chrome, I cleared the cache and checked again, I am still feeling a lag. One more thing, when I tried it before clearing the cache it was too slow, and it also gave the following error, but after clearing everything it did not gave any error, and it also not lagged like that but still lag a little or maybe I am being too fast. Well, I will upload the video if it feels to laggy again, or will test it on differnt chromes, but for now I think it's personal perspective not an error.

Count me in as well, the intent is to find as many bugs as I can to win the first reward haha just kidding, although it is convincing haha. I will share once I found any bug or error as many have already shared by others.

Bug Report 9


I called this a report since I'm not sure it's a bug, but maybe...

When I got to the Transaction Status page in the TRX/SOL pair, the flowsheet showed blue on the created element. After I made a deposit, the deposit element also showed blue. This is where things got quiet and uncertain. The processing element showed its default color, and even after I saw double check marks on the completed element, I was at a loss if those check marks have been there prior to my deposit or not.

What I'm saying is that there should be a clear indication of progress made in the course of the transaction. As it stands, after making a deposit and several minutes after the deposit has been confirmed, there was no indication of any progress and I didn't see any indication that the funds have been received by my SOL wallet.

So I suggest an automatic change of color of elements as each stage is completed. I also suggest that the buyer finds evidence that their coins are in their wallet after the Completed element shows blue. Perhaps this page should automatically link to the transaction ID that sent the coin to the buyer.

Update: I saw that this has been implemented. Though the user has to close the deal window to see it on the main dashboard page. Well, there should be information about this for new users' sake

On a side note, how would someone know that the buffer wallet isn't in control of one person who could commandeered the funds if it's tempting enough? For transparency, this should be made obvious on the homepage.

https://www.talkimg.com/images/2025/08/20/UZn822.png

Bug 10

I sent TRX but didn't get SOL. Here is my txid: 17f0d22fdfbaffb27de80eed2f8b5ae78c3de69e206caaacaf4fac7f5de84591

You can see it's been over one hour.

https://www.talkimg.com/images/2025/08/20/UZnpOq.png

Welcome to the Beta Test, and we are glad to have you on board!

---

As mentioned earlier, there is no need for this feature with BTC, ETH, TRX, or SOL, since these blockchains are fully traceable.
In case of any failure, deposited funds can always be returned to the original sending wallet automatically.

However, Monero (XMR) works differently, its blockchain is designed for privacy and can't be traced in the same way.
That's why, for Monero specifically, the system needs to know in advance where to send the funds back during a Rollback procedure.

---

Welcome to the Beta Test! Your feedback will shape the future of our platform!

---

Yes, managing Bitcointalk threads can be quite time-consuming, but we fully understand how important this is at the current stage.
Users are dedicating their time to help us improve the project, and we want to give them the best possible support so we are doing our best to stay active.
That said, after two very intense weeks (Beta release preparations and release, [ANN] announcement preparations, launching the Beta [BOUNTY], and bug fixing), we will definitely need a short 2–3 day break closer to the upcoming weekend to recharge and come back with fresh energy.

---

As mentioned earlier, the popup screen currently doesn’t have an auto-update feature. For real-time tracking of your transactions, it’s better to use the My Deals/My Offers pages, where auto-update is already available in the offers table.
We've also noted above that the popup auto-update will be added in one of the upcoming bug-fix updates.
For now, we recommend simply closing the popup after confirming your deposit and tracking the status directly on the My Deals page.
Status: [Already added to backlog]

---

That’s interesting because we haven’t encountered any lag issues on the platform before.
If possible, could you please share the specs of your hardware? And if you are able to record a short video showing the input lag, that would be extremely helpful for us to investigate further.
You can send the video to the support account on Telegram: https://t.me/bridgoro_support (https://t.me/bridgoro_support)

---

Welcome to the Beta Test and thank you for joining us on this journey!

---

We have already taken into account adding the auto-update feature to popup screens, and we will notify users once it's implemented.
Also, your idea about using different colors for statuses is a great suggestion, we really like it, and we've added it to our backlog for future updates.
Status: [Already added to backlog]

---

To be honest, I don't have a clear answer to this question at the moment. I will need to discuss it with my teammate, and if we come up with any solid ideas, we will definitely share them here.
But I've already answered for similar question for another user, so let me put this answer for saving time:

---

Let us finish fixing the current batch of reported bugs, and then we will investigate your transaction in detail.
We will get back to you with the results as soon as the investigation is complete.
Status: [Added to backlog]

Here are the results of our brief investigation:
We can confirm that about 51.2 TRX was sent roughly 2 hours ago, and the Offer was was partially exchanged (you exchanged only partial amount from the total offer amount).
The corresponding SOL release was made to the following Solana Devnet wallet address:
Could you please double-check your receiving SOL wallet address and review the transaction history there to verify?

For transparency, this Offer was created by our team, and we can confirm that we received the TRX you sent for the exchange.

My initial plan was to post one complete review, but it's going to be bits and pieces as I go now.

There's a rounding problem when accepting someone's offer. I entered the Maximum Exchange Amount (BTC):
https://loyce.club/other/bridgoro1.png
When I entered that amount, I didn't realize it would lead to a XMR amount that's higher in the 6th decimal. Result:
https://loyce.club/other/bridgoro2.png
When I tried again, the maximum BTC amount was a few sat lower, I copied the Receiving Amount (XMR), I could create this deal without problems:
https://loyce.club/other/bridgoro3.png

TL;DR: expected behavior in my first attempt: the BTC amount should have been accepted, and the XMR amount should have been adjusted to the Maximum to get.

Thanks for the explanation. I confirm that I have received the SOL payment.



This is expected, taking liquidity at this time into cognizance.

One more thing. I was wondering if this project's code is open source. I am saying this because the community would trust it if it is.  

Another Bug report

I tried the ETH/TRX pair but it couldn't create deal. The error message said to enter supposedly smaller amount but the exchange proposal I made was the least.

https://www.talkimg.com/images/2025/08/20/UZQwc2.png

Posted this twice. Will delete.

Thank you for reporting this bug.
We are already working on issues with the Min / Half / Max buttons, and we've added the rounding value fix to the same bug list.
Status: [Added to Backlog]

---

We are glad to hear that your trade went smoothly.

---

We will be doing the same at release: creating as many exchange offers as possible with open amounts (Flexible Offers), backed by our own liquidity of $15k–$20k.
This way, even if no new offers are created by other users right away, anyone who simply wants to exchange will still be able to use the service.

We understand that our liquidity is just a drop in the ocean compared to the broader market, but we hope our exchange will still find its users and community.

---

The project will become open-source once we've polished all parts and ensured that releasing the code won't expose users to risks. We just want to be confident that making it public won't give potential bad actors an opportunity to look for exploits. After that, we will be glad to open it up to the community.
As mentioned earlier, we are fully prepared to undergo a complete audit by a trusted, official company. This would be done under an NDA, ensuring that the code won't be published or disclosed until we decide to make the project open-source.

---

The Dead Wallet Amount bug has already been added to our backlog. We expect to have it fixed by tomorrow, or at the latest, within the next few days.
Status: [Already added to Backlog]

---

Thank you all for constantly sharing your feedback and bug reports.
We really appreciate it!
At this point, we've collected a number of bugs and are focusing on tracking and fixing them. Managing the thread is quite time-consuming, so for today, we'd like to dedicate our efforts fully to development and bug fixing.
Of course, please continue sending your feedback, and we will make sure to review it tomorrow.

Unconfirmed Bug at the ETH/SOL pair

Cross-check a potential bug in the ETH/SOL pair. I couldn't grab a screenshot because when I repeated the process, the system said the deal was no longer active. As usual, I wanted to place an order using the minimum amount but got an error message. Paraphased, the message said the order amount (output) was lower than the fees or something like that. Is this how the platform is progrmmed to work? As in you don't process order whose value is lower than their network fee?

According to Bridgoro I was the first one to notice a bug with using this exchange, and I already reported this to main exchange topic.

I used Firefox browser first time I registered on Bridgoro and everything looked fine, I received 6 numbers on my email and I was able to enter them to confirm my registration.
But as soon as I opened my account I saw that I was not able to use it because it was constantly loading, and whatever I clicked on it was not working.
Page was spinning constantly and it was impossible to do anything on website.
I did not take any screenshots at this time.

I made a break and decided to try creating another account and see if that could solve my issue, but I run into second bug.
Procedure was the same like the first time, but this time I was unable to login to my account after entering 6 numbers and solving captcha correctly.
I saved the screenshot showing this error User not assigned:

https://www.talkimg.com/images/2025/08/20/UZG1P3.jpeg

1. At the end of the website front page, there is a button with the name of "support" that is not working, or maybe the information is not adding, because whenever I click to open this page, it says this site can not be reached, maybe because this button is linked with the project team's Telegram account. If that's so, my honest suggestion here is that the team should move to some other sources and add those links that can be accessed by anyone, anytime, and anywhere in the world. These kinds of links represent the project worldwide, and as far as I know, Telegram is banned in some countries. I also know that they all can use VPNs to use Telegram, but this is a kind of hurdle that is coming between the users and the project team. One more thing, this kind of thing disturbs the reputable project's image and puts a negative image in the users' minds when they are unable to use the services properly.

https://talkimg.com/images/2025/08/20/UZGEP2.png


2. When I am using the TradingView chart at the beginning of the page, there are some indicators there, and when I click them, it drags me down to the contact page and says that "Verification expired; check the checkbox again." The charts are page views, somehow linked to the contact form page. Need to update this bug, as it can disturb the users who are visiting the website.

https://talkimg.com/images/2025/08/20/UZGV4Z.png                        https://talkimg.com/images/2025/08/20/UZGjx8.png


3. This is one of the big mistakes near me, as it also represents the quality of the project teamwork. When I scrolled down a little, I saw an 'About' section about the project. There, I noticed that there are many mistakes in the brand name because the real name of the brand is "bridgoro", but there it is written as "Brigdoro". I am mentioning only the first brand name mistake, but there are some others as well. Please replace it with the correct one.


4. At the end of the page, I found that there is a whitepaper page of the project. But when I click it, then it redirects me to the page where users can read about the roadmap, plans, transparency of the project, security for the user, KYC terms and conditions, and that kind of thing. But there is no clear sign about this when I open this page, and there it is just written "coming soon". The project is currently live, and I believe that this kind of thing should be posted before anything else because this represents the project's plans, terms, and conditions, and many other factors. My suggestion here is that this page should be completed as soon as possible.



I will keep updating myself in this thread so that I can help or contribute to finding more mistakes and bugs for the better representation of this project. Best of luck and best wishes for the project's success.  :)

Thank you for your report!
This isn't actually a bug, rather, it's a contradiction between the minimum exchange amount and the Dead Wallet Amount. On top of that, we've identified another conflict with dust transactions.
We are already working on both issues. In the meantime, we kindly ask users not to trade with amounts below $12 (USD equivalent) until the fixes are in place.
Status: [Work in Progress]

---

A few days ago, we experienced a bug that caused an endless page refresh loop, but this issue has already been fixed.
Please try clearing your browser cache, logging in again, and let us know if the problem still occurs.

As for your report about the User not assigned error message, we've added it to our backlog.
We will investigate further and get back to you with a detailed report once we have more information.
Status: [Added to backlog]

---

This sounds unusual, since the Support button is linked correctly:
https://t.me/bridgoro_support. (https://t.me/bridgoro_support.)
This link leads to our Telegram support account. Normally, when you open it, the Telegram web version should appear, followed by a popup prompting you to open the Telegram app.
Could you please try opening this link in your browser again and share a screenshot of the error page, making sure the URL bar is visible as well?
Status: [Under investigation]

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.

---

We will check this.
If possible, please try clearing your browser cache, attempt to recreate the issue, and let us know if the bug still appears.
Status: [Added to backlog]

---

Thank you for pointing out the text mistakes as well. We really appreciate it and will count this as a bug.
All text errors on the exchange will be reviewed and corrected shortly.
Status: [Added to backlog]

---

This is not a bug.
On the main page of our GitBook, we've added a note that clearly states:
Note: The guide is a work in progress and will be continuously updated and refined.

As for the Whitepaper, it's coming soon. Right now, it's under review to make sure no sensitive information is included that could potentially be misused by bad actors and put users' accounts at risk.
Status: [Not a Bug]

---

We truly appreciate your effort in helping us polish the project.

it sends me to this page:

https://www.talkimg.com/images/2025/08/21/UZmcka.png (https://www.talkimg.com/image/UZmcka)

---

also, i found something else, i don't know if it was already reported or not

but if u click on the (i) button next to a 'trade' on 'explore offers' page

it opens up a window that shows the buffer address and an icon next to it to copy it

and another icon further next to it 🔍 which opens up the blockchain explorer for the buffer address

but if the address is too long, the search icon disappears and in some cases, even the copy icon vanishes

i'll post some images to prove what i am saying:

1. here u can see that the address is small and both icons are perfectly visible:

https://www.talkimg.com/images/2025/08/21/UZm7h1.png (https://www.talkimg.com/image/UZm7h1)

2. and here is what happens if the address is too long:

https://www.talkimg.com/images/2025/08/21/UZmiVJ.png (https://www.talkimg.com/image/UZmiVJ)
https://www.talkimg.com/images/2025/08/21/UZm8DC.png (https://www.talkimg.com/image/UZm8DC)
https://www.talkimg.com/images/2025/08/21/UZmgmW.png (https://www.talkimg.com/image/UZmgmW)

---

one more thing:

what is 'deposit deadline' is it a date when a trade offer auto expires?

https://www.talkimg.com/images/2025/08/21/UZmWdg.png (https://www.talkimg.com/image/UZmWdg)

because if that is right then this offer shouldn't be active?

---

found something else..

this is my cpu usage without bridgoro open:

https://www.talkimg.com/images/2025/08/21/UZ6Qj3.png

and this is after i open bridgoro

https://www.talkimg.com/images/2025/08/21/UZ6C68.png

note:: the cpu only jumps on the homepage, if i go to the exchange offers page

it cools back down

https://www.talkimg.com/images/2025/08/21/UZ6mn9.png (https://www.talkimg.com/image/UZ6mn9)

Thanks for testing the Support button.
It appears to be working properly, so this case is now closed.

---

Yes, we see the issue, this is a frontend bug. You likely encountered it because we are currently working on improving page adaptivity for all screen sizes.
In any case, we've added your report to our backlog and will recheck it once the Screen Adaptivity Fix is completed.
Status: [Added to backlog]

---

The Deposit Deadline is the time limit after which a created offer or accepted deal will expire if funds aren’t sent to the Buffer Wallet Address or even if you press Confirm, but the deposit doesn’t actually arrive.

For your information: this specific offer was created by us last week during internal tests and is still active.
It's strange that you are seeing an incorrect status, since on our side, it shows as active on different test accounts.
Could you please refresh the page (press Shift+F4 on Windows or CMD+Shift+R on Mac) and check the offer status again?
Status: [Under investigation]

---

This happens because we added a visual frontend effect with flying particles designed to look like Earth.
If it causes CPU overload on your side, we will consider either turning it off permanently or adding an option for users to disable it manually via a switch next to the Light/Dark theme toggle.
Such bug reports are also precious, thanks.
Status: [Added to backlog]

Bug Report

Even without taking action, when I access the Explore Offers page using Chrome, I routinely get this error message: 'Unexpected error' even when I hadn't taken an action. I doubt this is a server overload issue but do check. It actively interferes with process buttons whenever it pops up. And it does pop up during any of the stages of creating deals.

https://www.talkimg.com/images/2025/08/21/UZ6tNT.png

i did something better, i opened up the site in the 'new incognito window' so that i don't get any old page due to cookies or whatever

logged in and went to the offers page and this is what i found:

https://www.talkimg.com/images/2025/08/21/UZ6EPm.png (https://www.talkimg.com/image/UZ6EPm)
https://www.talkimg.com/images/2025/08/21/UZ6IjW.png (https://www.talkimg.com/image/UZ6IjW)
https://www.talkimg.com/images/2025/08/21/UZ6Fx1.png (https://www.talkimg.com/image/UZ6Fx1)

Thanks for your report!
This error occurred during the current server maintenance update with bug fixes.
We will keep it in mind for the future and continue monitoring it closely.
For testing purposes: Could you please try logging in with a different browser (one you haven’t used for this project yet) and let us know if the error appears again?

---

I see.
Could you please also try using a different browser (one that hasn’t been used previously for this project) and check again if the issue appears?

yeah it says active,, only says that 'deposit deadline' when clicking the clock icon below ⏱️

We've finally managed to catch this bug and confirmed that, in some cases, the ACTIVE status changes incorrectly to DEPOSIT DEADLINE.
This issue is already under investigation, and we will share updates as soon as we have more details.

---

Bug Fix Report is coming soon
Since the launch of the Beta Test, we've already fixed a lot of bugs, and there are still many more to work on.
To keep everyone updated, we've decided to prepare a Bug Fix Report for our users. (will be published soon)

Bug and Issue Report
Date: 08/21/2025

Fixed:
- Screen Adaptiveness - improved for all resolutions, including smaller screens down to 640px.
- Scrollbar for Smaller Screens - added to improve navigation.
- Endless Refresh Loop / UI Blink - resolved.
- Sign-Up Bug with CAPTCHA - fixed.
- CAPTCHA Optimization - improved stability and behavior.
- Homepage Text Mistakes - corrected.
- Explore Offers Table Content - fixed to display correctly.
- Info Icon on Explore Page - replaced with improved version.
- Filters on All Pages - corrected for consistent behavior.
- Offer Details Popup - now displays accurate information.
- Notifications via Telegram Bot - fixed to work properly.
- Invite Code Button - corrected appearance.
- BRGX Withdrawal Page - conversion to USDT and network fee deduction fixed.
- Page Refresh Handling - fixed to refresh correctly without redirection.
- Account XP Crediting - corrected when registrations come from trusted domains (e.g., gmail.com).
- Username Change Bug - fixed on Edit Profile page.
- CAPTCHA Bug During Registration - resolved.
- Profile -> Balance History Tabs - corrected BRGX description tags.

Under Investigation:
- Release Ready Stuck Status - linked to dust transactions.
- Deposit Deadline Status - inconsistent behavior under review.
- TradingView Charts Bug - currently investigating.
- User Not Assigned Error - reported, pending deeper analysis.
- Button Click Delay / Lag - requires more reproduction data.

Work in Progress:
- Frontend Visual Effect Optimization - Homepage performance tuning.
- Dead Wallet Amount Bug (Min Amount) - reworking logic (backend).
- Amount Rounding Bug - fix in development.
- Dead Wallet Buffer Error Popup - improvement in progress.
- Popup Status Auto-Update Feature - being implemented.
- QR Code Implementation - feature in development.

Summary:
- 18 issues fixed (UI, adaptive design, signup, notifications, withdrawal, profile, XP crediting, etc.).
- 5 issues under investigation (status handling, charting, lag, assignment errors).
- 6 items actively in progress (UX/UI improvements, error handling, QR feature).

---

Along with the Bug Report, we would also like to share some development details.
This might be interesting for the dev-minded members of the community, and we would be glad to hear your feedback or thoughts about our tech stack.

Behind the Development

Our platform is built with Rust, one of the most reliable and secure programming languages in the world.
Rust is known for its safety, high performance, and ability to handle complex tasks without compromising speed, making it a perfect match for financial and blockchain applications.

At the core, we use Tokio, a powerful asynchronous engine running in multi-threaded mode.
This means that every incoming HTTP request is processed in a dedicated thread, allowing our system to handle massive loads and thousands of simultaneous requests without slowing down.
We've designed the system with a modular architecture, and each module works as an independent service, ensuring both efficiency and fault tolerance.

For example:
The Exchange Rate Module runs in its own thread, pulling prices from three independent sources. It continuously caches, updates, and delivers real-time exchange rates to the client. If one API fails, the system automatically switches to a backup, guaranteeing uninterrupted service. All rate history is stored, with updates synced every minute in line with CoinMarketCap's API limits.

For the web server, we rely on Axum, developed by the same creators behind Tokio. Axum combined with Tokio gives us the ability to sustain extremely high volumes of traffic and process a massive number of requests in parallel: ensuring reliability, stability, and speed under any conditions.

In short, our system was designed from the ground up to be fast, resilient, and secure.
Whether it's handling real-time exchange rates, managing blockchain interactions, or processing thousands of requests simultaneously, the architecture ensures that users always get a seamless and reliable experience.

https://talkimg.com/images/2025/08/21/UZRG3N.png

It is still not opening on my side, because I already mentioned that Telegram is banned in many countries, and to use this app, we have to use a VPN to access the Telegram app. So my honest suggestion to the team is to add some other source of support so that anyone can approach the team without having any problem or trouble.

We are sorry to hear that Telegram is blocked in your country.
For now, you can still reach us through the Contact Form (https://bridgoro.com/#contact) 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.

---

Information for users who tested the Contact Form

Yes, the Contact Form works correctly, and we've received your TEST messages.
Thank you for taking the time to test this feature as well!

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.

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: https://talkimg.com/images/2025/08/22/UZtTfW.png

Referrals tab : https://talkimg.com/images/2025/08/22/UZtFHC.png


2nd:

Submitted button is spinning that is not stopping:

https://talkimg.com/images/2025/08/22/UZtUUG.png


3rd:

https://talkimg.com/images/2025/08/22/UZtaRD.png

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)
https://talkimg.com/images/2025/08/21/UZPpag.png


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'

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.

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  ;D.

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]

---

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]

---

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]

---

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]

---

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]

---

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]

---

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

---

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]

---

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]

---

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.

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

---

---

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.

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.

---

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.

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.

https://www.talkimg.com/images/2025/08/22/UZNlpZ.png

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, I will love to say someone here on the forum about my contributions. That's the part I love most.

This is great, thanks for the approval.

---

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.

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.

"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]

---

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]

---

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.

---

Who doesn't love  :)

---

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

---

Thanks a lot. Doing our best.

---

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]

---

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]

---

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]

---

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.

https://www.talkimg.com/images/2025/08/23/UZsFH5.jpeg
@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.

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??
https://www.talkimg.com/images/2025/08/23/UZs9JT.png

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 ?

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.

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.

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

---

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.

           https://talkimg.com/images/2025/08/24/UZfN2W.png               https://talkimg.com/images/2025/08/24/UZfz5m.png

Other than this, other small tasks were completed and claimed smoothly. I have even received their completion mail on my Gmail account.

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.

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:

https://www.talkimg.com/images/2025/08/25/UZr2Zb.png

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.

---

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 (https://bridgoro.gitbook.io/bridgoro-docs/terms-and-privacy/terms-and-conditions) and Privacy Policy (https://bridgoro.gitbook.io/bridgoro-docs/terms-and-privacy/privacy-policy) for details.

---

We are actively working on reported issues. Don't worry, we will update you as soon as the next fixes are rolled out.

---

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]

---

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.

---

We will investigate this Invite Code link bug.
Status: [Under investigation]

---

We will check this bug as well.
Status: [Under investigation]

---

Thanks for your reports.

---

We will post an update on both the ANN and BOUNTY threads once the Discord server is launched.
Thank you for your support!

---

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]

---

All of this has been possible thanks to you - the Bitcointalk community.

---

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

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

https://talkimg.com/images/2025/08/24/UZJ4uD.png

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

https://talkimg.com/images/2025/08/24/UZJ5Nf.png

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.

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.

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

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.

---

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

---

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

I'll continue my testing in this topic.

First: after all the annoying captchas to get started, I'm glad to see Bridgoro.com stays logged in on for days on Tor browser. It's still working since my first session.

I think both were mine. I've received 0.00021777 BTC with txid 0d44d609e4ef116abe2652542a312ab8dff9b83bcb1d0a4445cc2f4cce7f41e2 in exchange for my XMR.
My other offer, in which I should receive XMR, says "RELEASE READY" but I haven't received anything yet.

I'll try to buy XMR again: txid 9c9ce257d909a8904928788141c6a95cb08f22195ac1e8794ae3bd2dfd199433. After 40+ confirmations, the status is "PARTIALLY CONFIRMED RELEASE", and XMR has 3 confirmations in my wallet. So this worked smooth :)

---

---

What if CMC fucks up big time, and displays the wrong price? This has happened before (https://markets.businessinsider.com/news/currencies/coinbase-coinmarketcap-crypto-price-glitch-exchange-data-provider-trading-error-2021-12), and if you don't detect this, some seller is going to be very disappointed while your buyer hits the jackpot!

There's a sequence of status change after the deposit is made by the buyer. The status before 'Partially Confirmed Release' has a typo. Even though I couldn't exactly know what it was because it had changed before I could read it, you should cross-check it.

https://www.talkimg.com/images/2025/08/25/UZLpdj.png

I've been having difficulties charging my Monero stagenet wallet. I don't know where the issue stems from but as soon as I succeed I'll check more pairs.

I'm incredibly impressed with the progress you've made on this project, particularly since you became active in the forum. The speed at which you've resolved most of the issues we identified during the bug bounty is remarkable. It's a testament to your painstaking work that the majority of the findings were frontend issues. The community is genuinely hopeful for Bridgoro's success and its future as a bulwark in the No KYC exchange market.

We couldn't reproduce the bug on our side, but we have reworked the TradingView chart and the CAPTCHA on the Contact Form.
Could you please clear your browser cache and check again on your end?
Let us know the results once you try.
Status: [Need to Test]

---

The Invite Link issue on the registration page, with the code not appearing correctly, has been fixed. The Invite Code should now display properly when the link is used.
Could you please clear your browser cache and check it again on your side?
Status: [Need to Test]

---

Here is the transaction path for ETH:
User A Wallet -> Buffer Wallet -> Smart Contract Address -> User B Wallet

---

We are sorry about the CAPTCHA issue.
This problem occurs specifically when using the TOR browser. Unfortunately, at this stage, we can't remove the Google CAPTCHA, but we do plan to implement our own CAPTCHA system later.

---

Glad to hear you were able to successfully make exchanges with BTC -> XMR and vice versa.
Thank you as well for providing valuable feedback regarding Dust Transactions, it really helps us improve the platform.

---

We anticipated that situations like this could happen if the CoinMarketCap API fails to work properly.
That's why we integrated two backup price providers: CoinGecko API and Coinlib API.

The system works as follows:
If CMC API goes down, then backup CoinGecko API is activated.
If CoinGecko API also fails ->  the second backup Coinlib API takes over.

The probability of all three APIs failing at the same time is extremely low.
Of course, I understand your concern, but nothing in crypto is 100% safe. But risks can be minimized through cautious preparation and layered backups, which is exactly what we've built in.

---

We will check for any typo mistakes and fix them if found.

In the meantime, have you looked at our GitBook Guide for Beta Testers (https://bridgoro.gitbook.io/bridgoro-docs/bridgoro-beta-test)?
If you still encounter issues with Monero GUI, feel free to share them here, and we'll do our best to help.
Status: [Added to Backlog]

---

Thank you for your support!
By the end of this week, we will publish another Bug Fix Report with the latest updates.
A backend patch with additional fixes will also be rolled out, though a bit later.

I have one question about the statement already added to backlog, does it mean the bug I reported has already been added to the backlog or someone else has reported it already before me, sorry if it is a silly question.

I just tested it and the issue still resist, I tested it on a new apple device and the issue is still there, do I still have to clear the cache even the device I am using has never been used before to use the bridgoro site before?

Thanks for the confirmation, actually I was also tracking the funds and found out that funds move into another wallet after they entered buffer wallet, like the smart contract address.

I get that you use backups, but from your explanation it's not clear if your system covers this scenario: what if CMC's API still works, but gives the wrong prices (as in: 1 BTC is worth $799 billion). Do you also compare those prices to other API prices?

8.

Range bug:

https://talkimg.com/images/2025/08/27/UZ7DF9.png
https://talkimg.com/images/2025/08/27/UZ79VD.png
https://talkimg.com/images/2025/08/27/UZ7Wxa.png

0 to 0.00014998999999999999 brings up ETH-BTC offer which I created.

10 to 1499.999999999999888 brings up the SOL-TRX pair which is created by another user.

0.25 to 0.286965323999999999 brings up the TRX-SOL pair which was created here in this report:

I would like to participate here as it's seems interesting. So add me there for submission.

If you see the status [Already added to backlog], it means that another participant has already reported this bug, and it's been scheduled for fixing.

---

No, you don't need to clear the cache if you are testing on a new browser or especially on a new device.
We will double-check the previous fix and get back to you once we are sure this bug is fully resolved.

---

I understand your question, and to be honest, the system currently doesn't compare API data from different sources for discrepancies.

However, your scenario makes sense, and we will take it into account.
In the future, we plan to update the price comparison system so that data from all three sources will be cross-checked.
If one source shows a discrepancy, the system will use the majority consensus from the other two.

---

Thanks for testing the Filters section.
The similar bug on the Withdrawal page is already in the process of being fixed. This new one has now been added to the backlog as well.
By the end of this week, we will publish another Bug and Issue Report with updates.
Status: [Added to backlog]

---

Welcome to the Beta Test, new participant!
Before you start testing Bridgoro, please take a moment to read the [Rules for Participating in the Beta Test and Earning Rewards] (https://bitcointalk.org/index.php?topic=5555796.0) section.
Please also keep in mind that the Beta Test ends on August 31 at 23:59.

I really appreciate you guys for fixing bugs like that. Now it is fine, I mean, there is no bug occurring at my side regarding the trading page view. The trading page is working very smoothly now, and I am not facing any kind of issue while using the Trading View page. I wish you guys the best of luck and wish for the long-term success of this project. Other than this, I hope that other bugs will also be sorted out soon.  :)

This brings me to a follow-up question/request. Bear with me:
If I place a sale order on Bridgoro, I'm basically saying I want to sell for:

• Market price
• A few percent under market price
• A few percent above market price

This is different from any exchange I know! I'm used to sell for:

• Current market price
• A certain fixed price that will sell once the market reaches that point

On Bridgoro, whenever the market price changes (and that happens quite literally all the time), my sales prices changes too. But my order is waiting for a buyer, which can take a while. By the time my order triggers, I may not want to make the exchange anymore.
So I'd like the possibility to set a limit: I place a 0.01 BTC order to buy XMR, 1% above market price (about 4.22 XMR at the moment), but I want the order to produce at least 4 XMR. If it drops further, I don't want to trade anymore. Would that be possible?
But, if the market price changes in the other direction and my 0.01 BTC can be sold for 5 XMR, I want to sell even if it means selling 5% under market price if that completes my sale faster. Does this make sense?

---

---

Bug: the exchange rate is correct, but the exchange amounts at the bottom are exchanged (pun intended):
https://loyce.club/other/bridgoro5.png
I send 1 XMR, I get 417 BTC!

I understand your point, but it seems you are confusing our P2P exchange with a full-fledged centralized exchange (like Coinbase, Binance, etc.) where users can place sell orders.
The purpose of creating our P2P exchange isn't trading in the traditional sense, but providing a way to freely exchange cryptocurrencies without relying on centralized platforms.
Let's be honest, many who already use centralized exchanges may not switch to our service, simply because CEXs are often easier and faster.
But there's a downside: all CEXs require KYC/AML checks, meaning every transaction confirms ownership of the crypto you deposit.

Our P2P service offers an alternative: no KYC, no AML, no confirmation of ownership, just a simple, private way to exchange crypto.

---

We are aware of this frontend bug. Sometimes the calculation shows the wrong exchange amount. However, if you continue creating the offer, the backend services will double-check the exchange rate and display the correct amount.
This bug is already on our list and will be fixed soon.

---

Please keep sharing your ideas and suggestions, I really like the way you think!
We would be happy to implement many of them, but if we tried to add everything right now, we would risk never launching and getting stuck in endless development.

That said, your suggestions are valuable and will be added to a separate list of future improvements.

---

Glad to hear that everything is working fine with the chart.
Please feel free to report any other bugs or issues you come across. We will be happy to fix them, as that's exactly what this stage is for.

And thank you for your kind support. Such words show us that we are moving in the right direction.

an ideas and bug found

---

1. Suggestion for input address

In this transaction, I input a non-testnet Bitcoin address, and the address was successfully submitted. This should have confirmed that the wallet was incompatible with the system or was not the correct address.
Users should be required to enter the correct wallet before submitted offer. For example, validation requires a testnet address, and if it's live, it must be a native Segwit address for BTC, etc. This can help minimizes address input errors due to lack of concentration and other factors.

https://talkimg.com/images/2025/08/28/UZi753.png
full image: https://talkimg.com/images/2025/08/28/UZi753.png

---

2. Notifications error still exist

Exchange rate error notification, even i doing hard refresh this notificatin still appear,
https://talkimg.com/images/2025/08/28/UZii1N.png
full image: https://talkimg.com/images/2025/08/28/UZii1N.png

---

3. Rollback hash not found

I canceled my created offer, it show
https://talkimg.com/images/2025/08/28/UZiD8l.png
full image: https://talkimg.com/images/2025/08/28/UZiD8l.png

https://talkimg.com/images/2025/08/28/UZiWA1.png
full image: https://talkimg.com/images/2025/08/28/UZiWA1.png

Rollback Txhash:
if you check the hash, it's not found. No other options to withdraw our deposited ETH, now it stuck on buffer address. Please tell me if this should be automatic or manual by the admin? If a txhash is generated, the rollback should have been performed. Please check.

Welcome to the Beta Test, our new participant!
Thank you for testing the address validation process.
We've built a blockchain address validation system, meaning you can only enter a BTC address for BTC transactions, and the same applies to other blockchains.
This isn't a bug. During the testnet phase, we widened the eligible addresses to include testnet / stagenet / devnet, depending on the blockchain. So while the validation system works correctly, it also accepts mainnet addresses at this stage.
Status: [Not a Bug]

---

At the moment, we aren't sure how to reproduce this "Exchange Rate Error" message.

Could you please try the following steps:
1. Clear your browser cache.
2. Log out and log back in.
3. Check again for any error messages.

If the issue appears again, please report it to us. Also, if you remember the exact steps that led to this error, it would be very helpful for our investigation.
Status: [Added to backlog]

---

I see the Rollback stuck transaction.
The hash can be checked on Etherscan, but the blockchain shows the status as Pending.
We will investigate the rollback stuck transaction for this exchange offer.
Just FYI: the Rollback process works automatically. If you cancel your offer, the deposited funds will be returned to the same wallet you originally used to send them.
Status: [Added to backlog]

I want to ask  Where i can submit bug report?

An error appeared after I made a transaction with Offer ID: 513c491a-5c79-4199-bc90-f8e50c3fcdc8. There was no exchange rate error notification before that transaction.

Please submit your bug report here.

---

Could you please clear your browser cache, then try creating a new offer and check if the error message still appears?
After that, you can also cancel the offer by pressing the Abort button and verify whether the Rollback procedure completes correctly.

Ohh I thought I was the first one to report that bug about the referral link, as I did not noticed anywhere if someone else has reported it before me, maybe I have missed some posts. I am not raising any thing here just to be clear.

Ok, no problem.

*Great initiative!* The Bridgoro beta testing program seems promising. I'm excited to explore its features and contribute feedback. Looking forward to a smooth and user-friendly experience.

Best of luck to the team!

I just opened from another browser, so far didn't see any error exchange rate notifications, even i created new offer and canceled the offer. But, this Offer ID: 513c491a-5c79-4199-bc90-f8e50c3fcdc8, stuck with status Release ready. as I say, in this transaction, I intentionally entered the mainnet address. In this case, nothing has happened for more than 24 hours, because the address entered wasn't a testnet address. In an incident like this, what should we do next? There must be a solution, whether a refund or automatic cancel or re-checking the address.

https://talkimg.com/images/2025/08/29/UZD0rw.png

---

suggestion
In this text "Deposit partially confirmed on blockchain" in the transaction details, it would be better to add, "0/2 confirmations for fully confirmed" or something like that. to info user how much confirmations needed to complete. example:

https://talkimg.com/images/2025/08/29/UZOaio.png

The reason your exchange offer got stuck is because mainnet address was entered instead of a testnet address.
The system can't validate mainnet addresses during Beta.

For stuck transactions, we already have a solution called the Collector Module. You can find more details about how it works here [GitBook Docs] (https://bridgoro.gitbook.io/bridgoro-docs/system-architecture/how-do-buffer-wallets-work#collector-module-security-from-errors).

---

Please note that more confirmations are required than just two (for example, BTC requires 6 confirmations).
But I understand your point, though, and we will discuss the possibility of adding confirmation count data to make it clearer.

By the way, based on user feedback, we recently added the auto-update feature for the status on the popup screen, so now you can track the status of your exchange in real-time.

Under Tasks, the latest Test Claim is showing 0 XP even after it has been claimed.

https://www.talkimg.com/images/2025/08/29/UZlUdj.png

Thanks for wishing the Bridgoro team the best of luck.As a member of the signature campaign I'm so concerned and I also wish the team growth and success.

Is i need to prove of registration?
Like others bounty program 

This isn't a bug, we were simply testing a Claim Task with 0 XP.

---

Thank you for supporting us both in the Beta Test and in the Signature Campaign.
It really means a lot!

---

There is no need to register, just comment here that you would like to join as a Beta Tester, and then start sending us your bug reports while testing Bridgoro.

Just a reminder: the Beta Test ends tomorrow, so if you want to participate, please hurry up.
Before submitting your report, make sure to check previously reported bugs. Duplicate reports won't be counted.
More details can be found in the section: [Rules for Participating in the Beta Test and Earning Rewards] (https://bitcointalk.org/index.php?topic=5555796.0)

My pleasure @Bridgoro,I admire your attitude of gratitude and being thankful at all times and how you respond to all the comments on this discussion.

My First report.
Browser: Chrome


1. Any window like the "offer detail" and "accept offer" and "create offer" etc. opens when we click the buttons but it will be cool to have them closed when we click on the sides unlike we have to click on the close button, I know this can lead to the unnecessary errors if clicked unintentionally, but what if we just do this for the "offer details" window, this way it will be cooler to see the details quickly for the trades. Like clicking on a button, don't like the offer, just click on the sides and the window closes and then we click on another trade and the flow will be very smooth.

2. On the withdrawal page of the brgx token, the wallet address place is not so visible because the box has the same color as the background it should have the same color as other boxes have.
https://www.talkimg.com/images/2025/08/30/UnX5Dd.png

3. While updating the profile picture, I chose nothing and closed the tab and an error was shown at the bottom "Failed to upload profile photo
" but I did not upload any profile I just clicked and close the tab so I should not be seeing the error.

4. After uploading the picture, the saving button keeps loading, it did not save my profile picture.

5. I did not get any notification when I deleted my profile picture, even if the picture gets deleted quickly and I can see, but a small pop up notification if not then a notification somewhere on that window should tell me the profile picture has been deleted.

https://www.talkimg.com/images/2025/08/30/UnX9Z5.png

6. Amazingly, I could save a whole article in my bio, by the way, I copied it from a blog, well, the article must be 1000 words long, anyway a bio should have a limit for words.
https://www.talkimg.com/images/2025/08/30/UnXWVD.png

Bug3

Jumped on the Bridgoro platform to see how much has changed from all the addressed bugs and all that...Not sure if this is because beta testing is coming to an end, but all trades that I accepted were returning an error of "internal server error" upon cleaning accept offer.

https://www.talkimg.com/images/2025/08/31/UnuQQD.png

-----------------------

Bug 4
Failed to create deal: from what was reported on bug 3, I thought the error was some kind of pop-up error which would let me trade, but this too is stopping a user like me from actually testing out the exchange process.

https://www.talkimg.com/images/2025/08/31/UnuMKZ.png

-----------------------
Bug 5

Visiting tthe tasks page, wanted to see what I have and havent done but unfortunately it shows no history of what claims or tasks I have done, other than show some upcoming gig from August 31 to September the 4th.
 
https://www.talkimg.com/images/2025/08/31/UnuPI3.png

Thanks for your bug report.
In the very beginning, we had this feature, but disabled it to avoid accidental closures. Now popups can only be closed intentionally via the X button.
Status: [Not a bug]

---

Withdrawal page UI Improvement Suggestion (Noted)
It will be fixed next week.
Status: [Added to backlog]

---

Avatar Bugs (3 reports)
All 3 reports were noted, reproduced, and confirmed.
Status: [Added to backlog]

---

BIO Section
You are the first to test this section, thank you!
Without Beta Tests, many of these issues could have been missed.
Status: [Added to backlog]

---

Internal Server Error & Offer Creation Error
Couldn't reproduce yet, but we will investigate further.
Status: [Added to backlog]

---

Tasks History Data
We are aware of the incorrect history data display and will fix it later according to the queue.
Status: [Already added to backlog]

---

Dear Beta Test participants and Bitcointalk community,
We are planning to launch a second Beta Test on Reddit.
Since we don't have much experience starting or managing threads there, we would really appreciate your advice and guidance on how to do it properly.
Your support has already helped us grow here on Bitcointalk, and we would be glad if you could share tips to make our Reddit launch just as successful.

The reason for launching a second Beta Test is the number of bug reports we have received and we need more time to carefully re-check everything and ensure the exchange is fully safe for users.
As a result, the exchange release is postponed to October 2025.
Phase Two of testing will begin in September, with full details to be published once we finish distributing rewards to active testers and addressing the current backlog of bugs.

Not an error or bug: I forgot to ask, I missed something on the main page, where is that globe which was very cool though, are you planning on changing that? Place something cooler in here, such as  some graphics to show p2p exchanges.

15. I did not understand what you mean here, launching a fully functional cross-chain bridge with projects own liquidity or project's own liquidity, there is a difference. This is a minor grammatical mistake that can create confusion.

16. Another minor grammatical mistake, the right sentence should be "Built-in gamification system with XP and in-exchange currency lets you earn BRGX assets and withdraw them directly into Tether (USDT)." As on the main page instead of "lets", "let's" is written, it is also a minor grammar mistake.

This is the 4th part, not so much because most of the errors have already been found and shared here. I read the announcement about another bounty launch on Reddit, I will also participate in that, if I can.

Didn't Bridgoro say this was disabled after someone on the thread said task manager was reporting crazy resources being used by chrome ??

I might have missed that discussion, thanks for sharing this although I did not noticed the resources being used by the chrome but the point is legit, it is better to replace the graphic with something better and cooler, like I said relevant to the exchange.

I already thought it would be like this because when I first opened the website, it was the same. Maybe that's why, when I was making this report, I kept clicking on the side so that this window would close.

Alright.

I was testing everything on the profile, as they are the main things most visit and they want to modify it according to their need. Glad to found these and report here.

Thank you for your report.
This was the last one before the Beta Test ended.
All noted typos have been added to our backlog for correction.
Status: [Added to backlog]

Beta Test Phase ONE is officially completed

Dear Beta Test participants,
On behalf of my teammate and me, I want to thank all of you for testing the Bridgoro exchange and submitting bug reports. Your contributions have been invaluable and will play a big role in further development and improvement.
As we mentioned earlier, based on the bug reports received, we need some time to apply fixes before moving forward. To ensure the exchange is safe for our users, we will launch a second Beta Test phase. This time on the Reddit forum. While we are still figuring out how to best organize it there, details will be published here in this [Bounty] (https://bitcointalk.org/index.php?topic=5555796.msg65705647#msg65705647) thread and also in our [ANN] (https://bitcointalk.org/index.php?topic=5555402.0) thread.

All Bitcointalk members with Reddit accounts (or those creating one now) are welcome to join. As before, the TOP 10 most active participants will receive rewards.

Since we are only a two-person team, we have just completed a thorough double-check of Phase ONE reports. Later today, we will be ready to send out rewards to the TOP 10 participants.
To speed up the process, we kindly ask the following forum members to send us their BTC addresses as soon as possible.

▄▄▄██████▄▄▄ ▄██▀▀▀░░░░░░▀▀▀██▄ ▄██▀░░░██░░░░██░░░▀██▄ ▄█▀░░░██▄█████▄░██░░░▀█▄ ██░▄▄▀▄░██░░░▀██░▄▀▄▄░██ ██▄▄▀▀░█░██░░░▄██░█░▀▀▄▄██ ██░▄░█░█░███████░░█░█░▄░██ ██░█░█░█░██░░░▀██░█░█░█░██ ███░█░█░██░░░▄██░█░█░███ ▀█▄░█░█░▀█████▀░░█░█░▄█▀ ▀██▄░█░██░░░░██░█░▄██▀ ▀██▄▄▄░░░░░░▄▄▄██▀ ▀▀▀██████▀▀▀ (https://bridgoro.com/)

Bridgoro  ▬▬▬▬▬  P2P EXCHANGE (https://bridgoro.com/)

[

JOIN THE BETA TEST, EARN UP TO $350! (https://bitcointalk.org/index.php?topic=5555796.0) ░░░░░░░$1,300 REWARD POOL░░░░░░░

|

✔  No KYC/AML ✔  Semi-Decentralized ✔  Secure Escrow

]

⮞ ANN (https://bitcointalk.org/index.php?topic=5555402.0) ⮞ BOUNTY (https://bitcointalk.org/index.php?topic=5555796.0) ⮞ WEB (https://bridgoro.com/)

---

1st Place
username: Faisal2202
Reward: $350 in BTC

---

2nd Place
username: ContentWriter
Reward: $250 in BTC

---

3rd Place
username: LoyceV
Reward: $200 in BTC

---

4th Place
username: IIrik11
Reward: $150 in BTC

---

5th Place
username: btcnbegun
Reward: $100 in BTC

---

6th to 10th Places
username: Hamza2424
username: snowpega
username: masulum
username: Woodie
username: dkbit98
Reward: $50 in BTC each

---

P.S. For full transparency, we will publish all payout TX hashes here.

Nice one, but second phase of the Reddit campaign should be emphasized that its not for amateurs(newbies)..Reddit has so much bureaucracy such that they suspend accounts for fun, but will see how this one goes provided we stay within the rules.

Btw congratulations to all the winner's...@content writer I enjoyed your aggressive approach 👍 8)

---

@Bridgoro do the earnings from Bridgoro platform have any value or it will be burned 🔥


Btw not sure we need to post addresses here on the thread or PM, but will go first

Btc addy:  bc1qgdrs2phjfwrvmm6ur2ncqd6ku3e5sg7pvnk724

Here is the btc address: bc1qcsq6nj80tn489me0nv9qa2zf0q0zdt2dl3auf8

Wish you and the team all the bitcoins in the world!

if u need any help with the reddit bug bounty,, let me know.. as i know a thing or 2 about reddit  ;)

here's my btc address for the reward:


thx  :)

I wish I was able to complete some transaction on exchange and spend more time testing but I had some serious bugs that prevented that (registration bug and canceled offer).
If that is possible I would like to continue and finish my testing once the issue with my canceled offer is resolved.

Here is my bitcoin address for reward:

That was a nice experience working with you guys. Besides this, as far as I remember, the campaign was announced to run for a 2-week period of time. CMIIW! What are your future plans, and will the signature campaign open for more members in the future?

Here is my BTC Segwit address: bc1q4tl2ec0xrulj5r240xzzgrtktfm8xyf5k3xmdk

Kind Regards

Snowpega

Thank you, Bridgoro! 💕💕I’m truly grateful to be in first place. Wishing you the very best for your Reddit campaign and all your future endeavors. I’m really happy to be part of this project and to contribute to its success.

My BTC address for the reward:

Congratulations on completing Beta Test Phase One.


Hopefully, this beta test will help you prepare the platform for launch. even though it started with just two person, you are doing a great job. Best of luck to Bridgoro.

And Congratulations to all the testers.

This is my BTC address:

Congratulations to me and everybody for winning the prizes and the number of developers does not matter, what matters is the devotion and the team has it. Best of luck to the Bridgoro and I am with you.

BTC Wallet Address:

Thanks! Reward received (in XMR).

I'm not much into Reddit so I'll skip the second phase of the Beta test.

Rewards Sent

We have just sent rewards in BTC to almost all participants (except @ContentWriter / reason: waiting for BTC address).
Please check your BTC wallets. For transparency, we also published all TX hashes of the transactions below.

IMPORTANT NOTE!
We kindly ask all participants to return unused testnet coins to the following wallets.
Faucets often provide very limited amounts, so your help will make further testing much easier for us.

We would also like to kindly ask all participants to leave their honest feedback about the project.
It can be positive or negative: that's entirely up to you. Our goal is to remain committed to honesty and transparency.

Thank you for supporting the project!

BTC Testnet v3:

ETH Sepolia:

SOL Devnet:

TRX Shasta:

XMR Stagenet:

---

Place: 1st
Username: Faisal2202
Account LVL: Hero Member
Payout amount: $350 in BTC = 0.00315716 BTC (CMC Rate: $110,859)
BTC Wallet Address: bc1q405q7232hjq4jc8u8txx44379ejes7ckuzv8c7
TXID of the payout: 28bde464e95a841d0363d4febc56b154a4be7b838c8e2b13a59456afe8e2af35

---

Place: 2nd
Username: ContentWriter
Account LVL: Member
Payout amount: $250 in BTC = 0.00225512 BTC (CMC Rate: $110,859)
BTC Wallet Address: pending
TXID of the payout: pending

---

Place: 3rd
Username: LoyceV
Account LVL: Legendary
Payout amount: $200 in XMR= 0.76335878 XMR (CMC Rate: $262)
XMR Wallet Address: the address is hidden for privacy
TXID of the payout: the hash is hidden for privacy

---

Place: 4th
Username: IIrik11
Account LVL: Member
Payout amount: $150 in BTC = 0.00135307 BTC (CMC Rate: $110,859)
BTC Wallet Address: bc1q7yzgx752med0kxvtxtyyput2muujdr35xu9nwt
TXID of the payout: d60b579b8c222c5eb8aaf80ca8363dd7d2a6b1b536e0f73cd2c395ae23f8e015

---

Place: 5th
Username: btcnbegun
Account LVL: Newbie
Payout amount: $100 in BTC = 0.00090205 BTC (CMC Rate: $110,859)
BTC Wallet Address: bc1qcsq6nj80tn489me0nv9qa2zf0q0zdt2dl3auf8
TXID of the payout: 76bcfc972e9eb70d1145a6776ead7d41f8fecff7a249d838b76c512e29009333

---

Place: 6th
Username: Hamza2424
Account LVL: Legendary
Payout amount: $50 in BTC = 0.00045102 BTC (CMC Rate: $110,859)
BTC Wallet Address: bc1qem6cf3vgmpn7vgnv4a5tlj6z3vj963d9uccwn5
TXID of the payout: dab4632c61fbbcdb832b781d09c4ebfdc4c657a6609a250c6deb73cd518fce22

---

Place: 7th
Username: snowpega
Account LVL: Sr. Member
Payout amount: $50 in BTC = 0.00045102 BTC (CMC Rate: $110,859)
BTC Wallet Address: bc1q4tl2ec0xrulj5r240xzzgrtktfm8xyf5k3xmdk
TXID of the payout: 8b7fce1746531fa0b15d8f2b089608997847240108dc017d219e0789ebdf07e5

---

Place: 8th
Username: masulum
Account LVL: Legendary
Payout amount: $50 in BTC = 0.00045102 BTC (CMC Rate: $110,859)
BTC Wallet Address: bc1qdhyka2rej93zm7eqf8u2wk69pzntnesay6f4kz
TXID of the payout: 22e4ffdea4d9b58ca2b19fd9c5f44270ee7b9828b80887fc9b5b72f88b183dbd

---

Place: 9th
Username: Woodie
Account LVL: Hero Member
Payout amount: $50 in BTC = 0.00045102 BTC (CMC Rate: $110,859)
BTC Wallet Address: bc1qgdrs2phjfwrvmm6ur2ncqd6ku3e5sg7pvnk724
TXID of the payout: 931d0ad2af0983a269edc41f21b5365d413e550e597e238240caab77c4fc1e7a

---

Place: 10th
Username: dkbit98
Account LVL: Legendary
Payout amount: $50 in BTC = 0.00045102 BTC (CMC Rate: $110,859)
BTC Wallet Address: bc1q3vt8qs87m36qhr5mx87s0a9gvzjx9pzwz667zh
TXID of the payout: ead9bff992a9abdc89e8a37b3c7c1f72084145df88e879d0b82064ee83573c30

---

Even though Beta Test Phase ONE is over and the start date for Phase TWO is still TBA (approx. starts in mid Sep), users who would like to test Bridgoro (https://bridgoro.com/) are still welcome.
You can run your own tests at any time and submit bug reports either here in the thread or via our support account on Telegram (https://t.me/bridgoro_support).

Payment received, Thanks 💕, and I have sent the testnet tokens back. I will love to keep using Bridgoro from time to time and will report if any bug is found and will also participate in Bridgoro's second beta test.

My honest review:
The platform is very smooth and UI-friendly—the concept is very good and practical—the team is devoted and hard-working and most of all very supportive. Although there were errors and bugs but it is still in the beta phase, and they were expected. As most of them have already been reported and will be solved by launch, the project will be a 10 by 10 by then. The idea of BRGX earning was also very unique, but even if it won't be added, things might be less complicated for the developers, but you still added it for the users to get something in return, as giving something in return back to the community is an indication that the project is not here to do business but fulfill the need.

It just doesn't end here, you also removed the fee on small amounts, and that is in itself a big contribution from the Bridgoro.

confirming i have received the reward  :)

my honest review: ur site is great and even though there were minor bugs here and there but mostly they were visual bugs

the site was working as intended and when the site goes live for real,, i'll definitely use it to convert my crypto to btc or vice versa

good luck with ur reddit bug testing,, ur gonna find some hackers there too, so be careful

and thx so much for the opportunity 🙏

Confirmed.
Thank you.

Will do.
I still need to finish transaction with testnet3.
I would suggest for next round of testing in September you should switch to bitcoin testnet4.

Smart  8)