Publier

shillomest
shillomest
TON processes transactions in parallel across different shards and that gives speed but there is a catch. Transactions from different shards hit contracts asynchronously and there is no guarantee they arrive in the order they were sent. For DeFi this is super critical. A liquidity pool is just reserves of two tokens and when two users swap into the same pool from different shards at the same time the contract gets two transactions milliseconds apart. If they get processed in the wrong order the rate calculation for the second one will be based on stale reserves and the user gets a wrong rate. On STONfi this matters even more because the aggregator constantly pushes big volume through tons of pools and any desync can mess up the price. This is a classic race condition where two processes try to change the same data at once. In traditional blockchains with sequential processing this is not an issue. But in TON async architecture it is and it has to be handled at the smart contract level. On STONfi this is handled through proper processing logic so you do not get surprised by the rate. $BICO

Avertissement : les contenus d'OKX Orbit sont uniquement publiés à titre informatif. En savoir plus

Réponses

Aucun commentaire pour le moment. Soyez le premier à répondre !