Test automated trades on the Mach exchange.
Project description
Cross Chain Trade Test (CCTT)
Test automated trades between multiple chains on Mach.
Overview
Test automated trades on Mach. Specify a start chain and symbol, and a policy determining how the destination token will be chosen (randomize chain and symbol, randomize chain and fix symbol). In each trade, the test wallet's entire balance of the source token will be sold for the destination token, and then the destination token because the new source token for the next trade. This continues until the script is killed by the user.
Usage
-
Install
python -m pip install mach-cctt
-
Usage
cctt --help
-
Example
# The script will create log files and an account data file. Make a working directory for it. mkdir cctt/ && cd cctt/ # Set password to avoid being prompted # export CCTT_PASSWORD="abc" # Backend defaults to production, change if necessary # export MACH_BACKEND_URL="https://cache-half-full-staging.fly.dev" cctt import # Import account cctt decrypt # Show public/private key cctt balances # Show account balances # Trade USDC on random chains, starting from optimism-USDC cctt run --source optimism-USDC --destination-policy fixed:USDC # Trade USDC on only arbitrum and optimism, starting from polygon-USDC cctt run --source polygon-USDC --destination-policy cheap:USDC # Trade between random tokens on random chains, starting from arbitrum-USDT cctt run --source arbitrum-USDT --destination-policy random # If the --source is empty, then an appropriate source with a non-zero balance is chosen for you. cctt run --source --destination-policy random
Notes:
- You need to have a gas on every chain, or a gas of exactly 0 on chains that you do not wish the testing script to trade on, which will cause those chains to be disabled.
- The
--source
token should be one that you hold a non-zero balance of in your wallet. If you set it to empty, it will be automatically chosen as any token with a non-zero balance in the wallet. - There is a known issue with trades filling for a single tick less than the order was placed at. As a preventative measure, any token balance of 1 tick in the wallet is treated as an empty balance.
Log Files
There are 4 log files created by the application:
app.log
- everythingdelayed_transactions.log
- the source funds where not withdrawn in timestuck_transactions.log
- the source funds were withdrawn but the destination funds were not received in timeimproper_fill.log
- the trade filled on the source chain for 1 tick less than the order was placed for. This has been observed to happen primarily to USDM (on multiple chains)
Account File
A plaintext JSON file storing your account encrypted with your password will be created once you first generate or import a wallet. By default this file is called account.json
but you can give a path to your own file via the --file PATH
flag. This file is required to be present for any operation other than importing or generating a new wallet.
Development
Requirements
You need the just
command runner and either Python 3.12.5+ with virtualenv
, or pyenv
.
Setup
-
Clone the repository
git clone https://github.com/tristeroresearch/cross-chain-trade-test.git cd cross-chain-trade-test
-
Create and activate a virtual environment
Using
venv
:python -m venv .venv source .venv/bin/activate
Or using
pyenv
:pyenv virtualenv 3.12.5 cctt pyenv activate
-
Install dependencies
just init
-
View available recipes
just -l
Note that there are recipes that allow you to run the application in-source without needed to build and package to PyPI first:
just account_file=account.json import <private key> # Import a new account just decrypt # Show public and private key just balances # List balances of account just source=arbitrum-USDC policy=random run # Run the trade tester, starting from arbitrum-USDC and trading to random tokens just wallet=<public key> withdraw # Withdraw funds from the stored account to the given wallet
-
Building
just build
Packaging
Make sure to bump the version number in pyproject.toml
.
To upload to the test PyPI:
just upload-test
To upload to the main PyPI:
just upload
TODO
- Move k8s/image building stuff to GCP (ran into issues adding this repo to GCP for some reason)
- Unit tests
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file mach_cctt-0.0.116.tar.gz
.
File metadata
- Download URL: mach_cctt-0.0.116.tar.gz
- Upload date:
- Size: 37.4 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.13.0
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 7609684ee6e980181d442761ce59a503a53fc9dc59cb360d8e67c96494e95ec7 |
|
MD5 | 1155f7e97d92e3f623875b554f657bd6 |
|
BLAKE2b-256 | 7b3a834081fa39e3d85d91ef7cfae386c10503ae6ff441ef369081902cf7d1f9 |
File details
Details for the file mach_cctt-0.0.116-py3-none-any.whl
.
File metadata
- Download URL: mach_cctt-0.0.116-py3-none-any.whl
- Upload date:
- Size: 48.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.13.0
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | a41e2936a98a0830fd210c960877d91740350344408499b151d69c31b04fda26 |
|
MD5 | 53c2f60931ecf6beb5ec222270965291 |
|
BLAKE2b-256 | 363df2a705a5148b7a2d938e214eaab1c4b9525b54baf3cedf3b1540e0846c34 |