ArgoX Protocol is a decentralized exchange based on the Limit Order Book. The combination of the Lightning network (State channel) and Batching mechanism helps increase the speed and throughput and reduce the gas usage of the exchange. This project has not been published yet.
This repository is a Go implementation of the ArgoX Protocol. We have kept the system the same as the protocol but have made some simplifications to make it easier to implement.
We use Perun - a state channel framework in Ethereum- as our state channel for communication between a user and a matcher. For more details, check this repo on GitHub: github.com/hyperledger-labs/go-perun
This diagram illustrates the relationships between the key entities in the ArgoX Protocol: Matcher
(for pre-batch order matching), Super Matcher (for managing and synchronizing batches), Searcher (for off-chain batch matching), and Reporter (for
monitoring on-chain batch execution)
- Access to
datafolder - Run the script with
./run.sh - Waiting for the results
ganache -a 200 -m '' -e 99999999999 --chain.chainId <CHAIN ID> --p <PORT>
Example, ganache -a 200 -m '' -e 99999999999 --chain.chainId 1337 --p 8545>
go run . <PORT> <CHAIN ID> <NUMBER OF MATCHERS> <SEND TO> run <FILE TO LOAD ORDERS> <FOLDER TO SAVE RESULTS>
with,
<NUMBER OF MATCHERS>is the total number of matchers in the protocol<SEND TO>is the number of matchers to which the user must send an order each time<FILE TO LOAD ORDERS>is a path to an orders file that you want to run in the protocol<FOLDER TO SAVE RESULTS>is a path to a directory, which you want to save the protocol's results (price curves, gas used, run time, etc.)
Example, go run . 8545 1337 5 1 run ./data/real_orders/real_orders_100.json ./data/results/priceCurve_1_5
- Don't forget to restart your ganache before each run
- With each ganache blockchain, you can only run one program. So if you want to run multiple instances of the protocol at a time, you should start multiple ganache blockchains using different ports and chain IDs