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

[Hamza2424]

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:

bc1qem6cf3vgmpn7vgnv4a5tlj6z3vj963d9uccwn5

[LoyceV]

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

Thanks! Reward received (in XMR).

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

[Bridgoro]

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:

Code:

tb1qvxc675crylmr7s5q9dq2gfyqw9evzta0he64mm

ETH Sepolia:

Code:

0xd1DB4fC4925C708FA5F1E49C49e4067ff2e282e6

SOL Devnet:

Code:

HFvrUjQa6RroqMLVo6i7DyF4S3QBYnLh9VjARdU7AQkm

TRX Shasta:

Code:

TWXTapLdxjfTrgj4zRpYGTeP6K5PcGNjwQ

XMR Stagenet:

Code:

75saVbZzQ7nHAwZcX4ZfnPTqrgdjfLiTfBwsAEt4WB2BCxZA2y1qPcST2EW6mYJVUseYoSb3Hg1JDCUV7jyw3ZXoPLEUhg1

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

[Faisal2202]

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

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

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.

[IIrik11]

We have just sent rewards in BTC to almost all participants

We would also like to kindly ask all participants to leave their honest feedback about the project.

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 🙏

[dkbit98]

Rewards Sent

Confirmed.
Thank you.

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

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.

Thanks! Reward received (in XMR).

Smart  

[Bridgoro]

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

@ContentWriter - we are still waiting for your BTC address so we can send you your reward.
Please provide it at your earliest convenience so we can complete the payout.

[ContentWriter]

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

@ContentWriter - we are still waiting for your BTC address so we can send you your reward.
Please provide it at your earliest convenience so we can complete the payout.

Hi Bridgoro. Thank you so much for this reward. Sorry I've been kept off forum due to unavoidable circumstances.

My address: bc1qw5jnk6ncv4k0625fu7xy4lq73cf09kfmwmyjcv

Hoping to join your bounty on Reddit if they'd permit me. Reddit seems to have expertise in shadow bans.

[Bridgoro]

Hi Bridgoro. Thank you so much for this reward. Sorry I've been kept off forum due to unavoidable circumstances.
My address: bc1qw5jnk6ncv4k0625fu7xy4lq73cf09kfmwmyjcv
Hoping to join your bounty on Reddit if they'd permit me. Reddit seems to have expertise in shadow bans.

Thank you, ContentWriter!
Your reward payout will be sent tomorrow, and we will also publish the transaction hash here for transparency.
We truly appreciate your participation and the valuable bug reports you've provided.

[Bridgoro]

Hi Bridgoro. Thank you so much for this reward. Sorry I've been kept off forum due to unavoidable circumstances.
My address: bc1qw5jnk6ncv4k0625fu7xy4lq73cf09kfmwmyjcv
Hoping to join your bounty on Reddit if they'd permit me. Reddit seems to have expertise in shadow bans.

Your reward payout has been sent.
Thank you for your participation in the Beta Test and for supporting the project.

Place: 2nd
Username: ContentWriter
Account LVL: Member
Payout amount: $250 in BTC = 0.00213981 BTC (CMC Rate: $116,833)
BTC Wallet Address: bc1qw5jnk6ncv4k0625fu7xy4lq73cf09kfmwmyjcv
TXID of the payout: fb3b67adcace908d6d3d4f20ba1f1089ca7919dd626027a86e2844ee52f5752f

[ContentWriter]

Hi Bridgoro. Thank you so much for this reward. Sorry I've been kept off forum due to unavoidable circumstances.
My address: bc1qw5jnk6ncv4k0625fu7xy4lq73cf09kfmwmyjcv
Hoping to join your bounty on Reddit if they'd permit me. Reddit seems to have expertise in shadow bans.

Your reward payout has been sent.
Thank you for your participation in the Beta Test and for supporting the project.

Place: 2nd
Username: ContentWriter
Account LVL: Member
Payout amount: $250 in BTC = 0.00213981 BTC (CMC Rate: $116,833)
BTC Wallet Address: bc1qw5jnk6ncv4k0625fu7xy4lq73cf09kfmwmyjcv
TXID of the payout: fb3b67adcace908d6d3d4f20ba1f1089ca7919dd626027a86e2844ee52f5752f

Thank you, Bridgoro.

Gaining trust in an ecosystem designed to function without it may seem like an uphill task, but history has shown that centralized platforms can, over time, earn the confidence of their users.

I have no doubt that Bridgoro will become one of the most reliable of such exchanges, because the team's sincerity and dedication are unquestionably evident. At BitcoinTalk, we are largely skeptical of similar claims, but I can confidently say that this is one project that will prove to be dependable.

[Bridgoro]

Bridgoro Project Update

Hey everyone,

We've just published important updates on the main [ANN] thread regarding the next development steps and Beta Test phase.

• Backend & Frontend patches: deployment planned for this week
• Beta Test Phase 2: scheduled to launch next week
• Reward Pool: $1,500 in BTC for the TOP 10 active participants

Full details are available on our main announcement thread: [ANN Thread Link]

