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

[LoyceV]

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.

Can OP (or anyone else) create some small BTC <> XMR offers? I'm low on test coins for both, but $15 or so should still work.
So far, I haven't been able to complete a single trade, and that's kinda disappointing.

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

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.

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.

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

Our platform uses CoinMarketCap rates directly, without adding any extra percentage on top, ensuring users always trade at fair market prices.

What if CMC fucks up big time, and displays the wrong price? This has happened before, and if you don't detect this, some seller is going to be very disappointed while your buyer hits the jackpot!

[ContentWriter]

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.



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.

~snip~

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

~snip~

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

[Bridgoro]

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.

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]

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.

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]

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

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

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.

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.

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

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.

What if CMC fucks up big time, and displays the wrong price? This has happened before, and if you don't detect this, some seller is going to be very disappointed while your buyer hits the jackpot!

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.

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

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

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.

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.

[Faisal2202]

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

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.

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]

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?

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

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.

[LoyceV]

What if CMC fucks up big time, and displays the wrong price? This has happened before, and if you don't detect this, some seller is going to be very disappointed while your buyer hits the jackpot!

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.

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?

[btcnbegun]

8.

Range bug:





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:

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.



Bug 10

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

You can see it's been over one hour.

[ZAINmalik75]

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

[Bridgoro]

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.

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.

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?

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 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?

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.

8. Range bug:
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:

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]

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

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] section.
Please also keep in mind that the Beta Test ends on August 31 at 23:59.

[snowpega]

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.

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]

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. 

[LoyceV]

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.

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

I send 1 XMR, I get 417 BTC!

[Bridgoro]

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?

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.

Bug: the exchange rate is correct, but the exchange amounts at the bottom are exchanged (pun intended):
I send 1 XMR, I get 417 BTC!

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.

This brings me to a follow-up question/request. Bear with me:

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.

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.  

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.

[masulum]

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.


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,

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

3. Rollback hash not found

I canceled my created offer, it show

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


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

Rollback Txhash:

Code:

0xaa45c9999636bb0d3ab6a375ebe398b8489dafb2f1a966a00ae22c8ef7d8fba4
https://sepolia.etherscan.io/tx/0xaa45c9999636bb0d3ab6a375ebe398b8489dafb2f1a966a00ae22c8ef7d8fba4

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.

[Bridgoro]

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.

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]

2. Notifications error still exist
Exchange rate error notification, even i doing hard refresh this notificatin still appear,

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]

3. Rollback hash not found
I canceled my created offer, it show
Rollback Txhash:

Code:

0xaa45c9999636bb0d3ab6a375ebe398b8489dafb2f1a966a00ae22c8ef7d8fba4
https://sepolia.etherscan.io/tx/0xaa45c9999636bb0d3ab6a375ebe398b8489dafb2f1a966a00ae22c8ef7d8fba4

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.

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]

[Afs25]

I want to ask  Where i can submit bug report?

[masulum]

if you remember the exact steps that led to this error, it would be very helpful for our investigation.

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.

[Bridgoro]

I want to ask  Where i can submit bug report?

Please submit your bug report here.

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.

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.

[Faisal2202]

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.

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.

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

Ok, no problem.

[Afs25]

*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!

[masulum]

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.

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.




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:

[Bridgoro]

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.

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

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:

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.