Non-custodial cross-chain swaps are a core innovation in decentralized finance, allowing users to exchange assets across different blockchains without ever surrendering control of their funds to a third party. STON.fi aims to support this with its Omniston system, but beneath the surface, delivering true “non-custodial” functionality becomes far more complex when moving tokens between chains.
In a single blockchain environment, non-custodial designs are easy to define: you initiate and sign the transaction yourself, and no other party—whether an individual, platform, or intermediary—takes possession of your assets. However, once more than one blockchain is involved, the lines start to blur. Each chain has its own rules, confirmation process, and infrastructure, making cross-chain custody a more nuanced and risk-prone affair.
STON.fi: Understanding “Non-Custodial” in Cross-Chain Context
The common definition of non-custodial, including that quoted by CoinMarketCap, is simple: your funds are never controlled by a platform or third party at any point in the transaction. But as STON.fi highlights in its own educational material, maintaining that guarantee across chains is technically difficult. In single-chain swaps, such as swapping one token for another on the same chain, your wallet interacts directly with a smart contract. You only lose custody when you choose to send tokens, and smart contracts can ensure either the transaction completes as intended or fails safely.
When you execute cross-chain swaps, though, your assets must effectively leave one blockchain and arrive on another. This creates a custody “gap”—a period in which someone, somewhere, must ensure that the original asset is safely locked or managed before you receive an equivalent on the target chain. Managing this without centralization is one of the hardest challenges in DeFi.
Challenges with Cross-Chain Swaps
Many platforms, including some branded as “decentralized,” adopt architectures involving reserve contracts and wrapped tokens. Typically, the original asset is locked on one blockchain, and a new, wrapped version is issued on another. The fundamental risk lies in whether the underlying reserves are managed transparently and securely. If the reserve is breached or manipulated, wrapped tokens on the new chain may become worthless—even if everything looks seamless on the interface.
Custody Risks in Cross-Chain Bridges
- Reserve Contracts: Most cross-chain bridges rely on reserve contracts to hold users’ original tokens before issuing a wrapped representation. If these reserves are not independently audited and securely managed, users remain exposed to behind-the-scenes failures.
- Validator and Relayer Groups: Many systems use validator or relayer groups to authorize and finalize transfers between chains. If this group is too small or poorly distributed, a single compromise or collusion could put all users’ funds at risk. History has shown that multisignature bridges are frequent targets for attacks.
- Representation of Assets: Rarely do you receive a “true” native asset on the destination blockchain. Instead, you get a wrapped token, whose redemption depends entirely on the ongoing integrity of the reserve system. If reserves are mismanaged, frozen, or lost, the wrapped assets lose value instantly—even if they appear legitimate in your wallet.
For a broader look at the security and tooling landscape on TON and similar networks, see TON tools and DeFi.
How to Assess Non-Custodial Claims on STON.fi
1. Do you ever lose full custody of your funds, even for a moment?
2. Does the process depend on trust in a validator group, reserve manager, or other intermediaries?
3. Are you always swapping for native assets, or are you being given wrapped representations?
4. Are robust cryptographic safety measures in place—such as Hashed Time Lock Contracts (HTLCs)—to guarantee swaps either complete or safely reverse?
5. Is the platform fully transparent about these details, with proof and documentation available for independent review?
Implications for STON.fi Users
Source reference: original source.