Beruflich Dokumente
Kultur Dokumente
Whitepaper
Table of Contents
Project Abstract
A Cross-Chain Token swapping platform that supports any token deployed on the following
chains Ethereum (ERC20), Binance (BEP-2), EOS. Multichain swap acts as a one stop
platform where token can be swapped across multiple chains maintaining the overall
market cap of the across chains.
Main Dashboard
Swapping Dashboard
• Speed and accuracy: Smart contracts are digital and automated, so you won’t have
to spend time processing paperwork or reconciling and correcting the errors that
are often written into documents that have been filled manually errors.
• Trust: Smart contracts automatically execute transactions following predetermined
rules, and the encrypted records of those transactions are shared across
participants.
• Security: Blockchain transaction records are encrypted, and that makes them very
hard to hack. Because each individual record is connected to previous and
subsequent records on a distributed ledger, the whole chain would need to be
altered to change a single record.
On the user experience side, Binance Chain is designed in a way that incorporates the most
user-friendly functions on the Binance website. It also provides people with many options
to participate in the chain. You can create your own address via the Binance Chain Web
Wallet, which has a user interface similar to what is on Binance. From there, wallets that
support Binance Chain include Trust Wallet, Binance’s official crypto app, as well as third-
party wallets like the Ledger Nano S and many more to come.
According to the EOS model, instead of “renting” computing power, EOS coin holders have
ownership of the network.
For example, if you owned a 1% stake in EOS coins, you would essentially own 1% of the
network, meaning you would own 1% of the required computing power to process the
transaction. This is what makes transactions free!
The EOS coin operates in the same way as any other cryptocurrency — you can send, hold
or receive funds between wallets. This makes it an excellent payment system as you can
transfer money to anyone in the world for free, in just a few seconds.
EOS allows well-defined levels of permission by incorporating features like web toolkit for
interface development, self-describing interfaces, self-describing database schemas, and a
declarative permission scheme.
In EOS the Governance is maintained by establishing jurisdiction and choice of law along
with other mutually accepted rules This is usually done via the legally binding constitution.
Every single transaction in EOS must include the hash of the constitution to the signature.
This, in-essence, binds the users to the constitution.
3. The Problem
Platforms like Ethereum, Binance and EOS have created an ecosystem where developers
can create and deploy their applications. The networks get constant updates which add
stability and a whole slew of features and extensions to increase development on their own
individual chains. These chains compete against each other in the crypto ecosystem trying
to bring more and more developers and users inside their ecosystem.
The underlying principle that developers utilize is the transfer of tokens from one account
to another on the same chain implemented according to their own rules. These tokens can’t
travel outside the chain.
MultiChain swap aims to solve this issue by acting as an intermediary layer with which any
token configured on the platform can be converted to any token pegged on a specific chain.
Such a system enables seamless transfer of token across chains bring interoperability to
the chains and allowing applications to now interact across chains and develop dApps that
are operable across multiple chains.
4. The Solution
4.1 Chain and Network Details
Currently Multichain swap is implemented for swapping tokens pegged on the following
chains.
• Ethereum Chain (Ropsten Test Network)
• Binance (Test Network)
• EOS (Jungle Test Network)
When a Binance/EOS Chain to Ethereum Token Swap Request enters the swapping engine
the Transaction type is determined by the Ethereum Swapping Engine and the details of
the transaction is extracted from the respective chain.
After the details have been extracted the transaction is sent to the Queue Handler which
stores the transaction until it is approved by the network. The Queue handler rejects the
transaction if no receiver is specified or if the transaction fails. In the case of Binance chain
the Swapping Engine receives an instant confirmation and its directly sent for Token
conversion.
At the Token Conversion Stage, the transaction details are used to remove the appropriate
amount from circulation from the 1st chain and brought onto the 2nd chain. The Transaction
hash for this conversion is sent back to the user.
The transaction hash acts as a proof that exact amount of tokens were transferred to the
user’s account subtracting the cross-network gas fees at that time. This transaction hash
can be looked up on a Block Explorer to verify the details of the swap.
When an Ethereum/EOS Chain to Binance Token Swap Request enters the swapping engine
the Transaction type is determined by the Binance Swapping Engine and the details of the
transaction is extracted from the respective chain.
After the details have been extracted the transaction is sent to the Queue Handler which
stores the transaction until it is approved by the network. The Queue handler rejects the
transaction if no receiver is specified or if the transaction fails. After the transaction is
approved by the network it is passed to the token converter.
At the Token Conversion Stage, the transaction details are used to remove the appropriate
amount from circulation from the 1st chain and brought onto the 2nd chain. The Transaction
hash for this conversion is sent back to the user.
The transaction hash acts as a proof that exact amount of tokens were transferred to the
user’s account subtracting the cross-network gas fees at that time. This transaction hash
can be looked up on a Block Explorer to verify the details of the swap.
When a Binance/Ethereum Chain to EOS Token Swap Request enters the swapping engine
the Transaction type is determined by the EOS Swapping Engine and the details of the
transaction is extracted from the respective chain.
After the details have been extracted the transaction is sent to the Queue Handler which
stores the transaction until it is approved by the network. The Queue handler rejects the
transaction if no receiver is specified or if the transaction fails. In the case of Binance chain
the Swapping Engine receives an instant confirmation and its directly sent for Token
conversion.
At the Token Conversion Stage, the transaction details are used to remove the appropriate
amount from circulation from the 1st chain and brought onto the 2nd chain. The Transaction
hash for this conversion is sent back to the user.
The transaction hash acts as a proof that exact amount of tokens were tra2nsferred to the
user’s account subtracting the cross-network gas fees at that time. This transaction hash
can be looked up on a Block Explorer to verify the details of the swap.
5. Conclusion
MultiChain Swap acts as bridge between multiple chains and brings interoperability to the
crypto ecosystem and the ability to exchange assets across chains in a seamless manner.
It gives the projects with tokens either on Ethereum Blockchain or EOS blockchain to easily
swap to Binance Chain (BEP2) to trade their tokens on Binance Dex seamlessly without any
hassles. The tokens can be completely migrated to Binance(BEP2) or can be converted in
some amount and then can reverse swap their tokens to the original blockchain.