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

[SamReomo]

Merry Christmas.

Merry Christmas, congratulations on running a successful beta test and getting proper fixes with the help of the community. Although, I wasn't able to be part of that Beta testing campaign but I've been active in reading this thread time after time and hopefully once the platform gets fully active I'll surely test it.

[Bridgoro]

Hey guys, hope your Christmas holidays are going well.

We've deployed a preliminary patch that addresses the RBF transaction issue, and a full backend update with additional fixes will be released at the beginning of January.

We would really appreciate your help testing the RBF behavior on Bitcoin pairs.
If you have some free time, please try placing a few test trades involving BTC (you can choose any Exchange Offer where BTC goes first, like BTC-ETH, BTC-TRX, etc.).
We understand that the Beta phase is officially over and there are no rewards for this round but any help would be greatly appreciated.

How to Test RBF in Electrum Wallet:

1. Create a Transaction (Mempool Mode)
- Go to the Send tab
- Choose Mempool-based fee estimation
- Select the lowest possible fee (slowest confirmation)
- Send the transaction

Note: Using the lowest mempool fee is important, it gives enough time to test RBF before the transaction gets confirmed.

2. Replace the Transaction (Bump Fee)
- Open the History tab
- Right-click the unconfirmed transaction
- Select <<Increase fee>>
- Set a higher fee and confirm

Note: Electrum will broadcast a replacement transaction using the same inputs.

3. Verify RBF Behavior
- The original transaction should be marked as replaced
- A new transaction with a new TXID will appear
- Only the replacement transaction will be confirmed on-chain

Important Notes:
- RBF only works for unconfirmed transactions
- Replacement must use a higher total fee
- Static or high-fee transactions may confirm too fast and prevent RBF testing

If you don't have enough BTC testnet tokens, you can use the Flexible Exchange Offers instead (where the Fixed Offer option is set to No).
At the moment, there are plenty of available offers where you can send BTC and receive another asset in return.

Thanks in advance for your support!

[Faisal2202]

I used the RBF feature, followed the steps you mentioned, checked on the explorer as well, and the transaction was completed, only it took some time, but I just checked it is completed.

I am sending you the tx hash in pm, so you can check by yourself as well.

[LoyceV]

We've deployed a preliminary patch that addresses the RBF transaction issue, and a full backend update with additional fixes will be released at the beginning of January.

Let's test this:

1. I created Offer ID: eb1bbd43-dace-44be-8d57-22343c7f185f (BTC > XMR), and deposited 0.001 BTC.
I bumped the fee from 1 to 5 to 10 to 20 sat/vbyte, before and after I clicked "Confirm deposit". Now we wait

2. I also bought some BTC with XMR to have more test coins later

3. I also bought XMR with BTC by Accepting Offer ID: ae166f40-3f59-49f2-9ca8-88e96859c58f. I bumped the fee from 1 to 2 to 4 to 8 to 16 sat/vbyte. Now we wait

Results: For both BTC transactions, the last fee bump is the one that got confirmed.

1. This failed: "Deposit Timeout". But this was my fault, I messed up: the transaction was sent to my own address. I think it's because "Increase fee" and "Cancel (double-spend) are so close together in Electrum.

2. My BTC arrived (txid: 4cd62bf1057340eaf0c9cab75cb5dcf87ad01bd8618560124e5e088832ffdbd5). This worked. BUT: 763 sats was still sent to another address. That's less than 0.1%, but for lower amounts (say $20 in Bitcoin) this would be significant if the same amount is turned to dust.

3. My XMR arrived.

Retry the first one:

4. I created Offer ID: b4365b63-9086-4658-a694-531dc3953ea1 (BTC > XMR), and deposited 0.001 BTC.
I bumped the fee from 1 to 5 to 10 to 20 sat/vbyte, then (and only then) I clicked "Confirm deposit". After this, I bumped the fee again to 50 sat/vbyte. Now we wait

Result: The transaction paying 50 sat/vbyte got confirmed and my Offer is Active. RBF seems to work okay now.

[Bridgoro]

Guys, thank you for taking the time to test the critical RBF-related issue.
We've completed our own testing as well and are happy to confirm that the problem has been resolved.

We will continue working and will share further updates after New Year's Eve.
Wishing you all a great celebration and a happy holiday season.

P.S. We are actively reading all messages across Bitcointalk, Telegram, and AltCoinsTalks, so feel free to reach out.
We are here and ready to respond.

[Bridgoro]

The pre-release patch has been deployed

Hope you are all doing great, guys!

We've just completed the final patch that addresses the bugs identified during the OPEN BETA. If you have some free time, we'd really appreciate it if you could test Bridgoro again, with a particular focus on the following areas:
- Invite code handling
- Session expiration
- Task claiming
- Correct data rendering in email notifications
- Telegram bot unbinding
- UX responsiveness and adaptability
- And related flows

Unfortunately, this round of testing doesn't include rewards, as most of the budget was already allocated to the previous Beta tests.

At this point, if everything goes smoothly, the Bridgoro release will proceed as planned.

[CONVOAI]

The pre-release patch has been deployed

Hope you are all doing great, guys!

We've just completed the final patch that addresses the bugs identified during the OPEN BETA. If you have some free time, we'd really appreciate it if you could test Bridgoro again, with a particular focus on the following areas:
- Invite code handling
- Session expiration
- Task claiming
- Correct data rendering in email notifications
- Telegram bot unbinding
- UX responsiveness and adaptability
- And related flows

Unfortunately, this round of testing doesn't include rewards, as most of the budget was already allocated to the previous Beta tests.

