Release Update
Guys, we know you are probably tired of reading another update about release delays. Trust us, we are just as tired of delays as you are. But releasing an unfinished product isn't an option for us, especially when user funds are involved.
We want to briefly explain why the delays are happening, despite two successful BETA TESTS.
TESTNET vs MAINNET reality: We've learned the hard way that successful testing on TESTNET doesn't guarantee identical behavior on MAINNET. Even with a carefully designed test environment, the differences between testnet and mainnet are significant. Many libraries behave differently or are simply incompatible, which forces us to update, rewrite, and adapt large portions of the system.
Solana (SOL) & Tron (TRX): Unexpected MAINNET behavior During TESTNET testing, Solana and Tron worked flawlessly. However, once deployed to MAINNET, we encountered a large volume of spam transactions, including dust transfers and lookalike transactions with similar amounts and addresses (a common wallet-level attack vector). In some cases, these micro-transactions were reaching the buffer wallet before legitimate user transfers. As a result, the system incorrectly assigned statuses such as Dead Wallet (due to extremely small amounts) or Underpayment, which prevented the exchange from executing. To resolve this, we built an anti-spam filtering layer for Solana and Tron from scratch, ensuring our blockchain module only processes the exact intended transfer amounts.
Monero (XMR): Mainnet Latency and Reverse Engineering With Monero, we initially tested on our own STAGENET node without issues. However, once switching to MAINNET, we began experiencing latency-related errors that caused failed sends. The difficult part: there is very limited documentation on this specific issue. We had to reverse-engineer the behavior and identify the root cause ourselves. It took significant time and effort, but the issue has now been resolved.
Collector Module rewrite: Because much of the blockchain module had to be rewritten for MAINNET compatibility, the original Collector Module became incompatible. Roughly 70% of it had to be rebuilt to align with the new architecture.
We are currently finalizing the updated Collector Module. Once this is complete and fully tested, we expect to move forward with the release.
Thank you to everyone in our community for your patience and support! It genuinely motivates us to keep pushing forward.
Yes, the community is still small but based on both beta tests, it's highly technical and incredibly sharp. We truly appreciate that!
Weare also seeing messages on Telegram from users asking why registration is closed because they want to use the exchange. That's a good sign. Registration will remain closed until the official release to ensure stability from day one. Launch is coming very soon.
At the end, we would like to say that looking at current crypto market trends, we are more confident than ever that we made the right decision with Bridgoro.
As more exchanges move toward mandatory KYC/AML frameworks, we believe there should still be space for privacy-focused infrastructure, lets say a small island for true crypto enthusiasts who value self-sovereignty. That's what we are building.
We will keep you updated.
|