Been a while since I used a decentralized no KYC platform, thanks team @Bridgoro for making this happen

Secondly will this cause any interoperability issues seeing the platform has support for several chains, we used to seeing EVM platforms and all but this is some hybrid stuff..any insights ??
That's why we say that
Bridgoro is semi-decentralized.
We don't want to confuse our users by claiming to be
"fully decentralized".
This was an intentional choice, as semi-decentralization allows us to balance security with better UX and user comfort.
600 Satoshi aren't even reach $1, not sure why you have to increase the minimum exchange for 2x-2.5x.
We will publish a detailed report after the Beta Test explaining why the Minimum Exchange Value was increased and how we avoided transaction stuck issues.
Please note: transaction fees differ between testnet and mainnet.
- On testnet we could keep the minimum at around $12.
- On mainnet, such a low value isn't possible due to real blockchain fee limitations.
People might trade large amount because they trade big coins, but if the exchange list so many coins and tokens, people will choose to trade small because they only want to hold in small amount since the coins/tokens are still new.
If Bridgoro can list so many coins/tokens like swap platform, they would able to compete with other exchanges because the main problem of no KYC P2P/DEX due to lack of coins/tokens listed.
More native coins will be added once the exchange is officially released.
You don't need to worry much about if people are suspicious of the newcomers coming up with a project. Once people use and test the platform and find it legit, these voices will be shut down automatically. You do not need to pay focus on such things and keep foucs on developing the project.
By the way, the beta phase is going great, and also those bug reports will help you make the platform better. Will you be ending the beta phase on 31 August, or any plans to extend it ?
Sometimes we see users asking questions already clearly answered in the ANN or GitBook.
We kindly ask everyone to spend a few minutes reading the provided materials before posting questions, as it helps reduce confusion and repetitive answers.
The minimum amount is 12$ so below $12 it will not continue. But If we select $12, the network fee is successfully deducted without triggering the dust transaction issue. Please correct me if I am wrong then why it gets stuck at 0.3% service fee on each transaction? It should be solved easily by asking the user to increase the amount by 0.3% of the total minimum amount which would be 12.036 and then deduct that amount from 12.036. I have understood that you are not using any third party module you have cleared this to me before, I think this reply was not for me but for loyce right? Anyway, I replied back with a question, one more thing the maximum amount in the detail we see, is it the amount we will receive after all the fee deductions?
Example of a Dust Transaction.Here's a real case we faced:
A user sent $10 in BTC, which was about 0.00008955 BTC.
A 0.3% Service Fee was applied, equal to 0.00000026 BTC.
Since it's impossible to send 26 satoshis (the transaction wouldn't even be processed), the transaction got stuck.
This is exactly why dust transactions are an issue and why careful value tuning is necessary.
I guess he complain about the reward distribution, you know it's really long if he need to wait till Q2 2026, it's around 7-10 months. Even there's no upfront deposit, but the effort and time for bug hunters spent should be calculated too.
But Bridgoro have clarified it, so he should have already understand.
Rewards will be distributed within 2 days after the Beta Test ends
(August 31, 2025).
So approximately, users can expect their rewards around
September 2, 2025.
These 2 days are necessary to:- Review participants' activity.
- Count and verify bug reports.
Since we are only two developers, we need this time to ensure rewards are distributed fairly and accurately