Your feedback and support are invaluable.
Thank you for being part of our journey!

[Bridgoro]

#PROOF OF REGISTRATION
Forum Username: ESE~
Forum Profile Link: https://bitcointalk.org/index.php?action=profile;u=3734381
Telegram Username:
Participated Campaigns: Twitter, telegram, tik tok
BSC Wallet Address: 0x1E4a9dE6fCbCFaCDd045a6ba0597209302192506

Hi buddy,
The first closed Beta for Bitcointalk participants ended back in August but you still have a great chance to try yourself in the OPEN BETA, which starts tomorrow in our Telegram channel.
Feel free to join in!

P.S. I was just about to post an announcement about the OPEN BETA in this thread when I saw your message.
Please check my next post for all the details.



ONE DAY BEFORE OPEN BETA

Hi dear Bitcointalkers,
Tomorrow marks the start of our OPEN BETA, and we sincerely hope to see you among the participants. You were the very first community to support us, so we would be glad to welcome you once again as our guests in testing.
We believe there's no need to repost all the Beta participation rules here, as most of you are already familiar with them. However, if you would like to refresh your memory, feel free to join our Telegram channel, the latest post contains the full list of rules and details.

Oh, one more thing...
...rewards will also apply to this Beta.
The total reward pool is $1,500 distributed in BTC or XMR (as usual).
Since we don’t expect a large number of participants, the chances of earning a reward are quite high.

Later today, we will publish the link to the dedicated bug-report chat, where all participants will be able to submit their findings.
We will also duplicate the link here on Bitcointalk for your convenience.

Thank you for staying with us, and see you in the Beta!

Telegram channel: https://t.me/bridgoro_exchange
Telegram Support: https://t.me/Bridgoro_helpdesk

[redfin31]

#PROOF OF REGISTRATION
Forum Username: ESE~
Forum Profile Link: https://bitcointalk.org/index.php?action=profile;u=3734381
Telegram Username:
Participated Campaigns: Twitter, telegram, tik tok
BSC Wallet Address: 0x1E4a9dE6fCbCFaCDd045a6ba0597209302192506

Hi buddy,
The first closed Beta for Bitcointalk participants ended back in August but you still have a great chance to try yourself in the OPEN BETA, which starts tomorrow in our Telegram channel.
Feel free to join in!

P.S. I was just about to post an announcement about the OPEN BETA in this thread when I saw your message.
Please check my next post for all the details.

Thanks for sharing, hope I still get a chance to participate.

[Bridgoro]

Thanks for sharing, hope I still get a chance to participate.

The OPEN BETA will run until November 30, so you'll have plenty of time to test Bridgoro and submit your reports in the dedicated Telegram chat.

You can find all additional details on our main Telegram channel.

[Bridgoro]

Hi Bitcointalkers,

If our project seems promising to you or at least interesting, we would like to ask one more small favor:

Please consider participating in our 2nd phase of the Beta, or at least join the OPEN BETA chat to show others that the testing is worth joining.
Your presence alone already helps a lot.

Telegram channel: https://t.me/bridgoro_exchange
OPEN BETA Chat: https://t.me/bridgoro_beta

[icopress]

Hello everyone. For those who missed the opportunity to join, hurry up (read the full announcement by clicking the quote).

Bridgoro also announced that a new patch will be released in the next few days that will fix all previously identified bugs. This will eliminate the need to review/refer to previous reports.

The OPEN BETA end date will be extended approximately until December 5-7 due to the preparation of new backend and frontend patches that include fixes for all bug reports submitted since Day 1. [...]

[Bridgoro]

The latest information has just been published.  

OPEN BETA / Brief Status Update [Day 14]

We can finally share the exact details for the further stage of the OPEN BETA.

The new patch which includes fixes for all previously reported bugs will be deployed tomorrow during the day. We will notify everyone once Bridgoro (https://bridgoro.com/) is available for testing again.

What's new?
- The new patch will fix all bugs found earlier (at least we hope so).
- The database will be wiped, so all participants will need to register again. This reset is necessary to avoid conflicts with the new patch.
- New exchange offers will be created by us across most trading pairs (your own offers will also be helpful).
- Due to the low number of participants, we are adding Bitcointalk as a second platform for submitting bug reports.
- The new OPEN BETA end date is December 7.
- After testing ends, we will need some time to fix any newly discovered bugs, and then we will move forward with the official release of Bridgoro.

OPEN BETA / Updated Details
1/ Participants can submit bug reports either in the dedicated Telegram chat or in the Bitcointalk thread.
2/ OPEN BETA end date: December 7.
3/ Rewards for the TOP 10 most active testers will be distributed no later than December 10.
3/ All previously reported bugs can be tested again after the patch.
4/ The first submitted bug report will be counted based on its timestamp to avoid duplicates across both platforms (Telegram / Bitcointalk).
5/ As usual, participants may submit suggestions to improve the project. If the suggestions are valuable, they will also be counted.
6/ Bug reports must be clear, reproducible, and include screenshots when possible.
7/ Rewards distribution remains the same:

Code:

Rank             Reward
1st Place        $400
2nd Place        $300
3rd Place        $250
4th Place        $200
5th Place        $100
6th–10th Places  $50 each

Total Pool       $1,500

Join OPEN BETA in Telegram or Bitcointalk

[mocacinno]

I was made aware of this beta test today, and since it looks like you've extended the test period, i looked at your site aswell.
Instead of looking at the user interface, i decided to look "under the hood"  

First things i noticed while running testssl.sh:
I couldn't help but notice "Server banner cloudflare". It looks like you use your own certificate, but you use cloudflare's proxy/CDN? Is this a correct assumption? I did a whole writeup on cloudflare a long time ago, but it's still valid: https://bitcointalk.org/index.php?topic=5247838.0 (sorry, the images are waaaaay gone, my dedicated box became to expensive, so i'm no longer running a lamp stack). Cloudflare has it's pro's and con's. On one side: it acts as a MITM, so your users never have absolute anonimity. On the other side it usually does a great job hiding your real setup, protecting you from DDOS attacks and mitigating vulnerability's that you have in your real setup. Even bitcointalk uses cloudflare since many years... Not a fan, but i get why people use it.