At this point, if everything goes smoothly, the Bridgoro release will proceed as planned.

I can't find any option to change the password. It would be better if you add this to security.

[LoyceV]

- Invite code handling

Testing this took more time than I expected.
When I visit my referral link https://bridgoro.com/join?code=3O6SXB5 , the site brings me to https://bridgoro.com/register where the Invite Code isn't filled yet. This should be pre-filled, now I don't know whether or not it's going to register (and if I click a link, I'm not manually going to do someone a favour).

After entering my email address and the captcha, I get this:

Suggestion: "Enter your password" should be "Create your password". I only have to enter the password once, which increases the risk of typos.

I noticed Bridgoro's password requirements are restricting: I can't use a simple word phrase with 90 bit entropy.

After I enter the email confirmation code and my new password, I have to login. Wouldn't it be better to be logged in already at that point and save me the hassle of another captcha?

After registering a new account, I get a "Referral error: you cannot activate your own referral." I don't remember the exact text. I registered in a private window on Tor, but it still uses the same IP address. Given enough Tor users, chances are someone is going to use the same IP if he also uses Tor. This complicates testing
I started Tails in a VM to try again. I now registered an account using my own referral link, but don't see anything about it on my original Profile. Shouldn't I be able to see my referrals?

[Husna QA]

-snip-

I can't find any option to change the password. It would be better if you add this to security.
-snip-

I also couldn’t find any option to change the password in the security menu.




An alternative way to change the password is by using the “Forgot Password” option and resetting it through the email registered on Bridgoro.

 

[Bridgoro]

I can't find any option to change the password. It would be better if you add this to security.

Thanks for testing, mate!
Originally, we decided to allow password changes only through the Password Reset flow for security reasons.
After the release, we will run a poll and discuss with the community whether to add a direct password change option in the Security tab or keep the current approach.

Testing this took more time than I expected.
When I visit my referral link https://bridgoro.com/join?code=3O6SXB5 , the site brings me to https://bridgoro.com/register where the Invite Code isn't filled yet. This should be pre-filled, now I don't know whether or not it's going to register (and if I click a link, I'm not manually going to do someone a favour).
After entering my email address and the captcha, I get this:

Hey LoyceV, glad to see you again.
Thanks for your testing, we really appreciate it. It looks like the Invite Code bug is still present. We will investigate it and get it fixed within a day or two.

Suggestion: "Enter your password" should be "Create your password". I only have to enter the password once, which increases the risk of typos.

Noted. This will be corrected.

I noticed Bridgoro's password requirements are restricting: I can't use a simple word phrase with 90 bit entropy.

Unfortunately, that's the reality of current standards.

After I enter the email confirmation code and my new password, I have to login. Wouldn't it be better to be logged in already at that point and save me the hassle of another captcha?

This was implemented for security reasons. That said, no worries we will refine the flow and make the overall process more user-friendly soon.

After registering a new account, I get a "Referral error: you cannot activate your own referral." I don't remember the exact text. I registered in a private window on Tor, but it still uses the same IP address. Given enough Tor users, chances are someone is going to use the same IP if he also uses Tor. This complicates testing
I started Tails in a VM to try again. I now registered an account using my own referral link, but don't see anything about it on my original Profile. Shouldn't I be able to see my referrals?

You can find your referral count on the Profile page under the Account Statistics tab.


Guys, we've also created several Claim tasks. If you have a few minutes to test them, that would be great as well.

Thank you all for being such a great community and for helping us shape Bridgoro.

[LoyceV]

It looks like the Invite Code bug is still present. We will investigate it and get it fixed within a day or two.

If you post here when it's fixed, I'll test it again.

You can find your referral count on the Profile page under the Account Statistics tab.

It's 0. The weird part is: I got a warning after I tried to refer myself (that was on a throw away account), but it didn't work when I completed the registration. In both cases I used the ref URL without manually entering the ref code.

Guys, we've also created several Claim tasks. If you have a few minutes to test them, that would be great as well.

I claimed 2 tasks, but I must say I'm not interested in earning "BRGX". I received this email:

Dear User,

You have successfully claimed the task "Claim Task (Test Task 1)". This task is now assigned to you.

Task Details:

-   Reward: 15 XP
-   Description:

Complete the task to earn your XP reward and improve your user level.

Best regards, Bridgoro team

It feels like I'm jumping through hoops of a customer loyalty program, aiming to get me hooked. I tend to ignore those on all websites.

[LastKiss]

The pre-release patch has been deployed
~snip~
- Invite code handling

I have the same problem as LoyceV. When I visit my referral link, I have to visit the same link twice for the invite code to appear.

- Session expiration

This works perfectly

- Task claiming

Task claiming works perfectly too, I have no problem with that

- Correct data rendering in email notifications

This is what I received in the email notification, I will try other things later 

Dear User,

You have successfully claimed the task "Claim Task (Test Task 1)". This task is now assigned to you.

Task Details:

Reward: 15 XP
Description:
Complete the task to earn your XP reward and improve your user level.

Best regards, Bridgoro team

[Bridgoro]

I have the same problem as LoyceV. When I visit my referral link, I have to visit the same link twice for the invite code to appear.

We acknowledge that the Invite Code bug still exists. We are actively working on it, and it will be fixed in the final release patch.

Task claiming works perfectly too, I have no problem with that

We've identified an issue with Claim tasks when the same task is claimed on the second day.
This will be fixed as well. It looks like we missed addressing it earlier, even though it was previously reported.


Thanks, bud, for taking part in testing, we really appreciate your help.