🚀Supported Operations
Liberty Swap provides a production-ready set of cross-chain swap and bridge operations designed to balance execution efficiency, user autonomy, and privacy. The protocol currently supports over 1,000 asset pairs across six blockchain networks: PulseChain, Ethereum, BNB Smart Chain, Arbitrum, Base, and Solana. Support for additional networks and pairs is introduced incrementally as liquidity conditions permit.
Liberty Swap’s operational design prioritizes PulseChain-centric interoperability. Bridging to and from PulseChain is the primary supported use case. Cross-chain swaps between non-PulseChain networks (for example, Base ↔ Ethereum) are conditionally enabled only when sufficient liquidity and execution guarantees are available, ensuring predictable settlement and minimizing execution risk.
All supported operations are non-custodial and executed entirely on-chain.
🔄 Standard Swaps
In standard mode, Liberty Swap executes swaps using account abstraction and intent-based routing. This mode is optimized for speed, composability, and ease of use, while preserving non-custodial guarantees.
Each user-initiated intent is assigned a unique Order ID, generated solely for temporary status tracking within the Liberty Swap interface. The Order ID serves as a short-lived reference to the execution lifecycle (e.g., pending, executing, completed) and automatically expires after 24 hours. It is not a persistent identifier and is not linked to wallet addresses, transaction hashes, or any form of user identity.
Upon successful execution, the user interface may display:
the Order ID, for short-term confirmation and support reference, and
the on-chain transaction hash(es) produced by the underlying blockchain execution.
Transaction hashes are provided strictly for user-side verification and transparency. Liberty Swap does not store, index, or retain transaction hashes, wallet addresses, or execution metadata off-chain. No internal mapping exists between Order IDs and transaction hashes once execution is complete.
As a result, only the user, by virtue of controlling the originating wallet or destination address, can independently verify or track a completed operation using public blockchain explorers. Liberty Swap does not monitor user transactions after execution, cannot reconstruct transaction histories, and does not maintain any proprietary record of user activity beyond ephemeral, execution-scoped state.
This design ensures that:
all transaction data remains exclusively on-chain,
post-settlement traceability is entirely under user control, and
Liberty Swap cannot correlate orders, addresses, or transactions across time.
In private execution mode, this principle is further strengthened through zero-knowledge settlement, where transaction hashes themselves do not reveal sender, recipient, asset type, or transferred amount. In both modes, privacy is preserved by design, and verification authority rests solely with the user.
The fastest path to use Standard Mode is to connect any EVM-compatible wallet (e.g. MetaMask, Rabby, or Pulse Wallet) and submit a swap intent. The user signs a single transaction in their wallet, and the protocol’s relayers immediately execute the swap. Because the user’s wallet is directly involved, execution is typically very quick (on the order of 0–2 minutes) and gas costs are minimized. The trade is settled on-chain with one signature, and the user’s funds remain in their wallet until the last step.
This standard mode applies account-abstraction technology so that the user need not hold any particular chain’s gas token, which makes it highly efficient and secure.
🕵️ Private Swaps
Liberty Swap's Private Swaps are designed for users prioritizing privacy and anonymity in their transactions. For users requiring strong anonymity, Liberty Swap’s Private Mode leverages the Railgun privacy protocol.
In practice, the user’s swap order is sent to Liberty Swap relayers, which deposit the funds into Railgun smart contracts. The Railgun system then generates zero-knowledge proofs so that the sender’s address, recipient’s address, and transfer amounts become confidential on-chain. After the zk-proof verifies on the target chain, the destination token is released to the receiver’s address. Throughout this process, no on-chain observer can link the input to the output. Railgun privatizes the sender, recipient, asset, and amount simultaneously.
Liberty Swap does not have access to viewing keys, private balances, or decrypted transaction details. Privacy guarantees are enforced cryptographically and remain fully under user control. Private mode operations incur additional computational overhead and may have longer settlement times compared to standard mode, reflecting the cost of zero-knowledge proof generation and verification. However, they provide more anonymity: the swap path mostly cannot be traced.
Gas Policy and Execution Costs
Liberty Swap maintains a gas abstraction policy across supported networks. Where possible, transaction fees are bundled or sponsored at the protocol level, allowing users to complete swaps without holding chain-native gas tokens.
Execution costs and protocol fees are clearly disclosed prior to confirmation. Fees are applied deterministically based on the selected route and execution mode. Liquidity-aware routing minimizes slippage, and no discretionary pricing adjustments are performed by the protocol.
Data Minimization and User Transparency
Liberty Swap is designed with strict data-minimization principles:
No user identity data is collected.
No wallet metadata is retained.
No transaction hashes are stored off-chain.
Order IDs are temporary, non-identifying, and expire automatically.
All transaction verification remains fully on-chain and independently auditable. Liberty Swap functions solely as execution infrastructure and does not monitor, aggregate, or analyze user activity beyond what is required for real-time transaction fulfillment.
Last updated