Contracts and tools to create a bridge between WAX tokens and an ERC-20 counterpart.
The version numbers are necessary to make all teleports compatible with custom frontends. This project is called version 1 and is a backwards compatible fork of the origin Alien Worlds teleport. The project of SavAct is a fork of version 1 and is called version 2. Each fork brings up a lot of new features and reduces the running costs.
Version 2 is not backwards compatible, but recommended for new projects because it offers the most advantages, is fully tested and already used by real world applications.
There are contracts available for both EOSIO chains and Ethereum, both should be deployed on their respective chains.
After deploying the EOSIO contract call the ini function to initialize it. Each ETH chain must be registered on the EOSIO contract with the addchain function.
Transferring from EOSIO -> ETH requires depositing the tokens to the EOSIO contract with a standard transfer (no memo required),
then teleporting the tokens using the teleport action.
Transferring from ETH -> EOSIO simply requires callint the teleport function on the Ethereum contract.
You can use the SavAct WebApp as frontend by entering your EOSIO contract and network. For direct selection add your settings to the URL https://savact.app/#/trx/teleport?bridge=other.worlds&eosio=WAXð=BSC
The app is only compatible with the EOSIO teleport contract of version 1 and higher. For more information see its README.md
To add your teleport in a select box of the SavAct WebApp, feel free to request the admins of https://t.me/SavActGroup
Oracle accounts must be registered using the regoracle (EOSIO) or regOracle (Ethereum) functions.
Oracles can then call the received function on each contract when they see a transaction on the opposing chain.
- Copy config-example.js to config.js
- Change the configuration settings to match your tokens
- Start the oracle using the following command
CONFIG=./[path/to/config] oracle-eos|eth.js