Coinbend is an experimental, high security, decentralized exchange for cryptocurrencies that lets strangers trade coins with each other without the risk of fraud. It works by using a combination of time-based crypto with a bunch of game theory to allow trades to take place with conventional smart contracts.
The exchange was built in response to the numerous hacks that have plagued the Bitcoin world which the software tries to avoid by removing the need for a third-party to be trusted with the user's money. The software is currently in a very experimental state and lacks a proper order book so users must find each other manually to trade but I'm releasing this as version 0.001.
Consider this the first practical P2P exchange for alt-coins. All existing exchanges make unrealistic assumptions about attackers, require the use of collateral as a fail-safe, or strictly depend on third-party trust to exchange currencies (either directly or indirectly as a side-effect of transaction malleability) but Coinbend avoids these problems by using modified micro-payment channels + timechains.
"In crypto with trust."
... or something like that.
Pre-alpha v0.01
Coinbend uses Vagrant to build reproducible development environments. Vagrant is like automation for VirtualBox and means you can have project specific developer environments that you can bring up with a single command (especially useful for Coinbend which has a lot of dependencies that could easily break across environments.)
First, fork the project to your Github and clone it to a new directory.
mkdir vagrant
cd vagrant
git clone [your-forked-copy-of-coinbend]Install the dependencies you need for Vagrant and Virtual box.
sudo apt-get install virtualbox vagrantDownload the virtual machine and setup a Coinbend dev environment:
cd coinbend/vagrant
sudo vagrant upThis command will take a while to complete as it has to download Python3.3 from scratch, compile it, install all the Python packages, download Litecoin + Dogecoin, plus do a lot of other stuff.
You can now make changes to the code with your favourite editor on your main OS and when you need to test the changes you can type sudo vagrant ssh to open a shell prompt to the VM. The VM already has everything needed to run the software from source so it's easy to hack at the code.
When you first login to the custom VM it will start up Litecoin and Dogecoin on the testnet + setup a number of virtual interfaces. Coinbend is currently designed to work dynamically with full node cryptocurrencies so unfortunately you will have to wait for the blockchains to download. On fast Internet that's around 2 hours of waiting but on a slow PC + Internet its incredibly painful: around 1 - 2 days of waiting for the chains to download and validate.
# 1 sep 2015 - blocks you need to DL.
# There will be a better way to develop Coinbend without full chains in the future.
vagrant@precise32:~$ /home/vagrant/coins/litecoin/bin/litecoin-cli getinfo
{
"blocks" : 682511
}
vagrant@precise32:~$ /home/vagrant/coins/dogecoin/bin/dogecoin-cli getinfo
{
"blocks" : 706056
}
After you login a number of virtual interfaces will be created. This allows you to simulate the interactions of nodes on a P2P network via the command line. By default IPs bound to eth1 and eth1:x will be accessible from your main / host OS so accessing the web UI of the software is as easy as visiting the IP in your browser.
To start the software for the first time:
vagrant@precise32:~$ cd /vagrant/coinbend
vagrant@precise32:~$ ifconfig | pcregrep -M "eth1:1[\s\S]*?inet addr"
eth1:1 Link encap:Ethernet HWaddr ...
inet addr:192.168.1.147 Bcast:192.168.255.0 Mask:255.255.255.255
vagrant@precise32:~$ python3.3 -m "coinbend.main" -externalexchange 0 -erateinit BTC_USD_358.03,USD_AUD_1.2116072,LTC_BT0.00996000,DOGE_BTC_0.00000056 -clockskew -1 -interface eth1:1 -uibind 192.168.1.147 -passivebind 192.168.1.147 -directbind 192.168.1.147 -skipbootstrap 1 -localonly 1 -uselocaltime 1
...
Web server started.
Bottle v0.13-dev server starting up (using WSGIRefServer())...
Listening on http://192.168.1.147:7777/And here's how it looks in the browser:
- Alice demo - http://alice.coinbend.com/
- Bob demo - http://bob.coinbend.com/
At this point you want to go to some faucets and send testcoins to your account addresses. Shoot me an email at matthew@roberts.pm if you need some testcoins or mine them yourself with the RPC command:
# Don't run them both at the same time - it will be too slow!
vagrant@precise32:~$ /home/vagrant/coins/litecoin/bin/litecoin-cli setgenerate true
vagrant@precise32:~$ /home/vagrant/coins/dogecoin/bin/dogecoin-cli setgenerate trueOnce you have a positive balance open two shells to your vagrant VM and do the following:
# Shell 1 - Alice
vagrant@precise32:~$ python3.3 -m "coinbend.main" -externalexchange 0 -erateinit BTC_USD_358.03,USD_AUD_1.2116072,LTC_BT0.00996000,DOGE_BTC_0.00000056 -clockskew -1 -interface eth1:1 -uibind 192.168.1.147 -passivebind 192.168.1.147 -directbind 192.168.1.147 -skipbootstrap 1 -localonly 1 -uselocaltime 1 -nodetype passive -trade "buy 200 dogecoin/litecoin @ 0.005"
# Shell 2 - Bob
vagrant@precise32:~$ python3.3 -m "coinbend.main" -externalexchange 0 -erateinit BTC_USD_358.03,USD_AUD_1.2116072,LTC_BT0.00996000,DOGE_BTC_0.00000056 -clockskew -1 -interface eth1:2 -uibind 192.168.1.148 -passivebind 192.168.1.148 -directbind 192.168.1.148 -skipbootstrap 1 -localonly 1 -uselocaltime 1 -nodetype passive -trade "sell 200 dogecoin/litecoin @ 0.005" -addnode passive://192.168.1.147:50500/p2pThese command line arguments tell the software not to calculate the exchange rate; not to detect the clock skew for the system clock; to bind to a specific virtual interface; to skip trying to find other nodes on the P2P network; to use LAN IP addresses for trade messages instead of WAN IPs (because WAN IPs don't work behind the same router); to switch the node type to passive (meaning you can accept inbound connections); to open a new order; and for Bob to connect to Alice.
Note that where an IP address is used as an argument you are expected to substitute it with the corresponding IP address for your interface. So for example: Alice is using eth1:1 and Bob is using eth1:2. Make sure that all the IPs they are using correspond to the right address for that interface by typing ifconfig to get the IP.
- E.g. Alice UI window on http://192.168.1.147:7777
- E.g. Bob UI window on http://192.168.1.148:7777
- Alice: open a new order to buy 200 Dogecoins at 0.001 Litecoins per Dogecoin. Click submit. A confirmation dialogue will pop up.
- Alice: at the bottom of the confirm dialogue click "generate copy of Node ID"
- Alice: cnt + c
- Bob: open a sell order to sell 200 Dogecoins at 0.001 Litecoins per Dogecoin. Click submit. A new confirmation dialogue will pop up.
- Bob: cnt + v into the input box to paste Alice's node ID.
- Bob: click "generate a copy of Node ID"
- Bob: cnt + c
- Alice: cnt + v into the input box to paste Bob's node ID.
- Submit the trade on both windows.
Video guide is here: https://www.youtube.com/watch?v=h7maCX8XKbg
I usually use the command line to test trading but the UI is easier for users obviously so it helps to be able to check this works.
Infrastructure for the project consists of 4 main components:
- Rendezvous server - used by nodes to connect to the p2p network
- Contract server - makes contracts more atomic + fixes a few security edge cases
- UI server - light weight bottle.py web server that hosts the UI
- Coinbend lighttpd - runs basic PHP scripts on www.coinbend.com
Folder structure:
- coinbend - all the main code
- install/www - has all the UI stuff / web modules or what you see on *:7777/satoshi
- server - code that runs on www.coinbend.com
- ~/.Coinbend - data directory on Linux. %appdata%\Coinbend on Windows.
What file are:
- main.py - the entry point to the whole program.
- build_binary.py - used to build platform specifc binaries for the software. Run sudo python3.3 build_binary.py build on the VM.
- net.py - class uses to provide p2p networking
- sock.py - provides a custom socket wrapped. Coinbend uses non-blocking sockets
- exchange_rate.py - gets the exchange rate for currencies from multiple sources. Uses a trimmed average for rates
- address.py - serialises and detribalises addresses between cryptocurrencies
- args.py - command line arguments for the software
- coin_config.py - parses + patches coins config files for RPC connectivity
- coinlib.py - functions for working with raw transactions
- contract_client.py - talking to the contract server so people can't waste each other's time
- contract_server.py - checks contracts and releases info needed to carry out contract
- cryptocurrencies.py - list of cryptocurrencies and associated currency codes
- currency_type.py - custom library for doing floating point operations as integer
- database.py - custom DB wrapper for forcing serializable, ACID transactions
- ecdsa_crypt.py - serializes and deserializes ECDSA pairs making signing simple
- fiatcurrencies.py - list of fiatcurrencies and their codes
- globals.py - list of module wide global variables
- green_address.py - provides a secure clearing house prior to setting up contracts
- hybrid_protocol.py - the networking protocol for the entire project
- hybrid_reply - dynamic replies from the protocol with complex routing behaviour
- ipgetter.py - gets the WAN IP
- json_rpc.py - wrapped for JSON RPC python library that fixes timeout bugs
- lib.py - small functions that dont fit in any specific module
- match_stype.py - handles state transitions for matches
- match_type.py - what a match looks like on the exchange
- microtransfer_contract.py - the magic file implementing Coinbend smart contracts
- nat_pmp.py - NAT hole punching with NAT-PMP
- order_book.py - saves orders (trades submitted to the main network) to a simple replicating DB
- order_type.py - what an order looks like
- parse_config.py - parses the main config file for the software into an immutable state
- password_complexity.py - designed for building secure passwords
- private_key.py - working with wallet-style private keys
- proof_of_work.py - calculating and verifying sha256-style proof-of-work
- rendezvous_client.py - talking to the rendezvous server to find p2p nodes
- rendezvous_server.py - custom server that supports TCP hole punching for NAT traversal + gives clietns fresh nodes to connect to the p2p network
- sys_clock.py - determines how much clock skew you have compared to a global NTP time
- trade_engine.py - handles opening trades and recording them
- trades.py - a collection of the users open trades
- trade_type.py - special type for serializing and deserializing trades. Also supports matching
- tx_monitor.py - event based, multi-currency, transaction monitor
- tx_push.py - push a tx to a p2p network using the raw protocol
- unl.py - universal node locator - used to connect to nodes
- upnp.py - uses UPnP to do NAT traversal
- user.py - creates a new user on Coinbend
- username_complexity.py - ensures usernames are unique and can't be brute forced
- user_web_server.py - the main web app for the UI. Also supports routes and API calls
So then ... there's no real documentation? Unfortunately no. As you can see: there's a lot of modules and a lot of code and I'm still the only developer but its definitely on my todo list.
Papers:
- Coinbend white paper - www.coinbend.com/whitepaper.pdf
- Timechain white paper - www.roberts.pm/timechain
Want to contribute? Great!
Contact me at matthew@roberts.pm if you need any help. Also, I'm still looking for a partner who wants to team up and help me get this to beta.
There's no license yet but all the code will be release under LGPL soon (when I have time.) The UI won't be released under an open source license but it will be free to use and download.
7e7adb106a4d5d82c125a3f2133408feca15454b16b9cabbbf2096c6bc14f89b