Files
gocryptotrader/backtester
cranktakular fd9aaf00a2 Coinbase: Update exchange implementation (#1480)
* Slight enhance of Coinbase tests

Continual enhance of Coinbase tests

The revamp continues

Oh jeez the Orderbook part's unfinished don't look

Coinbase revamp, Orderbook still unfinished

* Coinbase revamp; CreateReport is still WIP

* More coinbase improvements; onto sandbox testing

* Coinbase revamp continues

* Coinbase revamp continues

* Coinbasepro revamp is ceaseless

* Coinbase revamp, starting on advanced trade API

* Coinbase Advanced Trade Starts in Ernest

V3 done, onto V2

Coinbase revamp nears completion

Coinbase revamp nears completion

Test commit should fail

Coinbase revamp nears completion

* Coinbase revamp stage wrapper

* Coinbase wrapper coherence continues

* Coinbase wrapper continues writhing

* Coinbase wrapper & codebase cleanup

* Coinbase updates & wrap progress

* More Coinbase wrapper progress

* Wrapper is wrapped, kinda

* Test & type checking

* Coinbase REST revamp finished

* Post-merge fix

* WS revamp begins

* WS Main Revamp Done?

* CB websocket tidying up

* Coinbase WS wrapperupperer

* Coinbase revamp done??

* Linter progress

* Continued lint cleanup

* Further lint cleanup

* Increased lint coverage

* Does this fix all sloppy reassigns & shadowing?

* Undoing retry policy change

* Documentation regeneration

* Coinbase code improvements

* Providing warning about known issue

* Updating an error to new format

* Making gocritic happy

* Review adherence

* Endpoints moved to V3 & nil pointer fixes

* Removing seemingly superfluous constant

* Glorious improvements

* Removing unused error

* Partial public endpoint addition

* Slight improvements

* Wrapper improvements; still a few errors left in other packages

* A lil Coinbase progress

* Json cleaning

* Lint appeasement

* Config repair

* Config fix (real)

* Little fix

* New public endpoint incorporation

* Additional fixes

* Improvements & Appeasements

* LineSaver

* Additional fixes

* Another fix

* Fixing picked nits

* Quick fixies

* Lil fixes

* Subscriptions: Add List.Enabled

* CoinbasePro: Add subscription templating

* fixup! CoinbasePro: Add subscription templating

* fixup! CoinbasePro: Add subscription templating

* Comment fix

* Subsequent fixes

* Issues hopefully fixed

* Lint fix

* Glorious fixes

* Json formatting

* ShazNits

* (L/N)i(n/)t

* Adding a test

* Tiny test improvement

* Template patch testing

* Fixes

* Further shaznits

* Lint nit

* JWT move and other fixes

* Small nits

* Shaznit, singular

* Post-merge fix

* Post-merge fixes

* Typo fix

* Some glorious nits

* Required changes

* Stop going

* Alias attempt

* Alias fix & test cleanup

* Test fix

* GetDepositAddress logic improvement

* Status update: Fixed

* Lint fix

* Happy birthday to PR 1480

* Cleanups

* Necessary nit corrections

* Fixing sillybug

* As per request

* Programming progress

* Order fixes

* Further fixies

* Test fix

* Pre-merge fixes

* More shaznits

* Context

* Sonic error handling

* Import fix

* Better Sonic error handling

* Perfect Sonic error handling?

* F purge

* Coinbase improvements

* API Update Conformity

* Coinbase continuation

* Coinbase order improvements

* Coinbase order improvements

* CreateOrderConfig improvements

* Managing API updates

* Coinbase API update progression

* jwt rename

* Comment link fix

* Coinbase v2 cleanup

* Post-merge fixes

* Review fixes

* GK's suggestions

* Linter fix

* Minor gbjk fixes

* Nit fixes

* Merge fix

* Lint fixes

* Coinbase rename stage 1

* Coinbase rename stage 2

* Coinbase rename stage 3

* Coinbase rename stage 4

* Coinbase rename final fix

* Coinbase: PoC on converting to request structs

* Applying requested changes

* Many review fixes, handled

* Thrashed by nits

* More minor modifications

* The last nit!?

---------

Co-authored-by: Gareth Kirwan <gbjkirwan@gmail.com>
2025-09-16 13:37:00 +10:00
..

GoCryptoTrader Backtester: Backtester package

Build Status Software License GoDoc Coverage Status Go Report Card

This backtester package is part of the GoCryptoTrader codebase.

This is still in active development

You can track ideas, planned features and what's in progress on our GoCryptoTrader Kanban board.

Join our slack to discuss all things related to GoCryptoTrader! GoCryptoTrader Slack

GoCryptoTrader Backtester

An event-driven backtesting tool to test and iterate trading strategies using historical or custom data.

Features

  • Works with all GoCryptoTrader exchanges that support trade/candle retrieval. See candle readme and trade readme for supported exchanges
  • CSV data import
  • Database data import
  • Proof of concept live data running
  • Shopspring decimal implementation to track stats more accurately
  • Can run strategies against multiple cryptocurrencies
  • Can run strategies that can assess multiple currencies simultaneously to make complex decisions
  • Dollar cost strategy example strategies
  • RSI example strategy
  • MFI example strategy
  • Rules customisation via config .strat files
  • Strategy config builder application
  • Strategy customisation without requiring recompilation. For example, customising RSI high, low and length values via config .strat files.
  • Report generation
  • Portfolio manager to help size orders based on config rules, risk and candle volume
  • Order manager to place orders with customisable slippage estimator
  • Helpful statistics to help determine whether a strategy was effective
  • Compliance manager to keep snapshots of every transaction and their changes at every interval
  • Exchange level funding allows funding to be shared across multiple currency pairs and to allow for complex strategy design
  • Fund transfer. At a strategy level, transfer funds between exchanges to allow for complex strategy design
  • Backtesting support for futures asset types
  • Example cash and carry spot futures strategy
  • Long-running application as a GRPC server
  • Custom strategy plugins
  • Live data source trading. Traders can move their back tested strategies and use them against current live data

Planned Features

We welcome pull requests on any feature for the Backtester! We will be especially appreciative of any contribution towards the following planned features:

Feature Description
Perpetual futures support Accounting for hourly funding rates in user's overall positions allows for much greater strategic depth
Margin borrowing support Allowing strategies to utilise margin borrowing to have larger positions and handling borrow rate payments
Leverage support Leverage is a good way to enhance profit and loss and is important to include in strategies
Live ticker data A potential feature as live trading works off candle data which is only processed at intervals. Adding ticker data as a strategic source allows for faster decision making
Live orderbook data Processing orders based off the latest orderbook data allows for much more accurate order placement and reduces surprise slippage
Enhance config-builder Create an application that can create strategy configs in a more visual manner and execute them via GRPC to allow for faster customisation of strategies
Save Backtester results to database This will allow for easier comparison of results over time
Backtester result comparison report Providing an executive summary of Backtester database results

How does it work?

  • The application will load a .strat config file as specified at runtime
  • The .strat config file will contain
    • Start & end dates
    • The strategy to run
    • The candle interval
    • Where the data is to be sourced (API, CSV, database, live)
    • Whether to use trade or candle data (readme)
    • A nickname for the strategy (to help differentiate between runs/configs using the same strategy)
    • The currency/currencies to use
    • The exchange(s) to run against
    • See readme for a breakdown of all config features
  • The GoCryptoTrader Backtester will retrieve the data specified in the config (readme)
  • The data is converted into candles and each candle is streamed as a data event.
  • The data event is analysed by the strategy which will output a purchasing signal such as BUY, SELL or DONOTHING (readme)
  • The purchase signal is then processed by the portfolio manager (readme) which will size the order (readme) and assess risk (readme) before sending it to the exchange
  • The exchange order event handler will size to the candle data and run a slippage estimator (readme) and place the order (readme)
  • Upon an order being placed, the order is snapshot for analysis in both the statistics package (readme) and the report package (readme)

Cool story, how do I use it?

To run the application using the provided dollar cost average strategy, simply run go run . from gocryptotrader/backtester. An output of the results will be put in the results folder.

How do I create my own config?

There is a config generating helper application under /backtester/config/configbuilder to help you create a .strat file. Read more about it here. There are also a number of tests under /config/config_test.go which generate configs into the examples folder, which if you have code knowledge, can write your own configs programmatically.

How do I create my own strategy?

Creating strategies requires programming skills. Here is a readme on the subject. After reading the readmes, please review the strategies here to gain an understanding on how to write your own.

How does it work technically?

  • The readmes linked in the "How does it work" covers the main parts of the application.
    • If you are still unsure, please raise an issue, ask a question in our Slack or open a pull request
  • Here is an overview workflow

Important notes

  • This application is not considered production ready and you may experience issues
    • If you encounter any issues, you can raise them in our Slack channel or via Github issues
  • Past performance is no guarantee of future results
  • While an experimental feature, it is not recommended to ever use live trading and real orders
  • Past performance is no guarantee of future results

Donations

If this framework helped you in any way, or you would like to support the developers working on it, please donate Bitcoin to:

bc1qk0jareu4jytc0cfrhr5wgshsq8282awpavfahc