Exchange fees on the application.yaml #228

New issue

Closed

opened 2020-10-14 05:24:04 -07:00 by dazito · 1 comment

dazito commented

2020-10-14 05:24:04 -07:00

(Migrated from github.com)

In the configuration yaml file there is the fees keyword to specify the exchange fees. What exactly is the fee expected here? I am asking because most (if not all) exchanges have a different fee if you are a maker or a taker in the market.

How should we specify the maker fee and the taker fee? Is it possible?

In the configuration yaml file there is the `fees` keyword to specify the exchange fees. What exactly is the fee expected here? I am asking because most (if not all) exchanges have a different fee if you are a maker or a taker in the market. How should we specify the maker fee and the taker fee? Is it possible?

scionaltera commented

2020-10-14 13:32:55 -07:00

(Migrated from github.com)

Arbitrader will always place a limit order which most exchanges consider a "maker" fee and charge at a lower rate.

Additionally, Arbitrader will always try to query the exchange's API to retrieve the current fees when it starts up. If it can get the fee directly from the exchange it will override the fees value. To confuse the issue a little further, I have found a couple exchanges such as Gemini that have APIs that return the wrong rate for their fees, so there is a feeOverride that you can set to make it ignore the exchange's API and force it to use your own value.

You can find examples of how to use these fields in application.example.yaml.

The value should be expressed as a decimal. Some examples:

6% would be 0.0006
16% would be 0.0016
60% would be 0.0060

Each exchange configuration has its own fees field, so you can define it independently for each exchange.

Arbitrader will always place a limit order which most exchanges consider a "maker" fee and charge at a lower rate. Additionally, Arbitrader will always try to query the exchange's API to retrieve the current fees when it starts up. If it can get the fee directly from the exchange it will override the `fees` value. To confuse the issue a little further, I have found a couple exchanges such as Gemini that have APIs that return the wrong rate for their fees, so there is a `feeOverride` that you can set to make it ignore the exchange's API and force it to use your own value. You can find examples of how to use these fields in `application.example.yaml`. The value should be expressed as a decimal. Some examples: 6% would be 0.0006 16% would be 0.0016 60% would be 0.0060 Each exchange configuration has its own `fees` field, so you can define it independently for each exchange.

Commenting is not possible because the repository is archived.