gUtexo guys Do you know Exchanges lose a lot of money by simply having funds sitting around. If an exchange wants users to withdraw USDT quickly, it usually has to keep money ready across different chains and different platforms. The problem is that this money is basically stuck there. It’s safe, but it can’t really do much until someone actually needs to withdraw. Now this is where I see @utexocom coming in. The idea is to let USDT move through Bitcoin using RGB, while Lightning can be used when that USDT needs to move between venues. So instead of relying on another smart contract chain for settlement, the settlement happens through Bitcoin. The big goal is speed. Imagine a market maker needs to move $2 million in USDT from one trading platform to another before the next trading session. With slower rails, they may have to send the money early and just wait. With faster Bitcoin-based USDT rails, they can move the funds much closer to when they are actually needed. Same thing with weekend withdrawals. An exchange might keep extra USDT sitting on Tron, Ethereum, and internal wallets just in case people start withdrawing. If those funds can move quickly when needed, the exchange may not need to keep as much capital sitting idle everywhere. And that’s really the point. Idle capital is expensive. Utexo is trying to make moving USDT closer to the moment it’s actually needed.
DreddShare

Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.
