Will be trying this..
Welcome to the Beta Test, and we are glad to have you on board!
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

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.
Quoting my posts from the other topic here as I was requested to post here to participate in the Beta Test Reward Program:
Welcome to the Beta Test! Your feedback will shape the future of our platform!
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.
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.
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.
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]
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.
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
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.
Welcome to the Beta Test and thank you for joining us on this journey!
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
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]
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.
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:
We fully understand your concern. Many people will initially think that any new crypto platform might be a scam.
That's a normal reaction.
To address this directly, at the start, our exchange will have maximum amount restrictions.
This is both for user protection and to limit unnecessary risks on our side. Initially, the maximum one-time exchange amount will be $5k in USD equivalent (for high-level accounts).
In the unlikely event of an issue, we, as guarantors, will restore the lost funds to one or both parties. While the chances are extremely small, we've prepared a plan to cover this scenario.
Keep in mind that development has already cost us over 7 months of R&D.
The value of that effort is far greater than any possible short-term scam (10x more than the maximum one-time transaction limit).
It simply wouldn't make sense to spend so much time and resources to risk everything for $5k.
Finally, once the bugs are fixed and we reach the final launch stage, we will conduct a full audit of the code and system.
This won't only increase trust but also serve as strong proof of reliability and great publicity for the platform.
Bug 10
I sent TRX but didn't get SOL. Here is my txid: 17f0d22fdfbaffb27de80eed2f8b5ae78c3de69e206caaacaf4fac7f5de84591
You can see it's been over one hour.
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]