This sounds like a problem in your implementation. When I take one UTXO (with non-rounded value) and send it to another address, there is no change address necessary. See
9a8e9bbe51c37c229eb5d9922a719af841e99cd3cffe8f6a2986a7f3f4ac0924 for example.
Maybe you're trying to calculate the amount to send by assuming a fee and subtracting it from the total, instead of doing "send all minus fee", as I did in the transaction above.
We did a small round of research regarding UTXOs, and we agree that the case where a transaction splits into two outputs with one of them being 311 sats, does happen. Our current method for handling Bitcoin blockchain data isn't perfect, and we definitely have room for improvement. Thank you for pointing this out, because honestly, we probably wouldn't have noticed it ourselves. Previously, we had noticed similar transactions, but since they were just UTXOs worth around 0.1-0.3 cents, we simply ignored that part.
Press the info icon (i) next to the Deal Details popup header.
Thanks, that's all I was looking for. It's amazing how blind I am to such obvious things.... I really searched for something!
It's not because you didn't see it, it's because our UX/UI wasn't done well in that part.
We will think it through and hopefully come up with a more intuitive UX solution.
I was alarmed for a different reason; acception isn't even a word that's used anymore. This isn't trivial, because any native English speaking customers are going to see that and probably jump to a quick conclusion that Bridgoro is another fly-by-night foreign exchange that's trying to attract English speaking traders (for whatever reason) but doesn't know the language themselves. Exception or acceptance would be what you're going for here.
That's constructive criticism, by the way. Hopefully I did not misinterpret something, lest I look like the entire rear end of a donkey.
Thank you for the thoughtful criticism.
Honestly, we didn't expect it to spark any discussion at all.
In any case, we genuinely appreciate the time you’ve invested in contributing to our project and for going through several, if not all, pages in this thread. Now, let me address your feedback. We accept your criticism, but we’d like to clarify a few points to avoid any misunderstandings.
First, we never claimed to be native English speakers. Yes, we speak English fluently, I'm fluent in three languages, and my teammate is fluent in two. So we don't see any issue with running the project in English, especially considering that it's an international language and roughly 99% of all projects use it as their primary communication medium.
Regarding the specific word you pointed out, I'd like to emphasize an important distinction: writing frontend text in English and writing the backend underlying code, including developer-mode error messages, are essentially two different English languages.
Also, if that RBF option can be abused successfully, you'll have a line of scammers ten thousand long just waiting to rip you off. I wish you luck and hope something like that doesn't happen.
RBF won't be abused in any way, because this part will be improved and properly fixed before launch.
And yes, we fully agree that a lot of scammers will try to target Bridgoro, that's exactly why we decided to run two Beta tests instead of pushing out a buggy release like many big companies do.
We care about what we are building, and before going live, we want to deliver something that may not be perfect, but as close to it as possible.
Whitepaper
Link:
https://bridgoro.gitbook.io/bridgoro-docs/terms-and-privacy/terms-and-conditionsCapital letters instead of small caps:
7. Intellectual Property
Bridgoro doesn't claim ownership of any intellectual property at this stage.
The project is not open source for now, as the core functionality (Cross-chain Bridge) is under active development.
core functionality (cross-chain bridge) is under active development.
In our case, we used Cross-Chain Bridge as an acronym. An acronym formed from the first letters of each word.
8. Data Collection and Privacy
Bridgoro exchange respects users' privacy. The only user data collected is the email address used for account registration and login. This data is:
'is' removal
The Data Collection and Privacy paragraph was fully rewritten because certain parts changed during the BETA phase, so we added an exception regarding our use of Cloudflare.
Fixed.
The amount descriptions were rewritten to make them clearer for users.
[Amount you sent] shows how much of the asset you submitted for the exchange.
[Amount you get] shows how much of the exchanged asset you will receive or have already received.
Page:
https://bridgoro.gitbook.io/bridgoro-docs/system-architecture/whitepaperBridgoro is a semi-decentralized exchange because it combines two worlds into one and takes the best parts. An automated escrow system using blockchain adapters and smart contracts ensures secure, trustless swaps come from the decentralized part, and user-friendly matchmaking and rate modules make the platform intuitive and smooth for all users is from the centralized world.
all users from
This paragraph has been fully revised and rewritten.
Bridgoro is a semi-decentralized exchange because it combines two worlds into one and takes the best of both. The automated escrow system, powered by blockchain adapters and smart contracts, delivers secure and trustless swaps from the decentralized side, while user-friendly matchmaking and rate modules provide the intuitive and smooth experience typical of centralized platforms.
Two-Factor Authentication (2FA) adds an additional layer of security to user accounts by requiring a secondary verification step after entering the password. Users can enable 2FA via their account settings. Need to implement Time-based One-Time Password (TOTP) via authenticator apps (e.g., Google Authenticator, Authy).If 2FA enabled, After successfully entering their password, users are prompted to complete 2FA.The system should also allow the user to save the recovery code so that they can restore 2FA in case they lose their phone. Additionally, there should be an option for administrators to disable 2FA if the user loses access.
is missing and after successfully
Fixed.
ETH Contract addresses bug:
Upon putting contract address instead of goto regular address, the XMR-ETH offer in the explore offers section is getting submitted without going through any address validity checker.
Contract Eth address used: 0x5AbFEc25f74Cd88437631a7731906932776356f9
=This should be prevented for causing loss of funds.
SOL token creator address or Mint address bug:
Offer creation is possible with a dummy mint address on the BTC-SOL pair
Mint address used: pumpCmXqMfrsAkQ5r49WcJnRayYRqmXz6ae8H7H9Dfn
TRon smart contract address:
BTC-TRX
Thanks for testing the address validation using contract addresses.
But if a user submits a contract address instead of their own standard wallet address, the resulting loss will be categorized as Dumb Loss.
As we mentioned earlier, if a user can't complete two basic steps like depositing the required amount into the designated wallet and confirming the deposit, then that user really shouldn't be handling crypto at all.
Tradingview Cookie:
Page: Homepage bridgoro.com
Cookie
tradingview-widget.sessions
Source: tradingview-widget.com
Site writes analytical or trading tool related aren't stored and session only
We have rewritten the T&C section in GitBook and will update the in-site version shortly.
8. Data Collection and Privacy
Bridgoro exchange respects users' privacy. The only user data collected is the email address used for account registration and login. Our data practices ensure the following:
Stored securely
Not used for tracking, marketing, or profiling
Never shared with third parties
Exception: We use Cloudflare, which may collect certain technical data for its own operational and security purposes. Unfortunately, we cannot restrict this collection, as Cloudflare is essential for protecting Bridgoro from DDoS attacks, intrusion attempts, and potential data leaks (including IP address exposure).
Users can view the Privacy Policy for more information.
