Decentralized asset exchange built on SOILcoin, forked from EtherEx.
This repository contains the source code that runs the exchange on Ethereum as a set of contracts, along with the UI, tests, tools and documentation.
- Serpent compiler by Vitalik Buterin
- go-ethereum client by Jeffrey Wilcke
- pyethereum Python Ethereum client (tests only)
- PyEPM for deployment
- node and grunt for UI development
Start by cloning this repository.
git clone https://github.com/abvhiael/etherex.git
This will install pyethereum and ethereum-serpent if you don't already have those installed.
pip install -r dev_requirements.txt
py.test -vvrs
Refer to Serpent and pyethereum for their respective usage.
You will need a working node.js setup (instructions) and globally installed grunt-cli (instructions).
cd frontend
npm install
grunt
And open http://localhost:8089/ in your browser.
Requires a local client (Go or C++) with JSONRPC, Serpent and PyEPM
cd contracts
pyepm EtherEx.yaml
***I've found, with SOILcoin, the best method of deploying the contracts is to launch gsoil.exe with the command line, to open an RPC connection, where 127.0.0.1 would be your locally hosted copy of SOIL-ex, or another server address would be a server hosted copy of the SOIL-ex front end.
gsoil --rpc --rpccorsdomain http://127.0.0.1:8089 --unlock 0 console
Deploying the contract .yaml file using pyepm in the code above resulted in a lot of failed compiling. I suggest using the following, replacing your wallet address that is being used to deploy the contracts:
pyepm EtherEx.yaml -a 0x012345
- The API is the format of the data field for the Ethereum transactions.
- Subcurrencies need to support the Subcurrency API.
- You only need an Ethereum client to use the API.
Methods (with serpent type definitions):
[
price:[int256]:int256,
buy:[int256,int256,int256]:int256,
sell:[int256,int256,int256]:int256,
trade:[int256,int256[]]:int256,
cancel:[int256]:int256,
deposit:[int256,int256]:int256,
withdraw:[int256,int256]:int256,
add_market:[int256,int256,int256,int256,int256,int256]:int256,
get_market_id:[int256]:int256,
get_last_market_id:[]:int256,
get_market:[int256]:int256[],
get_trade:[int256]:int256[],
get_trade_ids:[int256]:int256[],
get_sub_balance:[int256,int256]:int256[]
]
price(market_id)
buy(amount, price, market_id)
sell(amount, price, market_id)
trade(max_amount, trade_ids)
deposit(amount, market_id)
withdraw(amount, market_id)
cancel(trade_id)
add_market(currency_name, contract_address, decimal_precision, price_denominator, minimum_total, category)
get_market_id(contract_address)
Market names follow the "/ETH" convention. When registering a new market, submit the currency name as a three or four letter uppercase identifier, ex.: "BOB" for BobCoin.
The subcurrency contract address.
The subcurrency's decimal precision as an integer.
- Denominator for price precision, ex. 10000 (10000 => 1 / 10000 => 0.0001)
When adding a subcurrency, set the minimum trade total high enough to make economic sense. A minimum of 1 SOIL (100000000000000000000 wei) is recommended.
1 = Subcurrencies
2 = Crypto-currencies
3 = Real-world assets
4 = Fiat currencies
SOIL-ex will allows you to categorize your assets into four main categories. Since everything is presently represented as subcurrencies, those categories are simply for convenience, and will be better enabled as we scale further towards full decentralized cryptocurrency exchange ability.
If you have a privtely issued token, DAO issued share, etc, that would go in the regular subcurrency section 1.
For other crypto-currencies like BTC, ETH, or DOGE redeemable through a gateway, add it to 2.
If your token represents a real-world asset or commodity like gold, minerals, etc. add it to 3.
If your token represents a fiat currency redeemable through a gateway, add it to 4.
1 = DEV/SOIL
New market IDs will be created as DAO creators and token administrators add their subcurrency to the exchange.
Subcurrency contracts need to support the Standardized Contract APIs (see current Draft), more specifically the approve, transferFrom and allowance methods for deposits, the transfer method for withdrawals and the balanceOf method for the UI to display the user's balance.
See the example ETX contract for a Serpent implementation, or a Standard Token in Solidity.
After registering the subcurrency using the add_market ABI call, the subcurrency will receive a market_id. You can retrieve the market ID with a call to get_market_id(contract_address).
To support deposits to EtherEx, your subcurrency needs to implement the approve and transferFrom methods. The former allows a one-time transfer from the user's address by the exchange's contract, while the latter is called from the contract to effectively make that transfer when the user calls the exchange's new deposit method. This allows to securely send a subcurrency's tokens to the exchange's contract while updating the user's available balance at the exchange.
If your subcurrency's default method for transferring funds is also named transfer like the standard examples above, with the _to and _value parameters (in that order), then there is nothing else you need to do to support withdrawals from SOIL-ex to a user's address. Otherwise, you'll need to implement that same transfer method with those two parameters, and "translate" that method call to yours, calling your other method with those parameters, in the order they're expected. You may also have to use tx.origin instead of msg.sender in your method as the latter will return your contract's address.
def transfer(_to, _value):
return(self.invertedtransfer(_value, _to))
Subcurrency contracts also need to implement a balanceOf method for the UI to display the user's balance in that contract (also called the subcurrency's wallet).
def balanceOf(_addr):
return(self.balances[_addr].balance)
- Your SOILcoin address is used as your identity
- Solidify btc-swap usage, investigate how to apply to cross chain assets
- Implement SchellingCoin-based pegged commodities
- Implement deeper market analysis tools.
- Graphs, beautiful graphs
- Advanced trading features (stoploss, etc.)
- Wallet design and theming
- Enable category drop downs.
Released under the MIT License, see LICENSE file.