You choose HIVE → USDC, click Swap, and a few moments later the USDC arrives.
Simple, right?
From the user's perspective, it should be. But behind that single button is a chain of services, requests, transactions, and confirmations working together to make the swap happen.
Here is what actually happens when you use our Aggregator.
1. You Choose Your Swap
You start by selecting the asset you want to swap, the asset you want to receive, and the amount.
For example:
100 HIVE → USDC
The Aggregator now needs to figure out how that swap can be executed.
It doesn't simply pick one provider and hope for the best.
2. The Aggregator Requests Quotes
The Aggregator sends the swap details to the available providers. Each provider can return different information:
- Exchange rate
- Expected amount received
- Fees
- Estimated completion time
- Available route
This is where having multiple providers becomes useful. The same swap can produce different results depending on the provider and route available at that moment.
3. The Quotes Are Compared
Once the responses come back, the Aggregator can compare them.
The goal isn't simply to find the provider with the lowest advertised fee. The actual result depends on the complete route, including the rate, fees, available liquidity, and other conditions since it can go throught different token inbetween the pair you choose. With this, the Aggregator select an available route for the swap.
This happens before the user signs anything.
4. The Transaction Begins
Once you confirm the swap, the required transaction is created.
For a HIVE swap, this means signing the corresponding Hive transaction through Keychain.
Your private keys stay under your control. Keychain signs the transaction without sending your private keys to the swap provider. The signed transaction is then broadcast to the network. Now the blockchain takes over.
5. The Provider Processes the Swap
After the required transaction is detected, the selected provider processes the exchange according to the chosen route. Depending on the route, this can involve different assets, networks, and blockchain transactions.
This is also why swaps aren't always instant. A provider may need to wait for a blockchain transaction, move funds between networks, execute the exchange, and then send the destination asset.
6. The Blockchain Confirms It
Eventually, the destination transaction is broadcast. The relevant blockchain confirms it, and the funds arrive in your destination wallet.
You started with:
HIVE
And end with:
USDC
The interface makes the journey look short because it is designed to hide the complexity.
One Button, Many Systems
This is the important part. When you click Swap, you're not interacting with a single exchange. You're interacting with an infrastructure layer that has to coordinate:
Your wallet → quote providers → route selection → blockchain transaction → swap provider → destination network → confirmation
And all of this has to happen while dealing with constantly changing exchange rates, network conditions, liquidity, fees, and transaction status. That's what our aggregator is really doing.
Why More Providers Matter
Adding more providers isn't just about having a longer list of names. More providers can mean more possible routes, assets, networks, rates, and availability. If one provider doesn't support a particular route, another might.
If one provider has a better rate at a given moment, the Aggregator can surface that option. The goal is to give you more ways to move your assets without having to manually check several services by yourself.
Now, it is almost time to swap multichain on Keychain.
Our Beta is getting the final touches and this is one the last steps for the Multichain update that we all have been waiting for. See you all soon!
Download the Apps / Extensions
The download links for our mobile Apps and extensions are available on our landing page
Discord
To communicate with us, report an issue or become a Beta tester, join our Discord by following this link : https://discord.gg/3EM6YfRrGv
Or scanning this QR Code :
Team
@stoodkev : Founder - Witness @cedricguillas : Lead Developer - Witness @krios003 : Full-stack Developer @manuphotos : Ecosystem Growth Lead - Witness @yabapmatt : Advisor - Witness
