Next scheduled rescrape ... in 3 days
Version 1
Last scraped
Scraped on 23/08/2025, 11:20:01 UTC
Bug Report
Microsoft browser Edge reports unknown error before and after logging in.
"User is not assigned" and "Unknown error": both are already in our backlog.Microsoft browser Edge reports unknown error before and after logging in.
The root cause seems to be a frontend conflict. We are investigating and expect to deliver a fix next week, followed by a detailed report.
Status: [Already added to backlog]
The browser also flags Bridgoro as not secure. With potentially a browser market war brewing with Google, you my have to sort this out.
If you see the "Not Secure Connection" flag, it usually means the site is being accessed via HTTP instead of HTTPS. Please use HTTPS as our SSL certificate is active.Third-party requests we use:
google.com -> CAPTCHA
gstatic.com -> Google Fonts
unpkg.com -> Cloudflare CDN
For security reasons, Cloudflare (unpkg) can’t be removed at this stage.
In the future, we may replace Google Fonts and possibly build our own CAPTCHA system to get rid of these two requests.
Status: [Not a bug]
I can understand the frontend can will imporved on the way, and you know what, perfect UI is usually invisible haha, I mean nothing can be perfect, every single platform can have UI or other problems, the main important thing should be the backend if it is working smoothly no one talks or find such UI errors, I am finding because it is the job here haha.
The Beta Test is essential for polishing all parts, especially the frontend. Massive testing has already uncovered several bugs in the backend as well. We won't move to release until the backend is fully stable. If any issue happens with a transaction during mainnet, we will restore funds from our own side, but we want to eliminate backend risks before going live.Thank you, I will love to say someone here on the forum about my contributions. That's the part I love most.
Who doesn't love 
This is great, thanks for the approval.
Thanks for your idea, which helps us improve the project.I am already proud to say I am helping in a project, I have wrote many reviews before but review and bug post are quite different.
Wish you best of luck.
Thanks a lot. Doing our best.Wish you best of luck.
The 0.3% Service Fee isn't enough to explain why 11.xx USD became less than 10 USD (which is the limit for this test).
When accepting a Deal, remember that the Buyer covers not only their own Network Fee but also the Seller's Network Fee (Compensation Fee).Status: [Not a bug]
Yesterday (8/22/2025, 7:15:07 PM), I tried again: deposit 85132ca6fbd1f6b2392a5622b50fd23f7df78232c6d909997cde8464ffc8378c to accept Offer ID: a44e20c6-15ad-4b00-8f2e-019080abc3e9:
0.00061747 BTC > 0.2694231 XMR
It gives the same result: RELEASE READY, and nothing happens despite being more than $60. So I don't think the "dust limit" causes this.
I only now noticed XMR should be on Stagenet, not Testnet (which is what I used). Could that be the cause of not sending my transaction?
I know about a stuck transaction, as this is our Exchange Offer from one of the test accounts.0.00061747 BTC > 0.2694231 XMR
It gives the same result: RELEASE READY, and nothing happens despite being more than $60. So I don't think the "dust limit" causes this.
I only now noticed XMR should be on Stagenet, not Testnet (which is what I used). Could that be the cause of not sending my transaction?
This isn't related to Dust Transactions. We are still investigating, as it may be linked to testnet XMR being sent instead of stagenet XMR. Backend bugs are critical for us, so this needs deep analysis.
Please expect a detailed report next week.
Status: [Under investigation]
One of your faucet-links on gitbook points to a Testnet faucet, not Stagenet.
Thanks for pointing it out.I mistakenly added a testnet faucet link instead of a stagenet faucet link earlier (just CypherFaucet provides both faucets: for testnet and stagenet).
The link is correct now.
Status: [Fixed]
With 4 confirmations, my Bitcoin deposit status was still "Partially confirmed". It would be nice to show how many confirmations are needed (and 4+ is excessive for Bitcoin). I didn't see exactly how many deposits it takes.
For BTC, 6 confirmations are currently required.Next week, we will experiment with reducing the number of confirmations across all blockchains to find a balance between speed and security.
Important note for our Beta Test community:
We will pause bug reviews and development work until Monday.
After weeks of intense work, my teammate and I need a short rest to "clear the cache in our heads."
But please keep sending us your reports if you find any issues.
Rest assured, every single report will be reviewed carefully.
Original archived Re: [BOUNTY] Beta Test & Earn: $1,300 Reward Pool for Top Testers!
Scraped on 23/08/2025, 11:15:32 UTC
Bug Report
Microsoft browser Edge reports unknown error before and after logging in.
"User is not assigned" and "Unknown error": both are already in our backlog.Microsoft browser Edge reports unknown error before and after logging in.
The root cause seems to be a frontend conflict. We are investigating and expect to deliver a fix next week, followed by a detailed report.
Status: [Already added to backlog]
The browser also flags Bridgoro as not secure. With potentially a browser market war brewing with Google, you my have to sort this out.
If you see the "Not Secure Connection" flag, it usually means the site is being accessed via HTTP instead of HTTPS. Please use HTTPS as our SSL certificate is active.Third-party requests we use:
google.com -> CAPTCHA
gstatic.com -> Google Fonts
unpkg.com -> Cloudflare CDN
For security reasons, Cloudflare (unpkg) can’t be removed at this stage.
In the future, we may replace Google Fonts and possibly build our own CAPTCHA system to get rid of these two requests.
Status: [Not a bug]
I can understand the frontend can will imporved on the way, and you know what, perfect UI is usually invisible haha, I mean nothing can be perfect, every single platform can have UI or other problems, the main important thing should be the backend if it is working smoothly no one talks or find such UI errors, I am finding because it is the job here haha.
The Beta Test is essential for polishing all parts, especially the frontend. Massive testing has already uncovered several bugs in the backend as well. We won't move to release until the backend is fully stable. If any issue happens with a transaction during mainnet, we will restore funds from our own side, but we want to eliminate backend risks before going live.Thank you, I will love to say someone here on the forum about my contributions. That's the part I love most.
Who doesn't love This is great, thanks for the approval.
Thanks for your idea, which helps us improve the project.I am already proud to say I am helping in a project, I have wrote many reviews before but review and bug post are quite different.
Wish you best of luck.
Thanks a lot. Doing our best.Wish you best of luck.
The 0.3% Service Fee isn't enough to explain why 11.xx USD became less than 10 USD (which is the limit for this test).
When accepting a Deal, remember that the Buyer covers not only their own Network Fee but also the Seller's Network Fee (Compensation Fee).Status: [Not a bug]
Yesterday (8/22/2025, 7:15:07 PM), I tried again: deposit 85132ca6fbd1f6b2392a5622b50fd23f7df78232c6d909997cde8464ffc8378c to accept Offer ID: a44e20c6-15ad-4b00-8f2e-019080abc3e9:
0.00061747 BTC > 0.2694231 XMR
It gives the same result: RELEASE READY, and nothing happens despite being more than $60. So I don't think the "dust limit" causes this.
I only now noticed XMR should be on Stagenet, not Testnet (which is what I used). Could that be the cause of not sending my transaction?
I know about a stuck transaction, as this is our Exchange Offer from one of the test accounts.0.00061747 BTC > 0.2694231 XMR
It gives the same result: RELEASE READY, and nothing happens despite being more than $60. So I don't think the "dust limit" causes this.
I only now noticed XMR should be on Stagenet, not Testnet (which is what I used). Could that be the cause of not sending my transaction?
This isn't related to Dust Transactions. We are still investigating, as it may be linked to testnet XMR being sent instead of stagenet XMR. Backend bugs are critical for us, so this needs deep analysis.
Please expect a detailed report next week.
Status: [Under investigation]
One of your faucet-links on gitbook points to a Testnet faucet, not Stagenet.
Thanks for pointing it out.I mistakenly added a testnet faucet link instead of a stagenet faucet link earlier (just CypherFaucet provides both faucets: for testnet and stagenet).
The link is correct now.
Status: [Fixed]
With 4 confirmations, my Bitcoin deposit status was still "Partially confirmed". It would be nice to show how many confirmations are needed (and 4+ is excessive for Bitcoin). I didn't see exactly how many deposits it takes.
For BTC, 6 confirmations are currently required.Next week, we will experiment with reducing the number of confirmations across all blockchains to find a balance between speed and security.
Important note for our Beta Test community:
We will pause bug reviews and development work until Monday.
After weeks of intense work, my teammate and I need a short rest to "clear the cache in our heads."