Re: [BOUNTY] Beta Test & Earn: $1,300 Reward Pool for Top Testers!
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.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
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.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.
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.