Astro
Astro used Velas while its original Cardano plan depended on KEVM
Astro, the AstroSwap project, used Velas for its decentralized exchange while its original Cardano plan depended on KEVM. Its cross-chain design connected supported Cardano assets with trading on Velas. Bridging assets into that environment and moving the exchange itself onto Cardano were separate parts of the original plan.
Velas execution and Cardano access
Velas supplied the exchange’s execution environment, while the bridge connected supported Cardano assets with that environment. AstroSwap aimed to make Cardano assets tradable. The execution network determined the contracts and transaction rules at the trading end of the connection.
Early development through bridging and listings
The early rollout developed the Velas-based exchange by connecting and listing Cardano assets. During March 2022, the project announced a collaboration involving World Mobile Token, a Cardano native asset. The collaboration concerned adding World Mobile Token to the trading offering through the existing cross-chain approach.
WagyuSwap supported the exchange within the Velas ecosystem.
The contract environment Velas supplied
Velas provided Ethereum Virtual Machine compatibility, which connected its own blockchain infrastructure with established smart contract tools.
EVM execution
The Ethereum Virtual Machine, usually shortened to EVM, defines an environment for executing smart contract code. Velas supported EVM transactions within its own network. Its architecture wrapped EVM execution in native transactions which invoked the EVM program. This arrangement let EVM applications operate on Velas without turning their transactions into Ethereum transactions.
Ethereum-compatible access
Velas also supported the Ethereum JSON-RPC API, a standard interface wallets and applications use to communicate with compatible nodes. Familiar tooling could therefore interact with a different blockchain through a compatible interface. The shared interface did not combine the ledgers or their balances. Wallet integration and contract execution both needed the destination network’s context, even when the software looked familiar.
Swapz and the cross-chain connection
Swapz supplied the original bridge connection between Cardano assets and the Velas trading environment. The launch-era design linked locked assets on one side with minted tokens on the other. That relationship gave the destination tokens their backing and allowed them to enter the exchange’s supported asset set. One-to-one backing belonged to the bridge design: it described the quantity of an underlying asset a representation corresponded to. It did not describe the exchange rate between two different tokens during a trade.
The bridge interface determined which assets users could select. The ability to represent Cardano assets across chains did not mean every asset immediately appeared as a selectable bridge option. The original expansion plan included adding further supported tokens.
Asset identity on each ledger
Cardano assets and their Velas representations belonged to different ledger contexts, even when their names referred to the same underlying asset.
Cardano native assets
Cardano’s ledger directly tracks custom native assets. Their identity combines a policy ID with an asset name, which distinguishes them from other assets sharing a display name. ADA has a separate role as Cardano’s native currency and does not use an explicit policy ID. Native asset transfers rely on the ledger’s built-in asset accounting, without requiring a separate token contract to track each transfer.
Destination-chain representations
The Velas-side representation had its own balance on the destination ledger. Its backing connected it with the source asset, while storage and transfer rules followed the destination environment.
Bridge issuance and exchange liquidity
Bridge issuance and exchange liquidity performed different jobs in the original design. Issuance created a destination-side representation backed through the bridge arrangement. Astro Pools supplied the token balances the automated market maker used for exchanges. A minted representation could exist without a usable trading pool for the desired exchange.
The bridge’s backing ratio therefore answered a different question from the pool’s trading conditions. A swap required enough liquidity in the relevant tokens. The amount a trade could receive depended on the exchange pool, rather than on a promise to mint an equal quantity of the same asset through the bridge.
Solar Farms rewarded deposits of liquidity provider tokens, while Galaxy Pools accepted the project’s ASTRO token directly. Those additional uses belonged to the exchange’s reward system.
Wallet context and network fees
Wallet access followed the network hosting the exchange, so the original MetaMask setup concerned the Velas environment. A Cardano asset held on its native ledger needed the supported cross-chain path before it could become a usable destination representation. The fee currencies also followed their respective networks: ADA paid Cardano transaction fees, while VLX paid Velas network fees. The asset passing through a bridge and the currency paying a network fee could consequently have different roles in the same cross-chain arrangement.
What role did KEVM play in AstroSwap’s Cardano plan?
KEVM was the execution dependency the project named for its proposed Cardano deployment. The technology specified EVM behavior through the K framework, including the rules governing machine state and execution. Its compatibility aimed to let applications written for the EVM execute in a formally specified environment. That relationship explains its relevance to an exchange already using an EVM-compatible blockchain. The proposed move concerned where the application could run, beyond the earlier bridge connection between assets on different networks.
The original Cardano deployment plan made KEVM availability a prerequisite. That condition applied to relocating the exchange’s execution. Extending the list of assets the bridge supported addressed a separate part of the service’s development.
Plutus and Cardano’s separate smart contract path
Cardano already had Plutus smart contract support before the exchange’s early 2022 rollout. The Alonzo upgrade introduced that support on 12 September 2021. Waiting for KEVM therefore concerned a particular compatibility path within the project’s plan. It did not describe Cardano waiting for all smart contract functionality. Plutus and an EVM-compatible execution environment addressed different ways of developing and running applications.
Plutus Core scripts participate in Cardano transaction validation through its extended UTXO model, which builds on unspent transaction outputs. That model allows outputs to carry spending conditions and additional data. The existence of this native contract system did not automatically deploy an EVM application onto Cardano. A project needed an application implementation appropriate to its chosen execution environment.
A Velas trade within the original design
In a hypothetical case, a reader asks whether a completed swap on the original Velas deployment, involving a supported bridged Cardano asset, means the exchange had moved onto Cardano.
The completed exchange changed token balances in the Velas environment. The Cardano connection concerned the input asset’s origin and backing.
The swap in this case was a Velas exchange involving a Cardano-linked asset. A different deployment executing the exchange transaction on Cardano would change the conclusion because it would change the execution network.
The scope of the original migration plan
The proposed Cardano move concerned application deployment, which would require more than expanding the supported asset catalogue. Runtime availability would address the named KEVM dependency. The exchange would also need contracts and asset handling appropriate to the new environment, with liquidity available for its supported trades. The historical plan explains why Velas appeared in a Cardano-focused service. The original KEVM requirement alone does not establish when or whether AstroSwap deployed on Cardano.
Astro: the short answers
Did KEVM’s 2018 testnet establish a Cardano production deployment for AstroSwap?
The KEVM testnet was an experimental environment separate from AstroSwap’s production exchange. Its launch on 28 May 2018 demonstrated EVM-compatible smart contract execution in a testing setting. The later AstroSwap plan concerned a production deployment on Cardano, where the required execution environment and the exchange application would both need to be available.
Does formal verification of KEVM certify the original bridge’s security?
Formal verification of a virtual machine does not certify every bridge or application using a compatible execution model. Contract verification requires specified properties and a demonstration the contract satisfies them. Bridge backing, asset issuance and cross-chain coordination involve their own implementation. KEVM’s formal specification therefore did not amount to a security guarantee for AstroSwap’s bridge or its trading contracts.
How could Cardano congestion affect the original route into Velas?
Cardano congestion could delay the source-chain part of the original bridge route. Velas transaction speed applied to work on the destination network, after assets reached that environment. Faster destination-side execution could not remove time spent completing the Cardano-side transfer. This distinction concerned the original cross-chain arrangement and did not supply a fixed end-to-end bridging time.
Would KEVM compatibility automatically transfer existing Velas liquidity positions onto Cardano?
KEVM compatibility alone would not transfer existing Velas liquidity positions onto Cardano. Those positions belonged to pool contracts and balances in the Velas environment. A separate deployment would need its own arrangement for handling the assets and representing liquidity ownership. Compatibility of contract execution did not itself define a conversion rule for liquidity provider tokens or move deposited assets between ledgers.
Updated