Please let us know once you have time to accept our offers and complete the transactions.
Your feedback on BTC/XMR is especially valuable, as these are the two main assets of our project.

---

Sure, we will do our best.
Bitcointalk can be time-consuming, but it's part of our job right now since this is our project and we are the ones who started the thread.
Thanks a lot for your support, it really motivates us.

---

Thanks for helping us answer users’ questions.
You are absolutely right, new coins will only be added after the final release.

We are also planning to launch let's say, a Coin List Vote, so the community can decide which assets should be added next.

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]

We accepted two available offers (not created by us) with the following pairs: XMR -> BTC and BTC -> XMR — hopefully those were yours.

In addition, we've also created two new Exchange Offers with the same pairs (XMR → BTC / BTC → XMR) as per your request.
One offer is already active, and the second one is partially confirmed and will be available soon.

Why read the manual now, when you can just read it later… once something goes wrong? 

---

As we posted earlier, there will be no Service Fee for the first 6 months, so this issue is temporarily resolved.

We will continue our deep research on Dust Transactions.
Thanks to your idea, we will also consider introducing fee-free exchanges for small amounts.

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

That's why we say that Bridgoro is semi-decentralized.
We don't want to confuse our users by claiming to be "fully decentralized".
This was an intentional choice, as semi-decentralization allows us to balance security with better UX and user comfort.

---

We will publish a detailed report after the Beta Test explaining why the Minimum Exchange Value was increased and how we avoided transaction stuck issues.

Please note: transaction fees differ between testnet and mainnet.

• On testnet we could keep the minimum at around $12.
• On mainnet, such a low value isn't possible due to real blockchain fee limitations.

---

More native coins will be added once the exchange is officially released.

---

Sometimes we see users asking questions already clearly answered in the ANN or GitBook.
We kindly ask everyone to spend a few minutes reading the provided materials before posting questions, as it helps reduce confusion and repetitive answers.

---

Example of a Dust Transaction.
Here's a real case we faced:
A user sent $10 in BTC, which was about 0.00008955 BTC.
A 0.3% Service Fee was applied, equal to 0.00000026 BTC.
Since it's impossible to send 26 satoshis (the transaction wouldn't even be processed), the transaction got stuck.
This is exactly why dust transactions are an issue and why careful value tuning is necessary.

---

Rewards will be distributed within 2 days after the Beta Test ends (August 31, 2025).
So approximately, users can expect their rewards around September 2, 2025.
These 2 days are necessary to:

• Review participants' activity.
• Count and verify bug reports.

Since we are only two developers, we need this time to ensure rewards are distributed fairly and accurately

---

Guys, hope you are all doing well!

As we move into the next week of the campaign, I'd like to kindly ask all participants to update your Signatures accordingly.

Thanks for your continued support!

P.S. As mentioned above, the payouts for your campaign participation will be made tomorrow.

You did an amazing job, we honestly didn't expect such a warm welcome on the forum, especially with gifts like the custom signatures you created.
We've reviewed the signatures, and we are really happy with them. We will definitely ask our campaign participants to update their signatures to use yours.
As a small token of gratitude, we'd like to thank you personally and send you $40 in BTC tomorrow, along with the participant payouts.
I know it's not a huge amount since our funds are limited at this stage, but it's important for us to show appreciation for the support we receive.

Please reply with your BTC address, and I will add you to the payout list.

Dear Signature Campaign Participants,

Today marks the end of the first week of our campaign.
Starting tomorrow, I will begin sending payouts in BTC, and for full transparency, all transaction hashes will be published here.

On behalf of myself and my teammate, I want to sincerely thank all of you for helping promote our project.
We've also noticed that many Signature Campaign participants have joined us in the Beta Test, which is truly amazing and shows real community support.

And here is the craziest part: one of our fellow Bitcointalk members even created custom signatures for us, and they look fantastic.
I will dedicate a separate post to properly thank this contributor.

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

Thank you for your interest in our project!
I understand your frustration about the absence of USDT on the platform.
However, we've clearly stated the currently supported assets on the homepage (BTC, ETH, SOL, TRX and XMR).
For a better understanding of the project, especially its key features, I recommend checking out our GitBook page.
FYI: Integration of stablecoin assets is planned for Q3 of this year.

We'd also like to invite you to join as a Beta Tester.
The Top 10 most active testers will share a $1.3k reward pool.
More details about Beta Test participation can be found in our [BOUNTY] thread.

The recent BTC -> XMR Dust Transaction occurred because we were testing a 0.3% Service Fee on each transaction. In this particular case, the exchanged amount was very small, and after the smart contract deducted the Service Fee (just a few satoshis), the transaction became stuck.

Temporary solution: For the first 6 months, there will be no Service Fee, which eliminates the risk of Dust Transactions for now.
Permanent solution: We will conduct in-depth research and calculations to ensure that such situations are avoided once fees are re-enabled after the initial 6 months.

And we would like to note that we don't use any third-party apps or solutions for blockchain adapters, escrow service, or the collector module, all of these are fully developed in-house.

---

It would be better to publish such requests on the [BOUNTY] page, since all Beta Testers are gathered there. That way, everyone involved will see the update in one place.
But we have created BTC -> XMR and XMR -> BTC offers for you.
Please note that the amounts aren't large, as we also need testnet tokens for our internal testing.

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 from the stuck exchange. We will update you next week with the results.

You are welcome!
We will also add this information to the GitBook page a bit later for easier reference.

---

Please also keep in mind that we don't rely on any third-party tools.
The entire backend has been fully developed in-house by us.

---

That's the reason we chose to build the system as semi-decentralized instead of fully decentralized.

---

Yes, there is a minimum exchange value, which unfortunately will need to be raised on mainnet. That said, we will do our best to keep it as low as possible.

You can check our GitBook page for instructions on how to test all available networks on the exchange, and we've also provided faucet links there to make testing easier.

Dead Wallet and Dust Transactions are not actual problems.
We are simply researching and fine-tuning the values to prevent them in all future transactions. The Beta phase showed us that these areas need a double-check, but once adjusted, they won't be an issue at all.

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

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

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

---

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]

---

Your request will be discussed with my teammate, and we will get back to you once we've reviewed it.
Status: [Added to backlog]

---

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.

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

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

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

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.

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)

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?

I understand why Bitcointalk members are often suspicious of newcomers.
Before asking further questions, please take a moment to read our [ANN] and [BOUNTY] posts: all the key information is clearly written there.

To clarify once again:
We don't ask anything from forum members.
As a new project, we've launched the Beta Test phase, where we invite interested users to participate by testing the platform and reporting bugs.
As a token of our gratitude, the TOP 10 most active testers will receive financial rewards.

The Beta phase runs until August 31, 2025, and rewards will be distributed within 1-2 days after we finish counting and reviewing all bug reports from each user.