• This (cloudflare useage) would also explain why TLS 1.0 and 1.1 are still exposed (this is their default setting)... I would strongly discourage anybody using cloudflare if they want absolute anonimity. It might be fine for your service tough, but you should disable TLS 1.0 and 1.1
• A second thing i noticed is that HSTS is off. Might be a good idear to turn it on...
• BEAST & LUCKY13 will no longer be flagged in testssl.sh once you turn TLS 1.0 and 1.1 off.

The rest looked ok, when it comes to SSL/TLS settings

Things i noticed while checking headers using curl

Code:

curl -v https://bridgoro.com

• HSTS is off (already mentioned above)
• Content-Security-Policy header missing
• X-Frame-Options missing
• X-Content-Type-Options missing
• Referrer-Policy missing
• Permissions-Policy missing
• Cross-Origin-Opener-Policy missing

If you're using cloudflare (and i assume you do), you should be able to enable those...

Things i learned whilst running nmap
Cloudflare does it's job ... Most of my probes were terminated or returned 4xx status codes... You're not leaking your real ip, i couldn't find it anywhere.
This being said, cloudflare is just a proxy... Since i couldn't find your real ip, there's no way of knowing if your actual setup has any vulnerability's...

That's basically the "conclusing" of this whole check: i'd recommend not using cloudflare, but in your case (not requiring absolute anonimity) it might be fine... The pro's do outweigh the con's very often. Even then: disable TLS1.0 and 1.1 and enable the necessary security headers. For the rest: cloudflare does it's job, it hides your real ip and basically blocks any attempt at finding vulnerability's. This being said: this security is NOT absolute! If somebody just scans your real ip range, finds your server and scans your actual setup, i have no idear what they'll find. Since cloudflare did it's job and hid your actual ip, i have no way of giving a report on your server.

IF (and only if) you want me to scan your actual setup instead of looking at the proxy, send me a PM and we'll find a way for you to send me your actual server's ip...  This is just an offer tough, it's up to you wether you want to do this or not.

Second part: the actual review of your site

• sign up works fine, code works fine.. But at first sight i don't see any 2FA options? Nobody likes 2FA, but from a security stance it's something that's required
• i tried creating an offer, but i was unable to modify the minimum buyer level... The "create offer" button was still clickable, but i got an "user level not found" error. I could not reproduce the error, the second time it worked just fine... Maybe you can find something in your logs, it was around 9:08 CET

One more bug, tried searching the thread and couldn't find it right away, hopefully it hasn't been reported before:

I tried creating an offer, had to pay 0,55 testnet SOL, and i wondered what would happen if i underfunded the deposit address... Left the screen open, and suddenly i got cloudflare output... Mind you: this has nothing to do with my previous tests, those were run from my linux VSP, and this test was run on my desktop machine (a completely different machine, from a completely different ip)



Each time there was a spinner next to the text "deposit confirmed, pending blockchain" the text on the right started scrolling... I guess your code wants to find out if i already deposited, but cloudflare stops the request...

Tried refreshing the page, now i get this one each time you're trying to see if i already deposited:


It's a request to this uri: https://bridgoro.com/api/xmrbridge_core/p2p/seller/offer/f86af5ff-1dc4-456e-b7a1-6e781b46ece5 that gets a 401

By the way: my initial test was "what happens if i do not deposit enough testnet sol", and the answer is unclear: i outran the clock, the time left to deposit disappeared, i get a message the deposit is confirmed, pending blockchain. But, in transactions i don't see a transaction...

[Bridgoro]

Hi [mocacinno],
Thanks for joining the Beta, but you started a bit early.
In our announcement, we mentioned that the new patch would be deployed today during the day, and it's still in progress.
The database was also wiped.
We will notify everyone here later today once Bridgoro is ready for testing again.