chore(deps-dev): bump ruff from 0.15.12 to 0.15.13

Bumps [ruff](https://github.com/astral-sh/ruff) from 0.15.12 to 0.15.13. - [Release notes](https://github.com/astral-sh/ruff/releases) - [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md) - [Commits](https://github.com/astral-sh/ruff/compare/0.15.12...0.15.13) --- updated-dependencies: - dependency-name: ruff dependency-version: 0.15.13 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Merge pull request #13180 from freqtrade/dependabot/pip/develop/mypy-2.1.0
2026-05-25 07:46:19 +00:00 · 2026-05-25 09:40:04 +02:00 · 2026-05-25 08:42:59 +02:00 · 2026-05-25 06:38:34 +00:00 · 2026-05-25 08:38:06 +02:00 · 2026-05-25 08:24:23 +02:00
431 changed files with 85480 additions and 48649 deletions
@@ -14,10 +14,11 @@ MANIFEST.in
 README.md
 freqtrade.service
 freqtrade.egg-info
+.venv/

 config.json*
 *.sqlite
-user_data
+user_data/
 *.log

 .vscode
@@ -1,5 +1,10 @@
 <!-- Thank you for sending your pull request. But first, have you included
 unit tests, and is your code PEP8 conformant? [More details](https://github.com/freqtrade/freqtrade/blob/develop/CONTRIBUTING.md)
+
+Did you use AI to create your changes?
+If so, please state it clearly in the PR description (failing to do so may result in your PR being closed).
+
+Also, please do a self review of the changes made before submitting the PR to make sure only relevant changes are included.
 -->
 ## Summary

@@ -0,0 +1,93 @@
+name: 'docker-tags'
+description: 'Set Docker default Tag environment variables'
+# inputs:
+outputs:
+  BRANCH_NAME:
+    description: 'The branch name'
+    value: ${{ steps.tags.outputs.BRANCH_NAME }}
+  TAG:
+    description: 'The Docker tag'
+    value: ${{ steps.tags.outputs.TAG }}
+  TAG_PLOT:
+    description: 'The Docker tag for the plot'
+    value: ${{ steps.tags.outputs.TAG_PLOT }}
+  TAG_FREQAI:
+    description: 'The Docker tag for the freqai'
+    value: ${{ steps.tags.outputs.TAG_FREQAI }}
+  TAG_FREQAI_RL:
+    description: 'The Docker tag for the freqai_rl'
+    value: ${{ steps.tags.outputs.TAG_FREQAI_RL }}
+  TAG_FREQAI_TORCH:
+    description: 'The Docker tag for the freqai_torch'
+    value: ${{ steps.tags.outputs.TAG_FREQAI_TORCH }}
+  TAG_ARM:
+    description: 'The Docker tag for the arm'
+    value: ${{ steps.tags.outputs.TAG_ARM }}
+  TAG_PLOT_ARM:
+    description: 'The Docker tag for the plot arm'
+    value: ${{ steps.tags.outputs.TAG_PLOT_ARM }}
+  TAG_FREQAI_ARM:
+    description: 'The Docker tag for the freqai arm'
+    value: ${{ steps.tags.outputs.TAG_FREQAI_ARM }}
+  TAG_FREQAI_RL_ARM:
+    description: 'The Docker tag for the freqai_rl arm'
+    value: ${{ steps.tags.outputs.TAG_FREQAI_RL_ARM }}
+  TAG_PI:
+    description: 'The Docker tag for the pi'
+    value: ${{ steps.tags.outputs.TAG_PI }}
+  CACHE_TAG_PI:
+    description: 'The Docker cache tag for the pi'
+    value: ${{ steps.tags.outputs.CACHE_TAG_PI }}
+runs:
+  using: "composite"
+  steps:
+    - name: Extract branch name
+      shell: bash
+      id: tags
+      env:
+        BRANCH_NAME_INPUT: ${{ github.event.inputs.branch_name }}
+        EVENT_NAME: ${{ github.event_name }}
+      run: |
+        if [ "${EVENT_NAME}" = "workflow_dispatch" ]; then
+          BRANCH_NAME="${BRANCH_NAME_INPUT}"
+        else
+          BRANCH_NAME="${GITHUB_REF##*/}"
+        fi
+
+        # Replace / with _ to create a valid tag
+        TAG=$(echo "${BRANCH_NAME}" | sed -e "s/\//_/g")
+        TAG_PLOT=${TAG}_plot
+        TAG_FREQAI=${TAG}_freqai
+        TAG_FREQAI_RL=${TAG_FREQAI}rl
+        TAG_FREQAI_TORCH=${TAG_FREQAI}torch
+
+        TAG_ARM=${TAG}_arm
+        TAG_PLOT_ARM=${TAG_PLOT}_arm
+        TAG_FREQAI_ARM=${TAG_FREQAI}_arm
+        TAG_FREQAI_RL_ARM=${TAG_FREQAI_RL}_arm
+
+        TAG_PI="${TAG}_pi"
+
+        CACHE_TAG_PI=${CACHE_IMAGE}:${TAG_PI}_cache
+
+        echo "BRANCH_NAME=${BRANCH_NAME}" >> "$GITHUB_OUTPUT"
+        echo "TAG=${TAG}" >> "$GITHUB_OUTPUT"
+        echo "TAG_PLOT=${TAG_PLOT}" >> "$GITHUB_OUTPUT"
+        echo "TAG_FREQAI=${TAG_FREQAI}" >> "$GITHUB_OUTPUT"
+        echo "TAG_FREQAI_RL=${TAG_FREQAI_RL}" >> "$GITHUB_OUTPUT"
+        echo "TAG_FREQAI_TORCH=${TAG_FREQAI_TORCH}" >> "$GITHUB_OUTPUT"
+        echo "TAG_ARM=${TAG_ARM}" >> "$GITHUB_OUTPUT"
+        echo "TAG_PLOT_ARM=${TAG_PLOT_ARM}" >> "$GITHUB_OUTPUT"
+        echo "TAG_FREQAI_ARM=${TAG_FREQAI_ARM}" >> "$GITHUB_OUTPUT"
+        echo "TAG_FREQAI_RL_ARM=${TAG_FREQAI_RL_ARM}" >> "$GITHUB_OUTPUT"
+        echo "TAG_PI=${TAG_PI}" >> "$GITHUB_OUTPUT"
+
+        echo "CACHE_TAG_PI=${CACHE_TAG_PI}" >> "$GITHUB_OUTPUT"
+
+        cat "$GITHUB_OUTPUT"
+
+    - name: Save commit SHA to file
+      shell: bash
+      # Add commit to docker container
+      run: |
+        echo "${GITHUB_SHA}" > freqtrade_commit
@@ -1,6 +1,10 @@
 version: 2
 updates:
- package-ecosystem: docker
+- package-ecosystem: docker  # zizmor: ignore[dependabot-cooldown] Docker does not support cooldowns at the moment.
+  # Docker does not support cooldowns at the moment.
+  # https://github.com/dependabot/dependabot-core/issues/14044
+  # cooldown:
+  #   default-days: 7
  directories:
    - "/"
    - "/docker"
@@ -11,12 +15,24 @@ updates:
    update-types: ["version-update:semver-major"]
  open-pull-requests-limit: 10

+- package-ecosystem: devcontainers
+  directory: "/"
+  cooldown:
+    default-days: 7
+  schedule:
+    interval: daily
+  open-pull-requests-limit: 10
+
 - package-ecosystem: pip
  directory: "/"
+  cooldown:
+    default-days: 7
+    exclude:
+      - ccxt
  schedule:
-    interval: weekly
-    time: "03:00"
-    timezone: "Etc/UTC"
+    interval: "cron"
+    # Monday at 03:00
+    cronjob: "0 3 * * 1"
  open-pull-requests-limit: 15
  target-branch: develop
  groups:
@@ -29,10 +45,29 @@ updates:
    mkdocs:
      patterns:
        - "mkdocs*"
-
+    scipy:
+      patterns:
+        - "scipy"
+        - "scipy-stubs"
+    gymnasium:
+      patterns:
+        - "gymnasium"
+        - "stable-baselines3"
+        - "sb3-contrib"
 - package-ecosystem: "github-actions"
  directory: "/"
+  cooldown:
+    default-days: 7
  schedule:
-    interval: "weekly"
+    interval: "cron"
+    # Monday at 03:00
+    cronjob: "0 3 * * 1"
  open-pull-requests-limit: 10
  target-branch: develop
+  groups:
+    actions:
+      patterns:
+        - "actions/*"
+    docker:
+      patterns:
+        - "docker/*"
@@ -2,29 +2,37 @@ name: Binance Leverage tiers update

 on:
  schedule:
-    - cron: "0 3 * * 4"
+    - cron: "25 2 * * 4"
  # on demand
  workflow_dispatch:

+concurrency:
+  group: ${{ github.workflow }}
+  cancel-in-progress: true
+
 permissions:
  contents: read

 jobs:
  auto-update:
+    name: "Auto Update Binance Leverage Tiers"
    runs-on: ubuntu-latest
    environment:
      name: develop
    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

-    - uses: actions/setup-python@v5
+    - name: Install uv and Python 🐍
+      uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
      with:
-        python-version: "3.12"
+        activate-environment: true
+        enable-cache: false
+        python-version: "3.14"

    - name: Install ccxt
-      run: pip install ccxt
+      run: uv pip install $(grep -E "^ccxt==" requirements.txt) $(grep -E "^orjson==" requirements.txt)

    - name: Run leverage tier update
      env:
@@ -34,7 +42,7 @@ jobs:
      run: python build_helpers/binance_update_lev_tiers.py


-    - uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
+    - uses: peter-evans/create-pull-request@5f6978faf089d4d20b00c7766989d076bb2fc7f1 # v8.1.1
      with:
        token: ${{ secrets.REPO_SCOPED_TOKEN }}
        add-paths: freqtrade/exchange/binance_leverage_tiers.json
@@ -43,7 +51,7 @@ jobs:
          Dependencies
        branch: update/binance-leverage-tiers
        title: Update Binance Leverage Tiers
-        commit-message: "chore: update pre-commit hooks"
+        commit-message: "chore: update binance leverage tiers"
        committer: Freqtrade Bot <154552126+freqtrade-bot@users.noreply.github.com>
        author: Freqtrade Bot <154552126+freqtrade-bot@users.noreply.github.com>
        body: Update binance leverage tiers.
@@ -16,55 +16,40 @@ on:
 concurrency:
  group: "${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}"
  cancel-in-progress: true
-permissions:
-  repository-projects: read
-jobs:
-  build-linux:
+permissions: {}

+jobs:
+  tests:
+    name: "Tests and Linting"
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
-        os: [ "ubuntu-22.04", "ubuntu-24.04" ]
-        python-version: ["3.10", "3.11", "3.12"]
+        os: [ "ubuntu-22.04", "ubuntu-24.04", "macos-14", "macos-15" , "windows-2022", "windows-2025" ]
+        python-version: ["3.11", "3.12", "3.13", "3.14"]

    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        python-version: ${{ matrix.python-version }}
-
-    - name: Install uv
-      uses: astral-sh/setup-uv@f0ec1fc3b38f5e7cd731bb6ce540c5af426746bb # v6.1.0
+    - name: Install uv and Python 🐍
+      uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
      with:
        activate-environment: true
        enable-cache: true
        python-version: ${{ matrix.python-version }}
        cache-dependency-glob: "requirements**.txt"
        cache-suffix: "${{ matrix.python-version }}"
-        prune-cache: false

-    - name: Cache_dependencies
-      uses: actions/cache@v4
-      id: cache
-      with:
-        path: ~/dependencies/
-        key: ${{ runner.os }}-dependencies
-
-    - name: TA binary *nix
-      if: steps.cache.outputs.cache-hit != 'true'
+    - name: Installation - macOS (Brew)
+      if: ${{ runner.os == 'macOS' }}
      run: |
-        cd build_helpers && ./install_ta-lib.sh ${HOME}/dependencies/; cd ..
+        # brew update
+        # TODO: Should be the brew upgrade
+        brew install libomp

-    - name: Installation - *nix
+    - name: Installation (python)
      run: |
-        uv pip install --upgrade wheel
-        export LD_LIBRARY_PATH=${HOME}/dependencies/lib:$LD_LIBRARY_PATH
-        export TA_LIBRARY_PATH=${HOME}/dependencies/lib
-        export TA_INCLUDE_PATH=${HOME}/dependencies/include
        uv pip install -r requirements-dev.txt
        uv pip install -e ft_client/
        uv pip install -e .
@@ -76,33 +61,38 @@ jobs:
    - name: Tests
      if: (!(runner.os == 'Linux' && matrix.python-version == '3.12' && matrix.os == 'ubuntu-24.04'))
      run: |
-        pytest --random-order
+        pytest --random-order --durations 20 -n auto

    - name: Tests with Coveralls
      if: (runner.os == 'Linux' && matrix.python-version == '3.12' && matrix.os == 'ubuntu-24.04')
      run: |
        pytest --random-order --cov=freqtrade --cov=freqtrade_client --cov-config=.coveragerc

-    - name: Coveralls
+    - uses: codecov/codecov-action@e79a6962e0d4c0c17b229090214935d2e33f8354 # v6.0.1
+      if: (runner.os == 'Linux' && matrix.python-version == '3.12' && matrix.os == 'ubuntu-24.04')
+      with:
+        fail_ci_if_error: true
+        token: ${{ secrets.CODECOV_TOKEN }}  # zizmor: ignore[secrets-outside-env] Intentionally not using environment variable.
+
+    - name: Cleanup codecov dirty state files
      if: (runner.os == 'Linux' && matrix.python-version == '3.12' && matrix.os == 'ubuntu-24.04')
-      env:
-        # Coveralls token. Not used as secret due to github not providing secrets to forked repositories
-        COVERALLS_REPO_TOKEN: 6D1m0xupS3FgutfuGao8keFf9Hc0FpIXu
      run: |
-        # Allow failure for coveralls
-        coveralls || true
+        # See https://github.com/codecov/codecov-action/issues/1851
+        rm -rf codecov codecov.SHA256SUM codecov.SHA256SUM.sig

    - name: Run json schema extract
-      # This should be kept before the repository check to ensure that the schema is up-to-date
+      # This must be kept before the repository check to ensure that the schema is up-to-date
      run: |
        python build_helpers/extract_config_json_schema.py

    - name: Run command docs partials extract
-      # This should be kept before the repository check to ensure that the docs are up-to-date
+      # This must be kept before the repository check to ensure that the docs are up-to-date
+      if: ${{ (matrix.python-version == '3.13') }}
      run: |
        python build_helpers/create_command_partials.py

-    - name: Check for repository changes
+    - name: Check for repository changes - *nix
+      if: ${{ (runner.os != 'Windows') }}
      run: |
        if [ -n "$(git status --porcelain)" ]; then
          echo "Repository is dirty, changes detected:"
@@ -113,212 +103,8 @@ jobs:
          echo "Repository is clean, no changes detected."
        fi

-    - name: Backtesting (multi)
-      run: |
-        cp tests/testdata/config.tests.json config.json
-        freqtrade create-userdir --userdir user_data
-        freqtrade new-strategy -s AwesomeStrategy
-        freqtrade new-strategy -s AwesomeStrategyMin --template minimal
-        freqtrade backtesting --datadir tests/testdata --strategy-list AwesomeStrategy AwesomeStrategyMin -i 5m
-
-    - name: Hyperopt
-      run: |
-        cp tests/testdata/config.tests.json config.json
-        freqtrade create-userdir --userdir user_data
-        freqtrade hyperopt --datadir tests/testdata -e 6 --strategy SampleStrategy --hyperopt-loss SharpeHyperOptLossDaily --print-all
-
-    - name: Sort imports (isort)
-      run: |
-        isort --check .
-
-    - name: Run Ruff
-      run: |
-        ruff check --output-format=github
-
-    - name: Run Ruff format check
-      run: |
-        ruff format --check
-
-    - name: Mypy
-      if: matrix.os == 'ubuntu-24.04'
-      run: |
-        mypy freqtrade scripts tests
-
-    - name: Discord notification
-      uses: rjstone/discord-webhook-notify@1399c1b2d57cc05894d506d2cfdc33c5f012b993 #v1.1.1
-      if: failure() && ( github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false)
-      with:
-          severity: error
-          details: Freqtrade CI failed on ${{ matrix.os }}
-          webhookUrl: ${{ secrets.DISCORD_WEBHOOK }}
-
-  build-macos:
-    runs-on: ${{ matrix.os }}
-    strategy:
-      matrix:
-        os: [ "macos-13", "macos-14", "macos-15" ]
-        python-version: ["3.10", "3.11", "3.12"]
-
-    steps:
-    - uses: actions/checkout@v4
-      with:
-        persist-credentials: false
-
-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        python-version: ${{ matrix.python-version }}
-        check-latest: true
-
-    - name: Install uv
-      uses: astral-sh/setup-uv@f0ec1fc3b38f5e7cd731bb6ce540c5af426746bb # v6.1.0
-      with:
-        activate-environment: true
-        enable-cache: true
-        python-version: ${{ matrix.python-version }}
-        cache-dependency-glob: "requirements**.txt"
-        cache-suffix: "${{ matrix.python-version }}"
-        prune-cache: false
-
-    - name: Cache_dependencies
-      uses: actions/cache@v4
-      id: cache
-      with:
-        path: ~/dependencies/
-        key: ${{ matrix.os }}-dependencies
-
-    - name: TA binary *nix
-      if: steps.cache.outputs.cache-hit != 'true'
-      run: |
-        cd build_helpers && ./install_ta-lib.sh ${HOME}/dependencies/; cd ..
-
-    - name: Installation - macOS (Brew)
-      run: |
-        # brew update
-        # TODO: Should be the brew upgrade
-        # homebrew fails to update python due to unlinking failures
-        # https://github.com/actions/runner-images/issues/6817
-        rm /usr/local/bin/2to3 || true
-        rm /usr/local/bin/2to3-3.11 || true
-        rm /usr/local/bin/2to3-3.12 || true
-        rm /usr/local/bin/idle3 || true
-        rm /usr/local/bin/idle3.11 || true
-        rm /usr/local/bin/idle3.12 || true
-        rm /usr/local/bin/pydoc3 || true
-        rm /usr/local/bin/pydoc3.11 || true
-        rm /usr/local/bin/pydoc3.12 || true
-        rm /usr/local/bin/python3 || true
-        rm /usr/local/bin/python3.11 || true
-        rm /usr/local/bin/python3.12 || true
-        rm /usr/local/bin/python3-config || true
-        rm /usr/local/bin/python3.11-config || true
-        rm /usr/local/bin/python3.12-config || true
-
-        brew install libomp
-
-    - name: Installation (python)
-      run: |
-        uv pip install wheel
-        export LD_LIBRARY_PATH=${HOME}/dependencies/lib:$LD_LIBRARY_PATH
-        export TA_LIBRARY_PATH=${HOME}/dependencies/lib
-        export TA_INCLUDE_PATH=${HOME}/dependencies/include
-        uv pip install -r requirements-dev.txt
-        uv pip install -e ft_client/
-        uv pip install -e .
-
-    - name: Tests
-      run: |
-        pytest --random-order
-
-    - name: Check for repository changes
-      run: |
-        if [ -n "$(git status --porcelain)" ]; then
-          echo "Repository is dirty, changes detected:"
-          git status
-          git diff
-          exit 1
-        else
-          echo "Repository is clean, no changes detected."
-        fi
-
-    - name: Backtesting
-      run: |
-        cp tests/testdata/config.tests.json config.json
-        freqtrade create-userdir --userdir user_data
-        freqtrade new-strategy -s AwesomeStrategyAdv --template advanced
-        freqtrade backtesting --datadir tests/testdata --strategy AwesomeStrategyAdv
-
-    - name: Hyperopt
-      run: |
-        cp tests/testdata/config.tests.json config.json
-        freqtrade create-userdir --userdir user_data
-        freqtrade hyperopt --datadir tests/testdata -e 5 --strategy SampleStrategy --hyperopt-loss SharpeHyperOptLossDaily --print-all
-
-    - name: Sort imports (isort)
-      run: |
-        isort --check .
-
-    - name: Run Ruff
-      run: |
-        ruff check --output-format=github
-
-    - name: Run Ruff format check
-      run: |
-        ruff format --check
-
-    - name: Mypy
-      if: matrix.os == 'macos-15'
-      run: |
-        mypy freqtrade scripts
-
-    - name: Discord notification
-      uses: rjstone/discord-webhook-notify@1399c1b2d57cc05894d506d2cfdc33c5f012b993 #v1.1.1
-      if: failure() && ( github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false)
-      with:
-          severity: info
-          details: Test Succeeded!
-          webhookUrl: ${{ secrets.DISCORD_WEBHOOK }}
-
-  build-windows:
-
-    runs-on: ${{ matrix.os }}
-    strategy:
-      matrix:
-        os: [ windows-latest ]
-        python-version: ["3.10", "3.11", "3.12"]
-
-    steps:
-    - uses: actions/checkout@v4
-      with:
-        persist-credentials: false
-
-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        python-version: ${{ matrix.python-version }}
-
-    - name: Install uv
-      uses: astral-sh/setup-uv@f0ec1fc3b38f5e7cd731bb6ce540c5af426746bb # v6.1.0
-      with:
-        activate-environment: true
-        enable-cache: true
-        python-version: ${{ matrix.python-version }}
-        cache-dependency-glob: "requirements**.txt"
-        cache-suffix: "${{ matrix.python-version }}"
-        prune-cache: false
-
-    - name: Installation
-      run: |
-        function uvpipFunction { uv pip $args }
-        Set-Alias -name pip -value uvpipFunction
-
-        ./build_helpers/install_windows.ps1
-
-    - name: Tests
-      run: |
-        pytest --random-order --durations 20 -n auto
-
-    - name: Check for repository changes
+    - name: Check for repository changes - Windows
+      if: ${{ runner.os == 'Windows' }}
      run: |
        if (git status --porcelain) {
          Write-Host "Repository is dirty, changes detected:"
@@ -330,17 +116,20 @@ jobs:
          Write-Host "Repository is clean, no changes detected."
        }

-    - name: Backtesting
+    - name: Backtesting (multi)
      run: |
-        cp tests/testdata/config.tests.json config.json
        freqtrade create-userdir --userdir user_data
-        freqtrade backtesting --datadir tests/testdata --strategy SampleStrategy
+        cp tests/testdata/config.tests.json user_data/config.json
+        freqtrade new-strategy -s AwesomeStrategy
+        freqtrade new-strategy -s AwesomeStrategyMin --template minimal
+        freqtrade new-strategy -s AwesomeStrategyAdv --template advanced
+        freqtrade backtesting --datadir tests/testdata --strategy-list AwesomeStrategy AwesomeStrategyMin AwesomeStrategyAdv -i 5m

    - name: Hyperopt
      run: |
        cp tests/testdata/config.tests.json config.json
        freqtrade create-userdir --userdir user_data
-        freqtrade hyperopt --datadir tests/testdata -e 5 --strategy SampleStrategy --hyperopt-loss SharpeHyperOptLossDaily --print-all
+        freqtrade hyperopt --datadir tests/testdata -e 6 --strategy SampleStrategy --hyperopt-loss SharpeHyperOptLossDaily --print-all

    - name: Run Ruff
      run: |
@@ -351,61 +140,72 @@ jobs:
        ruff format --check

    - name: Mypy
+      if: ${{ matrix.os == 'ubuntu-24.04' || matrix.os == 'macos-15' }}
      run: |
        mypy freqtrade scripts tests

    - name: Run Pester tests (PowerShell)
+      if: ${{ runner.os == 'Windows' }}
+      shell: powershell
      run: |
        $PSVersionTable
-        Set-PSRepository psgallery -InstallationPolicy trusted
-        Install-Module -Name Pester -RequiredVersion 5.3.1 -Confirm:$false -Force -SkipPublisherCheck
+        Get-PSRepository | Format-List *
+        if (-not (Get-PSRepository -Name PSGallery -ErrorAction SilentlyContinue)) {
+          Register-PSRepository -Default
+        }
+        Set-PSRepository PSGallery -InstallationPolicy Trusted
+        Install-Module -Name Pester -RequiredVersion 5.7.1 -Confirm:$false -Force -SkipPublisherCheck
        $Error.clear()
        Invoke-Pester -Path "tests" -CI
        if ($Error.Length -gt 0) {exit 1}

-      shell: powershell
-
    - name: Discord notification
-      uses: rjstone/discord-webhook-notify@1399c1b2d57cc05894d506d2cfdc33c5f012b993 #v1.1.1
-      if: failure() && ( github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false)
+      uses: sarisia/actions-status-discord@eb045afee445dc055c18d3d90bd0f244fd062708 # v1.16.0
+      if: ${{ failure() && ( github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false) }}
      with:
-          severity: error
-          details: Test Failed
-          webhookUrl: ${{ secrets.DISCORD_WEBHOOK }}
+          color: '#FF0000' # red
+          title: Freqtrade CI failed on ${{ matrix.os }} with Python ${{ matrix.python-version }}!
+          webhook: ${{ secrets.DISCORD_WEBHOOK }}  # zizmor: ignore[secrets-outside-env] Intentionally not using environment variable.

  mypy-version-check:
-    runs-on: ubuntu-22.04
+    name: "Mypy Version Check"
+    runs-on: ubuntu-24.04
    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

-    - name: Set up Python
-      uses: actions/setup-python@v5
+    - name: Install uv and Python 🐍
+      uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
      with:
-        python-version: "3.12"
+        activate-environment: true
+        python-version: "3.13"

    - name: pre-commit dependencies
      run: |
-        pip install pyaml
+        uv pip install $(grep -E "^pyyaml==" requirements-dev.txt)
        python build_helpers/pre_commit_update.py

  pre-commit:
+    name: "Pre-commit checks"
    runs-on: ubuntu-22.04
    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

-    - uses: actions/setup-python@v5
+    - name: Set up Python 🐍
+      uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6.2.0
      with:
-        python-version: "3.12"
+        python-version: "3.13"
+
    - uses: pre-commit/action@2c7b3805fd2a0fd8c1884dcaebf91fc102a13ecd # v3.0.1

  docs-check:
+    name: "Documentation build"
    runs-on: ubuntu-22.04
    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

@@ -413,134 +213,118 @@ jobs:
      run: |
        ./tests/test_docs.sh

-    - name: Set up Python
-      uses: actions/setup-python@v5
+    - name: Install uv and Python 🐍
+      uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
      with:
-        python-version: "3.12"
+        activate-environment: true
+        python-version: "3.13"

    - name: Documentation build
      run: |
-        pip install -r docs/requirements-docs.txt
+        uv pip install -r docs/requirements-docs.txt
        mkdocs build

    - name: Discord notification
-      uses: rjstone/discord-webhook-notify@1399c1b2d57cc05894d506d2cfdc33c5f012b993 #v1.1.1
+      uses: sarisia/actions-status-discord@eb045afee445dc055c18d3d90bd0f244fd062708 # v1.16.0
      if: failure() && ( github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false)
      with:
-          severity: error
-          details: Freqtrade doc test failed!
-          webhookUrl: ${{ secrets.DISCORD_WEBHOOK }}
+          color: '#FF0000' # red
+          title: Freqtrade doc test failed!
+          webhook: ${{ secrets.DISCORD_WEBHOOK }}  # zizmor: ignore[secrets-outside-env] Intentionally not using environment variable.


  build-linux-online:
    # Run pytest with "live" checks
+    name: "Online / live tests"
    runs-on: ubuntu-24.04
+    strategy:
+      matrix:
+        python-version: ["3.12"]
    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        python-version: "3.12"
-
-    - name: Install uv
-      uses: astral-sh/setup-uv@f0ec1fc3b38f5e7cd731bb6ce540c5af426746bb # v6.1.0
+    - name: Install uv and Python 🐍
+      uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
      with:
        activate-environment: true
        enable-cache: true
-        python-version: "3.12"
+        python-version: "${{ matrix.python-version }}"
        cache-dependency-glob: "requirements**.txt"
        cache-suffix: "3.12"
-        prune-cache: false
-
-    - name: Cache_dependencies
-      uses: actions/cache@v4
-      id: cache
-      with:
-        path: ~/dependencies/
-        key: ${{ runner.os }}-dependencies
-
-
-    - name: TA binary *nix
-      if: steps.cache.outputs.cache-hit != 'true'
-      run: |
-        cd build_helpers && ./install_ta-lib.sh ${HOME}/dependencies/; cd ..

    - name: Installation - *nix
      run: |
-        uv pip install --upgrade wheel
-        export LD_LIBRARY_PATH=${HOME}/dependencies/lib:$LD_LIBRARY_PATH
-        export TA_LIBRARY_PATH=${HOME}/dependencies/lib
-        export TA_INCLUDE_PATH=${HOME}/dependencies/include
        uv pip install -r requirements-dev.txt
        uv pip install -e ft_client/
        uv pip install -e .

    - name: Tests incl. ccxt compatibility tests
      env:
-        CI_WEB_PROXY: http://152.67.78.211:13128
+        CI_WEB_PROXY: http://152.67.66.8:13128
      run: |
        pytest --random-order --longrun --durations 20 -n auto


  # Notify only once - when CI completes (and after deploy) in case it's successful
  notify-complete:
+    name: "Notify CI Completion"
    needs: [
-      build-linux,
-      build-macos,
-      build-windows,
-      docs-check,
-      mypy-version-check,
-      pre-commit,
+      build,
      build-linux-online
    ]
    runs-on: ubuntu-22.04
    # Discord notification can't handle schedule events
    if: github.event_name != 'schedule' && github.repository == 'freqtrade/freqtrade'
-    permissions:
-      repository-projects: read
    steps:

-    - name: Check user permission
-      id: check
-      uses: scherermichael-oss/action-has-permission@136e061bfe093832d87f090dd768e14e27a740d3 # 1.0.6
-      with:
-        required-permission: write
-      env:
-        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
    - name: Discord notification
-      uses: rjstone/discord-webhook-notify@1399c1b2d57cc05894d506d2cfdc33c5f012b993 #v1.1.1
-      if: always() && steps.check.outputs.has-permission && ( github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false)
+      uses: sarisia/actions-status-discord@eb045afee445dc055c18d3d90bd0f244fd062708 # v1.16.0
+      if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false
      with:
-          severity: info
-          details: Test Completed!
-          webhookUrl: ${{ secrets.DISCORD_WEBHOOK }}
+          color: '#00FF00' # green
+          title: Test Completed!
+          webhook: ${{ secrets.DISCORD_WEBHOOK }}  # zizmor: ignore[secrets-outside-env] Intentionally not using environment variable.

  build:
+    if: always()
    name: "Build"
-    needs: [ build-linux, build-macos, build-windows, docs-check, mypy-version-check, pre-commit ]
+    needs: [
+      tests,
+      docs-check,
+      mypy-version-check,
+      pre-commit,
+    ]
    runs-on: ubuntu-22.04
+    strategy:
+      matrix:
+        python-version: ["3.13"]

    steps:
-    - uses: actions/checkout@v4
+
+    - name: Decide whether the needed jobs succeeded or failed
+      uses: re-actors/alls-green@05ac9388f0aebcb5727afa17fcccfecd6f8ec5fe  # v1.2.2
+      with:
+        jobs: ${{ toJSON(needs) }}
+
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

-    - name: Set up Python
-      uses: actions/setup-python@v5
+    - name: Install uv and Python 🐍
+      uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
      with:
-        python-version: "3.12"
+        activate-environment: true
+        python-version: "${{ matrix.python-version }}"

    - name: Build distribution
      run: |
-        pip install -U build
+        uv pip install $(grep -E "^build==" requirements-dev.txt)
        python -m build --sdist --wheel

    - name: Upload artifacts 📦
-      uses: actions/upload-artifact@v4
+      uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
      with:
        name: freqtrade-build
        path: |
@@ -549,11 +333,10 @@ jobs:

    - name: Build Client distribution
      run: |
-        pip install -U build
        python -m build --sdist --wheel ft_client

    - name: Upload artifacts 📦
-      uses: actions/upload-artifact@v4
+      uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
      with:
        name: freqtrade-client-build
        path: |
@@ -569,22 +352,22 @@ jobs:
      name: testpypi
      url: https://test.pypi.org/p/freqtrade
    permissions:
-      id-token: write
+      id-token: write # Needed for pypa/gh-action-pypi-publish

    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

    - name: Download artifact  📦
-      uses: actions/download-artifact@v4
+      uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
      with:
        pattern: freqtrade*-build
        path: dist
        merge-multiple: true

    - name: Publish to PyPI (Test)
-      uses: pypa/gh-action-pypi-publish@76f52bc884231f62b9a034ebfe128415bbaabdfc # v1.12.4
+      uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0
      with:
        repository-url: https://test.pypi.org/legacy/

@@ -598,118 +381,46 @@ jobs:
      name: pypi
      url: https://pypi.org/p/freqtrade
    permissions:
-      id-token: write
+      id-token: write # Needed for pypa/gh-action-pypi-publish

    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

    - name: Download artifact  📦
-      uses: actions/download-artifact@v4
+      uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
      with:
        pattern: freqtrade*-build
        path: dist
        merge-multiple: true

    - name: Publish to PyPI
-      uses: pypa/gh-action-pypi-publish@76f52bc884231f62b9a034ebfe128415bbaabdfc # v1.12.4
+      uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0


-  deploy-docker:
-    needs: [ build-linux, build-macos, build-windows, docs-check, mypy-version-check, pre-commit ]
-    runs-on: ubuntu-22.04
-
+  docker-build:
+    name: "Docker Build and Deploy"
+    needs: [
+     build,
+    ]
    if: (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'release') && github.repository == 'freqtrade/freqtrade'
-
-    steps:
-    - uses: actions/checkout@v4
-      with:
-        persist-credentials: false
-
-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        python-version: "3.12"
-
-    - name: Extract branch name
-      id: extract-branch
-      run: |
-        echo "GITHUB_REF='${GITHUB_REF}'"
-        echo "branch=${GITHUB_REF##*/}" >> "$GITHUB_OUTPUT"
-
-    - name: Dockerhub login
-      env:
-        DOCKER_PASSWORD: ${{ secrets.DOCKER_PASSWORD }}
-        DOCKER_USERNAME: ${{ secrets.DOCKER_USERNAME }}
-      run: |
-        echo "${DOCKER_PASSWORD}" | docker login --username ${DOCKER_USERNAME} --password-stdin
-
-    # We need docker experimental to pull the ARM image.
-    - name: Switch docker to experimental
-      run: |
-          docker version -f '{{.Server.Experimental}}'
-          echo $'{\n    "experimental": true\n}' | sudo tee /etc/docker/daemon.json
-          sudo systemctl restart docker
-          docker version -f '{{.Server.Experimental}}'
-
-    - name: Set up QEMU
-      uses: docker/setup-qemu-action@29109295f81e9208d7d86ff1c6c12d2833863392 # v3.6.0
-
-    - name: Set up Docker Buildx
-      id: buildx
-      uses: docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2 #v3.10.0
-
-    - name: Available platforms
-      run: echo ${PLATFORMS}
-      env:
-        PLATFORMS: ${{ steps.buildx.outputs.platforms }}
-
-    - name: Build and test and push docker images
-      env:
-        BRANCH_NAME: ${{ steps.extract-branch.outputs.branch }}
-      run: |
-        build_helpers/publish_docker_multi.sh
-
-  deploy-arm:
-    name: "Deploy Docker"
+    uses: ./.github/workflows/docker-build.yml
    permissions:
-      packages: write
-    needs: [ deploy-docker ]
-    # Only run on 64bit machines
-    runs-on: [self-hosted, linux, ARM64]
-    if: (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'release') && github.repository == 'freqtrade/freqtrade'
+      packages: write # Needed to push package versions
+      contents: read
+    secrets:
+      DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}  # zizmor: ignore[secrets-outside-env] Intentionally not using environment variable.
+      DOCKERHUB_USERNAME: ${{ secrets.DOCKERHUB_USERNAME }}
+      DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}

-    steps:
-    - uses: actions/checkout@v4
-      with:
-        persist-credentials: false

-    - name: Extract branch name
-      id: extract-branch
-      run: |
-        echo "GITHUB_REF='${GITHUB_REF}'"
-        echo "branch=${GITHUB_REF##*/}" >> "$GITHUB_OUTPUT"
-
-    - name: Dockerhub login
-      env:
-        DOCKER_PASSWORD: ${{ secrets.DOCKER_PASSWORD }}
-        DOCKER_USERNAME: ${{ secrets.DOCKER_USERNAME }}
-      run: |
-        echo "${DOCKER_PASSWORD}" | docker login --username ${DOCKER_USERNAME} --password-stdin
-
-    - name: Build and test and push docker images
-      env:
-        BRANCH_NAME: ${{ steps.extract-branch.outputs.branch }}
-        GHCR_USERNAME: ${{ github.actor }}
-        GHCR_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      run: |
-        build_helpers/publish_docker_arm64.sh
-
-    - name: Discord notification
-      uses: rjstone/discord-webhook-notify@1399c1b2d57cc05894d506d2cfdc33c5f012b993 #v1.1.1
-      if: always() && ( github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false) && (github.event_name != 'schedule')
-      with:
-          severity: info
-          details: Deploy Succeeded!
-          webhookUrl: ${{ secrets.DISCORD_WEBHOOK }}
+  packages-cleanup:
+    name: "Docker Package Cleanup"
+    uses: ./.github/workflows/packages-cleanup.yml
+    # Only run on push, schedule, or release events
+    if: (github.event_name == 'push' || github.event_name == 'schedule') && github.repository == 'freqtrade/freqtrade'
+    permissions:
+      packages: write # Needed to delete package versions
+    with:
+      package_name: 'freqtrade'
@@ -11,6 +11,9 @@ on:
 # disable permissions for all of the available permissions
 permissions: {}

+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true

 jobs:
  build-docs:
@@ -19,19 +22,19 @@ jobs:
    name: Deploy Docs through mike
    runs-on: ubuntu-latest
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          persist-credentials: true

-      - name: Set up Python
-        uses: actions/setup-python@v5
+      - name: Install uv and Python 🐍
+        uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
        with:
-          python-version: '3.12'
+          activate-environment: true
+          python-version: '3.13'

      - name: Install dependencies
        run: |
-          python -m pip install --upgrade pip
-          pip install -r docs/requirements-docs.txt
+          uv pip install -r docs/requirements-docs.txt

      - name: Fetch gh-pages branch
        run: |
@@ -17,26 +17,40 @@ concurrency:
  group: "${{ github.workflow }}"
  cancel-in-progress: true

+permissions:
+  contents: read

 jobs:
  build-and-push:
+    name: "Build and Push Devcontainer Image"
    permissions:
-      packages: write
+      packages: write  # Needed to push package versions
    runs-on: ubuntu-latest
    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false
    - name: Login to GitHub Container Registry
-      uses: docker/login-action@74a5d142397b4f367a81961eba4e8cd7edddf772 # v3.4.0
+      uses: docker/login-action@4907a6ddec9925e35a0a9e82d7399ccc52663121 # v4.1.0
      with:
        registry: ghcr.io
        username: ${{ github.actor }}
        password: ${{ secrets.GITHUB_TOKEN }}
    - name: Pre-build dev container image
-      uses: devcontainers/ci@8bf61b26e9c3a98f69cb6ce2f88d24ff59b785c6 # v0.3.19
+      uses: devcontainers/ci@b63b30de439b47a52267f241112c5b453b673db5 # v0.3.1900000449
      with:
        subFolder: .github
        imageName: ghcr.io/${{ github.repository }}-devcontainer
        cacheFrom: ghcr.io/${{ github.repository }}-devcontainer
        push: always
+
+
+  packages-cleanup:
+    name: "Docker Package Cleanup"
+    uses: ./.github/workflows/packages-cleanup.yml
+    # Only run on push, schedule, or release events
+    if: (github.event_name == 'push' || github.event_name == 'schedule') && github.repository == 'freqtrade/freqtrade'
+    permissions:
+      packages: write # Needed to delete package versions
+    with:
+      package_name: 'freqtrade-devcontainer'
@@ -0,0 +1,317 @@
+name: Docker Build and Deploy
+
+on:
+  workflow_call:
+    secrets:
+      DOCKERHUB_USERNAME:
+        required: true
+      DOCKERHUB_TOKEN:
+        required: true
+      DISCORD_WEBHOOK:
+        required: false
+  workflow_dispatch:
+    inputs:
+      branch_name:
+        description: 'Branch name to build Docker images for'
+        required: false
+        default: 'develop'
+        type: string
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+env:
+  IMAGE_NAME: "freqtradeorg/freqtrade"
+  CACHE_IMAGE: "freqtradeorg/freqtrade_cache"
+  GHCR_IMAGE_NAME: "ghcr.io/freqtrade/freqtrade"
+  PI_PLATFORM: "linux/arm/v7"
+
+jobs:
+  deploy-docker:
+    name: "Deploy Docker x64 and armv7l"
+    runs-on: ubuntu-22.04
+    if: github.repository == 'freqtrade/freqtrade'
+    environment:
+      name: docker
+
+    steps:
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      with:
+        persist-credentials: false
+
+    - name: Visualize disk usage before build
+      run: df -h
+
+    - name: Cleanup some disk space
+      run: |
+        docker system prune -a --force || true
+        docker builder prune -af || true
+
+    - name: Visualize disk usage after cleanup
+      run: df -h
+
+    - name: Set docker tag names
+      id: tags
+      uses: ./.github/actions/docker-tags
+
+    - name: Login to Docker Hub
+      uses: docker/login-action@4907a6ddec9925e35a0a9e82d7399ccc52663121 # v4.1.0
+      with:
+        username: ${{ secrets.DOCKERHUB_USERNAME }}
+        password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+    - name: Set up QEMU
+      uses: docker/setup-qemu-action@ce360397dd3f832beb865e1373c09c0e9f86d70a # v4.0.0
+      with:
+        cache-image: false
+
+    - name: Set up Docker Buildx
+      id: buildx
+      uses: docker/setup-buildx-action@4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd #v4.0.0
+
+    - name: Available platforms
+      run: echo ${PLATFORMS}
+      env:
+        PLATFORMS: ${{ steps.buildx.outputs.platforms }}
+
+    - name: Build image without cache
+      if: github.event_name == 'schedule'
+      env:
+        TAG: ${{ steps.tags.outputs.TAG }}
+      run: |
+        docker build -t ${CACHE_IMAGE}:${TAG} .
+
+    - name: Build ARMHF image without cache
+      if: github.event_name == 'schedule'
+      env:
+        TAG_PI: ${{ steps.tags.outputs.TAG_PI }}
+        CACHE_TAG_PI: ${{ steps.tags.outputs.CACHE_TAG_PI }}
+      run: |
+        docker buildx build \
+          --cache-to=type=registry,ref=${CACHE_TAG_PI} \
+          -f docker/Dockerfile.armhf \
+          --platform ${PI_PLATFORM} \
+          -t ${IMAGE_NAME}:${TAG_PI} \
+          --push \
+          --provenance=false \
+          .
+
+    - name: Build image with cache
+      if: github.event_name != 'schedule'
+      env:
+        TAG: ${{ steps.tags.outputs.TAG }}
+      run: |
+        docker pull ${IMAGE_NAME}:${TAG} || true
+        docker build --cache-from ${IMAGE_NAME}:${TAG} -t ${CACHE_IMAGE}:${TAG} .
+
+    - name: Build ARMHF image with cache
+      if: github.event_name != 'schedule'
+      # disable provenance due to https://github.com/docker/buildx/issues/1509
+      env:
+        TAG_PI: ${{ steps.tags.outputs.TAG_PI }}
+        CACHE_TAG_PI: ${{ steps.tags.outputs.CACHE_TAG_PI }}
+      run: |
+        docker buildx build \
+          --cache-from=type=registry,ref=${CACHE_TAG_PI} \
+          --cache-to=type=registry,ref=${CACHE_TAG_PI} \
+          -f docker/Dockerfile.armhf \
+          --platform ${PI_PLATFORM} \
+          -t ${IMAGE_NAME}:${TAG_PI} \
+          --push \
+          --provenance=false \
+          .
+
+    - name: Run build for AI images
+      env:
+        TAG: ${{ steps.tags.outputs.TAG }}
+        TAG_PLOT: ${{ steps.tags.outputs.TAG_PLOT }}
+        TAG_FREQAI: ${{ steps.tags.outputs.TAG_FREQAI }}
+        TAG_FREQAI_RL: ${{ steps.tags.outputs.TAG_FREQAI_RL }}
+      run: |
+        docker build --build-arg sourceimage=${CACHE_IMAGE} --build-arg sourcetag=${TAG} -t ${CACHE_IMAGE}:${TAG_PLOT} -f docker/Dockerfile.plot .
+        docker build --build-arg sourceimage=${CACHE_IMAGE} --build-arg sourcetag=${TAG} -t ${CACHE_IMAGE}:${TAG_FREQAI} -f docker/Dockerfile.freqai .
+        docker build --build-arg sourceimage=${CACHE_IMAGE} --build-arg sourcetag=${TAG_FREQAI} -t ${CACHE_IMAGE}:${TAG_FREQAI_RL} -f docker/Dockerfile.freqai_rl .
+
+
+    - name: Run backtest in Docker
+      env:
+        TAG: ${{ steps.tags.outputs.TAG }}
+      run: |
+        docker run --rm -v $(pwd)/tests/testdata/config.tests.json:/freqtrade/config.json:ro -v $(pwd)/tests:/tests ${CACHE_IMAGE}:${TAG} backtesting --datadir /tests/testdata --strategy-path /tests/strategy/strats/ --strategy StrategyTestV3
+
+    - name: Push cache images
+      env:
+        TAG: ${{ steps.tags.outputs.TAG }}
+        TAG_PLOT: ${{ steps.tags.outputs.TAG_PLOT }}
+        TAG_FREQAI: ${{ steps.tags.outputs.TAG_FREQAI }}
+        TAG_FREQAI_RL: ${{ steps.tags.outputs.TAG_FREQAI_RL }}
+      run: |
+        docker push ${CACHE_IMAGE}:$TAG
+        docker push ${CACHE_IMAGE}:$TAG_PLOT
+        docker push ${CACHE_IMAGE}:$TAG_FREQAI
+        docker push ${CACHE_IMAGE}:$TAG_FREQAI_RL
+
+    - name: list Images
+      run: |
+        docker images
+
+    - name: Visualize disk usage after build
+      run: df -h
+
+  deploy-arm:
+    name: "Deploy Docker ARM64"
+    permissions:
+      packages: write # Needed to push package versions
+    needs: [ deploy-docker ]
+    # Only run on 64bit machines
+    runs-on: [self-hosted, linux, ARM64]
+    if: github.repository == 'freqtrade/freqtrade'
+    environment:
+      name: docker
+
+    steps:
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      with:
+        persist-credentials: false
+
+    - name: Set docker tag names
+      id: tags
+      uses: ./.github/actions/docker-tags
+
+    - name: Login to Docker Hub
+      uses: docker/login-action@4907a6ddec9925e35a0a9e82d7399ccc52663121 # v4.1.0
+      with:
+        username: ${{ secrets.DOCKERHUB_USERNAME }}
+        password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+    - name: Login to github
+      uses: docker/login-action@4907a6ddec9925e35a0a9e82d7399ccc52663121 # v4.1.0
+      with:
+        registry: ghcr.io
+        username: ${{ github.actor }}
+        password: ${{ secrets.GITHUB_TOKEN }}
+
+    - name: Build image without cache
+      if: github.event_name == 'schedule'
+      env:
+        TAG_ARM: ${{ steps.tags.outputs.TAG_ARM }}
+      run: |
+        docker build -t ${IMAGE_NAME}:${TAG_ARM} .
+
+    - name: Build image with cache
+      if: github.event_name != 'schedule'
+      env:
+        TAG_ARM: ${{ steps.tags.outputs.TAG_ARM }}
+      run: |
+        docker pull ${IMAGE_NAME}:${TAG_ARM} || true
+        docker build --cache-from ${IMAGE_NAME}:${TAG_ARM} -t ${CACHE_IMAGE}:${TAG_ARM} .
+
+    - name: Run build for AI images
+      env:
+        TAG_ARM: ${{ steps.tags.outputs.TAG_ARM }}
+        TAG_PLOT_ARM: ${{ steps.tags.outputs.TAG_PLOT_ARM }}
+        TAG_FREQAI_ARM: ${{ steps.tags.outputs.TAG_FREQAI_ARM }}
+        TAG_FREQAI_RL_ARM: ${{ steps.tags.outputs.TAG_FREQAI_RL_ARM }}
+      run: |
+        docker build --build-arg sourceimage=${CACHE_IMAGE} --build-arg sourcetag=${TAG_ARM} -t ${CACHE_IMAGE}:${TAG_PLOT_ARM} -f docker/Dockerfile.plot .
+        docker build --build-arg sourceimage=${CACHE_IMAGE} --build-arg sourcetag=${TAG_ARM} -t ${CACHE_IMAGE}:${TAG_FREQAI_ARM} -f docker/Dockerfile.freqai .
+        docker build --build-arg sourceimage=${CACHE_IMAGE} --build-arg sourcetag=${TAG_FREQAI_ARM} -t ${CACHE_IMAGE}:${TAG_FREQAI_RL_ARM} -f docker/Dockerfile.freqai_rl .
+
+
+    - name: Run backtest in Docker
+      env:
+        TAG_ARM: ${{ steps.tags.outputs.TAG_ARM }}
+      run: |
+        docker run --rm -v $(pwd)/tests/testdata/config.tests.json:/freqtrade/config.json:ro -v $(pwd)/tests:/tests ${CACHE_IMAGE}:${TAG_ARM} backtesting --datadir /tests/testdata --strategy-path /tests/strategy/strats/ --strategy StrategyTestV3
+
+    - name: Docker images
+      run: |
+        docker images
+
+    - name: Push cache images
+      env:
+        TAG_ARM: ${{ steps.tags.outputs.TAG_ARM }}
+        TAG_PLOT_ARM: ${{ steps.tags.outputs.TAG_PLOT_ARM }}
+        TAG_FREQAI_ARM: ${{ steps.tags.outputs.TAG_FREQAI_ARM }}
+        TAG_FREQAI_RL_ARM: ${{ steps.tags.outputs.TAG_FREQAI_RL_ARM }}
+      run: |
+        docker push ${CACHE_IMAGE}:$TAG_PLOT_ARM
+        docker push ${CACHE_IMAGE}:$TAG_FREQAI_ARM
+        docker push ${CACHE_IMAGE}:$TAG_FREQAI_RL_ARM
+        docker push ${CACHE_IMAGE}:$TAG_ARM
+
+    - name: Create manifests
+      env:
+        TAG_ARM: ${{ steps.tags.outputs.TAG_ARM }}
+        TAG: ${{ steps.tags.outputs.TAG }}
+        TAG_PI: ${{ steps.tags.outputs.TAG_PI }}
+      run: |
+        docker buildx imagetools create \
+          --tag ${IMAGE_NAME}:${TAG} \
+          --tag ${GHCR_IMAGE_NAME}:${TAG} \
+          ${CACHE_IMAGE}:${TAG} ${CACHE_IMAGE}:${TAG_ARM} ${IMAGE_NAME}:${TAG_PI}
+
+    - name: Create multiarch image - Plot
+      env:
+        TAG_PLOT: ${{ steps.tags.outputs.TAG_PLOT }}
+        TAG_PLOT_ARM: ${{ steps.tags.outputs.TAG_PLOT_ARM }}
+      run: |
+        docker buildx imagetools create \
+          --tag ${IMAGE_NAME}:${TAG_PLOT} \
+          --tag ${GHCR_IMAGE_NAME}:${TAG_PLOT} \
+          ${CACHE_IMAGE}:${TAG_PLOT} ${CACHE_IMAGE}:${TAG_PLOT_ARM}
+
+    - name: Create multiarch image - FreqAI
+      env:
+        TAG_FREQAI: ${{ steps.tags.outputs.TAG_FREQAI }}
+        TAG_FREQAI_ARM: ${{ steps.tags.outputs.TAG_FREQAI_ARM }}
+      run: |
+        docker buildx imagetools create \
+          --tag ${IMAGE_NAME}:${TAG_FREQAI} \
+          --tag ${GHCR_IMAGE_NAME}:${TAG_FREQAI} \
+          ${CACHE_IMAGE}:${TAG_FREQAI} ${CACHE_IMAGE}:${TAG_FREQAI_ARM}
+
+    - name: Create multiarch image - FreqAI RL
+      env:
+        TAG_FREQAI_RL: ${{ steps.tags.outputs.TAG_FREQAI_RL }}
+        TAG_FREQAI_RL_ARM: ${{ steps.tags.outputs.TAG_FREQAI_RL_ARM }}
+        TAG_FREQAI_TORCH: ${{ steps.tags.outputs.TAG_FREQAI_TORCH }}
+      run: |
+        # Create special Torch tag - which is identical to the RL tag.
+        docker buildx imagetools create \
+          --tag ${IMAGE_NAME}:${TAG_FREQAI_RL} \
+          --tag ${GHCR_IMAGE_NAME}:${TAG_FREQAI_RL} \
+          --tag ${IMAGE_NAME}:${TAG_FREQAI_TORCH} \
+          --tag ${GHCR_IMAGE_NAME}:${TAG_FREQAI_TORCH} \
+          ${CACHE_IMAGE}:${TAG_FREQAI_RL} ${CACHE_IMAGE}:${TAG_FREQAI_RL_ARM}
+
+    - name: Tag latest
+      if: env.TAG == 'develop'
+      env:
+        TAG: ${{ steps.tags.outputs.TAG }}
+      run: |
+        # Tag image as latest
+        docker buildx imagetools create \
+          --tag ${GHCR_IMAGE_NAME}:${TAG} \
+          --tag ${GHCR_IMAGE_NAME}:latest \
+          --tag ${IMAGE_NAME}:latest \
+          ${IMAGE_NAME}:${TAG}
+
+    - name: Docker images
+      run: |
+        docker images
+
+    - name: Image cleanup
+      run: |
+        docker image prune -a --force --filter "until=24h"
+
+    - name: Discord notification
+      uses: sarisia/actions-status-discord@eb045afee445dc055c18d3d90bd0f244fd062708 # v1.16.0
+      if: always() && ( github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false) && (github.event_name != 'schedule')
+      with:
+          title: Deploy Succeeded!
+          webhook: ${{ secrets.DISCORD_WEBHOOK }}
@@ -3,21 +3,29 @@ on:
  push:
    branches:
    - stable
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}
+  cancel-in-progress: true

 # disable permissions for all of the available permissions
 permissions: {}

 jobs:
  dockerHubDescription:
+    name: "Update Docker Hub Description"
    runs-on: ubuntu-latest
+    environment:
+      name: docker
    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

    - name: Docker Hub Description
-      uses: peter-evans/dockerhub-description@432a30c9e07499fd01da9f8a49f0faf9e0ca5b77 # v4.0.2
+      uses: peter-evans/dockerhub-description@1b9a80c056b620d92cedb9d9b5a223409c68ddfa # v5.0.0
      with:
-        username: ${{ secrets.DOCKER_USERNAME }}
-        password: ${{ secrets.DOCKER_PASSWORD }}
+        username: ${{ secrets.DOCKERHUB_USERNAME }}
+        password: ${{ secrets.DOCKERHUB_TOKEN }}
        repository: freqtradeorg/freqtrade
@@ -0,0 +1,52 @@
+name: Cleanup Packages
+
+on:
+  workflow_call:
+    inputs:
+       package_name:
+        description: 'Package name to clean up'
+        required: false
+        default: 'freqtrade'
+        type: string
+
+  workflow_dispatch:
+    inputs:
+      package_name:
+        description: 'Package name to clean up'
+        required: false
+        default: 'freqtrade'
+        type: choice
+        options:
+          - 'freqtrade'
+          - 'freqtrade-devcontainer'
+      delete-untagged:
+        description: 'Whether to delete only untagged images'
+        required: false
+        default: true
+        type: boolean
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: false
+
+env:
+  PACKAGE_NAME: "freqtrade"
+
+permissions: {}
+
+jobs:
+  deploy-docker:
+    name: "Delete Packages"
+    runs-on: ubuntu-24.04
+    if: github.repository == 'freqtrade/freqtrade'
+    permissions:
+      packages: write  # Needed to delete package versions
+
+    steps:
+    - name: "Delete untagged Package Versions"
+      uses: actions/delete-package-versions@e5bc658cc4c965c472efe991f8beea3981499c55 # v5.0.0
+      with:
+        package-name: ${{ inputs.package_name || env.PACKAGE_NAME }}
+        package-type: 'container'
+        min-versions-to-keep: 10
+        delete-only-untagged-versions: ${{ inputs.delete-untagged || 'true' }}
@@ -0,0 +1,53 @@
+name: Pre-commit Types update
+
+on:
+  pull_request:
+    branches:
+      - "develop"
+
+concurrency:
+  group: "${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}"
+  cancel-in-progress: true
+permissions: {}
+
+jobs:
+  mypy-version-update:
+    name: "Pre-commit mypy type versions update"
+    runs-on: ubuntu-24.04
+    # Only run this job for pull requests created by dependabot[bot]
+    if: >
+      github.event.pull_request.user.login == 'dependabot[bot]' &&
+      github.repository == github.event.pull_request.head.repo.full_name &&
+      github.event_name == 'pull_request' &&
+      startsWith(github.head_ref, 'dependabot/')
+
+    environment:
+      name: dependabot-pulls
+
+    steps:
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      with:
+        persist-credentials: true
+        token: ${{ secrets.REPO_SCOPED_TOKEN_DEP }}
+        ref: ${{ github.head_ref || github.ref }}
+
+    - name: Install uv and Python 🐍
+      uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
+      with:
+        activate-environment: true
+        python-version: "3.13"
+
+    - name: Install PyYAML
+      run: |
+
+    - name: pre-commit dependencies
+      run: |
+        uv pip install $(grep -E "^pyyaml==" requirements-dev.txt)
+        python build_helpers/pre_commit_update.py --update
+
+    - uses: stefanzweifel/git-auto-commit-action@04702edda442b2e678b25b537cec683a1493fcb9 # v7
+      with:
+        commit_message: "chore(deps): Apply pre-commit types update"
+        commit_user_name: Freqtrade Bot
+        commit_user_email: 154552126+freqtrade-bot@users.noreply.github.com
+        commit_author: Freqtrade Bot <154552126+freqtrade-bot@users.noreply.github.com>
@@ -2,33 +2,42 @@ name: Pre-commit auto-update

 on:
  schedule:
-    - cron: "0 3 * * 2"
+    - cron: "13 1 * * 2"
  # on demand
  workflow_dispatch:

 permissions:
  contents: read

+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
 jobs:
  auto-update:
+    name: Auto-update pre-commit hooks
    runs-on: ubuntu-latest
+    environment:
+      name: develop
+
    steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      with:
        persist-credentials: false

-    - uses: actions/setup-python@v5
+    - name: Install uv and Python 🐍
+      uses: astral-sh/setup-uv@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0
      with:
-        python-version: "3.12"
-
+        activate-environment: true
+        python-version: "3.13"

    - name: Install pre-commit
-      run: pip install pre-commit
+      run: uv pip install $(grep -E "^pre-commit==" requirements-dev.txt)

    - name: Run auto-update
      run: pre-commit autoupdate

-    - uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
+    - uses: peter-evans/create-pull-request@5f6978faf089d4d20b00c7766989d076bb2fc7f1 # v8.1.1
      with:
        token: ${{ secrets.REPO_SCOPED_TOKEN }}
        add-paths: .pre-commit-config.yaml
@@ -0,0 +1,34 @@
+name: GitHub Actions Security Analysis with zizmor 🌈
+
+on:
+  push:
+    branches:
+      - develop
+      - stable
+  pull_request:
+    branches:
+      - develop
+      - stable
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: false
+
+permissions: {}
+
+jobs:
+  zizmor:
+    name: Run zizmor 🌈
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write # Required for upload-sarif (used by zizmor-action) to upload SARIF files.
+      # contents: read         # Only needed for private repos. Needed to clone the repo.
+      # actions: read          # Only needed for private repos. Needed for upload-sarif to read workflow run info.
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        with:
+          persist-credentials: false
+
+      - name: Run zizmor 🌈
+        uses: zizmorcore/zizmor-action@b1d7e1fb5de872772f31590499237e7cce841e8e # v0.5.3
@@ -13,43 +13,31 @@ repos:
        pass_filenames: false
        additional_dependencies: ["python-rapidjson", "jsonschema"]

-  - repo: https://github.com/pycqa/flake8
-    rev: "7.2.0"
-    hooks:
-      - id: flake8
-        additional_dependencies: [Flake8-pyproject]
-        # stages: [push]

  - repo: https://github.com/pre-commit/mirrors-mypy
-    rev: "v1.15.0"
+    rev: "v2.1.0"
    hooks:
      - id: mypy
        exclude: build_helpers
        additional_dependencies:
-          - types-cachetools==6.0.0.20250525
+          - types-cachetools==7.0.0.20260503
          - types-filelock==3.2.7
-          - types-requests==2.32.0.20250515
-          - types-tabulate==0.9.0.20241207
-          - types-python-dateutil==2.9.0.20250516
-          - SQLAlchemy==2.0.41
-        # stages: [push]
-
-  - repo: https://github.com/pycqa/isort
-    rev: "6.0.1"
-    hooks:
-      - id: isort
-        name: isort (python)
+          - types-requests==2.33.0.20260508
+          - types-tabulate==0.10.0.20260508
+          - types-python-dateutil==2.9.0.20260508
+          - scipy-stubs==1.17.1.4
+          - SQLAlchemy==2.0.49
        # stages: [push]

  - repo: https://github.com/charliermarsh/ruff-pre-commit
    # Ruff version.
-    rev: 'v0.11.11'
+    rev: 'v0.15.13'
    hooks:
      - id: ruff
      - id: ruff-format

  - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v5.0.0
+    rev: v6.0.0
    hooks:
      - id: end-of-file-fixer
        exclude: |
@@ -69,12 +57,12 @@ repos:
            )$

  - repo: https://github.com/stefmolin/exif-stripper
-    rev: 0.6.2
+    rev: 1.2.0
    hooks:
      - id: strip-exif

  - repo: https://github.com/codespell-project/codespell
-    rev: v2.4.1
+    rev: v2.4.2
    hooks:
    - id: codespell
      additional_dependencies:
@@ -82,6 +70,6 @@ repos:

  # Ensure github actions remain safe
  - repo: https://github.com/woodruffw/zizmor-pre-commit
-    rev: v1.8.0
+    rev: v1.24.1
    hooks:
    - id: zizmor
@@ -9,8 +9,11 @@ Issues labeled [good first issue](https://github.com/freqtrade/freqtrade/labels/
 Few pointers for contributions:

 - Create your PR against the `develop` branch, not `stable`.
- New features need to contain unit tests, must conform to PEP8 (max-line-length = 100) and should be documented with the introduction PR.
- PR's can be declared as `[WIP]` - which signify Work in Progress Pull Requests (which are not finished).
+- Stick to english in both commit messages, PR descriptions and code comments and variable names.
+- New features need to contain unit tests, must pass CI (run pre-commit and pytest to get an early feedback) and should be documented with the introduction PR.
+- PR's can be declared as draft - signaling Work in Progress for Pull Requests (which are not finished). We'll still aim to provide feedback on draft PR's in a timely manner.
+- If you're using AI for your PR, please both mention it in the PR description and do a thorough review of the generated code yourself.  
+  The final responsibility for the code with the PR author, not with the AI, which also means that commits must be linked to your (human) account, not some generic AI account.

 If you are unsure, discuss the feature on our [discord server](https://discord.gg/p7nuUNVfP7) or in a [issue](https://github.com/freqtrade/freqtrade/issues) before a Pull Request.

@@ -22,8 +25,7 @@ Best start by reading the [documentation](https://www.freqtrade.io/) to get a fe

 ### 1. Run unit tests

-All unit tests must pass. If a unit test is broken, change your code to 
-make it pass. It means you have introduced a regression.
+All unit tests must pass. If a unit test is broken, change your code to make it pass. It means you have introduced a regression.

 #### Test the whole project

@@ -43,43 +45,43 @@ pytest tests/test_<file_name>.py
 pytest tests/test_<file_name>.py::test_<method_name>
 ```

-### 2. Test if your code is PEP8 compliant
+### 2. Test if your code corresponds to our style guide

-#### Run Ruff
+We receive a lot of code that fails preliminary CI checks.  
+To help with that, we encourage contributors to install the git pre-commit hook that will let you know immediately when you try to commit code that fails these checks.
+
+You can manually run pre-commit with `pre-commit run -a` - or install the git hook with `pre-commit install` to have it run automatically on each commit.
+
+Running `pre-commit run -a` will run all checks, including `ruff`, `mypy` and `codespell` (among others).
+
+#### Additional styles applied
+
+- Have docstrings on all public methods
+- Use double-quotes for docstrings
+- Multiline docstrings should be indented to the level of the first quote
+- Doc-strings should follow the reST format (`:param xxx: ...`, `:return: ...`, `:raises KeyError: ...`)
+
+#### Manually run the individual checks
+
+The following sections describe how to run the individual checks that are running  as part of the pre-commit hook.
+
+##### Run ruff
+
+Check your code with ruff to ensure that it follows the style guide.

 ```bash
 ruff check .
+ruff format .
 ```

-We receive a lot of code that fails the `ruff` checks.
-To help with that, we encourage you to install the git pre-commit 
-hook that will warn you when you try to commit code that fails these checks.
+##### Run mypy

-you can manually run pre-commit with `pre-commit run -a`.
-
-##### Additional styles applied
-
-* Have docstrings on all public methods
-* Use double-quotes for docstrings
-* Multiline docstrings should be indented to the level of the first quote
-* Doc-strings should follow the reST format (`:param xxx: ...`, `:return: ...`, `:raises KeyError: ... `)
-
-### 3. Test if all type-hints are correct
-
-#### Run mypy
+Check your code with mypy to ensure that it follows the type-hinting rules.

 ``` bash
 mypy freqtrade
 ```

-### 4. Ensure formatting is correct
-
-#### Run ruff
-
-``` bash
-ruff format .
-```
-
 ## (Core)-Committer Guide

 ### Process: Pull Requests
@@ -118,18 +120,18 @@ Exceptions:
 - Ensure cross-platform compatibility for every change that's accepted. Windows, Mac & Linux.
 - Ensure no malicious code is introduced into the core code.
 - Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
- Keep feature versions as small as possible, preferably one new feature per version.
+- Keep feature PR's as small as possible, preferably one new feature per PR.
 - Be welcoming to newcomers and encourage diverse new contributors from all backgrounds. See the Python Community Code of Conduct (https://www.python.org/psf/codeofconduct/).

 ### Becoming a Committer

 Contributors may be given commit privileges. Preference will be given to those with:

-1. Past contributions to Freqtrade and other related open-source projects. Contributions to Freqtrade include both code (both accepted and pending) and friendly participation in the issue tracker and Pull request reviews. Both quantity and quality are considered.
+1. Past contributions to Freqtrade and other related open source projects. Contributions to Freqtrade include both code (both accepted and pending) and friendly participation in the issue tracker and Pull request reviews. Both quantity and quality are considered.
 1. A coding style that the other core committers find simple, minimal, and clean.
 1. Access to resources for cross-platform development and testing.
 1. Time to devote to the project regularly.

-Being a Committer does not grant write permission on `develop` or `stable` for security reasons (Users trust Freqtrade with their Exchange API keys).
+Being a Committer does not automatically grant write permission on `develop` or `stable` for security reasons (Users trust Freqtrade with their Exchange API keys).

 After being Committer for some time, a Committer may be named Core Committer and given full repository access.
@@ -1,10 +1,10 @@
-FROM python:3.12.10-slim-bookworm as base
+FROM python:3.14.5-slim-trixie AS base

 # Setup env
-ENV LANG C.UTF-8
-ENV LC_ALL C.UTF-8
-ENV PYTHONDONTWRITEBYTECODE 1
-ENV PYTHONFAULTHANDLER 1
+ENV LANG=C.UTF-8
+ENV LC_ALL=C.UTF-8
+ENV PYTHONDONTWRITEBYTECODE=1
+ENV PYTHONFAULTHANDLER=1
 ENV PATH=/home/ftuser/.local/bin:$PATH
 ENV FT_APP_ENV="docker"

@@ -21,27 +21,22 @@ RUN mkdir /freqtrade \
 WORKDIR /freqtrade

 # Install dependencies
-FROM base as python-deps
+FROM base AS python-deps
 RUN  apt-get update \
  && apt-get -y install build-essential libssl-dev git libffi-dev libgfortran5 pkg-config cmake gcc \
  && apt-get clean \
  && pip install --upgrade pip wheel

-# Install TA-lib
-COPY build_helpers/* /tmp/
-RUN cd /tmp && /tmp/install_ta-lib.sh && rm -r /tmp/*ta-lib*
-ENV LD_LIBRARY_PATH /usr/local/lib
-
 # Install dependencies
 COPY --chown=ftuser:ftuser requirements.txt requirements-hyperopt.txt /freqtrade/
 USER ftuser
-RUN  pip install --user --no-cache-dir "numpy<2.0" \
+RUN  pip install --user --no-cache-dir "numpy<3.0" \
  && pip install --user --no-cache-dir -r requirements-hyperopt.txt

 # Copy dependencies to runtime-image
-FROM base as runtime-image
+FROM base AS runtime-image
 COPY --from=python-deps /usr/local/lib /usr/local/lib
-ENV LD_LIBRARY_PATH /usr/local/lib
+ENV LD_LIBRARY_PATH=/usr/local/lib

 COPY --from=python-deps --chown=ftuser:ftuser /home/ftuser/.local /home/ftuser/.local

@@ -49,7 +44,7 @@ USER ftuser
 # Install and execute
 COPY --chown=ftuser:ftuser . /freqtrade/

-RUN pip install -e . --user --no-cache-dir --no-build-isolation \
+RUN pip install -e . --user --no-cache-dir \
  && mkdir /freqtrade/user_data/ \
  && freqtrade install-ui

@@ -1,10 +1,10 @@
 # ![freqtrade](https://raw.githubusercontent.com/freqtrade/freqtrade/develop/docs/assets/freqtrade_poweredby.svg)

-[![Freqtrade CI](https://github.com/freqtrade/freqtrade/actions/workflows/ci.yml/badge.svg?branch=develop)](https://github.com/freqtrade/freqtrade/actions/)
+[![Freqtrade CI](https://github.com/freqtrade/freqtrade/actions/workflows/ci.yml/badge.svg?branch=develop)](https://github.com/freqtrade/freqtrade/actions/workflows/ci.yml)
 [![DOI](https://joss.theoj.org/papers/10.21105/joss.04864/status.svg)](https://doi.org/10.21105/joss.04864)
-[![Coverage Status](https://coveralls.io/repos/github/freqtrade/freqtrade/badge.svg?branch=develop&service=github)](https://coveralls.io/github/freqtrade/freqtrade?branch=develop)
+[![codecov](https://codecov.io/gh/freqtrade/freqtrade/branch/develop/graph/badge.svg?token=AD5BG3ATKI)](https://codecov.io/gh/freqtrade/freqtrade)
 [![Documentation](https://readthedocs.org/projects/freqtrade/badge/)](https://www.freqtrade.io)
-[![Maintainability](https://api.codeclimate.com/v1/badges/5737e6d668200b7518ff/maintainability)](https://codeclimate.com/github/freqtrade/freqtrade/maintainability)
+[![Discord Server](https://img.shields.io/badge/Freqtrade_Discord-4E4E4E?logo=discord)](https://discord.gg/p7nuUNVfP7)

 Freqtrade is a free and open source crypto trading bot written in Python. It is designed to support all major exchanges and be controlled via Telegram or webUI. It contains backtesting, plotting and money management tools as well as strategy optimization by machine learning.

@@ -16,7 +16,7 @@ This software is for educational purposes only. Do not risk money which
 you are afraid to lose. USE THE SOFTWARE AT YOUR OWN RISK. THE AUTHORS
 AND ALL AFFILIATES ASSUME NO RESPONSIBILITY FOR YOUR TRADING RESULTS.

-Always start by running a trading bot in Dry-run and do not engage money
+Always start by running a trading bot in Dry-Run and do not engage money
 before you understand how it works and what profit/loss you should
 expect.

@@ -25,11 +25,14 @@ hesitate to read the source code and understand the mechanism of this bot.

 ## Supported Exchange marketplaces

-Please read the [exchange specific notes](docs/exchanges.md) to learn about eventual, special configurations needed for each exchange.
+Please read the [exchange-specific notes](https://www.freqtrade.io/en/stable/exchanges/) to learn about special configurations that maybe needed for each exchange.
+
+### Supported Spot Exchanges

 - [X] [Binance](https://www.binance.com/)
- [X] [Bitmart](https://bitmart.com/)
 - [X] [BingX](https://bingx.com/invite/0EM9RX)
+- [X] [Bitget](https://www.bitget.com/)
+- [X] [Bitmart](https://bitmart.com/)
 - [X] [Bybit](https://bybit.com/)
 - [X] [Gate.io](https://www.gate.io/ref/6266643)
 - [X] [HTX](https://www.htx.com/)
@@ -39,15 +42,17 @@ Please read the [exchange specific notes](docs/exchanges.md) to learn about even
 - [X] [MyOKX](https://okx.com/) (OKX EEA)
 - [ ] [potentially many others](https://github.com/ccxt/ccxt/). _(We cannot guarantee they will work)_

-### Supported Futures Exchanges (experimental)
+### Supported Futures Exchanges

 - [X] [Binance](https://www.binance.com/)
+- [X] [Bitget](https://www.bitget.com/)
 - [X] [Gate.io](https://www.gate.io/ref/6266643)
 - [X] [Hyperliquid](https://hyperliquid.xyz/) (A decentralized exchange, or DEX)
 - [X] [OKX](https://okx.com/)
 - [X] [Bybit](https://bybit.com/)
+- [X] [Kraken](https://www.kraken.com/features/futures)

-Please make sure to read the [exchange specific notes](docs/exchanges.md), as well as the [trading with leverage](docs/leverage.md) documentation before diving in.
+Please make sure to read the [exchange specific notes](https://www.freqtrade.io/en/stable/exchanges/), as well as the [trading with leverage](https://www.freqtrade.io/en/stable/leverage/) documentation before diving in.

 ### Community tested

@@ -64,13 +69,12 @@ Please find the complete documentation on the [freqtrade website](https://www.fr

 ## Features

- [x] **Based on Python 3.10+**: For botting on any operating system - Windows, macOS and Linux.
+- [x] **Based on Python 3.11+**: For botting on any operating system - Windows, macOS and Linux.
 - [x] **Persistence**: Persistence is achieved through sqlite.
 - [x] **Dry-run**: Run the bot without paying money.
 - [x] **Backtesting**: Run a simulation of your buy/sell strategy.
 - [x] **Strategy Optimization by machine learning**: Use machine learning to optimize your buy/sell strategy parameters with real exchange data.
 - [X] **Adaptive prediction modeling**: Build a smart strategy with FreqAI that self-trains to the market via adaptive machine learning methods. [Learn more](https://www.freqtrade.io/en/stable/freqai/)
- [x] **Edge position sizing** Calculate your win rate, risk reward ratio, the best stoploss and adjust your position size before taking a position for each specific market. [Learn more](https://www.freqtrade.io/en/stable/edge/).
 - [x] **Whitelist crypto-currencies**: Select which crypto-currency you want to trade or use dynamic whitelists.
 - [x] **Blacklist crypto-currencies**: Select which crypto-currency you want to avoid.
 - [x] **Builtin WebUI**: Builtin web UI to manage your bot.
@@ -112,7 +116,6 @@ positional arguments:
    backtesting-show    Show past Backtest results
    backtesting-analysis
                        Backtest Analysis module.
-    edge                Edge module.
    hyperopt            Hyperopt module.
    hyperopt-list       List Hyperopt results
    hyperopt-show       Show details of Hyperopt results
@@ -141,13 +144,15 @@ options:

 ### Telegram RPC commands

-Telegram is not mandatory. However, this is a great way to control your bot. More details and the full command list on the [documentation](https://www.freqtrade.io/en/latest/telegram-usage/)
+Telegram is not mandatory. However, this is a great way to control your bot. More details and the full command list on the [documentation](https://www.freqtrade.io/en/stable/telegram-usage/)

 - `/start`: Starts the trader.
 - `/stop`: Stops the trader.
 - `/stopentry`: Stop entering new trades.
 - `/status <trade_id>|[table]`: Lists all or specific open trades.
 - `/profit [<n>]`: Lists cumulative profit from all finished trades, over the last n days.
+- `/profit_long [<n>]`: Lists cumulative profit from all finished long trades, over the last n days.
+- `/profit_short [<n>]`: Lists cumulative profit from all finished short trades, over the last n days.
 - `/forceexit <trade_id>|all`: Instantly exits the given trade (Ignoring `minimum_roi`).
 - `/fx <trade_id>|all`: Alias to `/forceexit`
 - `/performance`: Show performance of each finished trade grouped by pair
@@ -156,6 +161,7 @@ Telegram is not mandatory. However, this is a great way to control your bot. Mor
 - `/help`: Show help message.
 - `/version`: Show version.

+
 ## Development branches

 The project is currently setup in two main branches:
@@ -221,7 +227,7 @@ To run this bot we recommend you a cloud instance with a minimum of:

 ### Software requirements

- [Python >= 3.10](http://docs.python-guide.org/en/latest/starting/installation/)
+- [Python >= 3.11](http://docs.python-guide.org/en/latest/starting/installation/)
 - [pip](https://pip.pypa.io/en/stable/installing/)
 - [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
 - [TA-Lib](https://ta-lib.github.io/ta-lib-python/)
@@ -1,53 +1,105 @@
+import os
 import subprocess  # noqa: S404, RUF100
+import sys
+from io import StringIO
 from pathlib import Path


-subcommands = [
-    "trade",
-    "create-userdir",
-    "new-config",
-    "show-config",
-    "new-strategy",
-    "download-data",
-    "convert-data",
-    "convert-trade-data",
-    "trades-to-ohlcv",
-    "list-data",
-    "backtesting",
-    "backtesting-show",
-    "backtesting-analysis",
-    "edge",
-    "hyperopt",
-    "hyperopt-list",
-    "hyperopt-show",
-    "list-exchanges",
-    "list-markets",
-    "list-pairs",
-    "list-strategies",
-    "list-hyperoptloss",
-    "list-freqaimodels",
-    "list-timeframes",
-    "show-trades",
-    "test-pairlist",
-    "convert-db",
-    "install-ui",
-    "plot-dataframe",
-    "plot-profit",
-    "webserver",
-    "strategy-updater",
-    "lookahead-analysis",
-    "recursive-analysis",
-]
-
-result = subprocess.run(["freqtrade", "--help"], capture_output=True, text=True)
-
-with Path("docs/commands/main.md").open("w") as f:
-    f.write(f"```\n{result.stdout}\n```\n")
+def _write_partial_file(filename: str, content: str):
+    with Path(filename).open("w") as f:
+        f.write(f"``` output\n{content}\n```\n")


-for command in subcommands:
-    print(f"Running for {command}")
-    result = subprocess.run(["freqtrade", command, "--help"], capture_output=True, text=True)
+def _get_help_output(parser) -> str:
+    """Capture the help output from a parser."""
+    output = StringIO()
+    parser.print_help(file=output)
+    return output.getvalue()

-    with Path(f"docs/commands/{command}.md").open("w") as f:
-        f.write(f"```\n{result.stdout}\n```\n")
+
+def extract_command_partials():
+    # Set terminal width to 80 columns for consistent output formatting
+    os.environ["COLUMNS"] = "80"
+
+    # Import Arguments here to avoid circular imports and ensure COLUMNS is set
+    from freqtrade.commands.arguments import Arguments
+
+    subcommands = [
+        "trade",
+        "create-userdir",
+        "new-config",
+        "show-config",
+        "new-strategy",
+        "download-data",
+        "convert-data",
+        "convert-trade-data",
+        "trades-to-ohlcv",
+        "list-data",
+        "backtesting",
+        "backtesting-show",
+        "backtesting-analysis",
+        "edge",
+        "hyperopt",
+        "hyperopt-list",
+        "hyperopt-show",
+        "list-exchanges",
+        "list-markets",
+        "list-pairs",
+        "list-strategies",
+        "list-hyperoptloss",
+        "list-freqaimodels",
+        "list-timeframes",
+        "show-trades",
+        "test-pairlist",
+        "convert-db",
+        "install-ui",
+        "plot-dataframe",
+        "plot-profit",
+        "webserver",
+        "strategy-updater",
+        "lookahead-analysis",
+        "recursive-analysis",
+    ]
+
+    # Build the Arguments class to get the parser with all subcommands
+    args = Arguments(None)
+    args._build_subcommands()
+
+    # Get main help output
+    main_help = _get_help_output(args.parser)
+    _write_partial_file("docs/commands/main.md", main_help)
+
+    # Get subparsers from the main parser
+    # The subparsers are stored in _subparsers._group_actions[0].choices
+    subparsers_action = None
+    for action in args.parser._subparsers._group_actions:
+        if hasattr(action, "choices"):
+            subparsers_action = action
+            break
+
+    if subparsers_action is None:
+        raise RuntimeError("Could not find subparsers in the main parser")
+
+    for command in subcommands:
+        print(f"Running for {command}")
+        if command in subparsers_action.choices:
+            subparser = subparsers_action.choices[command]
+            help_output = _get_help_output(subparser)
+            _write_partial_file(f"docs/commands/{command}.md", help_output)
+        else:
+            print(f" Warning: subcommand '{command}' not found in parser")
+
+    # freqtrade-client still uses subprocess as requested
+    print("Running for freqtrade-client")
+    result_client = subprocess.run(["freqtrade-client", "--show"], capture_output=True, text=True)
+
+    _write_partial_file("docs/commands/freqtrade-client.md", result_client.stdout)
+
+
+if __name__ == "__main__":
+    if sys.version_info < (3, 13):  # pragma: no cover
+        sys.exit(
+            "argparse output changed in Python 3.13+. "
+            "To keep command partials up to date, please run this script with Python 3.13+."
+        )
+    extract_command_partials()
@@ -1,35 +0,0 @@
-if [ -z "$1" ]; then
-  INSTALL_LOC=/usr/local
-else
-  INSTALL_LOC=${1}
-fi
-echo "Installing to ${INSTALL_LOC}"
-if [ -n "$2" ] || [ ! -f "${INSTALL_LOC}/lib/libta_lib.a" ]; then
-  tar zxvf ta-lib-0.4.0-src.tar.gz
-  cd ta-lib \
-  && sed -i.bak "s|0.00000001|0.000000000000000001 |g" src/ta_func/ta_utility.h \
-  && echo "Downloading gcc config.guess and config.sub" \
-  && curl -s 'https://raw.githubusercontent.com/gcc-mirror/gcc/master/config.guess' -o config.guess \
-  && curl -s 'https://raw.githubusercontent.com/gcc-mirror/gcc/master/config.sub' -o config.sub \
-  && ./configure --prefix=${INSTALL_LOC}/ \
-  && make
-  if [ $? -ne 0 ]; then
-    echo "Failed building ta-lib."
-    cd .. && rm -rf ./ta-lib/
-    exit 1
-  fi
-  if [ -z "$2" ]; then
-    which sudo && sudo make install || make install
-    if [ -x "$(command -v apt-get)" ]; then
-      echo "Updating library path using ldconfig"
-      sudo ldconfig
-    fi
-  else
-    # Don't install with sudo
-    make install
-  fi
-
-  cd .. && rm -rf ./ta-lib/
-else
-  echo "TA-lib already installed, skipping installation"
-fi
@@ -1,10 +0,0 @@
-# vendored Wheels compiled via https://github.com/xmatthias/ta-lib-python/tree/ta_bundled_040
-
-python -m pip install --upgrade pip
-python -c "import sys; print(f'{sys.version_info.major}.{sys.version_info.minor}')"
-
-pip install -U wheel "numpy<2"
-pip install --only-binary ta-lib --find-links=build_helpers\ ta-lib
-
-pip install -r requirements-dev.txt
-pip install -e .
@@ -1,5 +1,7 @@
 # File used in CI to ensure pre-commit dependencies are kept up-to-date.

+import argparse
+import re
 import sys
 from pathlib import Path

@@ -10,16 +12,48 @@ pre_commit_file = Path(".pre-commit-config.yaml")
 require_dev = Path("requirements-dev.txt")
 require = Path("requirements.txt")

+
+parser = argparse.ArgumentParser()
+parser.add_argument("--update", action="store_true")
+args = parser.parse_args()
+
+
+def replace_dependency_version(pre_commit_text: str, dependency: str) -> tuple[str, bool]:
+    """
+    Regex-based replacement of a dependency version in the pre-commit config file.
+    using regex here ensures we only replace the version of the dependency while
+    keeping the overall file intact.
+    """
+    package_name = dependency.split("==", 1)[0]
+    pattern = re.compile(rf"^(\s*-\s+){re.escape(package_name)}==.*$", re.MULTILINE)
+    updated_text, replacements = pattern.subn(rf"\1{dependency}", pre_commit_text, count=1)
+    return updated_text, replacements > 0 and updated_text != pre_commit_text
+
+
 with require_dev.open("r") as rfile:
    requirements = rfile.readlines()

 with require.open("r") as rfile:
    requirements.extend(rfile.readlines())

-# Extract types only
-type_reqs = [
-    r.strip("\n") for r in requirements if r.startswith("types-") or r.startswith("SQLAlchemy")
-]
+# Extract relevant types only
+supported = ("types-", "SQLAlchemy", "scipy-stubs")
+
+# Find relevant dependencies
+# Only keep the first part of the line up to the first space
+type_reqs = [r.strip("\n").split()[0] for r in requirements if r.startswith(supported)]
+
+with pre_commit_file.open("r") as file:
+    pre_commit_text = file.read()
+
+updated = False
+for req in type_reqs:
+    pre_commit_text, req_updated = replace_dependency_version(pre_commit_text, req)
+    updated = updated or req_updated
+
+if args.update and updated:
+    with pre_commit_file.open("w") as file:
+        file.write(pre_commit_text)

 with pre_commit_file.open("r") as file:
    f = yaml.load(file, Loader=yaml.SafeLoader)
@@ -38,12 +72,20 @@ for hook in hooks:

 for req in type_reqs:
    if req not in hooks:
-        errors.append(f"{req} is missing in pre-config file.")
+        errors.append(f"{req} is missing in pre-commit config file.")
+
+if updated:
+    if args.update:
+        errors.append(".pre-commit-config.yaml was updated to match the requirements files.")
+    else:
+        errors.append(
+            ".pre-commit-config.yaml is outdated. Run build_helpers/pre_commit_update.py --update."
+        )


 if errors:
    for e in errors:
        print(e)
-    sys.exit(1)
+    sys.exit(1 if not (args.update and updated) else 0)

 sys.exit(0)
@@ -1,119 +0,0 @@
-#!/bin/sh
-
-# Use BuildKit, otherwise building on ARM fails
-export DOCKER_BUILDKIT=1
-
-IMAGE_NAME=freqtradeorg/freqtrade
-CACHE_IMAGE=freqtradeorg/freqtrade_cache
-GHCR_IMAGE_NAME=ghcr.io/freqtrade/freqtrade
-
-# Replace / with _ to create a valid tag
-TAG=$(echo "${BRANCH_NAME}" | sed -e "s/\//_/g")
-TAG_PLOT=${TAG}_plot
-TAG_FREQAI=${TAG}_freqai
-TAG_FREQAI_RL=${TAG_FREQAI}rl
-TAG_FREQAI_TORCH=${TAG_FREQAI}torch
-TAG_PI="${TAG}_pi"
-
-TAG_ARM=${TAG}_arm
-TAG_PLOT_ARM=${TAG_PLOT}_arm
-TAG_FREQAI_ARM=${TAG_FREQAI}_arm
-TAG_FREQAI_RL_ARM=${TAG_FREQAI_RL}_arm
-
-echo "Running for ${TAG}"
-
-# Add commit and commit_message to docker container
-echo "${GITHUB_SHA}" > freqtrade_commit
-
-if [ "${GITHUB_EVENT_NAME}" = "schedule" ]; then
-    echo "event ${GITHUB_EVENT_NAME}: full rebuild - skipping cache"
-    # Build regular image
-    docker build -t freqtrade:${TAG_ARM} .
-
-else
-    echo "event ${GITHUB_EVENT_NAME}: building with cache"
-    # Build regular image
-    docker pull ${IMAGE_NAME}:${TAG_ARM}
-    docker build --cache-from ${IMAGE_NAME}:${TAG_ARM} -t freqtrade:${TAG_ARM} .
-
-fi
-
-if [ $? -ne 0 ]; then
-    echo "failed building multiarch images"
-    return 1
-fi
-
-docker build --build-arg sourceimage=freqtrade --build-arg sourcetag=${TAG_ARM} -t freqtrade:${TAG_PLOT_ARM} -f docker/Dockerfile.plot .
-docker build --build-arg sourceimage=freqtrade --build-arg sourcetag=${TAG_ARM} -t freqtrade:${TAG_FREQAI_ARM} -f docker/Dockerfile.freqai .
-docker build --build-arg sourceimage=freqtrade --build-arg sourcetag=${TAG_FREQAI_ARM} -t freqtrade:${TAG_FREQAI_RL_ARM} -f docker/Dockerfile.freqai_rl .
-
-# Tag image for upload and next build step
-docker tag freqtrade:$TAG_ARM ${CACHE_IMAGE}:$TAG_ARM
-docker tag freqtrade:$TAG_PLOT_ARM ${CACHE_IMAGE}:$TAG_PLOT_ARM
-docker tag freqtrade:$TAG_FREQAI_ARM ${CACHE_IMAGE}:$TAG_FREQAI_ARM
-docker tag freqtrade:$TAG_FREQAI_RL_ARM ${CACHE_IMAGE}:$TAG_FREQAI_RL_ARM
-
-# Run backtest
-docker run --rm -v $(pwd)/tests/testdata/config.tests.json:/freqtrade/config.json:ro -v $(pwd)/tests:/tests freqtrade:${TAG_ARM} backtesting --datadir /tests/testdata --strategy-path /tests/strategy/strats/ --strategy StrategyTestV3
-
-if [ $? -ne 0 ]; then
-    echo "failed running backtest"
-    return 1
-fi
-
-docker images
-
-docker push ${CACHE_IMAGE}:$TAG_PLOT_ARM
-docker push ${CACHE_IMAGE}:$TAG_FREQAI_ARM
-docker push ${CACHE_IMAGE}:$TAG_FREQAI_RL_ARM
-docker push ${CACHE_IMAGE}:$TAG_ARM
-
-# Create multi-arch image
-# Make sure that all images contained here are pushed to github first.
-# Otherwise installation might fail.
-echo "create manifests"
-
-docker manifest create ${IMAGE_NAME}:${TAG} ${CACHE_IMAGE}:${TAG} ${CACHE_IMAGE}:${TAG_ARM} ${IMAGE_NAME}:${TAG_PI}
-docker manifest push -p ${IMAGE_NAME}:${TAG}
-
-docker manifest create ${IMAGE_NAME}:${TAG_PLOT} ${CACHE_IMAGE}:${TAG_PLOT} ${CACHE_IMAGE}:${TAG_PLOT_ARM}
-docker manifest push -p ${IMAGE_NAME}:${TAG_PLOT}
-
-docker manifest create ${IMAGE_NAME}:${TAG_FREQAI} ${CACHE_IMAGE}:${TAG_FREQAI} ${CACHE_IMAGE}:${TAG_FREQAI_ARM}
-docker manifest push -p ${IMAGE_NAME}:${TAG_FREQAI}
-
-docker manifest create ${IMAGE_NAME}:${TAG_FREQAI_RL} ${CACHE_IMAGE}:${TAG_FREQAI_RL} ${CACHE_IMAGE}:${TAG_FREQAI_RL_ARM}
-docker manifest push -p ${IMAGE_NAME}:${TAG_FREQAI_RL}
-
-# Create special Torch tag - which is identical to the RL tag.
-docker manifest create ${IMAGE_NAME}:${TAG_FREQAI_TORCH} ${CACHE_IMAGE}:${TAG_FREQAI_RL} ${CACHE_IMAGE}:${TAG_FREQAI_RL_ARM}
-docker manifest push -p ${IMAGE_NAME}:${TAG_FREQAI_TORCH}
-
-# copy images to ghcr.io
-
-alias crane="docker run --rm -i -v $(pwd)/.crane:/home/nonroot/.docker/ gcr.io/go-containerregistry/crane"
-mkdir .crane
-chmod a+rwx .crane
-
-echo "${GHCR_TOKEN}" | crane auth login ghcr.io -u "${GHCR_USERNAME}" --password-stdin
-
-crane copy ${IMAGE_NAME}:${TAG_FREQAI_RL} ${GHCR_IMAGE_NAME}:${TAG_FREQAI_RL}
-crane copy ${IMAGE_NAME}:${TAG_FREQAI_RL} ${GHCR_IMAGE_NAME}:${TAG_FREQAI_TORCH}
-crane copy ${IMAGE_NAME}:${TAG_FREQAI} ${GHCR_IMAGE_NAME}:${TAG_FREQAI}
-crane copy ${IMAGE_NAME}:${TAG_PLOT} ${GHCR_IMAGE_NAME}:${TAG_PLOT}
-crane copy ${IMAGE_NAME}:${TAG} ${GHCR_IMAGE_NAME}:${TAG}
-
-# Tag as latest for develop builds
-if [ "${TAG}" = "develop" ]; then
-    echo 'Tagging image as latest'
-    docker manifest create ${IMAGE_NAME}:latest ${CACHE_IMAGE}:${TAG_ARM} ${IMAGE_NAME}:${TAG_PI} ${CACHE_IMAGE}:${TAG}
-    docker manifest push -p ${IMAGE_NAME}:latest
-
-    crane copy ${IMAGE_NAME}:latest ${GHCR_IMAGE_NAME}:latest
-fi
-
-docker images
-rm -rf .crane
-
-# Cleanup old images from arm64 node.
-docker image prune -a --force --filter "until=24h"
@@ -1,89 +0,0 @@
-#!/bin/sh
-
-# The below assumes a correctly setup docker buildx environment
-
-IMAGE_NAME=freqtradeorg/freqtrade
-CACHE_IMAGE=freqtradeorg/freqtrade_cache
-# Replace / with _ to create a valid tag
-TAG=$(echo "${BRANCH_NAME}" | sed -e "s/\//_/g")
-TAG_PLOT=${TAG}_plot
-TAG_FREQAI=${TAG}_freqai
-TAG_FREQAI_RL=${TAG_FREQAI}rl
-TAG_PI="${TAG}_pi"
-
-PI_PLATFORM="linux/arm/v7"
-echo "Running for ${TAG}"
-CACHE_TAG=${CACHE_IMAGE}:${TAG_PI}_cache
-
-# Add commit and commit_message to docker container
-echo "${GITHUB_SHA}" > freqtrade_commit
-
-if [ "${GITHUB_EVENT_NAME}" = "schedule" ]; then
-    echo "event ${GITHUB_EVENT_NAME}: full rebuild - skipping cache"
-    # Build regular image
-    docker build -t freqtrade:${TAG} .
-    # Build PI image
-    docker buildx build \
-        --cache-to=type=registry,ref=${CACHE_TAG} \
-        -f docker/Dockerfile.armhf \
-        --platform ${PI_PLATFORM} \
-        -t ${IMAGE_NAME}:${TAG_PI} \
-        --push \
-        --provenance=false \
-        .
-else
-    echo "event ${GITHUB_EVENT_NAME}: building with cache"
-    # Build regular image
-    docker pull ${IMAGE_NAME}:${TAG}
-    docker build --cache-from ${IMAGE_NAME}:${TAG} -t freqtrade:${TAG} .
-
-    # Pull last build to avoid rebuilding the whole image
-    # docker pull --platform ${PI_PLATFORM} ${IMAGE_NAME}:${TAG}
-    # disable provenance due to https://github.com/docker/buildx/issues/1509
-    docker buildx build \
-        --cache-from=type=registry,ref=${CACHE_TAG} \
-        --cache-to=type=registry,ref=${CACHE_TAG} \
-        -f docker/Dockerfile.armhf \
-        --platform ${PI_PLATFORM} \
-        -t ${IMAGE_NAME}:${TAG_PI} \
-        --push \
-        --provenance=false \
-        .
-fi
-
-if [ $? -ne 0 ]; then
-    echo "failed building multiarch images"
-    return 1
-fi
-# Tag image for upload and next build step
-docker tag freqtrade:$TAG ${CACHE_IMAGE}:$TAG
-
-docker build --build-arg sourceimage=freqtrade --build-arg sourcetag=${TAG} -t freqtrade:${TAG_PLOT} -f docker/Dockerfile.plot .
-docker build --build-arg sourceimage=freqtrade --build-arg sourcetag=${TAG} -t freqtrade:${TAG_FREQAI} -f docker/Dockerfile.freqai .
-docker build --build-arg sourceimage=freqtrade --build-arg sourcetag=${TAG_FREQAI} -t freqtrade:${TAG_FREQAI_RL} -f docker/Dockerfile.freqai_rl .
-
-docker tag freqtrade:$TAG_PLOT ${CACHE_IMAGE}:$TAG_PLOT
-docker tag freqtrade:$TAG_FREQAI ${CACHE_IMAGE}:$TAG_FREQAI
-docker tag freqtrade:$TAG_FREQAI_RL ${CACHE_IMAGE}:$TAG_FREQAI_RL
-
-# Run backtest
-docker run --rm -v $(pwd)/tests/testdata/config.tests.json:/freqtrade/config.json:ro -v $(pwd)/tests:/tests freqtrade:${TAG} backtesting --datadir /tests/testdata --strategy-path /tests/strategy/strats/ --strategy StrategyTestV3
-
-if [ $? -ne 0 ]; then
-    echo "failed running backtest"
-    return 1
-fi
-
-docker images
-
-docker push ${CACHE_IMAGE}:$TAG
-docker push ${CACHE_IMAGE}:$TAG_PLOT
-docker push ${CACHE_IMAGE}:$TAG_FREQAI
-docker push ${CACHE_IMAGE}:$TAG_FREQAI_RL
-
-docker images
-
-if [ $? -ne 0 ]; then
-    echo "failed building image"
-    return 1
-fi
@@ -180,6 +180,16 @@
      "description": "Offset for profit exit. \nUsually specified in the strategy and missing in the configuration.",
      "type": "number"
    },
+    "recursive_strategy_search": {
+      "description": "Enable recursive strategy search.",
+      "type": "boolean"
+    },
+    "user_data_dir": {
+      "description": "Path to the user data directory."
+    },
+    "datadir": {
+      "description": "Path to the data directory."
+    },
    "fee": {
      "description": "Trading fee percentage. Can help to simulate slippage in backtesting",
      "type": "number",
@@ -258,10 +268,77 @@
          "day",
          "week",
          "month",
-          "year"
+          "year",
+          "weekday"
        ]
      }
    },
+    "backtest_cache": {
+      "description": "Load a cached backtest result no older than specified age.",
+      "type": "string",
+      "enum": [
+        "none",
+        "day",
+        "week",
+        "month"
+      ]
+    },
+    "skip_wallet_history_migration": {
+      "description": "Disable wallet history migration.",
+      "type": "boolean"
+    },
+    "hyperopt_path": {
+      "description": "Specify additional lookup path for Hyperopt Loss functions.",
+      "type": "string"
+    },
+    "epochs": {
+      "description": "Number of training epochs for Hyperopt.",
+      "type": "integer",
+      "minimum": 1
+    },
+    "early_stop": {
+      "description": "Early stop hyperopt if no improvement after <epochs>. Set to 0 to disable.",
+      "type": "integer",
+      "minimum": 0
+    },
+    "spaces": {
+      "description": "Hyperopt parameter spaces to optimize. Default is the default set andincludes all spaces except for 'trailing', 'protection', and 'trades'.",
+      "type": "array",
+      "items": {
+        "type": "string"
+      },
+      "default": [
+        "default"
+      ]
+    },
+    "analyze_per_epoch": {
+      "description": "Perform analysis after each epoch in Hyperopt.",
+      "type": "boolean"
+    },
+    "print_all": {
+      "description": "Print all hyperopt trials, not just the best ones.",
+      "type": "boolean",
+      "default": false
+    },
+    "hyperopt_jobs": {
+      "description": "The number of concurrently running jobs for hyperoptimization (hyperopt worker processes). If -1 (default), all CPUs are used, for -2, all CPUs but one are used, etc. If 1 is given, no parallel computing is used.",
+      "type": "integer",
+      "default": -1
+    },
+    "hyperopt_random_state": {
+      "description": "Random state for hyperopt trials.",
+      "type": "integer",
+      "minimum": 0
+    },
+    "hyperopt_min_trades": {
+      "description": "Minimum number of trades per epoch for hyperopt.",
+      "type": "integer",
+      "minimum": 0
+    },
+    "hyperopt_loss": {
+      "description": "The class name of the hyperopt loss function class (IHyperOptLoss). Different functions can generate completely different results, since the target for optimization is different. Built-in Hyperopt-loss-functions are: ShortTradeDurHyperOptLoss, OnlyProfitHyperOptLoss, SharpeHyperOptLoss, SharpeHyperOptLossDaily, SortinoHyperOptLoss, SortinoHyperOptLossDaily, CalmarHyperOptLoss, MaxDrawDownHyperOptLoss, MaxDrawDownRelativeHyperOptLoss, MaxDrawDownPerPairHyperOptLoss, ProfitDrawDownHyperOptLoss, MultiMetricHyperOptLoss",
+      "type": "string"
+    },
    "bot_name": {
      "description": "Name of the trading bot. Passed via API to a client.",
      "type": "string"
@@ -538,10 +615,6 @@
      "description": "Exchange configuration.",
      "$ref": "#/definitions/exchange"
    },
-    "edge": {
-      "description": "Edge configuration.",
-      "$ref": "#/definitions/edge"
-    },
    "log_config": {
      "description": "Logging configuration.",
      "$ref": "#/definitions/logging"
@@ -566,6 +639,7 @@
    "pairlists": {
      "description": "Configuration for pairlists.",
      "type": "array",
+      "minItems": 1,
      "items": {
        "type": "object",
        "properties": {
@@ -579,7 +653,9 @@
              "ProducerPairList",
              "RemotePairList",
              "MarketCapPairList",
+              "CrossMarketPairList",
              "AgeFilter",
+              "DelistFilter",
              "FullTradesFilter",
              "OffsetFilter",
              "PerformanceFilter",
@@ -986,7 +1062,9 @@
        },
        "jwt_secret_key": {
          "description": "Secret key for JWT authentication.",
-          "type": "string"
+          "type": "string",
+          "default": "somethingRandomSomethingRandom123",
+          "minLength": 32
        },
        "CORS_origins": {
          "description": "List of allowed CORS origins.",
@@ -1009,7 +1087,8 @@
        "listen_ip_address",
        "listen_port",
        "username",
-        "password"
+        "password",
+        "jwt_secret_key"
      ]
    },
    "db_url": {
@@ -1247,7 +1326,11 @@
          "type": "object"
        },
        "ccxt_async_config": {
-          "description": "CCXT asynchronous configuration settings.",
+          "description": "CCXT asynchronous configuration settings.Usually ccxt_config should be used instead.",
+          "type": "object"
+        },
+        "ccxt_sync_config": {
+          "description": "CCXT synchronous configuration settings. Usually ccxt_config should be used instead.",
          "type": "object"
        }
      },
@@ -1255,52 +1338,6 @@
        "name"
      ]
    },
-    "edge": {
-      "type": "object",
-      "properties": {
-        "enabled": {
-          "type": "boolean"
-        },
-        "process_throttle_secs": {
-          "type": "integer",
-          "minimum": 600
-        },
-        "calculate_since_number_of_days": {
-          "type": "integer"
-        },
-        "allowed_risk": {
-          "type": "number"
-        },
-        "stoploss_range_min": {
-          "type": "number"
-        },
-        "stoploss_range_max": {
-          "type": "number"
-        },
-        "stoploss_range_step": {
-          "type": "number"
-        },
-        "minimum_winrate": {
-          "type": "number"
-        },
-        "minimum_expectancy": {
-          "type": "number"
-        },
-        "min_trade_number": {
-          "type": "number"
-        },
-        "max_trade_duration_minute": {
-          "type": "integer"
-        },
-        "remove_pumps": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "process_throttle_secs",
-        "allowed_risk"
-      ]
-    },
    "logging": {
      "type": "object",
      "properties": {
@@ -1495,6 +1532,11 @@
          "type": "boolean",
          "default": false
        },
+        "override_exchange_check": {
+          "description": "Override the exchange check to force FreqAI to use exchanges that may not have enough historic data. Turn this to True if you know your FreqAI model and strategy do not require historical data.",
+          "type": "boolean",
+          "default": false
+        },
        "feature_parameters": {
          "description": "The parameters used to engineer the feature set",
          "type": "object",
@@ -2,7 +2,7 @@
    "$schema": "https://schema.freqtrade.io/schema.json",
    "max_open_trades": 3,
    "stake_currency": "USDT",
-    "stake_amount": 0.05,
+    "stake_amount": 30,
    "tradable_balance_ratio": 0.99,
    "fiat_display_currency": "USD",
    "timeframe": "5m",
@@ -70,7 +70,7 @@
        "listen_ip_address": "127.0.0.1",
        "listen_port": 8080,
        "verbosity": "error",
-        "jwt_secret_key": "somethingrandom",
+        "jwt_secret_key": "somethingRandomSomethingRandom123",
        "CORS_origins": [],
        "username": "freqtrader",
        "password": "SuperSecurePassword"
@@ -25,10 +25,10 @@
    "trading_mode": "spot",
    "margin_mode": "",
    "minimal_roi": {
-        "40":  0.0,
-        "30":  0.01,
-        "20":  0.02,
-        "0":  0.04
+        "40": 0.0,
+        "30": 0.01,
+        "20": 0.02,
+        "0": 0.04
    },
    "stoploss": -0.10,
    "unfilledtimeout": {
@@ -47,7 +47,7 @@
            "bids_to_ask_delta": 1
        }
    },
-    "exit_pricing":{
+    "exit_pricing": {
        "price_side": "same",
        "use_order_book": true,
        "order_book_top": 1,
@@ -70,18 +70,38 @@
        "exit": "GTC"
    },
    "pairlists": [
-        {"method": "StaticPairList"},
-        {"method": "FullTradesFilter"},
+        {
+            "method": "StaticPairList"
+        },
+        {
+            "method": "DelistFilter",
+            "max_days_from_now": 0,
+        },
+        {
+            "method": "FullTradesFilter"
+        },
        {
            "method": "VolumePairList",
            "number_assets": 20,
            "sort_key": "quoteVolume",
            "refresh_period": 1800
        },
-        {"method": "AgeFilter", "min_days_listed": 10},
-        {"method": "PrecisionFilter"},
-        {"method": "PriceFilter", "low_price_ratio": 0.01, "min_price": 0.00000010},
-        {"method": "SpreadFilter", "max_spread_ratio": 0.005},
+        {
+            "method": "AgeFilter",
+            "min_days_listed": 10
+        },
+        {
+            "method": "PrecisionFilter"
+        },
+        {
+            "method": "PriceFilter",
+            "low_price_ratio": 0.01,
+            "min_price": 0.00000010
+        },
+        {
+            "method": "SpreadFilter",
+            "max_spread_ratio": 0.005
+        },
        {
            "method": "RangeStabilityFilter",
            "lookback_days": 10,
@@ -121,20 +141,6 @@
        "outdated_offset": 5,
        "markets_refresh_interval": 60
    },
-    "edge": {
-        "enabled": false,
-        "process_throttle_secs": 3600,
-        "calculate_since_number_of_days": 7,
-        "allowed_risk": 0.01,
-        "stoploss_range_min": -0.01,
-        "stoploss_range_max": -0.1,
-        "stoploss_range_step": -0.01,
-        "minimum_winrate": 0.60,
-        "minimum_expectancy": 0.20,
-        "min_trade_number": 10,
-        "max_trade_duration_minute": 1440,
-        "remove_pumps": false
-    },
    "telegram": {
        "enabled": false,
        "token": "your_telegram_token",
@@ -171,7 +177,7 @@
        "listen_port": 8080,
        "verbosity": "error",
        "enable_openapi": false,
-        "jwt_secret_key": "somethingrandom",
+        "jwt_secret_key": "somethingRandomSomethingRandom123",
        "CORS_origins": [],
        "username": "freqtrader",
        "password": "SuperSecurePassword",
@@ -180,12 +186,12 @@
    "external_message_consumer": {
        "enabled": false,
        "producers": [
-          {
-            "name": "default",
-            "host": "127.0.0.2",
-            "port": 8080,
-            "ws_token": "secret_ws_t0ken."
-          }
+            {
+                "name": "default",
+                "host": "127.0.0.2",
+                "port": 8080,
+                "ws_token": "secret_ws_t0ken."
+            }
        ],
        "wait_timeout": 300,
        "ping_timeout": 10,
@@ -75,7 +75,7 @@
        "listen_ip_address": "127.0.0.1",
        "listen_port": 8080,
        "verbosity": "error",
-        "jwt_secret_key": "somethingrandom",
+        "jwt_secret_key": "somethingRandomSomethingRandom123",
        "CORS_origins": [],
        "username": "freqtrader",
        "password": "SuperSecurePassword"
@@ -1,10 +1,10 @@
-FROM python:3.11.12-slim-bookworm as base
+FROM python:3.11.15-slim-bookworm AS base

 # Setup env
-ENV LANG C.UTF-8
-ENV LC_ALL C.UTF-8
-ENV PYTHONDONTWRITEBYTECODE 1
-ENV PYTHONFAULTHANDLER 1
+ENV LANG=C.UTF-8
+ENV LC_ALL=C.UTF-8
+ENV PYTHONDONTWRITEBYTECODE=1
+ENV PYTHONFAULTHANDLER=1
 ENV PATH=/home/ftuser/.local/bin:$PATH
 ENV FT_APP_ENV="docker"

@@ -22,7 +22,7 @@ RUN mkdir /freqtrade \
 WORKDIR /freqtrade

 # Install dependencies
-FROM base as python-deps
+FROM base AS python-deps
 RUN  apt-get update \
  && apt-get -y install build-essential libssl-dev libffi-dev libgfortran5 pkg-config cmake gcc \
  && apt-get clean \
@@ -34,14 +34,13 @@ COPY build_helpers/* /tmp/
 # Install dependencies
 COPY --chown=ftuser:ftuser requirements.txt /freqtrade/
 USER ftuser
-RUN  pip install --user --no-cache-dir "numpy<2" \
-  && pip install --user --no-index --find-links /tmp/ pyarrow TA-Lib \
+RUN  pip install --user --only-binary=:all: --find-links /tmp/ pyarrow TA-Lib \
  && pip install --user --no-cache-dir -r requirements.txt

 # Copy dependencies to runtime-image
-FROM base as runtime-image
+FROM base AS runtime-image
 COPY --from=python-deps /usr/local/lib /usr/local/lib
-ENV LD_LIBRARY_PATH /usr/local/lib
+ENV LD_LIBRARY_PATH=/usr/local/lib

 COPY --from=python-deps --chown=ftuser:ftuser /home/ftuser/.local /home/ftuser/.local

@@ -49,7 +48,7 @@ USER ftuser
 # Install and execute
 COPY --chown=ftuser:ftuser . /freqtrade/

-RUN pip install -e . --user --no-cache-dir --no-build-isolation\
+RUN pip install -e . --user --no-cache-dir \
  && mkdir /freqtrade/user_data/ \
  && freqtrade install-ui

@@ -1,10 +0,0 @@
-FROM freqtradeorg/freqtrade:develop
-
-# Install dependencies
-COPY requirements-dev.txt /freqtrade/
-
-RUN pip install numpy --user --no-cache-dir \
-  && pip install -r requirements-dev.txt --user --no-cache-dir
-
-# Empty the ENTRYPOINT to allow all commands
-ENTRYPOINT []
@@ -41,34 +41,36 @@ ranging from the simplest (0) to the most detailed per pair, per buy and per sel
 * 1: profit summaries grouped by enter_tag
 * 2: profit summaries grouped by enter_tag and exit_tag
 * 3: profit summaries grouped by pair and enter_tag
-* 4: profit summaries grouped by pair, enter_ and exit_tag (this can get quite large)
+* 4: profit summaries grouped by pair, enter_tag and exit_tag (this can get quite large)
 * 5: profit summaries grouped by exit_tag

 More options are available by running with the `-h` option.

-### Using export-filename
+### Using backtest-filename

-Normally, `backtesting-analysis` uses the latest backtest results, but if you wanted to go
-back to a previous backtest output, you need to supply the `--export-filename` option.
-You can supply the same parameter to `backtest-analysis` with the name of the final backtest
-output file. This allows you to keep historical versions of backtest results and re-analyse
-them at a later date:
+By default, `backtesting-analysis` processes the most recent backtest results in the `user_data/backtest_results` directory. 
+If you want to analyze results from an earlier backtest, use the `--backtest-filename` option to specify the desired file. This lets you revisit and re-analyze historical backtest outputs at any time by providing the filename of the relevant backtest result:

 ``` bash
-freqtrade backtesting -c <config.json> --timeframe <tf> --strategy <strategy_name> --timerange=<timerange> --export=signals --export-filename=/tmp/mystrat_backtest.json
+freqtrade backtesting -c <config.json> --strategy <strategy_name> --timerange <timerange> --export signals --backtest-filename backtest-result-2025-03-05_20-38-34.zip
 ```

-You should see some output similar to below in the logs with the name of the timestamped
-filename that was exported:
+You should see some output similar to below in the logs with the name of the timestamped filename that was exported:

 ```
-2022-06-14 16:28:32,698 - freqtrade.misc - INFO - dumping json to "/tmp/mystrat_backtest-2022-06-14_16-28-32.json"
+2022-06-14 16:28:32,698 - freqtrade.misc - INFO - dumping json to "mystrat_backtest-2022-06-14_16-28-32.json"
 ```

 You can then use that filename in `backtesting-analysis`:

+``` bash
+freqtrade backtesting-analysis -c <config.json> --backtest-filename=backtest-result-2025-03-05_20-38-34.zip
 ```
-freqtrade backtesting-analysis -c <config.json> --export-filename=/tmp/mystrat_backtest-2022-06-14_16-28-32.json
+
+To use a result from a different results directory, you can use  `--backtest-directory` to specify the directory
+
+``` bash
+freqtrade backtesting-analysis -c <config.json> --backtest-directory custom_results/ --backtest-filename backtest-result-2025-03-05_20-38-34.zip
 ```

 ### Tuning the buy tags and sell tags to display
@@ -82,7 +84,7 @@ To show only certain buy and sell tags in the displayed output, use the followin

 For example:

-```bash
+``` bash
 freqtrade backtesting-analysis -c <config.json> --analysis-groups 0 2 --enter-reason-list enter_tag_a enter_tag_b --exit-reason-list roi custom_exit_tag_a stop_loss
 ```

@@ -93,7 +95,7 @@ values present on signal candles to allow fine-grained investigation and tuning
 indicators. To print out a column for a given set of indicators, use the `--indicator-list`
 option:

-```bash
+``` bash
 freqtrade backtesting-analysis -c <config.json> --analysis-groups 0 2 --enter-reason-list enter_tag_a enter_tag_b --exit-reason-list roi custom_exit_tag_a stop_loss --indicator-list rsi rsi_1h bb_lowerband ema_9 macd macdsignal
 ```

@@ -105,24 +107,24 @@ output.
    The indicator values will be displayed for both entry and exit points. If `--indicator-list all` is specified, 
    only the indicators at the entry point will be shown to avoid excessively large lists, which could occur depending on the strategy.

-There are a range of candle and trade-related fields that are included in the analysis so are 
+There are a range of candle and trade-related fields that are included in the analysis so are
 automatically accessible by including them on the indicator-list, and these include:

- **open_date     :** trade open datetime
- **close_date    :** trade close datetime
- **min_rate      :** minimum price seen throughout the position
- **max_rate      :** maximum price seen throughout the position
- **open          :** signal candle open price
- **close         :** signal candle close price
- **high          :** signal candle high price
- **low           :** signal candle low price
- **volume        :** signal candle volume
- **profit_ratio  :** trade profit ratio
- **profit_abs    :** absolute profit return of the trade 
+* **open_date     :** trade open datetime
+* **close_date    :** trade close datetime
+* **min_rate      :** minimum price seen throughout the position
+* **max_rate      :** maximum price seen throughout the position
+* **open          :** signal candle open price
+* **close         :** signal candle close price
+* **high          :** signal candle high price
+* **low           :** signal candle low price
+* **volume        :** signal candle volume
+* **profit_ratio  :** trade profit ratio
+* **profit_abs    :** absolute profit return of the trade 

 #### Sample Output for Indicator Values

-```bash
+``` bash
 freqtrade backtesting-analysis -c user_data/config.json --analysis-groups 0 --indicator-list chikou_span tenkan_sen 
 ```

@@ -155,13 +157,13 @@ The `--indicator-list` option, by default, displays indicator values for both en

 Example: Display indicator values at entry signals:

-```bash
+``` bash
 freqtrade backtesting-analysis -c user_data/config.json --analysis-groups 0 --indicator-list chikou_span tenkan_sen --entry-only
 ```

 Example: Display indicator values at exit signals:

-```bash
+``` bash
 freqtrade backtesting-analysis -c user_data/config.json --analysis-groups 0 --indicator-list chikou_span tenkan_sen --exit-only
 ```

@@ -178,7 +180,7 @@ To show only trades between dates within your backtested timerange, supply the u

 For example, if your backtest timerange was `20220101-20221231` but you only want to output trades in January:

-```bash
+``` bash
 freqtrade backtesting-analysis -c <config.json> --timerange 20220101-20220201
 ```

@@ -186,7 +188,7 @@ freqtrade backtesting-analysis -c <config.json> --timerange 20220101-20220201

 Use the `--rejected-signals` option to print out rejected signals.

-```bash
+``` bash
 freqtrade backtesting-analysis -c <config.json> --rejected-signals
 ```

@@ -195,13 +197,13 @@ freqtrade backtesting-analysis -c <config.json> --rejected-signals
 Some of the tabular outputs can become large, so printing them out to the terminal is not preferable.
 Use the `--analysis-to-csv` option to disable printing out of tables to standard out and write them to CSV files.

-```bash
+``` bash
 freqtrade backtesting-analysis -c <config.json> --analysis-to-csv
 ```

 By default this will write one file per output table you specified in the `backtesting-analysis` command, e.g.

-```bash
+``` bash
 freqtrade backtesting-analysis -c <config.json> --analysis-to-csv --rejected-signals --analysis-groups 0 1
 ```

@@ -213,6 +215,6 @@ This will write to `user_data/backtest_results`:

 To override where the files will be written, also specify the `--analysis-csv-path` option.

-```bash
+``` bash
 freqtrade backtesting-analysis -c <config.json> --analysis-to-csv --analysis-csv-path another/data/path/
 ```
@@ -133,7 +133,7 @@ class MyAwesomeStrategy(IStrategy):
        ]

        # Define a custom max_open_trades space
-        def max_open_trades_space(self) -> List[Dimension]:
+        def max_open_trades_space() -> List[Dimension]:
            return [
                Integer(-1, 10, name='max_open_trades'),
            ]
@@ -142,7 +142,7 @@ class MyAwesomeStrategy(IStrategy):
 !!! Note
    All overrides are optional and can be mixed/matched as necessary.

-### Dynamic parameters
+## Dynamic parameters

 Parameters can also be defined dynamically, but must be available to the instance once the [`bot_start()` callback](strategy-callbacks.md#bot-start) has been called.

@@ -159,7 +159,7 @@ class MyAwesomeStrategy(IStrategy):
 !!! Warning
    Parameters created this way will not show up in the `list-strategies` parameter count.

-### Overriding Base estimator
+## Overriding Base estimator

 You can define your own optuna sampler for Hyperopt by implementing `generate_estimator()` in the Hyperopt subclass.

@@ -208,7 +208,6 @@ Some research will be necessary to find additional Samplers (from optunahub) for

    Obviously the same approach will work for all other Samplers optuna supports.

-
 ## Space options

 For the additional spaces, scikit-optimize (in combination with Freqtrade) provides the following space types:
@@ -73,7 +73,7 @@ services:
    volumes:
      - "./user_data:/freqtrade/user_data"
    # Expose api on port 8080 (localhost only)
-    # Please read the https://www.freqtrade.io/en/latest/rest-api/ documentation
+    # Please read the https://www.freqtrade.io/en/stable/rest-api/ documentation
    # before enabling this.
     ports:
     - "127.0.0.1:8080:8080"
@@ -100,7 +100,7 @@ services:
    volumes:
      - "./user_data:/freqtrade/user_data"
    # Expose api on port 8080 (localhost only)
-    # Please read the https://www.freqtrade.io/en/latest/rest-api/ documentation
+    # Please read the https://www.freqtrade.io/en/stable/rest-api/ documentation
    # before enabling this.
    ports:
      - "127.0.0.1:8081:8080"
@@ -134,10 +134,10 @@ The following systems have been tested and are known to work with freqtrade:
 ### PostgreSQL

 Installation:
-`pip install psycopg2-binary`
+`pip install "psycopg[binary]"`

 Usage:
-`... --db-url postgresql+psycopg2://<username>:<password>@localhost:5432/<database>`
+`... --db-url postgresql+psycopg://<username>:<password>@localhost:5432/<database>`

 Freqtrade will automatically create the tables necessary upon startup.

@@ -5,6 +5,8 @@ This page explains how to validate your strategy performance by using Backtestin
 Backtesting requires historic data to be available.
 To learn how to get data for the pairs and exchange you're interested in, head over to the [Data Downloading](data-download.md) section of the documentation.

+Backtesting is also available in [webserver mode](freq-ui.md#backtesting), which allows you to run backtests via the web interface.
+
 ## Backtesting command reference

 --8<-- "commands/backtesting.md"
@@ -103,12 +105,14 @@ Only use this if you're sure you'll not want to plot or analyze your results fur

 ---

-Exporting trades to file specifying a custom filename
+Exporting trades to file specifying a custom directory

 ```bash
-freqtrade backtesting --strategy backtesting --export trades --export-filename=backtest_samplestrategy.json
+freqtrade backtesting --strategy backtesting --export trades --backtest-directory=user_data/custom-backtest-results
 ```

+---
+
 Please also read about the [strategy startup period](strategy-customization.md#strategy-startup-period).

 ---
@@ -156,117 +160,150 @@ The most important in the backtesting is to understand the result.
 A backtesting result will look like that:

 ```
-================================================ BACKTESTING REPORT =================================================
-| Pair     | Trades |   Avg Profit % |   Tot Profit BTC |   Tot Profit % | Avg Duration |  Wins Draws Loss   Win%  |
-|----------+--------+----------------+------------------+----------------+--------------+--------------------------|
-| ADA/BTC  |     35 |          -0.11 |      -0.00019428 |          -1.94 | 4:35:00      |    14     0    21   40.0 |
-| ARK/BTC  |     11 |          -0.41 |      -0.00022647 |          -2.26 | 2:03:00      |     3     0     8   27.3 |
-| BTS/BTC  |     32 |           0.31 |       0.00048938 |           4.89 | 5:05:00      |    18     0    14   56.2 |
-| DASH/BTC |     13 |          -0.08 |      -0.00005343 |          -0.53 | 4:39:00      |     6     0     7   46.2 |
-| ENG/BTC  |     18 |           1.36 |       0.00122807 |          12.27 | 2:50:00      |     8     0    10   44.4 |
-| EOS/BTC  |     36 |           0.08 |       0.00015304 |           1.53 | 3:34:00      |    16     0    20   44.4 |
-| ETC/BTC  |     26 |           0.37 |       0.00047576 |           4.75 | 6:14:00      |    11     0    15   42.3 |
-| ETH/BTC  |     33 |           0.30 |       0.00049856 |           4.98 | 7:31:00      |    16     0    17   48.5 |
-| IOTA/BTC |     32 |           0.03 |       0.00005444 |           0.54 | 3:12:00      |    14     0    18   43.8 |
-| LSK/BTC  |     15 |           1.75 |       0.00131413 |          13.13 | 2:58:00      |     6     0     9   40.0 |
-| LTC/BTC  |     32 |          -0.04 |      -0.00006886 |          -0.69 | 4:49:00      |    11     0    21   34.4 |
-| NANO/BTC |     17 |           1.26 |       0.00107058 |          10.70 | 1:55:00      |    10     0     7   58.5 |
-| NEO/BTC  |     23 |           0.82 |       0.00094936 |           9.48 | 2:59:00      |    10     0    13   43.5 |
-| REQ/BTC  |      9 |           1.17 |       0.00052734 |           5.27 | 3:47:00      |     4     0     5   44.4 |
-| XLM/BTC  |     16 |           1.22 |       0.00097800 |           9.77 | 3:15:00      |     7     0     9   43.8 |
-| XMR/BTC  |     23 |          -0.18 |      -0.00020696 |          -2.07 | 5:30:00      |    12     0    11   52.2 |
-| XRP/BTC  |     35 |           0.66 |       0.00114897 |          11.48 | 3:49:00      |    12     0    23   34.3 |
-| ZEC/BTC  |     22 |          -0.46 |      -0.00050971 |          -5.09 | 2:22:00      |     7     0    15   31.8 |
-| TOTAL    |    429 |           0.36 |       0.00762792 |          76.20 | 4:12:00      |   186     0   243   43.4 |
-============================================= LEFT OPEN TRADES REPORT =============================================
-| Pair     |  Trades |   Avg Profit % |   Tot Profit BTC |   Tot Profit % | Avg Duration   |  Win Draw Loss Win% |
-|----------+---------+----------------+------------------+----------------+----------------+---------------------|
-| ADA/BTC  |       1 |           0.89 |       0.00004434 |           0.44 | 6:00:00        |    1    0    0  100 |
-| LTC/BTC  |       1 |           0.68 |       0.00003421 |           0.34 | 2:00:00        |    1    0    0  100 |
-| TOTAL    |       2 |           0.78 |       0.00007855 |           0.78 | 4:00:00        |    2    0    0  100 |
-==================== EXIT REASON STATS ====================
-| Exit Reason        |   Exits |  Wins |  Draws |  Losses |
-|--------------------+---------+-------+--------+---------|
-| trailing_stop_loss |     205 |   150 |      0 |      55 |
-| stop_loss          |     166 |     0 |      0 |     166 |
-| exit_signal        |      56 |    36 |      0 |      20 |
-| force_exit         |       2 |     0 |      0 |       2 |
+                                               BACKTESTING REPORT                                                
+┏━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃          Pair ┃ Trades ┃ Avg Profit % ┃  Tot Profit ┃ Tot Profit % ┃    Avg Duration ┃  Win  Draw  Loss  Win% ┃
+┡━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━┩
+│ LTC/USDT:USDT │     16 │         1.01 │      56.882 │         5.69 │        16:16:00 │   16     0     0   100 │
+│ ETC/USDT:USDT │     12 │         0.73 │      31.513 │         3.15 │         9:55:00 │   11     0     1  91.7 │
+│ ETH/USDT:USDT │      8 │         0.69 │      18.659 │         1.87 │ 1 day, 13:55:00 │    7     0     1  87.5 │
+│ XLM/USDT:USDT │     10 │          0.3 │      10.694 │         1.07 │        12:08:00 │    9     0     1  90.0 │
+│ BTC/USDT:USDT │      8 │         0.22 │       7.502 │         0.75 │ 3 days, 1:24:00 │    6     0     2  75.0 │
+│ XRP/USDT:USDT │      9 │        -0.13 │      -6.837 │        -0.68 │        21:18:00 │    8     0     1  88.9 │
+│ DOT/USDT:USDT │      6 │        -0.39 │      -9.169 │        -0.92 │         5:35:00 │    4     0     2  66.7 │
+│ ADA/USDT:USDT │      8 │        -1.75 │     -52.089 │        -5.21 │        11:38:00 │    6     0     2  75.0 │
+│         TOTAL │     77 │         0.23 │      57.157 │         5.72 │        22:12:00 │   67     0    10  87.0 │
+└───────────────┴────────┴──────────────┴─────────────┴──────────────┴─────────────────┴────────────────────────┘
+                                             LEFT OPEN TRADES REPORT                                              
+┏━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃          Pair ┃ Trades ┃ Avg Profit % ┃  Tot Profit ┃ Tot Profit % ┃     Avg Duration ┃  Win  Draw  Loss  Win% ┃
+┡━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━┩
+│ BTC/USDT:USDT │      1 │        -4.14 │      -9.930 │        -0.99 │ 17 days, 8:00:00 │    0     0     1     0 │
+│ ETC/USDT:USDT │      1 │        -4.24 │     -15.365 │        -1.54 │         10:40:00 │    0     0     1     0 │
+│ DOT/USDT:USDT │      1 │        -5.29 │     -19.166 │        -1.92 │         11:30:00 │    0     0     1     0 │
+│         TOTAL │      3 │        -4.56 │     -44.461 │        -4.45 │  6 days, 2:03:00 │    0     0     3     0 │
+└───────────────┴────────┴──────────────┴─────────────┴──────────────┴──────────────────┴────────────────────────┘
+                                              ENTER TAG STATS                                              
+┏━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃ Enter Tag ┃ Entries ┃ Avg Profit % ┃  Tot Profit ┃ Tot Profit % ┃ Avg Duration ┃  Win  Draw  Loss  Win% ┃
+┡━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━┩
+│     OTHER │      77 │         0.23 │      57.157 │         5.72 │     22:12:00 │   67     0    10  87.0 │
+│     TOTAL │      77 │         0.23 │      57.157 │         5.72 │     22:12:00 │   67     0    10  87.0 │
+└───────────┴─────────┴──────────────┴─────────────┴──────────────┴──────────────┴────────────────────────┘
+                                              EXIT REASON STATS                                               
+┏━━━━━━━━━━━━━┳━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃ Exit Reason ┃ Exits ┃ Avg Profit % ┃  Tot Profit ┃ Tot Profit % ┃    Avg Duration ┃  Win  Draw  Loss  Win% ┃
+┡━━━━━━━━━━━━━╇━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━┩
+│         roi │    67 │         1.06 │     245.117 │        24.51 │        15:49:00 │   67     0     0   100 │
+│ exit_signal │     4 │        -2.23 │     -31.226 │        -3.12 │  1 day, 8:38:00 │    0     0     4     0 │
+│  force_exit │     3 │        -4.56 │     -44.461 │        -4.45 │ 6 days, 2:03:00 │    0     0     3     0 │
+│   stop_loss │     3 │       -10.14 │    -112.273 │       -11.23 │  1 day, 3:05:00 │    0     0     3     0 │
+│       TOTAL │    77 │         0.23 │      57.157 │         5.72 │        22:12:00 │   67     0    10  87.0 │
+└─────────────┴───────┴──────────────┴─────────────┴──────────────┴─────────────────┴────────────────────────┘
+                                                      MIXED TAG STATS                                                      
+┏━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃ Enter Tag ┃ Exit Reason ┃ Trades ┃ Avg Profit % ┃  Tot Profit ┃ Tot Profit % ┃    Avg Duration ┃  Win  Draw  Loss  Win% ┃
+┡━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━┩
+│           │         roi │     67 │         1.06 │     245.117 │        24.51 │        15:49:00 │   67     0     0   100 │
+│           │ exit_signal │      4 │        -2.23 │     -31.226 │        -3.12 │  1 day, 8:38:00 │    0     0     4     0 │
+│           │  force_exit │      3 │        -4.56 │     -44.461 │        -4.45 │ 6 days, 2:03:00 │    0     0     3     0 │
+│           │   stop_loss │      3 │       -10.14 │    -112.273 │       -11.23 │  1 day, 3:05:00 │    0     0     3     0 │
+│     TOTAL │             │     77 │         0.23 │      57.157 │         5.72 │        22:12:00 │   67     0    10  87.0 │
+└───────────┴─────────────┴────────┴──────────────┴─────────────┴──────────────┴─────────────────┴────────────────────────┘
+                                   SUMMARY METRICS                                    
+┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃ Metric                                 ┃ Value                                     ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
+│ Backtesting from                       │ 2025-07-01 00:00:00                       │
+│ Backtesting to                         │ 2025-08-01 00:00:00                       │
+│ Trading Mode                           │ Isolated Futures                          │
+│ Max open trades                        │ 3                                         │
+│                                        │                                           │
+│ Total/Daily Avg Trades                 │ 77 / 2.48                                 │
+│ Starting balance                       │ 1000 USDT                                 │
+│ Final balance                          │ 1057.157 USDT                             │
+│ Absolute profit                        │ 57.157 USDT                               │
+│ Total profit %                         │ 5.72%                                     │
+│ CAGR %                                 │ 92.41%                                    │
+│ Sharpe (closed trades)                 │ 3.89                                      │
+│ Sortino (closed trades)                │ 2.57                                      │
+│ Calmar (closed trades)                 │ 43.03                                     │
+│ SQN                                    │ 0.71                                      │
+│ Profit factor                          │ 1.30                                      │
+│ Expectancy (Ratio)                     │ 0.74 (0.04)                               │
+│ Avg. daily profit                      │ 1.844 USDT                                │
+│ Avg. stake amount                      │ 345.478 USDT                              │
+│ Market change                          │ 30.51%                                    │
+│ Total trade volume                     │ 53390.788 USDT                            │
+│                                        │                                           │
+│ Long / Short trades                    │ 67 / 10                                   │
+│ Long / Short profit %                  │ 9.19% / -3.48%                            │
+│ Long / Short profit USDT               │ 91.940 / -34.783                          │
+│                                        │                                           │
+│ Best Pair                              │ LTC/USDT:USDT 5.69%                       │
+│ Worst Pair                             │ ADA/USDT:USDT -5.21%                      │
+│ Best trade                             │ XRP/USDT:USDT 2.00%                       │
+│ Worst trade                            │ ADA/USDT:USDT -10.17%                     │
+│ Best day                               │ 27.031 USDT                               │
+│ Worst day                              │ -47.826 USDT                              │
+│ Days win/draw/lose                     │ 20 / 6 / 5                                │
+│ Min/Max/Avg. Duration Winners          │ 0d 00:35 / 5d 18:15 / 0d 15:49            │
+│ Min/Max/Avg. Duration Losers           │ 0d 10:40 / 17d 08:00 / 2d 17:00           │
+│ Max Consecutive Wins / Loss            │ 36 / 3                                    │
+│ Rejected Entry signals                 │ 258                                       │
+│ Entry/Exit Timeouts                    │ 0 / 0                                     │
+│                                        │                                           │
+│ Min/Max balance (closed trades)        │ 1003.205 USDT / 1151.425 USDT             │
+│ Max % of account underwater            │ 8.19%                                     │
+│ Absolute drawdown                      │ 94.268 USDT (8.19%)                       │
+│ Drawdown duration                      │ 9 days 08:50:00                           │
+│ Profit at drawdown start               │ 151.425 USDT                              │
+│ Profit at drawdown end                 │ 57.157 USDT                               │
+│ Drawdown start                         │ 2025-07-22 15:10:00                       │
+│ Drawdown end                           │ 2025-08-01 00:00:00                       │
+│                                        │                                           │
+│ Wallet based Metrics                   │                                           │
+│ Min/Max balance (wallet balance)       │ 1000 USDT / 1151.425 USDT                 │
+│ Min/Max balance dates (wallet balance) │ 2025-07-01 00:05:00 / 2025-07-22 15:15:00 │
+│ Max % of account underwater (balance)  │ 5.01%                                     │
+│ Absolute drawdown (wallet balance)     │ 54.76 USDT (4.76%)                        │
+│ Drawdown duration                      │ 7 days 20:35:00                           │
+│ Profit at drawdown start               │ 151.425 USDT                              │
+│ Profit at drawdown end                 │ 96.664 USDT                               │
+│ Drawdown start                         │ 2025-07-22 15:15:00                       │
+│ Drawdown end                           │ 2025-07-30 11:50:00                       │
+│ Sharpe (daily wallet balance)          │ 4.42                                      │
+│ Sortino (daily wallet balance)         │ 4.35                                      │
+│ Calmar (daily wallet balance)          │ 136.07                                    │
+└────────────────────────────────────────┴───────────────────────────────────────────┘
+
+Backtested 2025-07-01 00:00:00 -> 2025-08-01 00:00:00 | Max open trades : 3
+                                                        STRATEGY SUMMARY                                                        
+┏━━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┓
+┃       Strategy ┃ Trades ┃ Avg Profit % ┃  Tot Profit ┃ Tot Profit % ┃ Avg Duration ┃  Win  Draw  Loss  Win% ┃       Drawdown ┃
+┡━━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━┩
+│ SampleStrategy │     77 │         0.23 │      57.157 │         5.72 │     22:12:00 │   67     0    10  87.0 │ 94.268   8.19% │
+└────────────────┴────────┴──────────────┴─────────────┴──────────────┴──────────────┴────────────────────────┴────────────────┘

-================== SUMMARY METRICS ==================
-| Metric                      | Value               |
-|-----------------------------+---------------------|
-| Backtesting from            | 2019-01-01 00:00:00 |
-| Backtesting to              | 2019-05-01 00:00:00 |
-| Trading Mode                | Spot                |
-| Max open trades             | 3                   |
-|                             |                     |
-| Total/Daily Avg Trades      | 429 / 3.575         |
-| Starting balance            | 0.01000000 BTC      |
-| Final balance               | 0.01762792 BTC      |
-| Absolute profit             | 0.00762792 BTC      |
-| Total profit %              | 76.2%               |
-| CAGR %                      | 460.87%             |
-| Sortino                     | 1.88                |
-| Sharpe                      | 2.97                |
-| Calmar                      | 6.29                |
-| SQN                         | 2.45                |
-| Profit factor               | 1.11                |
-| Expectancy (Ratio)          | -0.15 (-0.05)       |
-| Avg. stake amount           | 0.001      BTC      |
-| Total trade volume          | 0.429      BTC      |
-|                             |                     |
-| Long / Short                | 352 / 77            |
-| Total profit Long %         | 1250.58%            |
-| Total profit Short %        | -15.02%             |
-| Absolute profit Long        | 0.00838792 BTC      |
-| Absolute profit Short       | -0.00076 BTC        |
-|                             |                     |
-| Best Pair                   | LSK/BTC 26.26%      |
-| Worst Pair                  | ZEC/BTC -10.18%     |
-| Best Trade                  | LSK/BTC 4.25%       |
-| Worst Trade                 | ZEC/BTC -10.25%     |
-| Best day                    | 0.00076 BTC         |
-| Worst day                   | -0.00036 BTC        |
-| Days win/draw/lose          | 12 / 82 / 25        |
-| Avg. Duration Winners       | 4:23:00             |
-| Avg. Duration Loser         | 6:55:00             |
-| Max Consecutive Wins / Loss | 3 / 4               |
-| Rejected Entry signals      | 3089                |
-| Entry/Exit Timeouts         | 0 / 0               |
-| Canceled Trade Entries      | 34                  |
-| Canceled Entry Orders       | 123                 |
-| Replaced Entry Orders       | 89                  |
-|                             |                     |
-| Min balance                 | 0.00945123 BTC      |
-| Max balance                 | 0.01846651 BTC      |
-| Max % of account underwater | 25.19%              |
-| Absolute Drawdown (Account) | 13.33%              |
-| Drawdown                    | 0.0015 BTC          |
-| Drawdown high               | 0.0013 BTC          |
-| Drawdown low                | -0.0002 BTC         |
-| Drawdown Start              | 2019-02-15 14:10:00 |
-| Drawdown End                | 2019-04-11 18:15:00 |
-| Market change               | -5.88%              |
-=====================================================
 ```

 ### Backtesting report table

-The 1st table contains all trades the bot made, including "left open trades".
+The first table contains all trades the bot made, including "left open trades".

 The last line will give you the overall performance of your strategy,
 here:

 ```
-| TOTAL    |    429 |           0.36 |         152.41 |       0.00762792 |          76.20 | 4:12:00      |   186     0   243   43.4 |
+│         TOTAL │     77 │         0.22 │          54.774 │         5.48 │        22:12:00 │   67     0    10  87.0 │
 ```

-The bot has made `429` trades for an average duration of `4:12:00`, with a performance of `76.20%` (profit), that means it has
-earned a total of `0.00762792 BTC` starting with a capital of 0.01 BTC.
+The bot has made `77` trades for an average duration of `22:12:00`, with a performance of `5.48%` (profit), that means it has earned a total of `54.774 USDT` starting with a capital of 1000 USDT.

 The column `Avg Profit %` shows the average profit for all trades made.
 The column `Tot Profit %` shows instead the total profit % in relation to the starting balance.
-In the above results, we have a starting balance of 0.01 BTC and an absolute profit of 0.00762792 BTC - so the `Tot Profit %` will be `(0.00762792 / 0.01) * 100 ~= 76.2%`.
+
+In the above results, we have a starting balance of 1000 USDT and an absolute profit of 54.774 USDT - so the `Tot Profit %` will be `(54.774 / 1000) * 100 ~= 5.48%`.

 Your strategy performance is influenced by your entry strategy, your exit strategy, and also by the `minimal_roi` and `stop_loss` you have set.

@@ -282,145 +319,185 @@ On the other hand, if you set a too high `minimal_roi` like `"0":  0.55`
 (55%), there is almost no chance that the bot will ever reach this profit.
 Hence, keep in mind that your performance is an integral mix of all different elements of the strategy, your configuration, and the crypto-currency pairs you have set up.

-### Exit reasons table
-
-The 2nd table contains a recap of exit reasons.
-This table can tell you which area needs some additional work (e.g. all or many of the `exit_signal` trades are losses, so you should work on improving the exit signal, or consider disabling it).
-
 ### Left open trades table

-The 3rd table contains all trades the bot had to `force_exit` at the end of the backtesting period to present you the full picture.
+The second table contains all trades the bot had to `force_exit` at the end of the backtesting period to present you the full picture.
 This is necessary to simulate realistic behavior, since the backtest period has to end at some point, while realistically, you could leave the bot running forever.
 These trades are also included in the first table, but are also shown separately in this table for clarity.

+### Enter tag stats table
+
+The third table provides a breakdown of trades by their entry tags (e.g., `enter_long`, `enter_short`), showing the number of entries, average profit percentage, total profit in the stake currency, total profit percentage, average duration, and the number of wins, draws, and losses for each tag.
+
+### Exit reason stats table
+
+The fourth table contains a recap of exit reasons (e.g., `exit_signal`, `roi`, `stop_loss`, `force_exit`). This table can tell you which area needs additional work (e.g., if many `exit_signal` trades are losses, you should work on improving the exit signal or consider disabling it).
+
+### Mixed tag stats table
+
+The fifth table combines entry tags and exit reasons, providing a detailed view of how different entry tags performed with specific exit reasons. This can help identify which combinations of entry and exit strategies are most effective.
+
 ### Summary metrics

 The last element of the backtest report is the summary metrics table.
-It contains some useful key metrics about performance of your strategy on backtesting data.
+It contains key metrics about the performance of your strategy on backtesting data.

 ```
-================== SUMMARY METRICS ==================
-| Metric                      | Value               |
-|-----------------------------+---------------------|
-| Backtesting from            | 2019-01-01 00:00:00 |
-| Backtesting to              | 2019-05-01 00:00:00 |
-| Trading Mode                | Spot                |
-| Max open trades             | 3                   |
-|                             |                     |
-| Total/Daily Avg Trades      | 429 / 3.575         |
-| Starting balance            | 0.01000000 BTC      |
-| Final balance               | 0.01762792 BTC      |
-| Absolute profit             | 0.00762792 BTC      |
-| Total profit %              | 76.2%               |
-| CAGR %                      | 460.87%             |
-| Sortino                     | 1.88                |
-| Sharpe                      | 2.97                |
-| Calmar                      | 6.29                |
-| SQN                         | 2.45                |
-| Profit factor               | 1.11                |
-| Expectancy (Ratio)          | -0.15 (-0.05)       |
-| Avg. stake amount           | 0.001      BTC      |
-| Total trade volume          | 0.429      BTC      |
-|                             |                     |
-| Long / Short                | 352 / 77            |
-| Total profit Long %         | 1250.58%            |
-| Total profit Short %        | -15.02%             |
-| Absolute profit Long        | 0.00838792 BTC      |
-| Absolute profit Short       | -0.00076 BTC        |
-|                             |                     |
-| Best Pair                   | LSK/BTC 26.26%      |
-| Worst Pair                  | ZEC/BTC -10.18%     |
-| Best Trade                  | LSK/BTC 4.25%       |
-| Worst Trade                 | ZEC/BTC -10.25%     |
-| Best day                    | 0.00076 BTC         |
-| Worst day                   | -0.00036 BTC        |
-| Days win/draw/lose          | 12 / 82 / 25        |
-| Avg. Duration Winners       | 4:23:00             |
-| Avg. Duration Loser         | 6:55:00             |
-| Max Consecutive Wins / Loss | 3 / 4               |
-| Rejected Entry signals      | 3089                |
-| Entry/Exit Timeouts         | 0 / 0               |
-| Canceled Trade Entries      | 34                  |
-| Canceled Entry Orders       | 123                 |
-| Replaced Entry Orders       | 89                  |
-|                             |                     |
-| Min balance                 | 0.00945123 BTC      |
-| Max balance                 | 0.01846651 BTC      |
-| Max % of account underwater | 25.19%              |
-| Absolute Drawdown (Account) | 13.33%              |
-| Drawdown                    | 0.0015 BTC          |
-| Drawdown high               | 0.0013 BTC          |
-| Drawdown low                | -0.0002 BTC         |
-| Drawdown Start              | 2019-02-15 14:10:00 |
-| Drawdown End                | 2019-04-11 18:15:00 |
-| Market change               | -5.88%              |
-=====================================================
-
+                                   SUMMARY METRICS                                    
+┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃ Metric                                 ┃ Value                                     ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
+│ Backtesting from                       │ 2025-07-01 00:00:00                       │
+│ Backtesting to                         │ 2025-08-01 00:00:00                       │
+│ Trading Mode                           │ Isolated Futures                          │
+│ Max open trades                        │ 3                                         │
+│                                        │                                           │
+│ Total/Daily Avg Trades                 │ 77 / 2.48                                 │
+│ Starting balance                       │ 1000 USDT                                 │
+│ Final balance                          │ 1057.157 USDT                             │
+│ Absolute profit                        │ 57.157 USDT                               │
+│ Total profit %                         │ 5.72%                                     │
+│ CAGR %                                 │ 92.41%                                    │
+│ Sharpe (closed trades)                 │ 3.89                                      │
+│ Sortino (closed trades)                │ 2.57                                      │
+│ Calmar (closed trades)                 │ 43.03                                     │
+│ SQN                                    │ 0.71                                      │
+│ Profit factor                          │ 1.30                                      │
+│ Expectancy (Ratio)                     │ 0.74 (0.04)                               │
+│ Avg. daily profit                      │ 1.844 USDT                                │
+│ Avg. stake amount                      │ 345.478 USDT                              │
+│ Market change                          │ 30.51%                                    │
+│ Total trade volume                     │ 53390.788 USDT                            │
+│                                        │                                           │
+│ Long / Short trades                    │ 67 / 10                                   │
+│ Long / Short profit %                  │ 9.19% / -3.48%                            │
+│ Long / Short profit USDT               │ 91.940 / -34.783                          │
+│                                        │                                           │
+│ Best Pair                              │ LTC/USDT:USDT 5.69%                       │
+│ Worst Pair                             │ ADA/USDT:USDT -5.21%                      │
+│ Best trade                             │ XRP/USDT:USDT 2.00%                       │
+│ Worst trade                            │ ADA/USDT:USDT -10.17%                     │
+│ Best day                               │ 27.031 USDT                               │
+│ Worst day                              │ -47.826 USDT                              │
+│ Days win/draw/lose                     │ 20 / 6 / 5                                │
+│ Min/Max/Avg. Duration Winners          │ 0d 00:35 / 5d 18:15 / 0d 15:49            │
+│ Min/Max/Avg. Duration Losers           │ 0d 10:40 / 17d 08:00 / 2d 17:00           │
+│ Max Consecutive Wins / Loss            │ 36 / 3                                    │
+│ Rejected Entry signals                 │ 258                                       │
+│ Entry/Exit Timeouts                    │ 0 / 0                                     │
+│                                        │                                           │
+│ Min/Max balance (closed trades)        │ 1003.205 USDT / 1151.425 USDT             │
+│ Max % of account underwater            │ 8.19%                                     │
+│ Absolute drawdown                      │ 94.268 USDT (8.19%)                       │
+│ Drawdown duration                      │ 9 days 08:50:00                           │
+│ Profit at drawdown start               │ 151.425 USDT                              │
+│ Profit at drawdown end                 │ 57.157 USDT                               │
+│ Drawdown start                         │ 2025-07-22 15:10:00                       │
+│ Drawdown end                           │ 2025-08-01 00:00:00                       │
+│                                        │                                           │
+│ Wallet based Metrics                   │                                           │
+│ Min/Max balance (wallet balance)       │ 1000 USDT / 1151.425 USDT                 │
+│ Min/Max balance dates (wallet balance) │ 2025-07-01 00:05:00 / 2025-07-22 15:15:00 │
+│ Max % of account underwater (balance)  │ 5.01%                                     │
+│ Absolute drawdown (wallet balance)     │ 54.76 USDT (4.76%)                        │
+│ Drawdown duration                      │ 7 days 20:35:00                           │
+│ Profit at drawdown start               │ 151.425 USDT                              │
+│ Profit at drawdown end                 │ 96.664 USDT                               │
+│ Drawdown start                         │ 2025-07-22 15:15:00                       │
+│ Drawdown end                           │ 2025-07-30 11:50:00                       │
+│ Sharpe (daily wallet balance)          │ 4.42                                      │
+│ Sortino (daily wallet balance)         │ 4.35                                      │
+│ Calmar (daily wallet balance)          │ 136.07                                    │
+└────────────────────────────────────────┴───────────────────────────────────────────┘
 ```

 - `Backtesting from` / `Backtesting to`: Backtesting range (usually defined with the `--timerange` option).
- `Max open trades`: Setting of `max_open_trades` (or `--max-open-trades`) - or number of pairs in the pairlist (whatever is lower).
 - `Trading Mode`: Spot or Futures trading.
+- `Max open trades`: Setting of `max_open_trades` (or `--max-open-trades`) - or number of pairs in the pairlist (whatever is lower).
 - `Total/Daily Avg Trades`: Identical to the total trades of the backtest output table / Total trades divided by the backtesting duration in days (this will give you information about how many trades to expect from the strategy).
 - `Starting balance`: Start balance - as given by dry-run-wallet (config or command line).
 - `Final balance`: Final balance - starting balance + absolute profit.
 - `Absolute profit`: Profit made in stake currency.
 - `Total profit %`: Total profit. Aligned to the `TOTAL` row's `Tot Profit %` from the first table. Calculated as `(End capital − Starting capital) / Starting capital`.
 - `CAGR %`: Compound annual growth rate.
- `Sortino`: Annualized Sortino ratio.
- `Sharpe`: Annualized Sharpe ratio.
- `Calmar`: Annualized Calmar ratio.
+- `Sharpe (closed trades)`: Annualized Sharpe ratio including only closed trades (ignoring open trades with profits or losses).
+- `Sortino (closed trades)`: Annualized Sortino ratio including only closed trades (ignoring open trades with profits or losses).
+- `Calmar (closed trades)`: Annualized Calmar ratio including only closed trades (ignoring open trades with profits or losses).
 - `SQN`: System Quality Number (SQN) - by Van Tharp.
- `Profit factor`: profit / loss.
+- `Profit factor`: Sum of the profits of all winning trades divided by the sum of the losses of all losing trades.
+- `Expectancy (Ratio)`: Expectancy ratio, which is the average profit or loss per trade. A negative expectancy ratio means that your strategy is not profitable.
+- `Avg. daily profit`: Average profit per day, calculated as `(Total Profit / Backtest Days)`.
 - `Avg. stake amount`: Average stake amount, either `stake_amount` or the average when using dynamic stake amount.
+- `Market change`: Change of the market during the backtest period. Calculated as the average of all pairs' changes from the first to the last candle using the "close" column.
 - `Total trade volume`: Volume generated on the exchange to reach the above profit.
- `Best Pair` / `Worst Pair`: Best and worst performing pair, and it's corresponding `Tot Profit %`.
- `Best Trade` / `Worst Trade`: Biggest single winning trade and biggest single losing trade.
+- `Long / Short trades`: Split long/short trade counts (only shown when short trades were made).
+- `Long / Short profit %`: Profit percentage for long and short trades (only shown when short trades were made).
+- `Long / Short profit USDT`: Profit in stake currency for long and short trades (only shown when short trades were made).
+- `Best Pair` / `Worst Pair`: Best and worst performing pair (based on total profit percentage), and its corresponding `Tot Profit %`.
+- `Best trade` / `Worst trade`: Biggest single winning trade and biggest single losing trade.
 - `Best day` / `Worst day`: Best and worst day based on daily profit.
- `Days win/draw/lose`: Winning / Losing days (draws are usually days without closed trade).
- `Avg. Duration Winners` / `Avg. Duration Loser`: Average durations for winning and losing trades.
+- `Days win/draw/lose`: Winning / Losing days (draws are usually days without closed trades).
+- `Min/Max/Avg. Duration Winners`: Minimum, maximum, and average durations for winning trades.
+- `Min/Max/Avg. Duration Losers`: Minimum, maximum, and average durations for losing trades.
 - `Max Consecutive Wins / Loss`: Maximum consecutive wins/losses in a row.
 - `Rejected Entry signals`: Trade entry signals that could not be acted upon due to `max_open_trades` being reached.
 - `Entry/Exit Timeouts`: Entry/exit orders which did not fill (only applicable if custom pricing is used).
- `Canceled Trade Entries`: Number of trades that have been canceled by user request via `adjust_entry_price`.
- `Canceled Entry Orders`: Number of entry orders that have been canceled by user request via `adjust_entry_price`.
- `Replaced Entry Orders`: Number of entry orders that have been replaced by user request via `adjust_entry_price`.
- `Min balance` / `Max balance`: Lowest and Highest Wallet balance during the backtest period.
- `Max % of account underwater`: Maximum percentage your account has decreased from the top since the simulation started.
-Calculated as the maximum of `(Max Balance - Current Balance) / (Max Balance)`.
- `Absolute Drawdown (Account)`: Maximum Account Drawdown experienced. Calculated as `(Absolute Drawdown) / (DrawdownHigh + startingBalance)`.
- `Drawdown`: Maximum, absolute drawdown experienced. Difference between Drawdown High and Subsequent Low point.
- `Drawdown high` / `Drawdown low`: Profit at the beginning and end of the largest drawdown period. A negative low value means initial capital lost.
- `Drawdown Start` / `Drawdown End`: Start and end datetime for this largest drawdown (can also be visualized via the `plot-dataframe` sub-command).
- `Market change`: Change of the market during the backtest period. Calculated as average of all pairs changes from the first to the last candle using the "close" column.
- `Long / Short`: Split long/short values (Only shown when short trades were made).
- `Total profit Long %` / `Absolute profit Long`: Profit long trades only (Only shown when short trades were made).
- `Total profit Short %` / `Absolute profit Short`: Profit short trades only (Only shown when short trades were made).
+- `Min/Max balance (closed trades)`: Lowest and Highest Wallet balance during the backtest period based on closed trades trades.
+- `Max % of account underwater`: Maximum percentage your account has decreased from the top since the simulation started. Calculated as the maximum of `(Max Balance - Current Balance) / (Max Balance)`.
+- `Absolute drawdown`: Maximum absolute drawdown experienced, including percentage relative to the account calculated as `(Absolute Drawdown) / (DrawdownHigh + startingBalance)`..
+- `Absolute drawdown (wallet balance)`: Maximum absolute drawdown experienced based on the unrealized balance, including percentage relative to the account calculated as `(Absolute Drawdown) / (DrawdownHigh + startingBalance)`.
+- `Drawdown duration`: Duration of the largest drawdown period.
+- `Profit at drawdown start` / `Profit at drawdown end`: Profit at the beginning and end of the largest drawdown period.
+- `Drawdown start` / `Drawdown end`: Start and end datetime for the largest drawdown (can also be visualized via the `plot-dataframe` sub-command).
+- `Min/Max balance (wallet balance)`: Lowest and Highest Wallet balance during the backtest period - including capital tied in open trades.
+- `Min/Max balance dates (wallet balance)`: Dates when the minimum and maximum unrealized balance occurred.
+- `Sharpe (wallet balance)` Annualized Sharpe ratio calculation including unrealized profits.
+- `Sortino (wallet balance)` Annualized Sortino ratio calculation including unrealized profits.
+- `Calmar (wallet balance)` Annualized Calmar ratio calculation including unrealized profits.

-### Daily / Weekly / Monthly breakdown
+!!! Tip "Wallet based Metrics"
+    The metrics under the "Wallet based Metrics" section are calculated based on the unrealized balance, which includes the capital tied in open trades. This provides a more comprehensive view of the strategy's performance, as it accounts for both realized and unrealized profits and losses.

-You can get an overview over daily / weekly or monthly results by using the `--breakdown <>` switch.
+### Daily / Weekly / Monthly / Yearly breakdown

-To visualize daily and weekly breakdowns, you can use the following:
+You can get an overview over daily, weekly, monthly, or yearly results by using the `--breakdown <>` switch.
+
+To visualize monthly and yearly breakdowns, you can use the following:

 ``` bash
-freqtrade backtesting --strategy MyAwesomeStrategy --breakdown day week
+freqtrade backtesting --strategy MyAwesomeStrategy --breakdown month year
 ```

 ``` output
-======================== DAY BREAKDOWN =========================
-|        Day |   Tot Profit USDT |   Wins |   Draws |   Losses |
-|------------+-------------------+--------+---------+----------|
-| 03/07/2021 |           200.0   |      2 |       0 |        0 |
-| 04/07/2021 |           -50.31  |      0 |       0 |        2 |
-| 05/07/2021 |           220.611 |      3 |       2 |        0 |
-| 06/07/2021 |           150.974 |      3 |       0 |        2 |
-| 07/07/2021 |           -70.193 |      1 |       0 |        2 |
-| 08/07/2021 |           212.413 |      2 |       0 |        3 |
-
+                                 MONTH BREAKDOWN
+┏━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃      Month ┃ Trades ┃ Tot Profit USDT ┃ Profit Factor ┃  Win  Draw  Loss  Win% ┃
+┡━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━┩
+│ 31/01/2020 │     12 │          44.451 │          7.28 │   10     0     2  83.3 │
+│ 29/02/2020 │     30 │           45.41 │          2.36 │   17     0    13  56.7 │
+│ 31/03/2020 │     35 │         142.024 │          2.42 │   14     0    21  40.0 │
+│ 30/04/2020 │     67 │         -23.692 │          0.81 │   24     0    43  35.8 │
+...
+...
+│ 30/04/2025 │    203 │          -63.43 │          0.81 │   73     0   130  36.0 │
+│ 31/05/2025 │    142 │         104.675 │          1.28 │   59     0    83  41.5 │
+│ 30/06/2025 │    177 │          -1.014 │           1.0 │   85     0    92  48.0 │
+│ 31/07/2025 │    155 │         232.762 │           1.6 │   63     0    92  40.6 │
+└────────────┴────────┴─────────────────┴───────────────┴────────────────────────┘
+                                  YEAR BREAKDOWN
+┏━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃       Year ┃ Trades ┃ Tot Profit USDT ┃ Profit Factor ┃  Win  Draw  Loss  Win% ┃
+┡━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━┩
+│ 31/12/2020 │    896 │         868.889 │          1.46 │  351     0   545  39.2 │
+│ 31/12/2021 │   1778 │        4487.163 │          1.93 │  745     0  1033  41.9 │
+│ 31/12/2022 │   1736 │          938.27 │          1.27 │  698     0  1038  40.2 │
+│ 31/12/2023 │   1712 │        1677.126 │          1.68 │  670     0  1042  39.1 │
+│ 31/12/2024 │   1609 │        3198.424 │          2.22 │  773     0   836  48.0 │
+│ 31/12/2025 │   1042 │         716.174 │          1.33 │  420     0   622  40.3 │
+└────────────┴────────┴─────────────────┴───────────────┴────────────────────────┘
 ```

-The output will show a table containing the realized absolute Profit (in stake currency) for the given timeperiod, as well as wins, draws and losses that materialized (closed) on this day. Below that there will be a second table for the summarized values of weeks indicated by the date of the closing Sunday. The same would apply to a monthly breakdown indicated by the last day of the month.
+The output will display tables containing the realized absolute profit (in stake currency) for the selected period, along with additional statistics such as number of trades, profit factor, and distribution of wins, draws, and losses that materialized (closed) on this period.

 ### Backtest result caching

@@ -435,15 +512,19 @@ To save time, by default backtest will reuse a cached result from within the las
 To further analyze your backtest results, freqtrade will export the trades to file by default.
 You can then load the trades to perform further analysis as shown in the [data analysis](strategy_analysis_example.md#load-backtest-results-to-pandas-dataframe) backtesting section.

+Also, you can use freqtrade in [webserver mode](freq-ui.md#backtesting) to visualize the backtest results in a web interface.
+This mode also allows you to load existing backtest results, so you can analyze them without running the backtest again.  
+For this mode - `--notes "<notes>"` can be used to add notes to the backtest results, which will be shown in the web interface.
+
 ### Backtest output file

 The output file freqtrade produces is a zip file containing the following files:

 - The backtest report in json format
- the market change data in feather format
- a copy of the strategy file
- a copy of the strategy parameters (if a parameter file was used)
- a sanitized copy of the config file
+- The market change data in feather format
+- A copy of the strategy file
+- A copy of the strategy parameters (if a parameter file was used)
+- A sanitized copy of the config file

 This will ensure results are reproducible - under the assumption that the same data is available.

@@ -461,7 +542,7 @@ Since backtesting lacks some detailed information about what happens within a ca
 - Exit-signal is favored over Stoploss, because exit-signals are assumed to trigger on candle's open
 - ROI
  - Exits are compared to high - but the ROI value is used (e.g. ROI = 2%, high=5% - so the exit will be at 2%)
-  - Exits are never "below the candle", so a ROI of 2% may result in a exit at 2.4% if low was at 2.4% profit
+  - Exits are never "below the candle", so a ROI of 2% may result in an exit at 2.4% if low was at 2.4% profit
  - ROI entries which came into effect on the triggering candle (e.g. `120: 0.02` for 1h candles, from `60: 0.05`) will use the candle's open as exit rate
  - Force-exits caused by `<N>=-1` ROI entries use low as exit value, unless N falls on the candle open (e.g. `120: -1` for 1h candles)
 - Stoploss exits happen exactly at stoploss price, even if low was lower, but the loss will be `2 * fees` higher than the stoploss price
@@ -527,7 +608,7 @@ freqtrade backtesting --strategy AwesomeStrategy --timeframe 1h --timeframe-deta

 This will load 1h data (the main timeframe) as well as 5m data (detail timeframe) for the selected timerange.
 The strategy will be analyzed with the 1h timeframe.
-Candles where activity may take place (there's an active signal, the pair is in a trade) are  evaluated at the 5m timeframe.
+Candles where activity may take place (there's an active signal, the pair is in a trade) are evaluated at the 5m timeframe.
 This will allow for a more accurate simulation of intra-candle movements - and can lead to different results, especially on higher timeframes.

 Entries will generally still happen at the main candle's open, however freed trade slots may be freed earlier (if the exit signal is triggered on the 5m candle), which can then be used for a new trade of a different pair.
@@ -590,5 +671,5 @@ Detailed output for all strategies one after the other will be available, so mak

 ## Next step

-Great, your strategy is profitable. What if the bot can give your the optimal parameters to use for your strategy?
+Great, your strategy is profitable. What if the bot can give you the optimal parameters to use for your strategy?
 Your next step is to learn [how to find optimal parameters with Hyperopt](hyperopt.md)
@@ -1,8 +1,9 @@
-```
+``` output
 usage: freqtrade backtesting-analysis [-h] [-v] [--no-color] [--logfile FILE]
                                      [-V] [-c PATH] [-d PATH]
                                      [--userdir PATH]
-                                      [--export-filename PATH]
+                                      [--backtest-filename PATH]
+                                      [--backtest-directory PATH]
                                      [--analysis-groups {0,1,2,3,4,5} [{0,1,2,3,4,5} ...]]
                                      [--enter-reason-list ENTER_REASON_LIST [ENTER_REASON_LIST ...]]
                                      [--exit-reason-list EXIT_REASON_LIST [EXIT_REASON_LIST ...]]
@@ -14,10 +15,15 @@ usage: freqtrade backtesting-analysis [-h] [-v] [--no-color] [--logfile FILE]

 options:
  -h, --help            show this help message and exit
-  --export-filename PATH, --backtest-filename PATH
-                        Use this filename for backtest results.Requires
-                        `--export` to be set as well. Example: `--export-filen
-                        ame=user_data/backtest_results/backtest_today.json`
+  --backtest-filename, --export-filename PATH
+                        Use this filename for backtest results.Example:
+                        `--backtest-
+                        filename=backtest_results_2020-09-27_16-20-48.json`.
+                        Assumes either `user_data/backtest_results/` or
+                        `--export-directory` as base directory.
+  --backtest-directory, --export-directory PATH
+                        Directory to use for backtest results. Example:
+                        `--export-directory=user_data/backtest_results/`.
  --analysis-groups {0,1,2,3,4,5} [{0,1,2,3,4,5} ...]
                        grouping output - 0: simple wins/losses by enter tag,
                        1: by enter_tag, 2: by enter_tag and exit_tag, 3: by
@@ -48,21 +54,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,39 +1,45 @@
-```
+``` output
 usage: freqtrade backtesting-show [-h] [-v] [--no-color] [--logfile FILE] [-V]
                                  [-c PATH] [-d PATH] [--userdir PATH]
-                                  [--export-filename PATH] [--show-pair-list]
-                                  [--breakdown {day,week,month,year} [{day,week,month,year} ...]]
+                                  [--backtest-filename PATH]
+                                  [--backtest-directory PATH]
+                                  [--show-pair-list]
+                                  [--breakdown {day,week,month,year,weekday} [{day,week,month,year,weekday} ...]]

 options:
  -h, --help            show this help message and exit
-  --export-filename PATH, --backtest-filename PATH
-                        Use this filename for backtest results.Requires
-                        `--export` to be set as well. Example: `--export-filen
-                        ame=user_data/backtest_results/backtest_today.json`
+  --backtest-filename, --export-filename PATH
+                        Use this filename for backtest results.Example:
+                        `--backtest-
+                        filename=backtest_results_2020-09-27_16-20-48.json`.
+                        Assumes either `user_data/backtest_results/` or
+                        `--export-directory` as base directory.
+  --backtest-directory, --export-directory PATH
+                        Directory to use for backtest results. Example:
+                        `--export-directory=user_data/backtest_results/`.
  --show-pair-list      Show backtesting pairlist sorted by profit.
-  --breakdown {day,week,month,year} [{day,week,month,year} ...]
+  --breakdown {day,week,month,year,weekday} [{day,week,month,year,weekday} ...]
                        Show backtesting breakdown per [day, week, month,
-                        year].
+                        year, weekday].

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade backtesting [-h] [-v] [--no-color] [--logfile FILE] [-V]
                             [-c PATH] [-d PATH] [--userdir PATH] [-s NAME]
                             [--strategy-path PATH]
@@ -10,18 +10,20 @@ usage: freqtrade backtesting [-h] [-v] [--no-color] [--logfile FILE] [-V]
                             [--stake-amount STAKE_AMOUNT] [--fee FLOAT]
                             [-p PAIRS [PAIRS ...]] [--eps]
                             [--enable-protections]
+                             [--enable-dynamic-pairlist]
                             [--dry-run-wallet DRY_RUN_WALLET]
                             [--timeframe-detail TIMEFRAME_DETAIL]
                             [--strategy-list STRATEGY_LIST [STRATEGY_LIST ...]]
                             [--export {none,trades,signals}]
-                             [--export-filename PATH]
-                             [--breakdown {day,week,month,year} [{day,week,month,year} ...]]
+                             [--backtest-filename PATH]
+                             [--backtest-directory PATH]
+                             [--breakdown {day,week,month,year,weekday} [{day,week,month,year,weekday} ...]]
                             [--cache {none,day,week,month}]
-                             [--freqai-backtest-live-models]
+                             [--freqai-backtest-live-models] [--notes TEXT]

 options:
  -h, --help            show this help message and exit
-  -i TIMEFRAME, --timeframe TIMEFRAME
+  -i, --timeframe TIMEFRAME
                        Specify timeframe (`1m`, `5m`, `30m`, `1h`, `1d`).
  --timerange TIMERANGE
                        Specify what timerange of data to use.
@@ -36,17 +38,24 @@ options:
                        setting.
  --fee FLOAT           Specify fee ratio. Will be applied twice (on trade
                        entry and exit).
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --eps, --enable-position-stacking
                        Allow buying the same pair multiple times (position
-                        stacking).
+                        stacking). Only applicable to backtesting and
+                        hyperopt. Results archived by this cannot be
+                        reproduced in dry/live trading.
  --enable-protections, --enableprotections
-                        Enable protections for backtesting.Will slow
+                        Enable protections for backtesting. Will slow
                        backtesting down by a considerable amount, but will
                        include configured protections
-  --dry-run-wallet DRY_RUN_WALLET, --starting-balance DRY_RUN_WALLET
+  --enable-dynamic-pairlist
+                        Enables dynamic pairlist refreshes in backtesting. The
+                        pairlist will be generated for each new candle if
+                        you're using a pairlist handler that supports this
+                        feature, for example, ShuffleFilter.
+  --dry-run-wallet, --starting-balance DRY_RUN_WALLET
                        Starting balance, used for backtesting / hyperopt and
                        dry-runs.
  --timeframe-detail TIMEFRAME_DETAIL
@@ -55,49 +64,50 @@ options:
  --strategy-list STRATEGY_LIST [STRATEGY_LIST ...]
                        Provide a space-separated list of strategies to
                        backtest. Please note that timeframe needs to be set
-                        either in config or via command line. When using this
-                        together with `--export trades`, the strategy-name is
-                        injected into the filename (so `backtest-data.json`
-                        becomes `backtest-data-SampleStrategy.json`
+                        either in config or via command line.
  --export {none,trades,signals}
                        Export backtest results (default: trades).
-  --export-filename PATH, --backtest-filename PATH
-                        Use this filename for backtest results.Requires
-                        `--export` to be set as well. Example: `--export-filen
-                        ame=user_data/backtest_results/backtest_today.json`
-  --breakdown {day,week,month,year} [{day,week,month,year} ...]
+  --backtest-filename, --export-filename PATH
+                        DEPRECATED: This option is deprecated for backtesting
+                        and will be removed in a future release. Using a
+                        custom filename for backtest results is no longer
+                        supported. Use `--backtest-directory` to specify the
+                        directory.
+  --backtest-directory, --export-directory PATH
+                        Directory to use for backtest results. Example:
+                        `--export-directory=user_data/backtest_results/`.
+  --breakdown {day,week,month,year,weekday} [{day,week,month,year,weekday} ...]
                        Show backtesting breakdown per [day, week, month,
-                        year].
+                        year, weekday].
  --cache {none,day,week,month}
                        Load a cached backtest result no older than specified
                        age (default: day).
  --freqai-backtest-live-models
                        Run backtest with ready models.
+  --notes TEXT          Add notes to the backtest results.

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 Strategy arguments:
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
@@ -1,17 +1,17 @@
-```
+``` output
 usage: freqtrade convert-data [-h] [-v] [--no-color] [--logfile FILE] [-V]
                              [-c PATH] [-d PATH] [--userdir PATH]
-                              [-p PAIRS [PAIRS ...]] --format-from
-                              {json,jsongz,feather,parquet} --format-to
-                              {json,jsongz,feather,parquet} [--erase]
-                              [--exchange EXCHANGE]
+                              [-p PAIRS [PAIRS ...]]
+                              --format-from {json,jsongz,feather,parquet}
+                              --format-to {json,jsongz,feather,parquet}
+                              [--erase] [--exchange EXCHANGE]
                              [-t TIMEFRAMES [TIMEFRAMES ...]]
                              [--trading-mode {spot,margin,futures}]
                              [--candle-types {spot,futures,mark,index,premiumIndex,funding_rate} [{spot,futures,mark,index,premiumIndex,funding_rate} ...]]

 options:
  -h, --help            show this help message and exit
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --format-from {json,jsongz,feather,parquet}
@@ -21,10 +21,10 @@ options:
  --erase               Clean all existing data for the selected
                        exchange/pairs/timeframes.
  --exchange EXCHANGE   Exchange name. Only valid if no config is provided.
-  -t TIMEFRAMES [TIMEFRAMES ...], --timeframes TIMEFRAMES [TIMEFRAMES ...]
+  -t, --timeframes TIMEFRAMES [TIMEFRAMES ...]
                        Specify which tickers to download. Space-separated
                        list. Default: `1m 5m`.
-  --trading-mode {spot,margin,futures}, --tradingmode {spot,margin,futures}
+  --trading-mode, --tradingmode {spot,margin,futures}
                        Select Trading mode
  --candle-types {spot,futures,mark,index,premiumIndex,funding_rate} [{spot,futures,mark,index,premiumIndex,funding_rate} ...]
                        Select candle type to convert. Defaults to all
@@ -34,21 +34,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade convert-db [-h] [--db-url PATH] [--db-url-from PATH]

 options:
@@ -1,14 +1,14 @@
-```
+``` output
 usage: freqtrade convert-trade-data [-h] [-v] [--no-color] [--logfile FILE]
                                    [-V] [-c PATH] [-d PATH] [--userdir PATH]
-                                    [-p PAIRS [PAIRS ...]] --format-from
-                                    {json,jsongz,feather,parquet,kraken_csv}
+                                    [-p PAIRS [PAIRS ...]]
+                                    --format-from {json,jsongz,feather,parquet,kraken_csv}
                                    --format-to {json,jsongz,feather,parquet}
                                    [--erase] [--exchange EXCHANGE]

 options:
  -h, --help            show this help message and exit
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --format-from {json,jsongz,feather,parquet,kraken_csv}
@@ -23,21 +23,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,9 +1,9 @@
-```
+``` output
 usage: freqtrade create-userdir [-h] [--userdir PATH] [--reset]

 options:
  -h, --help            show this help message and exit
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.
  --reset               Reset sample files to their original state.

@@ -1,20 +1,22 @@
-```
+``` output
 usage: freqtrade download-data [-h] [-v] [--no-color] [--logfile FILE] [-V]
                               [-c PATH] [-d PATH] [--userdir PATH]
                               [-p PAIRS [PAIRS ...]] [--pairs-file FILE]
                               [--days INT] [--new-pairs-days INT]
                               [--include-inactive-pairs]
+                               [--no-parallel-download]
                               [--timerange TIMERANGE] [--dl-trades]
                               [--convert] [--exchange EXCHANGE]
                               [-t TIMEFRAMES [TIMEFRAMES ...]] [--erase]
                               [--data-format-ohlcv {json,jsongz,feather,parquet}]
                               [--data-format-trades {json,jsongz,feather,parquet}]
                               [--trading-mode {spot,margin,futures}]
+                               [--candle-types {spot,futures,mark,index,premiumIndex,funding_rate} [{spot,futures,mark,index,premiumIndex,funding_rate} ...]]
                               [--prepend]

 options:
  -h, --help            show this help message and exit
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --pairs-file FILE     File containing a list of pairs. Takes precedence over
@@ -24,6 +26,9 @@ options:
                        Default: `None`.
  --include-inactive-pairs
                        Also download data from inactive pairs.
+  --no-parallel-download
+                        Disable parallel startup download. Only use this if
+                        you experience issues.
  --timerange TIMERANGE
                        Specify what timerange of data to use.
  --dl-trades           Download trades instead of OHLCV data.
@@ -33,7 +38,7 @@ options:
                        OHLCV (e.g. Kraken). If not provided, use `trades-to-
                        ohlcv` to convert trades data to OHLCV data.
  --exchange EXCHANGE   Exchange name. Only valid if no config is provided.
-  -t TIMEFRAMES [TIMEFRAMES ...], --timeframes TIMEFRAMES [TIMEFRAMES ...]
+  -t, --timeframes TIMEFRAMES [TIMEFRAMES ...]
                        Specify which tickers to download. Space-separated
                        list. Default: `1m 5m`.
  --erase               Clean all existing data for the selected
@@ -44,29 +49,33 @@ options:
  --data-format-trades {json,jsongz,feather,parquet}
                        Storage format for downloaded trades data. (default:
                        `feather`).
-  --trading-mode {spot,margin,futures}, --tradingmode {spot,margin,futures}
+  --trading-mode, --tradingmode {spot,margin,futures}
                        Select Trading mode
+  --candle-types {spot,futures,mark,index,premiumIndex,funding_rate} [{spot,futures,mark,index,premiumIndex,funding_rate} ...]
+                        Select candle type to download. Defaults to the
+                        necessary candles for the selected trading mode (e.g.
+                        'spot' or ('futures', 'funding_rate' and 'mark') for
+                        futures).
  --prepend             Allow data prepending. (Data-appending is disabled)

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade edge [-h] [-v] [--no-color] [--logfile FILE] [-V] [-c PATH]
                      [-d PATH] [--userdir PATH] [-s NAME]
                      [--strategy-path PATH] [--recursive-strategy-search]
@@ -7,11 +7,10 @@ usage: freqtrade edge [-h] [-v] [--no-color] [--logfile FILE] [-V] [-c PATH]
                      [--data-format-ohlcv {json,jsongz,feather,parquet}]
                      [--max-open-trades INT] [--stake-amount STAKE_AMOUNT]
                      [--fee FLOAT] [-p PAIRS [PAIRS ...]]
-                      [--stoplosses STOPLOSS_RANGE]

 options:
  -h, --help            show this help message and exit
-  -i TIMEFRAME, --timeframe TIMEFRAME
+  -i, --timeframe TIMEFRAME
                        Specify timeframe (`1m`, `5m`, `30m`, `1h`, `1d`).
  --timerange TIMERANGE
                        Specify what timerange of data to use.
@@ -26,39 +25,32 @@ options:
                        setting.
  --fee FLOAT           Specify fee ratio. Will be applied twice (on trade
                        entry and exit).
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
-  --stoplosses STOPLOSS_RANGE
-                        Defines a range of stoploss values against which edge
-                        will assess the strategy. The format is "min,max,step"
-                        (without any space). Example:
-                        `--stoplosses=-0.01,-0.1,-0.001`

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 Strategy arguments:
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
@@ -0,0 +1,197 @@
+``` output
+Possible commands:
+
+available_pairs
+	Return available pair (backtest data) based on timeframe / stake_currency selection
+
+:param timeframe: Only pairs with this timeframe available.
+:param stake_currency: Only pairs that include this stake currency.
+
+balance
+	Get the account balance.
+
+blacklist
+	Show the current blacklist.
+
+:param add: List of coins to add (example: "BNB/BTC")
+
+cancel_open_order
+	Cancel open order for trade.
+
+:param trade_id: Cancels open orders for this trade.
+
+count
+	Return the amount of open trades.
+
+daily
+	Return the profits for each day, and amount of trades.
+
+delete_lock
+	Delete (disable) lock from the database.
+
+:param lock_id: ID for the lock to delete
+
+delete_trade
+	Delete trade from the database.
+Tries to close open orders. Requires manual handling of this asset on the exchange.
+
+:param trade_id: Deletes the trade with this ID from the database.
+
+entries
+	Returns List of dicts containing all Trades, based on buy tag performance
+Can either be average for all pairs or a specific pair provided
+
+exits
+	Returns List of dicts containing all Trades, based on exit reason performance
+Can either be average for all pairs or a specific pair provided
+
+forcebuy
+	Buy an asset.
+
+:param pair: Pair to buy (ETH/BTC)
+:param price: Optional - price to buy
+
+forceenter
+	Force entering a trade
+
+:param pair: Pair to buy (ETH/BTC)
+:param side: 'long' or 'short'
+:param price: Optional - price to buy
+:param order_type: Optional keyword argument - 'limit' or 'market'
+:param stake_amount: Optional keyword argument - stake amount (as float)
+:param leverage: Optional keyword argument - leverage (as float)
+:param enter_tag: Optional keyword argument - entry tag (as string, default: 'force_enter')
+
+forceexit
+	Force-exit a trade.
+
+:param tradeid: Id of the trade (can be received via status command)
+:param ordertype: Order type to use (must be market or limit)
+:param amount: Amount to sell. Full sell if not given
+
+health
+	Provides a quick health check of the running bot.
+
+list_custom_data
+	List custom-data of the running bot for a specific trade.
+
+:param trade_id: ID of the trade
+:param key: str, optional - Key of the custom-data
+
+list_open_trades_custom_data
+	List open trades custom-data of the running bot.
+
+:param key: str, optional - Key of the custom-data
+:param limit: limit of trades
+:param offset: trades offset for pagination
+
+lock_add
+	Lock pair
+
+:param pair: Pair to lock
+:param until: Lock until this date (format "2024-03-30 16:00:00Z")
+:param side: Side to lock (long, short, *)
+:param reason: Reason for the lock
+
+locks
+	Return current locks
+
+logs
+	Show latest logs.
+
+:param limit: Limits log messages to the last <limit> logs. No limit to get the entire log.
+
+mix_tags
+	Returns List of dicts containing all Trades, based on entry_tag + exit_reason performance
+Can either be average for all pairs or a specific pair provided
+
+monthly
+	Return the profits for each month, and amount of trades.
+
+pair_candles
+	Return live dataframe for <pair><timeframe>.
+
+:param pair: Pair to get data for
+:param timeframe: Only pairs with this timeframe available.
+:param limit: Limit result to the last n candles.
+:param columns: List of dataframe columns to return. Empty list will return OHLCV.
+
+pair_history
+	Return historic, analyzed dataframe
+
+:param pair: Pair to get data for
+:param timeframe: Only pairs with this timeframe available.
+:param strategy: Strategy to analyze and get values for
+:param freqaimodel: FreqAI model to use for analysis
+:param timerange: Timerange to get data for (same format than --timerange endpoints)
+
+pairlists_available
+	Lists available pairlist providers
+
+performance
+	Return the performance of the different coins.
+
+ping
+	simple ping
+
+plot_config
+	Return plot configuration if the strategy defines one.
+
+profit
+	Return the profit summary.
+
+reload_config
+	Reload configuration.
+
+show_config
+	Returns part of the configuration, relevant for trading operations.
+
+start
+	Start the bot if it's in the stopped state.
+
+stats
+	Return the stats report (durations, sell-reasons).
+
+status
+	Get the status of open trades.
+
+stop
+	Stop the bot. Use `start` to restart.
+
+stopbuy
+	Stop buying (but handle sells gracefully). Use `reload_config` to reset.
+
+strategies
+	Lists available strategies
+
+strategy
+	Get strategy details
+
+:param strategy: Strategy class name
+
+sysinfo
+	Provides system information (CPU, RAM usage)
+
+trade
+	Return specific trade
+
+:param trade_id: Specify which trade to get.
+
+trades
+	Return trades history, sorted by id (or by latest timestamp if order_by_id=False)
+
+:param limit: Limits trades to the X last trades. Max 500 trades.
+:param offset: Offset by this amount of trades.
+:param order_by_id: Sort trades by id (default: True). If False, sorts by latest timestamp.
+
+version
+	Return the version of the bot.
+
+weekly
+	Return the profits for each week, and amount of trades.
+
+whitelist
+	Show the current whitelist.
+
+
+```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade hyperopt-list [-h] [-v] [--no-color] [--logfile FILE] [-V]
                               [-c PATH] [-d PATH] [--userdir PATH] [--best]
                               [--profitable] [--min-trades INT]
@@ -44,21 +44,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,16 +1,16 @@
-```
+``` output
 usage: freqtrade hyperopt-show [-h] [-v] [--no-color] [--logfile FILE] [-V]
                               [-c PATH] [-d PATH] [--userdir PATH] [--best]
                               [--profitable] [-n INT] [--print-json]
                               [--hyperopt-filename FILENAME] [--no-header]
                               [--disable-param-export]
-                               [--breakdown {day,week,month,year} [{day,week,month,year} ...]]
+                               [--breakdown {day,week,month,year,weekday} [{day,week,month,year,weekday} ...]]

 options:
  -h, --help            show this help message and exit
  --best                Select only best epochs.
  --profitable          Select only profitable epochs.
-  -n INT, --index INT   Specify the index of the epoch to print details for.
+  -n, --index INT       Specify the index of the epoch to print details for.
  --print-json          Print output in JSON format.
  --hyperopt-filename FILENAME
                        Hyperopt result filename.Example: `--hyperopt-
@@ -18,29 +18,28 @@ options:
  --no-header           Do not print epoch details header.
  --disable-param-export
                        Disable automatic hyperopt parameter export.
-  --breakdown {day,week,month,year} [{day,week,month,year} ...]
+  --breakdown {day,week,month,year,weekday} [{day,week,month,year,weekday} ...]
                        Show backtesting breakdown per [day, week, month,
-                        year].
+                        year, weekday].

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade hyperopt [-h] [-v] [--no-color] [--logfile FILE] [-V]
                          [-c PATH] [-d PATH] [--userdir PATH] [-s NAME]
                          [--strategy-path PATH] [--recursive-strategy-search]
@@ -11,16 +11,15 @@ usage: freqtrade hyperopt [-h] [-v] [--no-color] [--logfile FILE] [-V]
                          [--eps] [--enable-protections]
                          [--dry-run-wallet DRY_RUN_WALLET]
                          [--timeframe-detail TIMEFRAME_DETAIL] [-e INT]
-                          [--spaces {all,buy,sell,roi,stoploss,trailing,protection,trades,default} [{all,buy,sell,roi,stoploss,trailing,protection,trades,default} ...]]
-                          [--print-all] [--print-json] [-j JOBS]
-                          [--random-state INT] [--min-trades INT]
-                          [--hyperopt-loss NAME] [--disable-param-export]
-                          [--ignore-missing-spaces] [--analyze-per-epoch]
-                          [--early-stop INT]
+                          [--spaces SPACES [SPACES ...]] [--print-all]
+                          [--print-json] [-j JOBS] [--random-state INT]
+                          [--min-trades INT] [--hyperopt-loss NAME]
+                          [--disable-param-export] [--ignore-missing-spaces]
+                          [--analyze-per-epoch] [--early-stop INT]

 options:
  -h, --help            show this help message and exit
-  -i TIMEFRAME, --timeframe TIMEFRAME
+  -i, --timeframe TIMEFRAME
                        Specify timeframe (`1m`, `5m`, `30m`, `1h`, `1d`).
  --timerange TIMERANGE
                        Specify what timerange of data to use.
@@ -35,31 +34,37 @@ options:
                        setting.
  --fee FLOAT           Specify fee ratio. Will be applied twice (on trade
                        entry and exit).
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --hyperopt-path PATH  Specify additional lookup path for Hyperopt Loss
                        functions.
  --eps, --enable-position-stacking
                        Allow buying the same pair multiple times (position
-                        stacking).
+                        stacking). Only applicable to backtesting and
+                        hyperopt. Results archived by this cannot be
+                        reproduced in dry/live trading.
  --enable-protections, --enableprotections
-                        Enable protections for backtesting.Will slow
+                        Enable protections for backtesting. Will slow
                        backtesting down by a considerable amount, but will
                        include configured protections
-  --dry-run-wallet DRY_RUN_WALLET, --starting-balance DRY_RUN_WALLET
+  --dry-run-wallet, --starting-balance DRY_RUN_WALLET
                        Starting balance, used for backtesting / hyperopt and
                        dry-runs.
  --timeframe-detail TIMEFRAME_DETAIL
                        Specify detail timeframe for backtesting (`1m`, `5m`,
                        `30m`, `1h`, `1d`).
-  -e INT, --epochs INT  Specify number of epochs (default: 100).
-  --spaces {all,buy,sell,roi,stoploss,trailing,protection,trades,default} [{all,buy,sell,roi,stoploss,trailing,protection,trades,default} ...]
+  -e, --epochs INT      Specify number of epochs (default: 100).
+  --spaces SPACES [SPACES ...]
                        Specify which parameters to hyperopt. Space-separated
-                        list.
+                        list. Available builtin options (custom spaces will
+                        not be listed here): default, all, buy, sell, enter,
+                        exit, roi, stoploss, trailing, protection, trades.
+                        Default: `default` - which includes all spaces except
+                        for 'trailing', 'protection', and 'trades'.
  --print-all           Print all results, not only the best ones.
  --print-json          Print output in JSON format.
-  -j JOBS, --job-workers JOBS
+  -j, --job-workers JOBS
                        The number of concurrently running jobs for
                        hyperoptimization (hyperopt worker processes). If -1
                        (default), all CPUs are used, for -2, all CPUs but one
@@ -69,7 +74,7 @@ options:
                        reproducible hyperopt results.
  --min-trades INT      Set minimal desired number of trades for evaluations
                        in the hyperopt optimization path (default: 1).
-  --hyperopt-loss NAME, --hyperoptloss NAME
+  --hyperopt-loss, --hyperoptloss NAME
                        Specify the class name of the hyperopt loss function
                        class (IHyperOptLoss). Different functions can
                        generate completely different results, since the
@@ -95,26 +100,24 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 Strategy arguments:
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade install-ui [-h] [--erase] [--prerelease]
                            [--ui-version UI_VERSION]

@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade list-data [-h] [-v] [--no-color] [--logfile FILE] [-V]
                           [-c PATH] [-d PATH] [--userdir PATH]
                           [--exchange EXCHANGE]
@@ -18,10 +18,10 @@ options:
                        Storage format for downloaded trades data. (default:
                        `feather`).
  --trades              Work on trades data instead of OHLCV data.
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
-  --trading-mode {spot,margin,futures}, --tradingmode {spot,margin,futures}
+  --trading-mode, --tradingmode {spot,margin,futures}
                        Select Trading mode
  --show-timerange      Show timerange available for available data. (May take
                        a while to calculate).
@@ -30,21 +30,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,31 +1,35 @@
-```
+``` output
 usage: freqtrade list-exchanges [-h] [-v] [--no-color] [--logfile FILE] [-V]
                                [-c PATH] [-d PATH] [--userdir PATH] [-1] [-a]
+                                [--trading-mode {spot,margin,futures}]
+                                [--dex-exchanges]

 options:
  -h, --help            show this help message and exit
  -1, --one-column      Print output in one column.
  -a, --all             Print all exchanges known to the ccxt library.
+  --trading-mode, --tradingmode {spot,margin,futures}
+                        Select Trading mode
+  --dex-exchanges       Print only DEX exchanges.

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade list-freqaimodels [-h] [-v] [--no-color] [--logfile FILE]
                                   [-V] [-c PATH] [-d PATH] [--userdir PATH]
                                   [--freqaimodel-path PATH] [-1]
@@ -13,21 +13,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade list-hyperoptloss [-h] [-v] [--no-color] [--logfile FILE]
                                   [-V] [-c PATH] [-d PATH] [--userdir PATH]
                                   [--hyperopt-path PATH] [-1]
@@ -13,21 +13,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade list-markets [-h] [-v] [--no-color] [--logfile FILE] [-V]
                              [-c PATH] [-d PATH] [--userdir PATH]
                              [--exchange EXCHANGE] [--print-list]
@@ -21,28 +21,27 @@ options:
                        Specify quote currency(-ies). Space-separated list.
  -a, --all             Print all pairs or market symbols. By default only
                        active ones are shown.
-  --trading-mode {spot,margin,futures}, --tradingmode {spot,margin,futures}
+  --trading-mode, --tradingmode {spot,margin,futures}
                        Select Trading mode

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade list-pairs [-h] [-v] [--no-color] [--logfile FILE] [-V]
                            [-c PATH] [-d PATH] [--userdir PATH]
                            [--exchange EXCHANGE] [--print-list]
@@ -21,28 +21,27 @@ options:
                        Specify quote currency(-ies). Space-separated list.
  -a, --all             Print all pairs or market symbols. By default only
                        active ones are shown.
-  --trading-mode {spot,margin,futures}, --tradingmode {spot,margin,futures}
+  --trading-mode, --tradingmode {spot,margin,futures}
                        Select Trading mode

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade list-strategies [-h] [-v] [--no-color] [--logfile FILE] [-V]
                                 [-c PATH] [-d PATH] [--userdir PATH]
                                 [--strategy-path PATH] [-1]
@@ -16,21 +16,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,32 +1,34 @@
-```
+``` output
 usage: freqtrade list-timeframes [-h] [-v] [--no-color] [--logfile FILE] [-V]
                                 [-c PATH] [-d PATH] [--userdir PATH]
                                 [--exchange EXCHANGE] [-1]
+                                 [--trading-mode {spot,margin,futures}]

 options:
  -h, --help            show this help message and exit
  --exchange EXCHANGE   Exchange name. Only valid if no config is provided.
  -1, --one-column      Print output in one column.
+  --trading-mode, --tradingmode {spot,margin,futures}
+                        Select Trading mode

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade lookahead-analysis [-h] [-v] [--no-color] [--logfile FILE]
                                    [-V] [-c PATH] [-d PATH] [--userdir PATH]
                                    [-s NAME] [--strategy-path PATH]
@@ -11,19 +11,22 @@ usage: freqtrade lookahead-analysis [-h] [-v] [--no-color] [--logfile FILE]
                                    [--stake-amount STAKE_AMOUNT]
                                    [--fee FLOAT] [-p PAIRS [PAIRS ...]]
                                    [--enable-protections]
+                                    [--enable-dynamic-pairlist]
                                    [--dry-run-wallet DRY_RUN_WALLET]
                                    [--timeframe-detail TIMEFRAME_DETAIL]
                                    [--strategy-list STRATEGY_LIST [STRATEGY_LIST ...]]
                                    [--export {none,trades,signals}]
-                                    [--export-filename PATH]
+                                    [--backtest-filename PATH]
+                                    [--backtest-directory PATH]
                                    [--freqai-backtest-live-models]
                                    [--minimum-trade-amount INT]
                                    [--targeted-trade-amount INT]
                                    [--lookahead-analysis-exportfilename LOOKAHEAD_ANALYSIS_EXPORTFILENAME]
+                                    [--allow-limit-orders]

 options:
  -h, --help            show this help message and exit
-  -i TIMEFRAME, --timeframe TIMEFRAME
+  -i, --timeframe TIMEFRAME
                        Specify timeframe (`1m`, `5m`, `30m`, `1h`, `1d`).
  --timerange TIMERANGE
                        Specify what timerange of data to use.
@@ -38,14 +41,19 @@ options:
                        setting.
  --fee FLOAT           Specify fee ratio. Will be applied twice (on trade
                        entry and exit).
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --enable-protections, --enableprotections
-                        Enable protections for backtesting.Will slow
+                        Enable protections for backtesting. Will slow
                        backtesting down by a considerable amount, but will
                        include configured protections
-  --dry-run-wallet DRY_RUN_WALLET, --starting-balance DRY_RUN_WALLET
+  --enable-dynamic-pairlist
+                        Enables dynamic pairlist refreshes in backtesting. The
+                        pairlist will be generated for each new candle if
+                        you're using a pairlist handler that supports this
+                        feature, for example, ShuffleFilter.
+  --dry-run-wallet, --starting-balance DRY_RUN_WALLET
                        Starting balance, used for backtesting / hyperopt and
                        dry-runs.
  --timeframe-detail TIMEFRAME_DETAIL
@@ -54,16 +62,18 @@ options:
  --strategy-list STRATEGY_LIST [STRATEGY_LIST ...]
                        Provide a space-separated list of strategies to
                        backtest. Please note that timeframe needs to be set
-                        either in config or via command line. When using this
-                        together with `--export trades`, the strategy-name is
-                        injected into the filename (so `backtest-data.json`
-                        becomes `backtest-data-SampleStrategy.json`
+                        either in config or via command line.
  --export {none,trades,signals}
                        Export backtest results (default: trades).
-  --export-filename PATH, --backtest-filename PATH
-                        Use this filename for backtest results.Requires
-                        `--export` to be set as well. Example: `--export-filen
-                        ame=user_data/backtest_results/backtest_today.json`
+  --backtest-filename, --export-filename PATH
+                        Use this filename for backtest results.Example:
+                        `--backtest-
+                        filename=backtest_results_2020-09-27_16-20-48.json`.
+                        Assumes either `user_data/backtest_results/` or
+                        `--export-directory` as base directory.
+  --backtest-directory, --export-directory PATH
+                        Directory to use for backtest results. Example:
+                        `--export-directory=user_data/backtest_results/`.
  --freqai-backtest-live-models
                        Run backtest with ready models.
  --minimum-trade-amount INT
@@ -73,31 +83,31 @@ options:
  --lookahead-analysis-exportfilename LOOKAHEAD_ANALYSIS_EXPORTFILENAME
                        Use this csv-filename to store lookahead-analysis-
                        results
+  --allow-limit-orders  Allow limit orders in lookahead analysis (could cause
+                        false positives in lookahead analysis results).

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 Strategy arguments:
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
@@ -1,7 +1,6 @@
-```
+``` output
 usage: freqtrade [-h] [-V]
-                 {trade,create-userdir,new-config,show-config,new-strategy,download-data,convert-data,convert-trade-data,trades-to-ohlcv,list-data,backtesting,backtesting-show,backtesting-analysis,edge,hyperopt,hyperopt-list,hyperopt-show,list-exchanges,list-markets,list-pairs,list-strategies,list-hyperoptloss,list-freqaimodels,list-timeframes,show-trades,test-pairlist,convert-db,install-ui,plot-dataframe,plot-profit,webserver,strategy-updater,lookahead-analysis,recursive-analysis}
-                 ...
+                 {trade,create-userdir,new-config,show-config,new-strategy,download-data,convert-data,convert-trade-data,trades-to-ohlcv,list-data,backtesting,backtesting-show,backtesting-analysis,edge,hyperopt,hyperopt-list,hyperopt-show,list-exchanges,list-markets,list-pairs,list-strategies,list-hyperoptloss,list-freqaimodels,list-timeframes,show-trades,test-pairlist,convert-db,install-ui,plot-dataframe,plot-profit,webserver,strategy-updater,lookahead-analysis,recursive-analysis} ...

 Free, open source crypto trading bot

@@ -22,7 +21,7 @@ positional arguments:
    backtesting-show    Show past Backtest results
    backtesting-analysis
                        Backtest Analysis module.
-    edge                Edge module.
+    edge                Edge module. No longer part of Freqtrade
    hyperopt            Hyperopt module.
    hyperopt-list       List Hyperopt results
    hyperopt-show       Show details of Hyperopt results
@@ -1,12 +1,11 @@
-```
+``` output
 usage: freqtrade new-config [-h] [-c PATH]

 options:
-  -h, --help            show this help message and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
-                        `userdir/config.json` or `config.json` whichever
-                        exists). Multiple --config options may be used. Can be
-                        set to `-` to read config from stdin.
+  -h, --help         show this help message and exit
+  -c, --config PATH  Specify configuration file (default:
+                     `userdir/config.json` or `config.json` whichever exists).
+                     Multiple --config options may be used. Can be set to `-`
+                     to read config from stdin.

 ```
@@ -1,14 +1,13 @@
-```
+``` output
 usage: freqtrade new-strategy [-h] [--userdir PATH] [-s NAME]
                              [--strategy-path PATH]
                              [--template {full,minimal,advanced}]

 options:
  -h, --help            show this help message and exit
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --template {full,minimal,advanced}
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade plot-dataframe [-h] [-v] [--no-color] [--logfile FILE] [-V]
                                [-c PATH] [-d PATH] [--userdir PATH] [-s NAME]
                                [--strategy-path PATH]
@@ -10,13 +10,13 @@ usage: freqtrade plot-dataframe [-h] [-v] [--no-color] [--logfile FILE] [-V]
                                [--plot-limit INT] [--db-url PATH]
                                [--trade-source {DB,file}]
                                [--export {none,trades,signals}]
-                                [--export-filename PATH]
+                                [--backtest-filename PATH]
                                [--timerange TIMERANGE] [-i TIMEFRAME]
                                [--no-trades]

 options:
  -h, --help            show this help message and exit
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --indicators1 INDICATORS1 [INDICATORS1 ...]
@@ -38,13 +38,15 @@ options:
                        (backtest file)) Default: file
  --export {none,trades,signals}
                        Export backtest results (default: trades).
-  --export-filename PATH, --backtest-filename PATH
-                        Use this filename for backtest results.Requires
-                        `--export` to be set as well. Example: `--export-filen
-                        ame=user_data/backtest_results/backtest_today.json`
+  --backtest-filename, --export-filename PATH
+                        Use this filename for backtest results.Example:
+                        `--backtest-
+                        filename=backtest_results_2020-09-27_16-20-48.json`.
+                        Assumes either `user_data/backtest_results/` or
+                        `--export-directory` as base directory.
  --timerange TIMERANGE
                        Specify what timerange of data to use.
-  -i TIMEFRAME, --timeframe TIMEFRAME
+  -i, --timeframe TIMEFRAME
                        Specify timeframe (`1m`, `5m`, `30m`, `1h`, `1d`).
  --no-trades           Skip using trades from backtesting file and DB.

@@ -52,26 +54,24 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 Strategy arguments:
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade plot-profit [-h] [-v] [--no-color] [--logfile FILE] [-V]
                             [-c PATH] [-d PATH] [--userdir PATH] [-s NAME]
                             [--strategy-path PATH]
@@ -6,23 +6,25 @@ usage: freqtrade plot-profit [-h] [-v] [--no-color] [--logfile FILE] [-V]
                             [--freqaimodel NAME] [--freqaimodel-path PATH]
                             [-p PAIRS [PAIRS ...]] [--timerange TIMERANGE]
                             [--export {none,trades,signals}]
-                             [--export-filename PATH] [--db-url PATH]
+                             [--backtest-filename PATH] [--db-url PATH]
                             [--trade-source {DB,file}] [-i TIMEFRAME]
                             [--auto-open]

 options:
  -h, --help            show this help message and exit
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --timerange TIMERANGE
                        Specify what timerange of data to use.
  --export {none,trades,signals}
                        Export backtest results (default: trades).
-  --export-filename PATH, --backtest-filename PATH
-                        Use this filename for backtest results.Requires
-                        `--export` to be set as well. Example: `--export-filen
-                        ame=user_data/backtest_results/backtest_today.json`
+  --backtest-filename, --export-filename PATH
+                        Use this filename for backtest results.Example:
+                        `--backtest-
+                        filename=backtest_results_2020-09-27_16-20-48.json`.
+                        Assumes either `user_data/backtest_results/` or
+                        `--export-directory` as base directory.
  --db-url PATH         Override trades database URL, this is useful in custom
                        deployments (default: `sqlite:///tradesv3.sqlite` for
                        Live Run mode, `sqlite:///tradesv3.dryrun.sqlite` for
@@ -30,7 +32,7 @@ options:
  --trade-source {DB,file}
                        Specify the source for trades (Can be DB or file
                        (backtest file)) Default: file
-  -i TIMEFRAME, --timeframe TIMEFRAME
+  -i, --timeframe TIMEFRAME
                        Specify timeframe (`1m`, `5m`, `30m`, `1h`, `1d`).
  --auto-open           Automatically open generated plot.

@@ -38,26 +40,24 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 Strategy arguments:
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade recursive-analysis [-h] [-v] [--no-color] [--logfile FILE]
                                    [-V] [-c PATH] [-d PATH] [--userdir PATH]
                                    [-s NAME] [--strategy-path PATH]
@@ -12,14 +12,14 @@ usage: freqtrade recursive-analysis [-h] [-v] [--no-color] [--logfile FILE]

 options:
  -h, --help            show this help message and exit
-  -i TIMEFRAME, --timeframe TIMEFRAME
+  -i, --timeframe TIMEFRAME
                        Specify timeframe (`1m`, `5m`, `30m`, `1h`, `1d`).
  --timerange TIMERANGE
                        Specify what timerange of data to use.
  --data-format-ohlcv {json,jsongz,feather,parquet}
                        Storage format for downloaded candle (OHLCV) data.
                        (default: `feather`).
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
  --startup-candle STARTUP_CANDLE [STARTUP_CANDLE ...]
@@ -30,26 +30,24 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 Strategy arguments:
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
@@ -1,13 +1,12 @@
-```
+``` output
 usage: freqtrade show-config [-h] [--userdir PATH] [-c PATH]
                             [--show-sensitive]

 options:
  -h, --help            show this help message and exit
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade show-trades [-h] [-v] [--no-color] [--logfile FILE] [-V]
                             [-c PATH] [-d PATH] [--userdir PATH]
                             [--db-url PATH]
@@ -19,21 +19,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade strategy-updater [-h] [-v] [--no-color] [--logfile FILE] [-V]
                                  [-c PATH] [-d PATH] [--userdir PATH]
                                  [--strategy-list STRATEGY_LIST [STRATEGY_LIST ...]]
@@ -10,10 +10,7 @@ options:
  --strategy-list STRATEGY_LIST [STRATEGY_LIST ...]
                        Provide a space-separated list of strategies to
                        backtest. Please note that timeframe needs to be set
-                        either in config or via command line. When using this
-                        together with `--export trades`, the strategy-name is
-                        injected into the filename (so `backtest-data.json`
-                        becomes `backtest-data-SampleStrategy.json`
+                        either in config or via command line.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
                        Recursively search for a strategy in the strategies
@@ -23,21 +20,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,15 +1,14 @@
-```
+``` output
 usage: freqtrade test-pairlist [-h] [--userdir PATH] [-v] [-c PATH]
                               [--quote QUOTE_CURRENCY [QUOTE_CURRENCY ...]]
                               [-1] [--print-json] [--exchange EXCHANGE]

 options:
  -h, --help            show this help message and exit
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade trade [-h] [-v] [--no-color] [--logfile FILE] [-V] [-c PATH]
                       [-d PATH] [--userdir PATH] [-s NAME]
                       [--strategy-path PATH] [--recursive-strategy-search]
@@ -15,7 +15,7 @@ options:
  --sd-notify           Notify systemd service manager.
  --dry-run             Enforce dry-run for trading (removes Exchange secrets
                        and simulates trades).
-  --dry-run-wallet DRY_RUN_WALLET, --starting-balance DRY_RUN_WALLET
+  --dry-run-wallet, --starting-balance DRY_RUN_WALLET
                        Starting balance, used for backtesting / hyperopt and
                        dry-runs.
  --fee FLOAT           Specify fee ratio. Will be applied twice (on trade
@@ -25,26 +25,24 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 Strategy arguments:
-  -s NAME, --strategy NAME
-                        Specify strategy class name which will be used by the
+  -s, --strategy NAME   Specify strategy class name which will be used by the
                        bot.
  --strategy-path PATH  Specify additional strategy lookup path.
  --recursive-strategy-search
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade trades-to-ohlcv [-h] [-v] [--no-color] [--logfile FILE] [-V]
                                 [-c PATH] [-d PATH] [--userdir PATH]
                                 [-p PAIRS [PAIRS ...]]
@@ -10,10 +10,10 @@ usage: freqtrade trades-to-ohlcv [-h] [-v] [--no-color] [--logfile FILE] [-V]

 options:
  -h, --help            show this help message and exit
-  -p PAIRS [PAIRS ...], --pairs PAIRS [PAIRS ...]
+  -p, --pairs PAIRS [PAIRS ...]
                        Limit command to these pairs. Pairs are space-
                        separated.
-  -t TIMEFRAMES [TIMEFRAMES ...], --timeframes TIMEFRAMES [TIMEFRAMES ...]
+  -t, --timeframes TIMEFRAMES [TIMEFRAMES ...]
                        Specify which tickers to download. Space-separated
                        list. Default: `1m 5m`.
  --exchange EXCHANGE   Exchange name. Only valid if no config is provided.
@@ -23,28 +23,27 @@ options:
  --data-format-trades {json,jsongz,feather,parquet}
                        Storage format for downloaded trades data. (default:
                        `feather`).
-  --trading-mode {spot,margin,futures}, --tradingmode {spot,margin,futures}
+  --trading-mode, --tradingmode {spot,margin,futures}
                        Select Trading mode

 Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -1,4 +1,4 @@
-```
+``` output
 usage: freqtrade webserver [-h] [-v] [--no-color] [--logfile FILE] [-V]
                           [-c PATH] [-d PATH] [--userdir PATH]

@@ -9,21 +9,20 @@ Common arguments:
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --no-color            Disable colorization of hyperopt results. May be
                        useful if you are redirecting output to a file.
-  --logfile FILE, --log-file FILE
+  --logfile, --log-file FILE
                        Log to the file specified. Special values are:
                        'syslog', 'journald'. See the documentation for more
                        details.
  -V, --version         show program's version number and exit
-  -c PATH, --config PATH
-                        Specify configuration file (default:
+  -c, --config PATH     Specify configuration file (default:
                        `userdir/config.json` or `config.json` whichever
                        exists). Multiple --config options may be used. Can be
                        set to `-` to read config from stdin.
-  -d PATH, --datadir PATH, --data-dir PATH
+  -d, --datadir, --data-dir PATH
                        Path to the base directory of the exchange with
                        historical backtesting data. To see futures data, use
                        trading-mode additionally.
-  --userdir PATH, --user-data-dir PATH
+  --userdir, --user-data-dir PATH
                        Path to userdata directory.

 ```
@@ -191,7 +191,7 @@ Mandatory parameters are marked as **Required**, which means that they are requi
 | | **Unfilled timeout**
 | `unfilledtimeout.entry` | **Required.** How long (in minutes or seconds) the bot will wait for an unfilled entry order to complete, after which the order will be cancelled. [Strategy Override](#parameters-in-the-strategy).<br> **Datatype:** Integer
 | `unfilledtimeout.exit` | **Required.** How long (in minutes or seconds) the bot will wait for an unfilled exit order to complete, after which the order will be cancelled and repeated at current (new) price, as long as there is a signal. [Strategy Override](#parameters-in-the-strategy).<br> **Datatype:** Integer
-| `unfilledtimeout.unit` | Unit to use in unfilledtimeout setting. Note: If you set unfilledtimeout.unit to "seconds", "internals.process_throttle_secs" must be inferior or equal to timeout [Strategy Override](#parameters-in-the-strategy). <br> *Defaults to `"minutes"`.* <br> **Datatype:** String
+| `unfilledtimeout.unit` | Unit to use in unfilledtimeout setting. Note: If you set `unfilledtimeout.unit` to "seconds", "internals.process_throttle_secs" must be inferior or equal to timeout [Strategy Override](#parameters-in-the-strategy). <br> *Defaults to `"minutes"`.* <br> **Datatype:** String
 | `unfilledtimeout.exit_timeout_count` | How many times can exit orders time out. Once this number of timeouts is reached, an emergency exit is triggered. 0 to disable and allow unlimited order cancels. [Strategy Override](#parameters-in-the-strategy).<br>*Defaults to `0`.* <br> **Datatype:** Integer
 | | **Pricing**
 | `entry_pricing.price_side` | Select the side of the spread the bot should look at to get the entry rate. [More information below](#entry-price).<br> *Defaults to `"same"`.* <br> **Datatype:** String (either `ask`, `bid`, `same` or `other`).
@@ -229,19 +229,18 @@ Mandatory parameters are marked as **Required**, which means that they are requi
 | `exchange.enable_ws` | Enable the usage of Websockets for the exchange. <br>[More information](#consuming-exchange-websockets).<br>*Defaults to `true`.* <br> **Datatype:** Boolean
 | `exchange.markets_refresh_interval` | The interval in minutes in which markets are reloaded. <br>*Defaults to `60` minutes.* <br> **Datatype:** Positive Integer
 | `exchange.skip_open_order_update` | Skips open order updates on startup should the exchange cause problems. Only relevant in live conditions.<br>*Defaults to `false`*<br> **Datatype:** Boolean
-| `exchange.unknown_fee_rate` | Fallback value to use when calculating trading fees. This can be useful for exchanges which have fees in non-tradable currencies. The value provided here will be multiplied with the "fee cost".<br>*Defaults to `None`<br> **Datatype:** float
+| `exchange.unknown_fee_rate` | Fallback value to use when calculating trading fees. This can be useful for exchanges which have fees in non-tradable currencies. The value provided here will be multiplied with the "fee cost".<br>*Defaults to `None`*<br> **Datatype:** float
 | `exchange.log_responses` | Log relevant exchange responses. For debug mode only - use with care.<br>*Defaults to `false`*<br> **Datatype:** Boolean
 | `exchange.only_from_ccxt` | Prevent data-download from data.binance.vision. Leaving this as false can greatly speed up downloads, but may be problematic if the site is not available.<br>*Defaults to `false`*<br> **Datatype:** Boolean
 | `experimental.block_bad_exchanges` | Block exchanges known to not work with freqtrade. Leave on default unless you want to test if that exchange works now. <br>*Defaults to `true`.* <br> **Datatype:** Boolean
 | | **Plugins**
-| `edge.*` | Please refer to [edge configuration document](edge.md) for detailed explanation of all possible configuration options.
 | `pairlists` | Define one or more pairlists to be used. [More information](plugins.md#pairlists-and-pairlist-handlers). <br>*Defaults to `StaticPairList`.*  <br> **Datatype:** List of Dicts
 | | **Telegram**
 | `telegram.enabled` | Enable the usage of Telegram. <br> **Datatype:** Boolean
 | `telegram.token` | Your Telegram bot token. Only required if `telegram.enabled` is `true`. <br>**Keep it in secret, do not disclose publicly.** <br> **Datatype:** String
 | `telegram.chat_id` | Your personal Telegram account id. Only required if `telegram.enabled` is `true`. <br>**Keep it in secret, do not disclose publicly.** <br> **Datatype:** String
 | `telegram.balance_dust_level` | Dust-level (in stake currency) - currencies with a balance below this will not be shown by `/balance`. <br> **Datatype:** float
-| `telegram.reload` | Allow "reload" buttons on telegram messages. <br>*Defaults to `true`.<br> **Datatype:** boolean
+| `telegram.reload` | Allow "reload" buttons on telegram messages. <br>*Defaults to `true`.*<br> **Datatype:** boolean
 | `telegram.notification_settings.*` | Detailed notification settings. Refer to the [telegram documentation](telegram-usage.md) for details.<br> **Datatype:** dictionary
 | `telegram.allow_custom_messages` | Enable the sending of Telegram messages from strategies via the dataprovider.send_msg() function. <br> **Datatype:** Boolean
 | | **Webhook**
@@ -281,8 +280,8 @@ Mandatory parameters are marked as **Required**, which means that they are requi
 | `add_config_files` | Additional config files. These files will be loaded and merged with the current config file. The files are resolved relative to the initial file.<br> *Defaults to `[]`*. <br> **Datatype:** List of strings
 | `dataformat_ohlcv` | Data format to use to store historical candle (OHLCV) data. <br> *Defaults to `feather`*. <br> **Datatype:** String
 | `dataformat_trades` | Data format to use to store historical trades data. <br> *Defaults to `feather`*. <br> **Datatype:** String
-| `reduce_df_footprint` | Recast all numeric columns to float32/int32, with the objective of reducing ram/disk usage (and decreasing train/inference timing backtesting/hyperopt and in FreqAI). <br> **Datatype:** Boolean. <br> Default: `False`.
-| `log_config` | Dictionary containing the log config for python logging. [more info](advanced-setup.md#advanced-logging) <br> **Datatype:** dict. <br> Default: `FtRichHandler`
+| `reduce_df_footprint` | Recast all numeric columns to float32/int32, with the objective of reducing ram/disk usage (and decreasing train/inference timing backtesting/hyperopt and in FreqAI). <br> Default: `False`. <br> **Datatype:** Boolean.
+| `log_config` | Dictionary containing the log config for python logging. [more info](advanced-setup.md#advanced-logging) <br> Default: `FtRichHandler` <br> **Datatype:** dict.

 ### Parameters in the strategy

@@ -567,14 +566,12 @@ Configuration:

 ### Understand order_time_in_force

-The `order_time_in_force` configuration parameter defines the policy by which the order
-is executed on the exchange. Three commonly used time in force are:
+The `order_time_in_force` configuration parameter defines the policy by which the order is executed on the exchange.  
+Commonly used time in force are:

 **GTC (Good Till Canceled):**

-This is most of the time the default time in force. It means the order will remain
-on exchange till it is cancelled by the user. It can be fully or partially fulfilled.
-If partially fulfilled, the remaining will stay on the exchange till cancelled.
+This is most of the time the default time in force. It means the order will remain on exchange till it is cancelled by the user. It can be fully or partially fulfilled. If partially fulfilled, the remaining will stay on the exchange till cancelled.

 **FOK (Fill Or Kill):**

@@ -582,19 +579,22 @@ It means if the order is not executed immediately AND fully then it is cancelled

 **IOC (Immediate Or Canceled):**

-It is the same as FOK (above) except it can be partially fulfilled. The remaining part
-is automatically cancelled by the exchange.
+It is the same as FOK (above) except it can be partially fulfilled. The remaining part is automatically cancelled by the exchange.
+
+Not necessarily recommended, as this can lead to partial fills below the minimum trade size.

 **PO (Post only):**

 Post only order. The order is either placed as a maker order, or it is canceled.
 This means the order must be placed on orderbook for at least time in an unfilled state.

+Please check the [Exchange documentation](exchanges.md) for supported time in force values for your exchange.
+
 #### time_in_force config

 The `order_time_in_force` parameter contains a dict with entry and exit time in force policy values.
 This can be set in the configuration file or in the strategy.
-Values set in the configuration file overwrites values set in the strategy.
+Values set in the configuration file overwrite values from in the strategy, following the regular [precedence rules](#configuration-option-prevalence).

 The possible values are: `GTC` (default), `FOK` or `IOC`.

@@ -606,9 +606,9 @@ The possible values are: `GTC` (default), `FOK` or `IOC`.
 ```

 !!! Warning
-    This is ongoing work. For now, it is supported only for binance, gate and kucoin.
    Please don't change the default value unless you know what you are doing and have researched the impact of using different values for your particular exchange.

+
 ### Fiat conversion

 Freqtrade uses the Coingecko API to convert the coin value to it's corresponding fiat value for the Telegram reports.
@@ -675,7 +675,7 @@ Should you experience problems you suspect are caused by websockets, you can dis
 Should you be required to use a proxy, please refer to the [proxy section](#using-a-proxy-with-freqtrade) for more information.

 !!! Info "Rollout"
-    We're implementing this out slowly, ensuring stability of your bots.
+    We're rolling this out slowly, ensuring stability of your bots.
    Currently, usage is limited to ohlcv data streams.
    It's also limited to a few exchanges, with new exchanges being added on an ongoing basis.

@@ -60,6 +60,7 @@ freqtrade download-data --exchange binance --pairs ".*/USDT"
 * Given starting points are ignored if data is already available, downloading only missing data up to today.
 * Use `--timeframes` to specify what timeframe download the historical candle (OHLCV) data for. Default is `--timeframes 1m 5m` which will download 1-minute and 5-minute data.
 * To use exchange, timeframe and list of pairs as defined in your configuration file, use the `-c/--config` option. With this, the script uses the whitelist defined in the config as the list of currency pairs to download data for and does not require the pairs.json file. You can combine `-c/--config` with most other options.
+* When downloading futures data (`--trading-mode futures` or a configuration specifying futures mode), freqtrade will automatically download the necessary candle types (e.g. `mark` and `funding_rate` candles) unless specified otherwise via `--candle-types`.

 ??? Note "Permission denied errors"
    If your configuration directory `user_data` was made by docker, you may get the following error:
@@ -268,6 +269,8 @@ If `--convert` is also provided, the resample step will happen automatically and
 !!! Note "Kraken user"
    Kraken users should read [this](exchanges.md#historic-kraken-data) before starting to download data.

+    Kraken Futures uses standard OHLCV downloads and does not require `--dl-trades`.
+
 Example call:

 ```bash
@@ -93,3 +93,55 @@ Please use the [`convert-data` subcommand](data-download.md#sub-command-convert-

 Configuring syslog and journald via `--logfile systemd` and `--logfile journald` respectively has been deprecated in 2025.3.
 Please use configuration based [log setup](advanced-setup.md#advanced-logging) instead.
+
+## Removal of the edge module
+
+The edge module has been deprecated in 2023.9 and removed in 2025.6.
+All functionalities of edge have been removed, and having edge configured will result in an error.
+
+## Adjustment to dynamic funding rate handling
+
+With version 2025.12, the handling of dynamic funding rates has been adjusted to also support dynamic funding rates down to 1h funding intervals.
+As a consequence, the mark and funding rate timeframes have been changed to 1h for every supported futures exchange.
+
+As the timeframe for both mark and funding_fee candles has changed (usually from 8h to 1h) - already downloaded data will have to be adjusted or partially re-downloaded.
+You can either re-download everything (`freqtrade download-data [...] --erase` - :warning: can take a long time) - or download the updated data selectively.
+
+### Strategy
+
+Most strategies should not need adjustments to continue to work as expected - however, strategies using `@informative("8h", candle_type="funding_rate")` or similar will have to switch the timeframe to 1h.
+The same is true for `dp.get_pair_dataframe(metadata["pair"], "8h", candle_type="funding_rate")` - which will need to be switched to 1h.
+
+freqtrade will auto-adjust the timeframe and return `funding_rates` despite the wrongly given timeframe. It'll issue a warning - and may still break your strategy.
+
+### Selective data re-download
+
+The script below should serve as an example - you may need to adjust the timeframe and exchange to your needs!
+
+``` bash
+# Cleanup no longer needed data
+rm user_data/data/<exchange>/futures/*-mark*
+rm user_data/data/<exchange>/futures/*-funding_rate*
+
+# download new data (only required once to fix the mark and funding fee data)
+freqtrade download-data -t 1h --trading-mode futures --candle-types funding_rate mark [...] --timerange <full timerange you've got other data for>
+
+```
+
+The result of the above will be that your funding_rates and mark data will have the 1h timeframe.
+you can verify this with `freqtrade list-data --exchange <yourexchange> --show`.
+
+!!! Note "Additional arguments"
+    Additional arguments to the above commands may be necessary, like configuration files or explicit user_data if they deviate from the default.
+
+**Hyperliquid** is a special case now - which will no longer require 1h mark data - but will use regular candles instead (this data never existed and is identical to 1h futures candles). As we don't support download-data for hyperliquid (they don't provide historic data) - there won't be actions necessary for hyperliquid users.
+
+## Catboost models in freqAI
+
+CatBoost models have been removed with version 2025.12 and are no longer actively supported.
+If you have existing bots using CatBoost models, you can still use them in your custom models by copy/pasting them from the git history (as linked below) and installing the Catboost library manually.
+We do however recommend switching to other supported model libraries like LightGBM or XGBoost for better support and future compatibility.
+
+* [CatboostRegressor](https://github.com/freqtrade/freqtrade/blob/c6f3b0081927e161a16b116cc47fb663f7831d30/freqtrade/freqai/prediction_models/CatboostRegressor.py)
+* [CatboostClassifier](https://github.com/freqtrade/freqtrade/blob/c6f3b0081927e161a16b116cc47fb663f7831d30/freqtrade/freqai/prediction_models/CatboostClassifier.py)
+* [CatboostClassifierMultiTarget](https://github.com/freqtrade/freqtrade/blob/c6f3b0081927e161a16b116cc47fb663f7831d30/freqtrade/freqai/prediction_models/CatboostClassifierMultiTarget.py)
@@ -26,10 +26,19 @@ Alternatively (e.g. if your system is not supported by the setup.sh script), fol

 This will install all required tools for development, including `pytest`, `ruff`, `mypy`, and `coveralls`.

-Then install the git hook scripts by running `pre-commit install`, so your changes will be verified locally before committing.
-This avoids a lot of waiting for CI already, as some basic formatting checks are done locally on your machine.
+Run the following command to install the git hook scripts:

-Before opening a pull request, please familiarize yourself with our [Contributing Guidelines](https://github.com/freqtrade/freqtrade/blob/develop/CONTRIBUTING.md).
+``` bash
+pre-commit install
+```
+
+These pre-commit scripts check your changes automatically before each commit.  
+If any formatting issues are found, the commit will fail and will prompt for fixes.
+This reduces unnecessary CI failures, reduces maintenance burden, and improves code quality.
+
+You can run the checks manually when necessary with `pre-commit run -a`.  
+
+Before opening a pull request, please also familiarize yourself with our [Contributing Guidelines](https://github.com/freqtrade/freqtrade/blob/develop/CONTRIBUTING.md).

 ### Devcontainer setup

@@ -304,6 +313,13 @@ The `IProtection` parent class provides a helper method for this in `calculate_l

 Most exchanges supported by CCXT should work out of the box.

+If you need to implement a specific exchange class, these are found in the `freqtrade/exchange` source folder. You'll also need to add the import to `freqtrade/exchange/__init__.py` to make the loading logic aware of the new exchange.  
+We recommend looking at existing exchange implementations to get an idea of what might be required.
+
+!!! Warning
+    Implementing and testing an exchange can be a lot of trial and error, so please bear this in mind.
+    You should also have some development experience, as this is not a beginner task.
+
 To quickly test the public endpoints of an exchange, add a configuration for your exchange to `tests/exchange_online/conftest.py` and run these tests with `pytest --longrun tests/exchange_online/test_ccxt_compat.py`.
 Completing these tests successfully a good basis point (it's a requirement, actually), however these won't guarantee correct exchange functioning, as this only tests public endpoints, but no private endpoint (like generate order or similar).

@@ -401,6 +417,21 @@ jupyter nbconvert --ClearOutputPreprocessor.enabled=True --inplace freqtrade/tem
 jupyter nbconvert --ClearOutputPreprocessor.enabled=True --to markdown freqtrade/templates/strategy_analysis_example.ipynb --stdout > docs/strategy_analysis_example.md
 ```

+## Backtest documentation results
+
+To generate backtest outputs, please use the following commands:
+
+``` bash
+# Assume a dedicated user directory for this output
+freqtrade create-userdir --userdir user_data_bttest/
+# set can_short = True
+sed -i "s/can_short: bool = False/can_short: bool = True/" user_data_bttest/strategies/sample_strategy.py
+
+freqtrade download-data --timerange 20250625-20250801 --config tests/testdata/config.tests.usdt.json --userdir user_data_bttest/ -t 5m
+
+freqtrade backtesting --config tests/testdata/config.tests.usdt.json -s SampleStrategy --userdir user_data_bttest/ --cache none --timerange 20250701-20250801
+```
+
 ## Continuous integration

 This documents some decisions taken for the CI Pipeline.
@@ -411,7 +442,6 @@ This documents some decisions taken for the CI Pipeline.
 * Docker images contain a file, `/freqtrade/freqtrade_commit` containing the commit this image is based of.
 * Full docker image rebuilds are run once a week via schedule.
 * Deployments run on ubuntu.
-* ta-lib binaries are contained in the build_helpers directory to avoid fails related to external unavailability.
 * All tests must pass for a PR to be merged to `stable` or `develop`.

 ## Creating a release
@@ -433,10 +463,10 @@ git checkout -b new_release <commitid>
 Determine if crucial bugfixes have been made between this commit and the current state, and eventually cherry-pick these.

 * Merge the release branch (stable) into this branch.
-* Edit `freqtrade/__init__.py` and add the version matching the current date (for example `2019.7` for July 2019). Minor versions can be `2019.7.1` should we need to do a second release that month. Version numbers must follow allowed versions from PEP0440 to avoid failures pushing to pypi.
+* Edit `freqtrade/__init__.py` and add the version matching the current date (for example `2025.7` for July 2025). Minor versions can be `2025.7.1` should we need to do a second release that month. Version numbers must follow allowed versions from PEP0440 to avoid failures pushing to pypi.
 * Commit this part.
 * Push that branch to the remote and create a PR against the **stable branch**.
-* Update develop version to next version following the pattern `2019.8-dev`.
+* Update develop version to next version following the pattern `2025.8-dev`.

 ### Create changelog from git commits

@@ -1,300 +0,0 @@
-# Edge positioning
-
-The `Edge Positioning` module uses probability to calculate your win rate and risk reward ratio. It will use these statistics to control your strategy trade entry points, position size and, stoploss.
-
-!!! Danger "Deprecated functionality"
-    `Edge positioning` (or short Edge) is currently in maintenance mode only (we keep existing functionality alive) and should be considered as deprecated.
-    It will currently not receive new features until either someone stepped forward to take up ownership of that module - or we'll decide to remove edge from freqtrade.
-
-!!! Warning
-    When using `Edge positioning` with a dynamic whitelist (VolumePairList), make sure to also use `AgeFilter` and set it to at least `calculate_since_number_of_days` to avoid problems with missing data.
-
-!!! Note
-    `Edge Positioning` only considers *its own* buy/sell/stoploss signals. It ignores the stoploss, trailing stoploss, and ROI settings in the strategy configuration file.
-    `Edge Positioning` improves the performance of some trading strategies and *decreases* the performance of others.
-
-
-## Introduction
-
-Trading strategies are not perfect. They are frameworks that are susceptible to the market and its indicators. Because the market is not at all predictable, sometimes a strategy will win and sometimes the same strategy will lose.
-
-To obtain an edge in the market, a strategy has to make more money than it loses. Making money in trading is not only about *how often* the strategy makes or loses money.
-
-!!! tip "It doesn't matter how often, but how much!"
-    A bad strategy might make 1 penny in *ten* transactions but lose 1 dollar in *one* transaction. If one only checks the number of winning trades, it would be misleading to think that the strategy is actually making a profit.
-
-The Edge Positioning module seeks to improve a strategy's winning probability and the money that the strategy will make *on the long run*. 
-
-We raise the following question[^1]:
-
-!!! Question "Which trade is a better option?"
-    a) A trade with 80% of chance of losing 100\$ and 20% chance of winning 200\$<br/>
-    b) A trade with 100% of chance of losing 30\$
-
-???+ Info "Answer"
-    The expected value of *a)* is smaller than the expected value of *b)*.<br/>
-    Hence, *b*) represents a smaller loss in the long run.<br/>
-    However, the answer is: *it depends*
-
-Another way to look at it is to ask a similar question:
-
-!!! Question "Which trade is a better option?"
-    a) A trade with 80% of chance of winning 100\$ and 20% chance of losing 200\$<br/>
-    b) A trade with 100% of chance of winning 30\$
-
-Edge positioning tries to answer the hard questions about risk/reward and position size automatically, seeking to minimizes the chances of losing of a given strategy.
-
-### Trading, winning and losing
-
-Let's call $o$ the return of a single transaction $o$ where $o \in \mathbb{R}$. The collection $O = \{o_1, o_2, ..., o_N\}$ is the set of all returns of transactions made during a trading session. We say that $N$ is the cardinality of $O$, or, in lay terms, it is the number of transactions made in a trading session.
-
-!!! Example
-    In a session where a strategy made three transactions we can say that $O = \{3.5, -1, 15\}$. That means that $N = 3$ and $o_1 = 3.5$, $o_2 = -1$, $o_3 = 15$.
-
-A winning trade is a trade where a strategy *made* money. Making money means that the strategy closed the position in a value that returned a profit, after all deducted fees. Formally, a winning trade will have a return $o_i > 0$. Similarly, a losing trade will have a return $o_j \leq 0$. With that, we can discover the set of all winning trades, $T_{win}$, as follows:
-
-$$ T_{win} = \{ o \in O | o > 0 \} $$
-
-Similarly, we can discover the set of losing trades $T_{lose}$ as follows:
-
-$$ T_{lose} = \{o \in O | o \leq 0\} $$
-
-!!! Example
-    In a section where a strategy made four transactions $O = \{3.5, -1, 15, 0\}$:<br>
-    $T_{win} = \{3.5, 15\}$<br>
-    $T_{lose} = \{-1, 0\}$<br>
-
-### Win Rate and Lose Rate
-
-The win rate $W$ is the proportion of winning trades with respect to all the trades made by a strategy. We use the following function to compute the win rate:
-
-$$W = \frac{|T_{win}|}{N}$$
-
-Where $W$ is the win rate, $N$ is the number of trades and, $T_{win}$ is the set of all trades where the strategy made money.
-
-Similarly, we can compute the rate of losing trades:
-
-$$ 
-    L = \frac{|T_{lose}|}{N} 
-$$
-
-Where $L$ is the lose rate, $N$ is the amount of trades made and, $T_{lose}$ is the set of all trades where the strategy lost money. Note that the above formula is the same as calculating $L = 1 – W$ or $W = 1 – L$
-
-### Risk Reward Ratio
-
-Risk Reward Ratio ($R$) is a formula used to measure the expected gains of a given investment against the risk of loss. It is basically what you potentially win divided by what you potentially lose. Formally:
-
-$$ R = \frac{\text{potential_profit}}{\text{potential_loss}} $$
-
-???+ Example "Worked example of $R$ calculation"
-    Let's say that you think that the price of *stonecoin* today is 10.0\$. You believe that, because they will start mining stonecoin, it will go up to 15.0\$ tomorrow. There is the risk that the stone is too hard, and the GPUs can't mine it, so the price might go to 0\$ tomorrow. You are planning to invest 100\$, which will give you 10 shares (100 / 10).
-
-    Your potential profit is calculated as:
-
-    $\begin{aligned} 
-        \text{potential_profit} &= (\text{potential_price} - \text{entry_price}) * \frac{\text{investment}}{\text{entry_price}} \\
-                                &= (15 - 10) * (100 / 10) \\
-                                &= 50
-    \end{aligned}$
-
-    Since the price might go to 0\$, the 100\$ dollars invested could turn into 0.
-
-    We do however use a stoploss of 15% - so in the worst case, we'll sell 15% below entry price (or at 8.5$\).
-
-    $\begin{aligned}
-        \text{potential_loss} &= (\text{entry_price} - \text{stoploss}) * \frac{\text{investment}}{\text{entry_price}} \\
-                                &= (10 - 8.5) * (100 / 10)\\
-                                &= 15
-    \end{aligned}$
-
-    We can compute the Risk Reward Ratio as follows:
-
-    $\begin{aligned}
-        R   &= \frac{\text{potential_profit}}{\text{potential_loss}}\\
-            &= \frac{50}{15}\\
-            &= 3.33
-    \end{aligned}$<br>
-    What it effectively means is that the strategy have the potential to make 3.33\$ for each 1\$ invested.
-
-On a long horizon, that is, on many trades, we can calculate the risk reward by dividing the strategy' average profit on winning trades by the strategy' average loss on losing trades. We can calculate the average profit, $\mu_{win}$, as follows:
-
-$$ \text{average_profit} = \mu_{win} = \frac{\text{sum_of_profits}}{\text{count_winning_trades}} = \frac{\sum^{o \in T_{win}} o}{|T_{win}|} $$
-
-Similarly, we can calculate the average loss, $\mu_{lose}$, as follows:
-
-$$ \text{average_loss} = \mu_{lose} = \frac{\text{sum_of_losses}}{\text{count_losing_trades}} = \frac{\sum^{o \in T_{lose}} o}{|T_{lose}|} $$
-
-Finally, we can calculate the Risk Reward ratio, $R$, as follows:
-
-$$ R = \frac{\text{average_profit}}{\text{average_loss}} = \frac{\mu_{win}}{\mu_{lose}}\\ $$
-
-
-???+ Example "Worked example of $R$ calculation using mean profit/loss"
-    Let's say the strategy that we are using makes an average win $\mu_{win} = 2.06$ and an average loss $\mu_{loss} = 4.11$.<br>
-    We calculate the risk reward ratio as follows:<br>
-    $R = \frac{\mu_{win}}{\mu_{loss}} = \frac{2.06}{4.11} = 0.5012...$
-    
-
-### Expectancy
-
-By combining the Win Rate $W$ and the Risk Reward ratio $R$ to create an expectancy ratio $E$. A expectance ratio is the expected return of the investment made in a trade. We can compute the value of $E$ as follows:
-
-$$E = R * W - L$$
-
-!!! Example "Calculating $E$"
-    Let's say that a strategy has a win rate $W = 0.28$ and a risk reward ratio $R = 5$. What this means is that the strategy is expected to make 5 times the investment around on 28% of the trades it makes. Working out the example:<br>
-    $E = R * W - L = 5 * 0.28 - 0.72 = 0.68$
-    <br>
-
-The expectancy worked out in the example above means that, on average, this strategy' trades will return 1.68 times the size of its losses. Said another way, the strategy makes 1.68\$ for every 1\$ it loses, on average. 
-
-This is important for two reasons: First, it may seem obvious, but you know right away that you have a positive return. Second, you now have a number you can compare to other candidate systems to make decisions about which ones you employ.
-
-It is important to remember that any system with an expectancy greater than 0 is profitable using past data. The key is finding one that will be profitable in the future.
-
-You can also use this value to evaluate the effectiveness of modifications to this system.
-
-!!! Note
-    It's important to keep in mind that Edge is testing your expectancy using historical data, there's no guarantee that you will have a similar edge in the future. It's still vital to do this testing in order to build confidence in your methodology but be wary of "curve-fitting" your approach to the historical data as things are unlikely to play out the exact same way for future trades.
-
-## How does it work?
-
-Edge combines dynamic stoploss, dynamic positions, and whitelist generation into one isolated module which is then applied to the trading strategy. If enabled in config, Edge will go through historical data with a range of stoplosses in order to find buy and sell/stoploss signals. It then calculates win rate and expectancy over *N* trades for each stoploss. Here is an example:
-
-| Pair   |      Stoploss      |  Win Rate | Risk Reward Ratio | Expectancy |
-|----------|:-------------:|-------------:|------------------:|-----------:|
-| XZC/ETH  |  -0.01        |   0.50       |1.176384           | 0.088      |
-| XZC/ETH  |  -0.02        |   0.51       |1.115941           | 0.079      |
-| XZC/ETH  |  -0.03        |   0.52       |1.359670           | 0.228      |
-| XZC/ETH  |  -0.04        |   0.51       |1.234539           | 0.117      |
-
-The goal here is to find the best stoploss for the strategy in order to have the maximum expectancy. In the above example stoploss at $3%$ leads to the maximum expectancy according to historical data.
-
-Edge module then forces stoploss value it evaluated to your strategy dynamically.
-
-### Position size
-
-Edge dictates the amount at stake for each trade to the bot according to the following factors:
-
- Allowed capital at risk
- Stoploss
-
-Allowed capital at risk is calculated as follows:
-
-```
-Allowed capital at risk = (Capital available_percentage) X (Allowed risk per trade)
-```
-
-Stoploss is calculated as described above with respect to historical data.
-
-The position size is calculated as follows:
-
-```
-Position size = (Allowed capital at risk) / Stoploss
-```
-
-Example:
-
-Let's say the stake currency is **ETH** and there is $10$ **ETH** on the wallet. The capital available percentage is $50%$ and the allowed risk per trade is $1\%$. Thus, the available capital for trading is $10 * 0.5 = 5$ **ETH** and the allowed capital at risk would be $5 * 0.01 = 0.05$ **ETH**.
-
-   **Trade 1:** The strategy detects a new buy signal in the **XLM/ETH** market. `Edge Positioning` calculates a stoploss of $2\%$ and a position of $0.05 / 0.02 = 2.5$ **ETH**. The bot takes a position of $2.5$ **ETH** in the **XLM/ETH** market.
-
-   **Trade 2:** The strategy detects a buy signal on the **BTC/ETH** market while **Trade 1** is still open. `Edge Positioning` calculates the stoploss of $4\%$ on this market. Thus, **Trade 2** position size is $0.05 / 0.04 = 1.25$ **ETH**.
-
-!!! Tip "Available Capital $\neq$ Available in wallet"
-    The available capital for trading didn't change in **Trade 2** even with **Trade 1** still open. The available capital **is not** the free amount in the wallet.
-
-   **Trade 3:** The strategy detects a buy signal in the **ADA/ETH** market. `Edge Positioning` calculates a stoploss of $1\%$ and a position of $0.05 / 0.01 = 5$ **ETH**. Since **Trade 1** has $2.5$ **ETH** blocked and **Trade 2** has $1.25$ **ETH** blocked, there is only $5 - 1.25 - 2.5 = 1.25$ **ETH** available. Hence, the position size of **Trade 3** is $1.25$ **ETH**. 
-
-!!! Tip "Available Capital Updates"
-    The available capital does not change before a position is sold. After a trade is closed the Available Capital goes up if the trade was profitable or goes down if the trade was a loss.
-
-   The strategy detects a sell signal in the **XLM/ETH** market. The bot exits **Trade 1** for a profit of $1$ **ETH**. The total capital in the wallet becomes $11$ **ETH** and the available capital for trading becomes $5.5$ **ETH**.
-
-   **Trade 4** The strategy detects a new buy signal int the **XLM/ETH** market. `Edge Positioning` calculates the stoploss of $2\%$, and the position size of $0.055 / 0.02 = 2.75$ **ETH**.
-
-## Edge command reference
-
--8<-- "commands/edge.md"
-
-## Configurations
-
-Edge module has following configuration options:
-
-|  Parameter | Description |
-|------------|-------------|
-| `enabled` | If true, then Edge will run periodically. <br>*Defaults to `false`.* <br> **Datatype:** Boolean
-| `process_throttle_secs` | How often should Edge run in seconds. <br>*Defaults to `3600` (once per hour).* <br> **Datatype:** Integer
-| `calculate_since_number_of_days` | Number of days of data against which Edge calculates Win Rate, Risk Reward and Expectancy. <br> **Note** that it downloads historical data so increasing this number would lead to slowing down the bot. <br>*Defaults to `7`.* <br> **Datatype:** Integer
-| `allowed_risk` | Ratio of allowed risk per trade. <br>*Defaults to `0.01` (1%)).* <br> **Datatype:** Float
-| `stoploss_range_min` | Minimum stoploss. <br>*Defaults to `-0.01`.* <br> **Datatype:** Float
-| `stoploss_range_max` | Maximum stoploss. <br>*Defaults to `-0.10`.* <br> **Datatype:** Float
-| `stoploss_range_step` | As an example if this is set to -0.01 then Edge will test the strategy for `[-0.01, -0,02, -0,03 ..., -0.09, -0.10]` ranges. <br> **Note** than having a smaller step means having a bigger range which could lead to slow calculation. <br> If you set this parameter to -0.001, you then slow down the Edge calculation by a factor of 10. <br>*Defaults to `-0.001`.* <br> **Datatype:** Float
-| `minimum_winrate` | It filters out pairs which don't have at least minimum_winrate. <br>This comes handy if you want to be conservative and don't comprise win rate in favour of risk reward ratio. <br>*Defaults to `0.60`.* <br> **Datatype:** Float
-| `minimum_expectancy` | It filters out pairs which have the expectancy lower than this number. <br>Having an expectancy of 0.20 means if you put 10\$ on a trade you expect a 12\$ return. <br>*Defaults to `0.20`.* <br> **Datatype:** Float
-| `min_trade_number` | When calculating *W*, *R* and *E* (expectancy) against historical data, you always want to have a minimum number of trades. The more this number is the more Edge is reliable. <br>Having a win rate of 100% on a single trade doesn't mean anything at all. But having a win rate of 70% over past 100 trades means clearly something. <br>*Defaults to `10` (it is highly recommended not to decrease this number).* <br> **Datatype:** Integer
-| `max_trade_duration_minute` | Edge will filter out trades with long duration. If a trade is profitable after 1 month, it is hard to evaluate the strategy based on it. But if most of trades are profitable and they have maximum duration of 30 minutes, then it is clearly a good sign.<br>**NOTICE:** While configuring this value, you should take into consideration your timeframe. As an example filtering out trades having duration less than one day for a strategy which has 4h interval does not make sense. Default value is set assuming your strategy interval is relatively small (1m or 5m, etc.).<br>*Defaults to `1440` (one day).* <br> **Datatype:** Integer
-| `remove_pumps` | Edge will remove sudden pumps in a given market while going through historical data. However, given that pumps happen very often in crypto markets, we recommend you keep this off.<br>*Defaults to `false`.* <br> **Datatype:** Boolean
-
-## Running Edge independently
-
-You can run Edge independently in order to see in details the result. Here is an example:
-
-``` bash
-freqtrade edge
-```
-
-An example of its output:
-
-| **pair**     |   **stoploss** |   **win rate** |   **risk reward ratio** |   **required risk reward** |   **expectancy** |   **total number of trades** |   **average duration (min)** |
-|:----------|-----------:|-----------:|--------------------:|-----------------------:|-------------:|-----------------:|---------------:|
-| **AGI/BTC**   |      -0.02 |       0.64 |                5.86 |                   0.56 |         3.41 |                       14 |                       54 |
-| **NXS/BTC**   |      -0.03 |       0.64 |                2.99 |                   0.57 |         1.54 |                       11 |                       26 |
-| **LEND/BTC**  |      -0.02 |       0.82 |                2.05 |                   0.22 |         1.50 |                       11 |                       36 |
-| **VIA/BTC**   |      -0.01 |       0.55 |                3.01 |                   0.83 |         1.19 |                       11 |                       48 |
-| **MTH/BTC**   |      -0.09 |       0.56 |                2.82 |                   0.80 |         1.12 |                       18 |                       52 |
-| **ARDR/BTC**  |      -0.04 |       0.42 |                3.14 |                   1.40 |         0.73 |                       12 |                       42 |
-| **BCPT/BTC**  |      -0.01 |       0.71 |                1.34 |                   0.40 |         0.67 |                       14 |                       30 |
-| **WINGS/BTC** |      -0.02 |       0.56 |                1.97 |                   0.80 |         0.65 |                       27 |                       42 |
-| **VIBE/BTC**  |      -0.02 |       0.83 |                0.91 |                   0.20 |         0.59 |                       12 |                       35 |
-| **MCO/BTC**   |      -0.02 |       0.79 |                0.97 |                   0.27 |         0.55 |                       14 |                       31 |
-| **GNT/BTC**   |      -0.02 |       0.50 |                2.06 |                   1.00 |         0.53 |                       18 |                       24 |
-| **HOT/BTC**   |      -0.01 |       0.17 |                7.72 |                   4.81 |         0.50 |                      209 |                        7 |
-| **SNM/BTC**   |      -0.03 |       0.71 |                1.06 |                   0.42 |         0.45 |                       17 |                       38 |
-| **APPC/BTC**  |      -0.02 |       0.44 |                2.28 |                   1.27 |         0.44 |                       25 |                       43 |
-| **NEBL/BTC**  |      -0.03 |       0.63 |                1.29 |                   0.58 |         0.44 |                       19 |                       59 |
-
-Edge produced the above table by comparing `calculate_since_number_of_days` to `minimum_expectancy` to find `min_trade_number` historical information based on the config file. The timerange Edge uses for its comparisons can be further limited by using the `--timerange` switch.
-
-In live and dry-run modes, after the `process_throttle_secs` has passed, Edge will again process `calculate_since_number_of_days` against `minimum_expectancy` to find `min_trade_number`. If no `min_trade_number` is found, the bot will return "whitelist empty". Depending on the trade strategy being deployed, "whitelist empty" may be return much of the time - or *all* of the time. The use of Edge may also cause trading to occur in bursts, though this is rare.
-
-If you encounter "whitelist empty" a lot, condsider tuning `calculate_since_number_of_days`, `minimum_expectancy`  and `min_trade_number` to align to the trading frequency of your strategy.
-
-### Update cached pairs with the latest data
-
-Edge requires historic data the same way as backtesting does.
-Please refer to the [Data Downloading](data-download.md) section of the documentation for details.
-
-### Precising stoploss range
-
-```bash
-freqtrade edge --stoplosses=-0.01,-0.1,-0.001 #min,max,step
-```
-
-### Advanced use of timerange
-
-```bash
-freqtrade edge --timerange=20181110-20181113
-```
-
-Doing `--timerange=-20190901` will get all available data until September 1st (excluding September 1st 2019).
-
-The full timerange specification:
-
-* Use tickframes till 2018/01/31: `--timerange=-20180131`
-* Use tickframes since 2018/01/31: `--timerange=20180131-`
-* Use tickframes since 2018/01/31 till 2018/03/01 : `--timerange=20180131-20180301`
-* Use tickframes between POSIX timestamps 1527595200 1527618600: `--timerange=1527595200-1527618600`
-
-
-[^1]: Question extracted from MIT Opencourseware S096 - Mathematics with applications in Finance: https://ocw.mit.edu/courses/mathematics/18-s096-topics-in-mathematics-with-applications-in-finance-fall-2013/
@@ -2,6 +2,10 @@

 This page combines common gotchas and Information which are exchange-specific and most likely don't apply to other exchanges.

+## Quick overview of supported exchange features
+
+--8<-- "includes/exchange-features.md"
+
 ## Exchange configuration

 Freqtrade is based on [CCXT library](https://github.com/ccxt/ccxt) that supports over 100 cryptocurrency
@@ -213,6 +217,32 @@ freqtrade download-data --exchange kraken --dl-trades -p BTC/EUR BCH/EUR
    Please pay attention that rateLimit configuration entry holds delay in milliseconds between requests, NOT requests/sec rate.
    So, in order to mitigate Kraken API "Rate limit exceeded" exception, this configuration should be increased, NOT decreased.

+## Kraken Futures
+
+Kraken Futures uses the exchange id `krakenfutures` and supports isolated futures mode.
+
+```jsonc
+"exchange": {
+    "name": "krakenfutures",
+    "key": "your_exchange_key",
+    "secret": "your_exchange_secret"
+},
+"trading_mode": "futures",
+"margin_mode": "isolated",
+"stake_currency": "USD"
+```
+
+!!! Tip "Stoploss on Exchange"
+    Kraken Futures supports `stoploss_on_exchange` with both `limit` and `market` stop orders.
+    Use `order_types.stoploss_price_type` to select the trigger price source (`mark`, `last`, or `index`).
+
+!!! Note "Collateral"
+    Kraken Futures is USD-settled. Use USD as your stake currency.
+
+!!! Note "Flex (Multi-collateral) Accounts"
+    Kraken Futures flex accounts allow collateral in multiple currencies, while trading remains USD-settled.
+    Freqtrade derives the `USD` balance from Kraken margin fields, so keep `stake_currency` set to `USD`.
+
 ## Kucoin

 Kucoin requires a passphrase for each api key, you will therefore need to add this key into the configuration so your exchange section looks as follows:
@@ -227,7 +257,7 @@ Kucoin requires a passphrase for each api key, you will therefore need to add th
 }
 ```

-Kucoin supports [time_in_force](configuration.md#understand-order_time_in_force).
+Kucoin supports [time_in_force](configuration.md#understand-order_time_in_force) with settings "GTC" (good till cancelled), "FOK" (full-or-cancel) and "IOC" (immediate-or-cancel) settings.

 !!! Tip "Stoploss on Exchange"
    Kucoin supports `stoploss_on_exchange` and can use both stop-loss-market and stop-loss-limit orders. It provides great advantages, so we recommend to benefit from it.
@@ -235,7 +265,7 @@ Kucoin supports [time_in_force](configuration.md#understand-order_time_in_force)

 ### Kucoin Blacklists

-For Kucoin, it is suggested to add `"KCS/<STAKE>"` to your blacklist to avoid issues, unless you are willing to maintain enough extra `KCS` on the account or unless you're willing to disable using `KCS` for fees. 
+For Kucoin, it is suggested to add `"KCS/<STAKE>"` to your blacklist to avoid issues, unless you are willing to maintain enough extra `KCS` on the account or unless you're willing to disable using `KCS` for fees.
 Kucoin accounts may use `KCS` for fees, and if a trade happens to be on `KCS`, further trades may consume this position and make the initial `KCS` trade unsellable as the expected amount is not there anymore.

 ## HTX
@@ -271,7 +301,9 @@ Using the wrong exchange will result in the error "OKX Error 50119: API key does
 ## Gate.io

 !!! Tip "Stoploss on Exchange"
-    Gate.io supports `stoploss_on_exchange` and uses `stop-loss-limit` orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange..
+    Gate.io supports `stoploss_on_exchange` and uses `stop-loss-limit` orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.
+
+Gate.io supports [time_in_force](configuration.md#understand-order_time_in_force) with settings "GTC" (good till cancelled), and "IOC" (immediate-or-cancel) settings.

 Gate.io allows the use of `POINT` to pay for fees. As this is not a tradable currency (no regular market available), automatic fee calculations will fail (and default to a fee of 0).
 The configuration parameter `exchange.unknown_fee_rate` can be used to specify the exchange rate between Point and the stake currency. Obviously, changing the stake-currency will also require changes to this value.
@@ -286,9 +318,22 @@ Without these permissions, the bot will not start correctly and show errors like

 ## Bybit

-Futures trading on bybit is currently supported for USDT markets, and will use isolated futures mode.
+!!! Tip "Stoploss on Exchange"
+    Bybit (futures only) supports `stoploss_on_exchange` and uses `stop-loss-limit` orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.
+    On futures, Bybit supports both `stop-limit` as well as `stop-market` orders. You can use either `"limit"` or `"market"` in the `order_types.stoploss` configuration setting to decide which type to use.

-On startup, freqtrade will set the position mode to "One-way Mode" for the whole (sub)account. This avoids making this call over and over again (slowing down bot operations), but means that changes to this setting may result in exceptions and errors.
+Bybit supports [time_in_force](configuration.md#understand-order_time_in_force) with settings "GTC" (good till cancelled), "FOK" (full-or-cancel), "IOC" (immediate-or-cancel) and "PO" (Post only) settings.
+
+!!! Warning "Unified accounts"
+    Freqtrade assumes accounts to be dedicated to the bot.
+    We therefore recommend the usage of one subaccount per bot. This is especially important when using unified accounts.  
+    Other configurations (multiple bots on one account, manual non-bot trades on the bot account) are not supported and may lead to unexpected behavior.
+
+### Bybit Futures
+
+Futures trading on bybit is supported for isolated futures mode.
+
+On startup, freqtrade will set the position mode to "One-way Mode" for the whole (sub)account. This avoids making this call over and over again (slowing down bot operations), but means that manual changes to this setting may result in exceptions and errors.

 As bybit doesn't provide funding rate history, the dry-run calculation is used for live trades as well.

@@ -300,15 +345,14 @@ API Keys for live futures trading must have the following permissions:

 We do strongly recommend to limit all API keys to the IP you're going to use it from.

-!!! Warning "Unified accounts"
-    Freqtrade assumes accounts to be dedicated to the bot.
-    We therefore recommend the usage of one subaccount per bot. This is especially important when using unified accounts.  
-    Other configurations (multiple bots on one account, manual non-bot trades on the bot account) are not supported and may lead to unexpected behavior.
+### Bybit Demo Mode

+Bybit has a [demo mode](https://learn.bybit.com/en/bybit-guide/how-to-use-bybit-demo-trading) - which can be activated by setting `exchange.demo_trading` to `true` in the configuration.
+Bybit uses live markets to simulate your trades (without market impact) - making it work very similar to freqtrade's dry-run mode.  

-!!! Tip "Stoploss on Exchange"
-    Bybit (futures only) supports `stoploss_on_exchange` and uses `stop-loss-limit` orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.
-    On futures, Bybit supports both `stop-limit` as well as `stop-market` orders. You can use either `"limit"` or `"market"` in the `order_types.stoploss` configuration setting to decide which type to use.
+You'll need to use separate API keys for demo trading, which you can create on bybit's demo page.
+
+Demo mode is incompatible with dry-run.

 ## Bitmart

@@ -328,24 +372,55 @@ It's therefore required to pass the UID as well.
 !!! Warning "Necessary Verification"
    Bitmart requires Verification Lvl2 to successfully trade on the spot market through the API - even though trading via UI works just fine with just Lvl1 verification.

+## Bitget
+
+Bitget requires a passphrase for each api key, you will therefore need to add this key into the configuration so your exchange section looks as follows:
+
+```json
+"exchange": {
+    "name": "bitget",
+    "key": "your_exchange_key",
+    "secret": "your_exchange_secret",
+    "password": "your_exchange_api_key_password",
+    // ...
+}
+```
+
+Bitget supports [time_in_force](configuration.md#understand-order_time_in_force) with settings "GTC" (good till cancelled), "FOK" (full-or-cancel), "IOC" (immediate-or-cancel) and "PO" (Post only) settings.
+
+!!! Tip "Stoploss on Exchange"
+    Bitget supports `stoploss_on_exchange` and can use both stop-loss-market and stop-loss-limit orders. It provides great advantages, so we recommend to benefit from it.
+    You can use either `"limit"` or `"market"` in the `order_types.stoploss` configuration setting to decide which type of stoploss shall be used.
+
+### Bitget Futures
+
+Futures trading on bitget is supported for isolated futures mode.
+
+On startup, freqtrade will set the position mode to "One-way Mode" for the whole (sub)account. This avoids making this call over and over again (slowing down bot operations), but means that manual changes to this setting may result in exceptions and errors.
+
 ## Hyperliquid

 !!! Tip "Stoploss on Exchange"
    Hyperliquid supports `stoploss_on_exchange` and uses `stop-loss-limit` orders. It provides great advantages, so we recommend to benefit from it.

+!!! Warning "Unified accounts"
+    Hyperliquid unified accounts are supported - though this relies freqtrade's assumption of "owning" the account, and being the only one trading on it (in this case, extended to both spot and futures).
+    We hence recommend the usage of subaccounts where possible, and to avoid manual trading on the same account while the bot is running.
+    Freqtrade will attempt to detect the account type on startup - changing the account type mid-trading is not supported and may lead to exceptions and errors.
+
 Hyperliquid is a Decentralized Exchange (DEX). Decentralized exchanges work a bit different compared to normal exchanges. Instead of authenticating private API calls using an API key, private API calls need to be signed with the private key of your wallet (We recommend using an api Wallet for this, generated either on Hyperliquid or in your wallet of choice).
 This needs to be configured like this:

 ```json
 "exchange": {
    "name": "hyperliquid",
-    "walletAddress": "your_eth_wallet_address",
+    "walletAddress": "your_eth_wallet_address",  // This should NOT be your API Wallet Address!
    "privateKey": "your_api_private_key",
    // ...
 }
 ```

-* walletAddress in hex format: `0x<40 hex characters>` - Can be easily copied from your wallet - and should be your wallet address, not your API Wallet Address.
+* walletAddress in hex format: `0x<40 hex characters>` - Can be easily copied from your wallet - and should be your main wallet address, not your API Wallet Address.
 * privateKey in hex format: `0x<64 hex characters>` - Use the key the API Wallet shows on creation.

 Hyperliquid handles deposits and withdrawals on the Arbitrum One chain, a Layer 2 scaling solution built on top of Ethereum. Hyperliquid uses USDC as quote / collateral. The process of depositing USDC on Hyperliquid requires a couple of steps, see [how to start trading](https://hyperliquid.gitbook.io/hyperliquid-docs/onboarding/how-to-start-trading) for details on what steps are needed.
@@ -363,10 +438,87 @@ Hyperliquid handles deposits and withdrawals on the Arbitrum One chain, a Layer
    * Create a different software wallet, only transfer the funds you want to trade with to that wallet, and use that wallet to trade on Hyperliquid.
    * If you have funds you don't want to use for trading (after making a profit for example), transfer them back to your hardware wallet.

+
+!!! Warning "Vaults and Subaccounts"
+    You can only use either a vault or a subaccount - not both at the same time.
+
+### Hyperliquid Subaccount
+
+Hyperliquid allows you to create subaccounts with sufficient previous trading volume.  
+To use subaccounts with Freqtrade, you will need to use the following configuration pattern:
+
+``` json
+"exchange": {
+    "name": "hyperliquid",
+    "walletAddress": "your_master_wallet_address", // Your master wallet address (not the API wallet or vault address - but not subaccount address).
+    "privateKey": "your_api_private_key", // API wallet private key (see https://app.hyperliquid.xyz/API). You'll only need the private key.
+    "ccxt_config": {
+        "options": {
+            "subAccountAddress": "your_subaccount_address" // Required if you want to use a subaccount.
+        }
+    },
+    // ...
+}
+```
+
+Your balance and trades will now be used from your subaccount - and no longer from your main account.
+
+### Hyperliquid Vault
+
+Hyperliquid allows you to create vaults. To use vaults with Freqtrade, you will need to use the following configuration pattern:
+
+``` json
+"exchange": {
+    "name": "hyperliquid",
+    "walletAddress": "your_vault_address", // Your vault wallet address (Must also be added below in the ccxt_config.options.vaultAddress field)
+    "privateKey": "your_api_private_key", // API wallet private key (see https://app.hyperliquid.xyz/API). You'll only need the private key.
+    "ccxt_config": {
+        "options": {
+            "vaultAddress": "your_vault_address", // Optional, only if you want to use a vault ... (vault address must also be added to walletAdress)
+        }
+    },
+    // ...
+}
+```
+
+Your balance and trades will now be used from your vault - and no longer from your main account.
+
 ### Historic Hyperliquid data

 The Hyperliquid API does not provide historic data beyond the single call to fetch current data, so downloading data is not possible, as the downloaded data would not constitute proper historic data.

+### HIP-3 DEXes
+
+Hyperliquid supports HIP-3 decentralized exchanges (DEXes), which are independent exchanges built on top of the Hyperliquid infrastructure.
+These DEXes operate similarly to the main Hyperliquid exchange but are community-created and managed.
+
+To trade on HIP-3 DEXes with Freqtrade, you need to add them to your configuration using the `hip3_dexes` parameter:
+
+```json
+"exchange": {
+    "name": "hyperliquid",
+    "walletAddress": "your_master_wallet_address",
+    "privateKey": "your_api_private_key",
+    "hip3_dexes": ["dex_name_1", "dex_name_2"]
+}
+```
+
+Replace `"dex_name_1"` and `"dex_name_2"` with the actual names of the HIP-3 DEXes you want to trade on (e.g. `vntl` and `xyz`).
+
+!!! Warning "Performance and Rate Limit Impact"
+    Each HIP-3 DEX you add significantly impacts bot performance and rate limits.
+
+    * **Additional API Calls**: For each HIP-3 DEX configured, Freqtrade needs to make additional API calls.
+    * **Rate Limit Pressure**: Additional API calls contribute to Hyperliquid's strict rate limits. With multiple DEXes, you may hit rate limits faster, or rather, slow down bot operations due to enforced delays.
+
+    Please only add HIP-3 DEXes that you actively trade on. Monitor your logs for rate limit warnings or signs of slowed operations, and adjust your configuration accordingly.  
+    Different HIP-3 DEXes may also use different quote currencies - so make sure to only add DEXes that are compatible with your stake currency to avoid unnecessary delays.
+
+!!! Note
+    HIP-3 DEXes share the same wallet and free amount of collateral as your main Hyperliquid account. Trades on different DEXes will affect your overall account balance and margin.
+
+    The pair name for HIP-3 pairs will be slightly different than non HIP-3 pairs. Please use `list-pairs` subcommand to get the correct pair naming for all pairs for the specified dexes.
+
 ## Bitvavo

 If your account is required to use an operatorId, you can set it in the configuration file as follows:
@@ -430,3 +582,5 @@ For example, to test the order type `FOK` with Kraken, and modify candle limit t

 !!! Warning
    Please make sure to fully understand the impacts of these settings before modifying them.
+    Using `_ft_has_params` overrides may lead to unexpected behavior, and may even break your bot.
+    We will not be able to provide support for issues caused by custom settings in `_ft_has_params`.
@@ -2,7 +2,7 @@

 ## Supported Markets

-Freqtrade supports spot trading, as well as (isolated) futures trading for some selected exchanges. Please refer to the [documentation start page](index.md#supported-futures-exchanges-experimental) for an up-to-date list of supported exchanges.
+Freqtrade supports spot trading, as well as futures trading for some selected exchanges. Please refer to the [documentation start page](index.md#supported-futures-exchanges) for an up-to-date list of supported exchanges.

 ### Can my bot open short positions?

@@ -14,7 +14,7 @@ In spot markets, you can in some cases use leveraged spot tokens, which reflect

 ### Can my bot trade options or futures?

-Futures trading is supported for selected exchanges. Please refer to the [documentation start page](index.md#supported-futures-exchanges-experimental) for an up-to-date list of supported exchanges.
+Futures trading is supported for selected exchanges. Please refer to the [documentation start page](index.md#supported-futures-exchanges) for an up-to-date list of supported exchanges.

 ## Beginner Tips & Tricks

@@ -29,6 +29,13 @@ You can however use the [`adjust_trade_position()` callback](strategy-callbacks.

 Backtesting provides an option for this in `--eps` - however this is only there to highlight "hidden" signals, and will not work in live.

+### Does freqtrade support sandbox accounts?
+
+No, but you can use dry-run mode to simulate trading without risking real funds.
+
+Sandbox markets are separate, simulated markets - which are not suitable to test your strategy in a realistic environment.
+These markets usually have different order books, liquidity and trading behaviour (usually with very few participants) - which makes them unsuitable for realistic tests of your strategy.
+
 ### The bot does not start

 Running the bot with `freqtrade trade --config config.json` shows the output `freqtrade: command not found`.
@@ -159,6 +166,14 @@ This warning can point to one of the below problems:
 * Barely traded pair -> Check the pair on the exchange webpage, look at the timeframe your strategy uses. If the pair does not have any volume in some candles (usually visualized with a "volume 0" bar, and a "_" as candle), this pair did not have any trades in this timeframe. These pairs should ideally be avoided, as they can cause problems with order-filling.
 * API problem -> API returns wrong data (this only here for completeness, and should not happen with supported exchanges).

+### I get the message "Couldn't reuse watch for xxx" in the log
+
+This is an informational message that the bot tried to use candles from the websocket, but the exchange didn't provide the right information.
+This can happen if there was an interruption to the websocket connection - or if the pair didn't have any trades happen in the timeframe you are using.
+
+Freqtrade will handle this gracefully by falling back to the REST api.
+While this makes the iteration slightly slower (due to the REST Api call) - it will not cause any problems to the bot's operation.
+
 ### I'm getting the "Exchange XXX does not support market orders." message and cannot run my strategy

 As the message says, your exchange does not support market orders and you have one of the [order types](configuration.md/#understand-order_types) set to "market". Your strategy was probably written with other exchanges in mind and sets "market" orders for "stoploss" orders, which is correct and preferable for most of the exchanges supporting market orders (but not for Gate.io).
@@ -276,20 +291,6 @@ Example: 4% profit 650 times vs 0,3% profit a trade 10000 times in a year. If we
 Example:
 `freqtrade --config config.json --strategy SampleStrategy --hyperopt SampleHyperopt -e 1000 --timerange 20190601-20200601`

-## Edge module
-
-### Edge implements interesting approach for controlling position size, is there any theory behind it?
-
-The Edge module is mostly a result of brainstorming of [@mishaker](https://github.com/mishaker) and [@creslinux](https://github.com/creslinux) freqtrade team members.
-
-You can find further info on expectancy, win rate, risk management and position size in the following sources:
-
- https://www.tradeciety.com/ultimate-math-guide-for-traders/
- https://samuraitradingacademy.com/trading-expectancy/
- https://www.learningmarkets.com/determining-expectancy-in-your-trading/
- https://www.lonestocktrader.com/make-money-trading-positive-expectancy/
- https://www.babypips.com/trading/trade-expectancy-matter
-
 ## Official channels

 Freqtrade is using exclusively the following official channels:
@@ -303,6 +304,13 @@ Should you be asked to expose your exchange keys or send funds to some random wa

 Failing to follow these guidelines will not be responsibility of freqtrade.

+## Support policy
+
+We provide free support for Freqtrade on our [Discord server](https://discord.gg/p7nuUNVfP7) and via GitHub issues.
+We only support the most recent release (e.g. 2025.8) and the current development branch (e.g. 2025.9-dev).
+
+If you're on an older version, please follow the [upgrade instructions](updating.md) and see if your problem has already been addressed.
+
 ## "Freqtrade token"

 Freqtrade does not have a Crypto token offering.
@@ -4,7 +4,7 @@ Freqtrade provides a builtin webserver, which can serve [FreqUI](https://github.

 By default, the UI is automatically installed as part of the installation (script, docker).
 freqUI can also be manually installed by using the `freqtrade install-ui` command.
-This same command can also be used to update freqUI to new new releases.
+This same command can also be used to update freqUI to new releases.

 Once the bot is started in trade / dry-run mode (with `freqtrade trade`) - the UI will be available under the configured API port (by default `http://127.0.0.1:8080`).

@@ -46,6 +46,23 @@ On this page, you can also interact with the bot by starting and stopping it and
 ![FreqUI - trade view](assets/freqUI-trade-pane-dark.png#only-dark)
 ![FreqUI - trade view](assets/freqUI-trade-pane-light.png#only-light)

+### Dashboard
+
+The dashboard view provides an overview of the bot's performance and status.
+If multiple bots are connected, the dashboard will show an overview of all connected bots, allowing you to easily switch between them or show just a subset of available bots.
+
+#### Wallet Balance
+
+New in freqtrade 2026.4: This shows the balance of the bot over time.
+
+Compared to the "cumulative Profit" chart, this chart will show the actual balance of the bot over time, including unrealized profit and losses, as well as deposits and withdrawals.
+
+Historic data has re-populated based on available exchange data - however is assumed to be best-effort and may not be 100% accurate.
+More specifically, it won't cover deposits and withdrawals, and will assume a starting balance of current balance - profit/losses.
+
+For clarity - a "Capture start" marker line is shown on the chart, which indicates the point at which the migration to the new wallet balance tracking system happened.
+Only beyond this point, the wallet balance is expected to be accurate.
+
 ### Plot Configurator

 FreqUI Plots can be configured either via a `plot_config` configuration object in the strategy (which can be loaded via "from strategy" button) or via the UI.
@@ -70,7 +87,16 @@ Things you can change (among others):
 ![FreqUI - Settings view](assets/frequi-settings-dark.png#only-dark)
 ![FreqUI - Settings view](assets/frequi-settings-light.png#only-light)

-## Backtesting
+## Webserver mode
+
+when freqtrade is started in [webserver mode](utils.md#webserver-mode) (freqtrade started with `freqtrade webserver`), the webserver will start in a special mode allowing for additional features, for example:
+
+* Downloading data
+* Testing pairlists
+* [Backtesting strategies](#backtesting)
+* ... to be expanded
+
+### Backtesting

 When freqtrade is started in [webserver mode](utils.md#webserver-mode) (freqtrade started with `freqtrade webserver`), the backtesting view becomes available.
 This view allows you to backtest strategies and visualize the results.
@@ -166,7 +166,7 @@ Below are the values you can expect to include/use inside a typical strategy dat
 | `df['do_predict']` | Indication of an outlier data point. The return value is integer between -2 and 2, which lets you know if the prediction is trustworthy or not. `do_predict==1` means that the prediction is trustworthy. If the Dissimilarity Index (DI, see details [here](freqai-feature-engineering.md#identifying-outliers-with-the-dissimilarity-index-di)) of the input data point is above the threshold defined in the config, FreqAI will subtract 1 from `do_predict`, resulting in `do_predict==0`. If `use_SVM_to_remove_outliers` is active, the Support Vector Machine (SVM, see details [here](freqai-feature-engineering.md#identifying-outliers-using-a-support-vector-machine-svm)) may also detect outliers in training and prediction data. In this case, the SVM will also subtract 1 from `do_predict`. If the input data point was considered an outlier by the SVM but not by the DI, or vice versa, the result will be `do_predict==0`. If both the DI and the SVM considers the input data point to be an outlier, the result will be `do_predict==-1`. As with the SVM, if `use_DBSCAN_to_remove_outliers` is active, DBSCAN (see details [here](freqai-feature-engineering.md#identifying-outliers-with-dbscan)) may also detect outliers and subtract 1 from `do_predict`. Hence, if both the SVM and DBSCAN are active and identify a datapoint that was above the DI threshold as an outlier, the result will be `do_predict==-2`. A particular case is when `do_predict == 2`, which means that the model has expired due to exceeding `expired_hours`. <br> **Datatype:** Integer between -2 and 2.
 | `df['DI_values']` | Dissimilarity Index (DI) values are proxies for the level of confidence FreqAI has in the prediction. A lower DI means the prediction is close to the training data, i.e., higher prediction confidence. See details about the DI [here](freqai-feature-engineering.md#identifying-outliers-with-the-dissimilarity-index-di). <br> **Datatype:** Float.
 | `df['%*']` | Any dataframe column prepended with `%` in `feature_engineering_*()` is treated as a training feature. For example, you can include the RSI in the training feature set (similar to in `templates/FreqaiExampleStrategy.py`) by setting `df['%-rsi']`. See more details on how this is done [here](freqai-feature-engineering.md). <br> **Note:** Since the number of features prepended with `%` can multiply very quickly (10s of thousands of features are easily engineered using the multiplictative functionality of, e.g., `include_shifted_candles` and `include_timeframes` as described in the [parameter table](freqai-parameter-table.md)), these features are removed from the dataframe that is returned from FreqAI to the strategy. To keep a particular type of feature for plotting purposes, you would prepend it with `%%` (see details below). <br> **Datatype:** Depends on the feature created by the user.
-| `df['%%*']` | Any dataframe column prepended with `%%` in `feature_engineering_*()` is treated as a training feature, just the same as the above `%` prepend. However, in this case, the features are returned back to the strategy for FreqUI/plot-dataframe plotting and monitoring in Dry/Live/Backtesting <br> **Datatype:** Depends on the feature created by the user. Please note that features created in `feature_engineering_expand()` will have automatic FreqAI naming schemas depending on the expansions that you configured (i.e. `include_timeframes`, `include_corr_pairlist`, `indicators_periods_candles`, `include_shifted_candles`). So if you want to plot `%%-rsi` from `feature_engineering_expand_all()`, the final naming scheme for your plotting config would be: `%%-rsi-period_10_ETH/USDT:USDT_1h` for the `rsi` feature with `period=10`, `timeframe=1h`, and `pair=ETH/USDT:USDT` (the `:USDT` is added if you are using futures pairs). It is useful to simply add `print(dataframe.columns)` in your `populate_indicators()` after `self.freqai.start()` to see the full list of available features that are returned to the strategy for plotting purposes.
+| `df['%%*']` | Any dataframe column prepended with `%%` in `feature_engineering_*()` is treated as a training feature, just the same as the above `%` prepend. However, in this case, the features are returned back to the strategy for FreqUI/plot-dataframe plotting and monitoring in Dry/Live/Backtesting <br> **Datatype:** Depends on the feature created by the user. <br>*Please note* that features created in `feature_engineering_expand()` will have automatic FreqAI naming schemas depending on the expansions that you configured (i.e. `include_timeframes`, `include_corr_pairlist`, `indicators_periods_candles`, `include_shifted_candles`). So if you want to plot `%%-rsi` from `feature_engineering_expand_all()`, the final naming scheme for your plotting config would be: `%%-rsi-period_10_ETH/USDT:USDT_1h` for the `rsi` feature with `period=10`, `timeframe=1h`, and `pair=ETH/USDT:USDT` (the `:USDT` is added if you are using futures pairs). It is useful to simply add `print(dataframe.columns)` in your `populate_indicators()` after `self.freqai.start()` to see the full list of available features that are returned to the strategy for plotting purposes.

 ## Setting the `startup_candle_count`

@@ -200,15 +200,15 @@ If this value is set, FreqAI will initially use the predictions from the trainin

 ## Using different prediction models

-FreqAI has multiple example prediction model libraries that are ready to be used as is via the flag `--freqaimodel`. These libraries include `CatBoost`, `LightGBM`, and `XGBoost` regression, classification, and multi-target models, and can be found in `freqai/prediction_models/`.
+FreqAI has multiple example prediction model libraries that are ready to be used as is via the flag `--freqaimodel`. These libraries include `LightGBM`, and `XGBoost` regression, classification, and multi-target models, and can be found in `freqai/prediction_models/`.

 Regression and classification models differ in what targets they predict - a regression model will predict a target of continuous values, for example what price BTC will be at tomorrow, whilst a classifier will predict a target of discrete values, for example if the price of BTC will go up tomorrow or not. This means that you have to specify your targets differently depending on which model type you are using (see details [below](#setting-model-targets)).

 All of the aforementioned model libraries implement gradient boosted decision tree algorithms. They all work on the principle of ensemble learning, where predictions from multiple simple learners are combined to get a final prediction that is more stable and generalized. The simple learners in this case are decision trees. Gradient boosting refers to the method of learning, where each simple learner is built in sequence - the subsequent learner is used to improve on the error from the previous learner. If you want to learn more about the different model libraries you can find the information in their respective docs:

-* CatBoost: https://catboost.ai/en/docs/
-* LightGBM: https://lightgbm.readthedocs.io/en/v3.3.2/#
-* XGBoost: https://xgboost.readthedocs.io/en/stable/#
+* LightGBM: <https://lightgbm.readthedocs.io/en/v3.3.2/#>
+* XGBoost: <https://xgboost.readthedocs.io/en/stable/#>
+* CatBoost: <https://catboost.ai/en/docs/> (No longer actively supported since 2025.12)

 There are also numerous online articles describing and comparing the algorithms. Some relatively lightweight examples would be [CatBoost vs. LightGBM vs. XGBoost — Which is the best algorithm?](https://towardsdatascience.com/catboost-vs-lightgbm-vs-xgboost-c80f40662924#:~:text=In%20CatBoost%2C%20symmetric%20trees%2C%20or,the%20same%20depth%20can%20differ.) and [XGBoost, LightGBM or CatBoost — which boosting algorithm should I use?](https://medium.com/riskified-technology/xgboost-lightgbm-or-catboost-which-boosting-algorithm-should-i-use-e7fda7bb36bc). Keep in mind that the performance of each model is highly dependent on the application and so any reported metrics might not be true for your particular use of the model.

@@ -219,7 +219,7 @@ Make sure to use unique names to avoid overriding built-in models.

 #### Regressors

-If you are using a regressor, you need to specify a target that has continuous values. FreqAI includes a variety of regressors, such as the `CatboostRegressor`via the flag `--freqaimodel CatboostRegressor`. An example of how you could set a regression target for predicting the price 100 candles into the future would be
+If you are using a regressor, you need to specify a target that has continuous values. FreqAI includes a variety of regressors, such as the `LightGBMRegressor`via the flag `--freqaimodel LightGBMRegressor`. An example of how you could set a regression target for predicting the price 100 candles into the future would be

 ```python
 df['&s-close_price'] = df['close'].shift(-100)
@@ -229,7 +229,7 @@ If you want to predict multiple targets, you need to define multiple labels usin

 #### Classifiers

-If you are using a classifier, you need to specify a target that has discrete values. FreqAI includes a variety of classifiers, such as the `CatboostClassifier` via the flag `--freqaimodel CatboostClassifier`. If you elects to use a classifier, the classes need to be set using strings. For example, if you want to predict if the price 100 candles into the future goes up or down you would set
+If you are using a classifier, you need to specify a target that has discrete values. FreqAI includes a variety of classifiers, such as the `LightGBMClassifier` via the flag `--freqaimodel LightGBMClassifier`. If you elects to use a classifier, the classes need to be set using strings. For example, if you want to predict if the price 100 candles into the future goes up or down you would set

 ```python
 df['&s-up_or_down'] = np.where( df["close"].shift(-100) > df["close"], 'up', 'down')
@@ -260,6 +260,10 @@ freqtrade trade --config config_examples/config_freqai.example.json --strategy F

    PyTorch dropped support for macOS x64 (intel based Apple devices) in version 2.3. Subsequently, freqtrade also dropped support for PyTorch on this platform.

+!!! Danger "Security notice"
+    Loading saved models from disk can cause security issues if using remote model files (files you downloaded from the internet or received from an untrusted source) due to having the necessity to have `weights_only=False`, which can cause security problems.
+    As long as you only load models that you have trained yourself, there is no risk.
+
 ### Structure

 #### Model
@@ -79,7 +79,7 @@ Mandatory parameters are marked as **Required** and have to be set in one of the
 | `model_type` | Model string from stable_baselines3 or SBcontrib. Available strings include: `'TRPO', 'ARS', 'RecurrentPPO', 'MaskablePPO', 'PPO', 'A2C', 'DQN'`. User should ensure that `model_training_parameters` match those available to the corresponding stable_baselines3 model by visiting their documentation. [PPO doc](https://stable-baselines3.readthedocs.io/en/master/modules/ppo.html) (external website) <br> **Datatype:** string.
 | `policy_type` | One of the available policy types from stable_baselines3 <br> **Datatype:** string.
 | `max_training_drawdown_pct` | The maximum drawdown that the agent is allowed to experience during training. <br> **Datatype:** float. <br> Default: 0.8
-| `cpu_count` | Number of threads/cpus to dedicate to the Reinforcement Learning training process (depending on if `ReinforcementLearning_multiproc` is selected or not). Recommended to leave this untouched, by default, this value is set to the total number of physical cores minus 1. <br> **Datatype:** int. 
+| `cpu_count` | Number of threads/cpus to dedicate to the Reinforcement Learning training process (depending on if `ReinforcementLearner_multiproc` is selected or not). Recommended to leave this untouched, by default, this value is set to the total number of physical cores minus 1. <br> **Datatype:** int.
 | `model_reward_parameters` | Parameters used inside the customizable `calculate_reward()` function in `ReinforcementLearner.py` <br> **Datatype:** int.
 | `add_state_info` | Tell FreqAI to include state information in the feature set for training and inferencing. The current state variables include trade duration, current profit, trade position. This is only available in dry/live runs, and is automatically switched to false for backtesting. <br> **Datatype:** bool. <br> Default: `False`.
 | `net_arch` | Network architecture which is well described in [`stable_baselines3` doc](https://stable-baselines3.readthedocs.io/en/master/guide/custom_policy.html#examples). In summary: `[<shared layers>, dict(vf=[<non-shared value network layers>], pi=[<non-shared policy network layers>])]`. By default this is set to `[128, 128]`, which defines 2 shared hidden layers with 128 units each.
@@ -106,7 +106,7 @@ Mandatory parameters are marked as **Required** and have to be set in one of the
 | `n_epochs`   | The `n_epochs` parameter is a crucial setting in the PyTorch training loop that determines the number of times the entire training dataset will be used to update the model's parameters. An epoch represents one full pass through the entire training dataset. Overrides `n_steps`. Either `n_epochs` or `n_steps` must be set. <br><br> **Datatype:** int. optional. <br> Default: `10`.
 | `n_steps`    | An alternative way of setting `n_epochs` -  the number of training iterations to run. Iteration here refer to the number of times we call `optimizer.step()`. Ignored if `n_epochs` is set. A simplified version of the function: <br><br> n_epochs = n_steps / (n_obs / batch_size) <br><br> The motivation here is that `n_steps` is easier to optimize and keep stable across different n_obs - the number of data points.  <br> <br> **Datatype:** int. optional. <br> Default: `None`.
 | `batch_size` | The size of the batches to use during training. <br><br> **Datatype:** int. <br> Default: `64`.
-
+| `early_stopping_patience` | Number of epochs with no improvement in validation loss before training is stopped early. This helps prevent overfitting by halting training when the model stops improving. Set to `0` to disable early stopping. Requires a test/validation split (`test_size > 0`). <br><br> **Datatype:** int. <br> Default: `0` (disabled).

 ### Additional parameters

@@ -116,3 +116,4 @@ Mandatory parameters are marked as **Required** and have to be set in one of the
 | `freqai.keras` | If the selected model makes use of Keras (typical for TensorFlow-based prediction models), this flag needs to be activated so that the model save/loading follows Keras standards. <br> **Datatype:** Boolean. <br> Default: `False`.
 | `freqai.conv_width` | The width of a neural network input tensor. This replaces the need for shifting candles (`include_shifted_candles`) by feeding in historical data points as the second dimension of the tensor. Technically, this parameter can also be used for regressors, but it only adds computational overhead and does not change the model training/prediction. <br> **Datatype:** Integer. <br> Default: `2`.
 | `freqai.reduce_df_footprint` | Recast all numeric columns to float32/int32, with the objective of reducing ram/disk usage and decreasing train/inference timing. This parameter is set in the main level of the Freqtrade configuration file (not inside FreqAI). <br> **Datatype:** Boolean. <br> Default: `False`.
+| `freqai.override_exchange_check` | Override the exchange check to force FreqAI to use exchanges that may not have enough historic data. Turn this to True if you know your FreqAI model and strategy do not require historical data. <br> **Datatype:** Boolean. <br> Default: `False`.
@@ -45,7 +45,7 @@ where `ReinforcementLearner` will use the templated `ReinforcementLearner` from

        More details about feature engineering available:

-        https://www.freqtrade.io/en/latest/freqai-feature-engineering
+        https://www.freqtrade.io/en/stable/freqai-feature-engineering

        :param df: strategy dataframe which will receive the targets
        usage example: dataframe["&-target"] = dataframe["close"].shift(-1) / dataframe["close"]
@@ -87,6 +87,10 @@ To save the models generated during a particular backtest so that you can start
    To ensure that the model can be reused, freqAI will call your strategy with a dataframe of length 1. 
    If your strategy requires more data than this to generate the same features, you can't reuse backtest predictions for live deployment and need to update your `identifier` for each new backtest.

+!!! Danger "Security notice"
+    Loading saved models from disk can cause security issues if using remote model files (files you downloaded from the internet or received from an untrusted source) due to having the necessity to have `weights_only=False`, which can cause security problems.
+    As long as you only load models that you have trained yourself, there is no risk.
+
 ### Backtest live collected predictions

 FreqAI allow you to reuse live historic predictions through the backtest parameter `--freqai-backtest-live-models`. This can be useful when you want to reuse predictions generated in dry/run for comparison or other study.
@@ -7,7 +7,7 @@
 FreqAI is a software designed to automate a variety of tasks associated with training a predictive machine learning model to generate market forecasts given a set of input signals. In general, FreqAI aims to be a sandbox for easily deploying robust machine learning libraries on real-time data ([details](#freqai-position-in-open-source-machine-learning-landscape)).

 !!! Note
-    FreqAI is, and always will be, a not-for-profit, open-source project. FreqAI does *not* have a crypto token, FreqAI does *not* sell signals, and FreqAI does not have a domain besides the present [freqtrade documentation](https://www.freqtrade.io/en/latest/freqai/).
+    FreqAI is, and always will be, a not-for-profit, open source project. FreqAI does *not* have a crypto token, FreqAI does *not* sell signals, and FreqAI does not have a domain besides the present [freqtrade documentation](https://www.freqtrade.io/en/stable/freqai/).

 Features include:

@@ -81,9 +81,9 @@ If you are using docker, a dedicated tag with FreqAI dependencies is available a
 !!! note "docker-compose-freqai.yml"
    We do provide an explicit docker-compose file for this in `docker/docker-compose-freqai.yml` - which can be used via `docker compose -f docker/docker-compose-freqai.yml run ...` - or can be copied to replace the original docker file. This docker-compose file also contains a (disabled) section to enable GPU resources within docker containers. This obviously assumes the system has GPU resources available.

-### FreqAI position in open-source machine learning landscape
+### FreqAI position in open source machine learning landscape

-Forecasting chaotic time-series based systems, such as equity/cryptocurrency markets, requires a broad set of tools geared toward testing a wide range of hypotheses. Fortunately, a recent maturation of robust machine learning libraries (e.g. `scikit-learn`) has opened up a wide range of research possibilities. Scientists from a diverse range of fields can now easily prototype their studies on an abundance of established machine learning algorithms. Similarly, these user-friendly libraries enable "citizen scientists" to use their basic Python skills for data exploration. However, leveraging these machine learning libraries on historical and live chaotic data sources can be logistically difficult and expensive. Additionally, robust data collection, storage, and handling presents a disparate challenge. [`FreqAI`](#freqai) aims to provide a generalized and extensible open-sourced framework geared toward live deployments of adaptive modeling for market forecasting. The `FreqAI` framework is effectively a sandbox for the rich world of open-source machine learning libraries. Inside the `FreqAI` sandbox, users find they can combine a wide variety of third-party libraries to test creative hypotheses on a free live 24/7 chaotic data source - cryptocurrency exchange data. 
+Forecasting chaotic time-series based systems, such as equity/cryptocurrency markets, requires a broad set of tools geared toward testing a wide range of hypotheses. Fortunately, a recent maturation of robust machine learning libraries (e.g. `scikit-learn`) has opened up a wide range of research possibilities. Scientists from a diverse range of fields can now easily prototype their studies on an abundance of established machine learning algorithms. Similarly, these user-friendly libraries enable "citizen scientists" to use their basic Python skills for data exploration. However, leveraging these machine learning libraries on historical and live chaotic data sources can be logistically difficult and expensive. Additionally, robust data collection, storage, and handling presents a disparate challenge. [`FreqAI`](#freqai) aims to provide a generalized and extensible open-sourced framework geared toward live deployments of adaptive modeling for market forecasting. The `FreqAI` framework is effectively a sandbox for the rich world of open source machine learning libraries. Inside the `FreqAI` sandbox, users find they can combine a wide variety of third-party libraries to test creative hypotheses on a free live 24/7 chaotic data source - cryptocurrency exchange data. 

 ### Citing FreqAI

@@ -46,10 +46,17 @@ Depending on the space you want to optimize, only some of the below are required

 * define parameters with `space='buy'` - for entry signal optimization
 * define parameters with `space='sell'` - for exit signal optimization
+* define parameters with `space='enter'` - for entry signal optimization
+* define parameters with `space='exit'` - for exit signal optimization
+* define parameters with `space='protection'` - for protection optimization
+* define parameters with `space='random_spacename'` - for better control over which parameters are optimized together
+
+Pick the space name that suits the parameter best. We recommend to use either `buy` / `sell` or `enter` / `exit` for clarity (however there's no technical limitation in this regard).

 !!! Note
    `populate_indicators` needs to create all indicators any of the spaces may use, otherwise hyperopt will not work.

+
 Rarely you may also need to create a [nested class](advanced-hyperopt.md#overriding-pre-defined-spaces) named `HyperOpt` and implement

 * `roi_space` - for custom ROI optimization (if you need the ranges for the ROI parameters in the optimization hyperspace that differ from default)
@@ -79,15 +86,15 @@ Based on the loss function result, hyperopt will determine the next set of param

 ### Configure your Guards and Triggers

-There are two places you need to change in your strategy file to add a new buy hyperopt for testing:
+There are two places you need to change in your strategy file to add a new hyperopt parameter for optimization:

 * Define the parameters at the class level hyperopt shall be optimizing.
 * Within `populate_entry_trend()` - use defined parameter values instead of raw constants.

 There you have two different types of indicators: 1. `guards` and 2. `triggers`.

-1. Guards are conditions like "never buy if ADX < 10", or never buy if current price is over EMA10.
-2. Triggers are ones that actually trigger buy in specific moment, like "buy when EMA5 crosses over EMA10" or "buy when close price touches lower Bollinger band".
+1. Guards are conditions like "never enter if ADX < 10", or never enter if current price is over EMA10.
+2. Triggers are ones that actually trigger entry in specific moment, like "enter when EMA5 crosses over EMA10" or "enter when close price touches lower Bollinger band".

 !!! Hint "Guards and Triggers"
    Technically, there is no difference between Guards and Triggers.  
@@ -160,9 +167,11 @@ We use these to either enable or disable the ADX and RSI guards.
 The last one we call `trigger` and use it to decide which buy trigger we want to use.

 !!! Note "Parameter space assignment"
-    Parameters must either be assigned to a variable named `buy_*` or `sell_*` - or contain `space='buy'` | `space='sell'` to be assigned to a space correctly.
-    If no parameter is available for a space, you'll receive the error that no space was found when running hyperopt.  
+    - Parameters must either be assigned to a variable named `buy_*`, `sell_*`, `enter_*` or `exit_*` or `protection_*` - or contain have a space assigned explicitly via parameter (`space='buy'`, `space='sell'`, `space='protection'`).  
+    - Parameters with conflicting assignments (e.g. `buy_adx = IntParameter(4, 24, default=14, space='sell')`) will use the explicit space assignment.  
+    - If no parameter is available for a space, you'll receive the error that no space was found when running hyperopt.  
    Parameters with unclear space (e.g. `adx_period = IntParameter(4, 24, default=14)` - no explicit nor implicit space) will not be detected and will therefore be ignored.
+    Spaces can also be custom named (e.g. `space='my_custom_space'`), with the only limitation that the space name cannot be `all`, `default` - and must result in a valid python identifier.

 So let's write the buy strategy using these values:

@@ -520,21 +529,24 @@ freqtrade hyperopt --strategy <strategyname> --timerange 20210101-20210201
 ### Running Hyperopt with Smaller Search Space

 Use the `--spaces` option to limit the search space used by hyperopt.
-Letting Hyperopt optimize everything is a huuuuge search space.
-Often it might make more sense to start by just searching for initial buy algorithm.
-Or maybe you just want to optimize your stoploss or roi table for that awesome new buy strategy you have.
+Letting Hyperopt optimize everything is often a huuuuge search space.
+Often it might make more sense to start by just searching for initial entry algorithm.
+Or maybe you just want to optimize your stoploss or roi table for that awesome new strategy you have.

 Legal values are:

-* `all`: optimize everything
+* `all`: optimize everything (including custom spaces)
 * `buy`: just search for a new buy strategy
 * `sell`: just search for a new sell strategy
+* `enter`: just search for a new entry logic
+* `exit`: just search for a new entry logic
 * `roi`: just optimize the minimal profit table for your strategy
 * `stoploss`: search for the best stoploss value
 * `trailing`: search for the best trailing stop values
 * `trades`: search for the best max open trades values
 * `protection`: search for the best protection parameters (read the [protections section](#optimizing-protections) on how to properly define these)
 * `default`: `all` except `trailing`, `trades` and `protection`
+* `custom_space_name`: any custom space used by any parameter in your strategy
 * space-separated list of any of the above values for example `--spaces roi stoploss`

 The default Hyperopt Search Space, used when no `--space` command line option is specified, does not include the `trailing` hyperspace. We recommend you to run optimization for the `trailing` hyperspace separately, when the best parameters for other hyperspaces were found, validated and pasted into your custom strategy.
@@ -15,7 +15,7 @@ Assuming your application is deployed as `https://frequi.freqtrade.io/home/` - t
 ```jsonc
 {
    //...
-    "jwt_secret_key": "somethingrandom",
+    "jwt_secret_key": "somethingRandomSomethingRandom123",
    "CORS_origins": ["https://frequi.freqtrade.io"],
    //...
 }
@@ -29,7 +29,7 @@ The correct configuration for this case is `http://localhost:8080` - the main pa
 ```jsonc
 {
    //...
-    "jwt_secret_key": "somethingrandom",
+    "jwt_secret_key": "somethingRandomSomethingRandom123",
    "CORS_origins": ["http://localhost:8080"],
    //...
 }
@@ -0,0 +1,22 @@
+
+| Exchange | Mode | Margin mode | Stoploss type | 
+|---------|---------|------|------------------|
+| [Binance](exchanges.md#binance) | spot | | limit |
+| [Binance](exchanges.md#binance) | futures | isolated, cross | market, limit |
+| [Bingx](exchanges.md#bingx) | spot | | market, limit |
+| [Bitmart](exchanges.md#bitmart) | spot | | ❌ (not supported) |
+| [Bitget](exchanges.md#bitget) | spot | | market, limit |
+| [Bitget](exchanges.md#bitget) | futures | isolated | market, limit |
+| [Bybit](exchanges.md#bybit) | spot | | ❌ (not supported) |
+| [Bybit](exchanges.md#bybit) | futures | isolated | market, limit |
+| [Gate.io](exchanges.md#gateio) | spot | | limit |
+| [Gate.io](exchanges.md#gateio) | futures | isolated | limit |
+| [HTX](exchanges.md#htx) | spot | | limit |
+| [Hyperliquid](exchanges.md#hyperliquid) | spot | | ❌ (not supported) |
+| [Hyperliquid](exchanges.md#hyperliquid) | futures | isolated, cross | limit |
+| [Kraken](exchanges.md#kraken) | spot | | market, limit |
+| [Kraken](exchanges.md#kraken-futures) | futures | isolated | market, limit |
+| [OKX](exchanges.md#okx) | spot | | limit |
+| [OKX](exchanges.md#okx) | futures | isolated | limit |
+| [Bitvavo](exchanges.md#bitvavo) | spot | | ❌ (not supported) |
+| [Kucoin](exchanges.md#kucoin) | spot | | market, limit |
@@ -2,11 +2,11 @@

 Pairlist Handlers define the list of pairs (pairlist) that the bot should trade. They are configured in the `pairlists` section of the configuration settings.

-In your configuration, you can use Static Pairlist (defined by the [`StaticPairList`](#static-pair-list) Pairlist Handler) and Dynamic Pairlist (defined by the [`VolumePairList`](#volume-pair-list) and [`PercentChangePairList`](#percent-change-pair-list) Pairlist Handlers).
+In your configuration, you can use Static Pairlist (defined by the [`StaticPairList`](#static-pair-list) Pairlist Handler) and Dynamic Pairlist (defined by the [`VolumePairList`](#volume-pair-list), [`CrossMarketPairList`](#crossmarketpairlist), [`MarketCapPairlist`](#marketcappairlist) and [`PercentChangePairList`](#percent-change-pair-list) Pairlist Handlers).

-Additionally, [`AgeFilter`](#agefilter), [`PrecisionFilter`](#precisionfilter), [`PriceFilter`](#pricefilter), [`ShuffleFilter`](#shufflefilter), [`SpreadFilter`](#spreadfilter) and [`VolatilityFilter`](#volatilityfilter) act as Pairlist Filters, removing certain pairs and/or moving their positions in the pairlist.
+Additionally, [`AgeFilter`](#agefilter), [`DelistFilter`](#delistfilter), [`PrecisionFilter`](#precisionfilter), [`PriceFilter`](#pricefilter), [`ShuffleFilter`](#shufflefilter), [`SpreadFilter`](#spreadfilter) and [`VolatilityFilter`](#volatilityfilter) act as Pairlist Filters, removing certain pairs and/or moving their positions in the pairlist.

-If multiple Pairlist Handlers are used, they are chained and a combination of all Pairlist Handlers forms the resulting pairlist the bot uses for trading and backtesting. Pairlist Handlers are executed in the sequence they are configured. You can define either `StaticPairList`, `VolumePairList`, `ProducerPairList`, `RemotePairList`, `MarketCapPairList` or `PercentChangePairList` as the starting Pairlist Handler.
+If multiple Pairlist Handlers are used, they are chained and a combination of all Pairlist Handlers forms the resulting pairlist the bot uses for trading and backtesting. Pairlist Handlers are executed in the sequence they are configured. You can define either `StaticPairList`, `VolumePairList`, `ProducerPairList`, `RemotePairList`, `MarketCapPairList`, `PercentChangePairList` or `CrossMarketPairList` as the starting Pairlist Handler.

 Inactive markets are always removed from the resulting pairlist. Explicitly blacklisted pairs (those in the `pair_blacklist` configuration setting) are also always removed from the resulting pairlist.

@@ -26,7 +26,9 @@ You may also use something like `.*DOWN/BTC` or `.*UP/BTC` to exclude leveraged
 * [`ProducerPairList`](#producerpairlist)
 * [`RemotePairList`](#remotepairlist)
 * [`MarketCapPairList`](#marketcappairlist)
+* [`CrossMarketPairList`](#crossmarketpairlist)
 * [`AgeFilter`](#agefilter)
+* [`DelistFilter`](#delistfilter)
 * [`FullTradesFilter`](#fulltradesfilter)
 * [`OffsetFilter`](#offsetfilter)
 * [`PerformanceFilter`](#performancefilter)
@@ -38,7 +40,7 @@ You may also use something like `.*DOWN/BTC` or `.*UP/BTC` to exclude leveraged
 * [`VolatilityFilter`](#volatilityfilter)

 !!! Tip "Testing pairlists"
-    Pairlist configurations can be quite tricky to get right. Best use the [`test-pairlist`](utils.md#test-pairlist) utility sub-command to test your configuration quickly.
+    Pairlist configurations can be quite tricky to get right. Best use freqUI in [webserver mode](freq-ui.md#webserver-mode) or the [`test-pairlist`](utils.md#test-pairlist) utility sub-command to test your Pairlist configuration quickly.

 #### Static Pair List

@@ -180,7 +182,7 @@ More sophisticated approach can be used, by using `lookback_timeframe` for candl
 * `refresh_period`: Defines the interval (in seconds) at which the pairlist will be refreshed. The default is 1800 seconds (30 minutes).
 * `lookback_days`: Number of days to look back. When `lookback_days` is selected, the `lookback_timeframe` is defaulted to 1 day.
 * `lookback_timeframe`: Timeframe to use for the lookback period.
-* `lookback_period`: Number of periods to look back at. 
+* `lookback_period`: Number of periods to look back at.

 When PercentChangePairList is used after other Pairlist Handlers, it will operate on the outputs of those handlers. If it is the leading Pairlist Handler, it will select pairs from all available markets with the specified stake currency.

@@ -270,7 +272,6 @@ You can limit the length of the pairlist with the optional parameter `number_ass
 ],
 ```

-
 !!! Tip "Combining pairlists"
    This pairlist can be combined with all other pairlists and filters for further pairlist reduction, and can also act as an "additional" pairlist, on top of already defined pairs.
    `ProducerPairList` can also be used multiple times in sequence, combining the pairs from multiple producers.
@@ -303,6 +304,8 @@ The optional `mode` option specifies if the pairlist should be used as a `blackl

 The optional `processing_mode` option in the RemotePairList configuration determines how the retrieved pairlist is processed. It can have two values: "filter" or "append". The default value is "filter".

+The optional `number_assets` option in the RemotePairList configuration determines how many pairs will be returned if used in whitelist `mode`. By default, all pairs will be returned. In blacklist `mode`, this option will be ignored.
+
 In "filter" mode, the retrieved pairlist is used as a filter. Only the pairs present in both the original pairlist and the retrieved pairlist are included in the final pairlist. Other pairs are filtered out.

 In "append" mode, the retrieved pairlist is added to the original pairlist. All pairs from both lists are included in the final pairlist without any filtering.
@@ -312,7 +315,7 @@ The `pairlist_url` option specifies the URL of the remote server where the pairl
 The `save_to_file` option, when provided with a valid filename, saves the processed pairlist to that file in JSON format. This option is optional, and by default, the pairlist is not saved to a file.

 ??? Example "Multi bot with shared pairlist example"
-    
+
    `save_to_file` can be used to save the pairlist to a file with Bot1:

    ```json
@@ -367,7 +370,7 @@ The optional `bearer_token` will be included in the requests Authorization Heade

 #### MarketCapPairList

-`MarketCapPairList` employs sorting/filtering of pairs by their marketcap rank based of CoinGecko. The returned pairlist will be sorted based of their marketcap ranks.
+`MarketCapPairList` employs sorting/filtering of pairs by their marketcap rank based of CoinGecko. The returned pairlist will be sorted based of their marketcap ranks if used in whitelist `mode`.

 ```json
 "pairlists": [
@@ -376,25 +379,38 @@ The optional `bearer_token` will be included in the requests Authorization Heade
        "number_assets": 20,
        "max_rank": 50,
        "refresh_period": 86400,
+        "mode": "whitelist",
        "categories": ["layer-1"]
    }
 ]
 ```

-`number_assets` defines the maximum number of pairs returned by the pairlist. `max_rank` will determine the maximum rank used in creating/filtering the pairlist. It's expected that some coins within the top `max_rank` marketcap will not be included in the resulting pairlist since not all pairs will have active trading pairs in your preferred market/stake/exchange combination.  
+`number_assets` defines the maximum number of pairs returned by the pairlist if used in whitelist `mode`. In blacklist `mode`, this setting will be ignored.
+
+`max_rank` will determine the maximum rank used in creating/filtering the pairlist. It's expected that some coins within the top `max_rank` marketcap will not be included in the resulting pairlist since not all pairs will have active trading pairs in your preferred market/stake/exchange combination.  
 While using a `max_rank` bigger than 250 is supported, it's not recommended, as it'll cause multiple API calls to CoinGecko, which can lead to rate limit issues.

 The `refresh_period` setting defines the interval (in seconds) at which the marketcap rank data will be refreshed. The default is 86,400 seconds (1 day). The pairlist cache (`refresh_period`) applies to both generating pairlists (when in the first position in the list) and filtering instances (when not in the first position in the list).

+The `mode` setting defines whether the plugin will filters in (whitelist `mode`) or filters out (blacklist `mode`) top marketcap ranked coins. By default, the plugin will be in whitelist mode.
+
 The `categories` setting specifies the [coingecko categories](https://www.coingecko.com/en/categories) from which to select coins from. The default is an empty list `[]`, meaning no category filtering is applied.
 If an incorrect category string is chosen, the plugin will print the available categories from CoinGecko and fail. The category should be the ID of the category, for example, for `https://www.coingecko.com/en/categories/layer-1`, the category ID would be `layer-1`. You can pass multiple categories such as `["layer-1", "meme-token"]` to select from several categories.

+Coins like 1000PEPE/USDT or KPEPE/USDT:USDT are detected on a best effort basis, with the prefixes `1000` and `K` being used to identify them.
+
 !!! Warning "Many categories"
    Each added category corresponds to one API call to CoinGecko. The more categories you add, the longer the pairlist generation will take, potentially causing rate limit issues.

 !!! Danger "Duplicate symbols in coingecko"
    Coingecko often has duplicate symbols, where the same symbol is used for different coins. Freqtrade will use the symbol as is and try to search for it on the exchange. If the symbol exists - it will be used. Freqtrade will however not check if the _intended_ symbol is the one coingecko meant. This can sometimes lead to unexpected results, especially on low volume coins or with meme coin categories.

+#### CrossMarketPairList
+
+Generate or filter pairs based of their availability on the opposite market.
+
+The `pairs_exist_on` setting defines whether the pairs should exists on both spot and futures market (`both_markets`) or only exist on the specified trading mode (`current_market_only`). By default, the plugin will be in `both_markets` setting, which means whitelisted pairs have to exists on both spot and futures markets.
+
 #### AgeFilter

 Removes pairs that have been listed on the exchange for less than `min_days_listed` days (defaults to `10`) or more than `max_days_listed` days (defaults `None` mean infinity).
@@ -405,6 +421,16 @@ be caught out buying before the pair has finished dropping in price.

 This filter allows freqtrade to ignore pairs until they have been listed for at least `min_days_listed` days and listed before `max_days_listed`.

+#### DelistFilter
+
+Removes pairs that will be delisted on the exchange maximum `max_days_from_now` days from now (defaults to `0` which remove all future delisted pairs no matter how far from now). Currently this filter only supports following exchanges:
+
+!!! Note "Available exchanges"
+    Delist filter is available on Bybit Futures, Bitget Futures and Binance, where Binance Futures will work for both dry and live modes, while Binance Spot is limited to live mode (for technical reasons).
+
+!!! Warning "Backtesting"
+    `DelistFilter` does not support backtesting mode.
+
 #### FullTradesFilter

 Shrink whitelist to consist only in-trade pairs when the trade slots are full (when `max_open_trades` isn't being set to `-1` in the config).
@@ -436,7 +462,7 @@ Example to remove the first 10 pairs from the pairlist, and takes the next 20 (t
 ```

 !!! Warning
-    When `OffsetFilter` is used to split a larger pairlist among multiple bots in combination with `VolumeFilter` 
+    When `OffsetFilter` is used to split a larger pairlist among multiple bots in combination with `VolumeFilter`
    it can not be guaranteed that pairs won't overlap due to slightly different refresh intervals for the
    `VolumeFilter`.

@@ -599,7 +625,7 @@ Adding `"sort_direction": "asc"` or `"sort_direction": "desc"` enables sorting m

 ### Full example of Pairlist Handlers

-The below example blacklists `BNB/BTC`, uses `VolumePairList` with `20` assets, sorting pairs by `quoteVolume` and applies [`PrecisionFilter`](#precisionfilter) and [`PriceFilter`](#pricefilter), filtering all assets where 1 price unit is > 1%. Then the [`SpreadFilter`](#spreadfilter) and [`VolatilityFilter`](#volatilityfilter) is applied and pairs are finally shuffled with the random seed set to some predefined value.
+The below example blacklists `BNB/BTC`, uses `VolumePairList` with `20` assets, sorting pairs by `quoteVolume`, then filter future delisted pairs using [`DelistFilter`](#delistfilter) and [`AgeFilter`](#agefilter) to remove pairs that are listed less than 10 days ago. After that [`PrecisionFilter`](#precisionfilter) and [`PriceFilter`](#pricefilter) are applied, filtering all assets where 1 price unit is > 1%. Then the [`SpreadFilter`](#spreadfilter) and [`VolatilityFilter`](#volatilityfilter) are applied and pairs are finally shuffled with the random seed set to some predefined value.

 ```json
 "exchange": {
@@ -612,6 +638,10 @@ The below example blacklists `BNB/BTC`, uses `VolumePairList` with `20` assets,
        "number_assets": 20,
        "sort_key": "quoteVolume"
    },
+    {
+        "method": "DelistFilter",
+        "max_days_from_now": 0,
+    },
    {"method": "AgeFilter", "min_days_listed": 10},
    {"method": "PrecisionFilter"},
    {"method": "PriceFilter", "low_price_ratio": 0.01},
@@ -20,15 +20,15 @@ All protection end times are rounded up to the next candle to avoid sudden, unex

 ### Common settings to all Protections

-|  Parameter| Description |
-|------------|-------------|
-| `method` | Protection name to use. <br> **Datatype:** String, selected from [available Protections](#available-protections)
-| `stop_duration_candles` | For how many candles should the lock be set? <br> **Datatype:** Positive integer (in candles)
-| `stop_duration` | how many minutes should protections be locked. <br>Cannot be used together with `stop_duration_candles`. <br> **Datatype:** Float (in minutes)
-| `lookback_period_candles` | Only trades that completed within the last `lookback_period_candles` candles will be considered. This setting may be ignored by some Protections. <br> **Datatype:** Positive integer (in candles).
-| `lookback_period` | Only trades that completed after `current_time - lookback_period` will be considered. <br>Cannot be used together with `lookback_period_candles`. <br>This setting may be ignored by some Protections. <br> **Datatype:**  Float (in minutes)
-| `trade_limit` | Number of trades required at minimum (not used by all Protections). <br> **Datatype:** Positive integer
-| `unlock_at` | Time when trading will be unlocked regularly (not used by all Protections). <br> **Datatype:** string <br>**Input Format:** "HH:MM" (24-hours)
+| Parameter | Description |
+| --------- | ---------- |
+| `method` | Protection name to use. <br> **Datatype:** String, selected from [available Protections](#available-protections) |
+| `stop_duration_candles` | For how many candles should the lock be set? <br> **Datatype:** Positive integer (in candles) |
+| `stop_duration` | how many minutes should protections be locked. <br>Cannot be used together with `stop_duration_candles`. <br> **Datatype:** Float (in minutes) |
+| `lookback_period_candles` | Only trades that completed within the last `lookback_period_candles` candles will be considered. This setting may be ignored by some Protections. <br> **Datatype:** Positive integer (in candles). |
+| `lookback_period` | Only trades that completed after `current_time - lookback_period` will be considered. <br>Cannot be used together with `lookback_period_candles`. <br>This setting may be ignored by some Protections. <br> **Datatype:**  Float (in minutes) |
+| `trade_limit` | Number of trades required at minimum (not used by all Protections). <br> **Datatype:** Positive integer |
+| `unlock_at` | Time when trading will be unlocked regularly (not used by all Protections). <br> **Datatype:** string <br>**Input Format:** "HH:MM" (24-hours) |

 !!! Note "Durations"
    Durations (`stop_duration*` and `lookback_period*` can be defined in either minutes or candles).
@@ -69,7 +69,17 @@ def protections(self):

 #### MaxDrawdown

-`MaxDrawdown` uses all trades within `lookback_period` in minutes (or in candles when using `lookback_period_candles`) to determine the maximum drawdown. If the drawdown is below `max_allowed_drawdown`, trading will stop for `stop_duration` in minutes (or in candles when using `stop_duration_candles`) after the last trade - assuming that the bot needs some time to let markets recover.
+The `MaxDrawdown` protection evaluates trades that closed within the current `lookback_period` (or `lookback_period_candles`).  
+It supports 2 calculation modes:
+
+- `calculation_mode: "ratios"` (default): Legacy approximation based on cumulative profit ratios.
+- `calculation_mode: "equity"`: Standard peak-to-trough drawdown on the account equity curve, using starting balance and cumulative absolute profit.
+
+With `calculation_mode: "ratios"`, drawdown is derived from cumulative trade profit ratios, not from the account equity curve. This is kept for backward compatibility and can differ from account-level drawdown when position sizing changes over time.
+
+For new setups, `calculation_mode: "equity"` is recommended. Prefer `calculation_mode: "ratios"` only when you intentionally rely on legacy behavior, especially with fixed stake amount configurations where ratio-based behavior is easier to reason about.
+
+If the observed drawdown exceeds `max_allowed_drawdown`, trading will stop for `stop_duration` after the last trade - assuming that the bot needs some time to let markets recover.

 The below sample stops trading for 12 candles if max-drawdown is > 20% considering all pairs - with a minimum of `trade_limit` trades - within the last 48 candles. If desired, `lookback_period` and/or `stop_duration` can be used.

@@ -79,6 +89,7 @@ def protections(self):
    return  [
        {
            "method": "MaxDrawdown",
+            "calculation_mode": "equity",
            "lookback_period_candles": 48,
            "trade_limit": 20,
            "stop_duration_candles": 12,
@@ -160,6 +171,7 @@ class AwesomeStrategy(IStrategy)
            },
            {
                "method": "MaxDrawdown",
+                "calculation_mode": "equity",
                "lookback_period_candles": 48,
                "trade_limit": 20,
                "stop_duration_candles": 4,
@@ -1,28 +1,28 @@
-## Highlighted changes
+# Highlighted changes

 - ...

-### How to update
+## How to update

 As always, you can update your bot using one of the following commands:

-#### docker-compose
+### docker-compose

 ```bash
 docker-compose pull
 docker-compose up -d
 ```

-#### Installation via setup script
+### Installation via setup script

-```
+``` bash
 # Deactivate venv and run 
 ./setup.sh --update
 ```

-#### Plain native installation
+### Plain native installation

-```
+``` bash
 git pull
 pip install -U -r requirements.txt
 ```
@@ -1,11 +1,11 @@
 This section will highlight a few projects from members of the community.
 !!! Note
-    The projects below are for the most part not maintained by the freqtrade , therefore use your own caution before using them.
+    The projects below are for the most part not maintained by the freqtrade team, therefore use your own caution before using them.

 - [Example freqtrade strategies](https://github.com/freqtrade/freqtrade-strategies/)
 - [FrequentHippo - Statistics of dry/live runs and backtests](http://frequenthippo.ddns.net) (by hippocritical).
 - [Online pairlist generator](https://remotepairlist.com/) (by Blood4rc).
 - [Freqtrade Backtesting Project](https://strat.ninja/) (by Blood4rc).
 - [Freqtrade analysis notebook](https://github.com/froggleston/freqtrade_analysis_notebook) (by Froggleston).
- [TUI for freqtrade](https://github.com/froggleston/freqtrade-frogtrade9000) (by Froggleston).
+- [FTUI - Terminal UI for freqtrade](https://github.com/freqtrade/ftui) (by Froggleston).
 - [Bot Academy](https://botacademy.ddns.net/) (by stash86) - Blog about crypto bot projects.
@@ -1,14 +1,15 @@
 ![freqtrade](assets/freqtrade_poweredby.svg)

-[![Freqtrade CI](https://github.com/freqtrade/freqtrade/actions/workflows/ci.yml/badge.svg?branch=develop)](https://github.com/freqtrade/freqtrade/actions/)
+[![Freqtrade CI](https://github.com/freqtrade/freqtrade/actions/workflows/ci.yml/badge.svg?branch=develop)](https://github.com/freqtrade/freqtrade/actions/workflows/ci.yml)
 [![DOI](https://joss.theoj.org/papers/10.21105/joss.04864/status.svg)](https://doi.org/10.21105/joss.04864)
-[![Coverage Status](https://coveralls.io/repos/github/freqtrade/freqtrade/badge.svg?branch=develop&service=github)](https://coveralls.io/github/freqtrade/freqtrade?branch=develop)
-[![Maintainability](https://api.codeclimate.com/v1/badges/5737e6d668200b7518ff/maintainability)](https://codeclimate.com/github/freqtrade/freqtrade/maintainability)
+[![codecov](https://codecov.io/gh/freqtrade/freqtrade/branch/develop/graph/badge.svg?token=AD5BG3ATKI)](https://codecov.io/gh/freqtrade/freqtrade)
+[![Documentation](https://readthedocs.org/projects/freqtrade/badge/)](https://www.freqtrade.io)
+[![Discord Server](https://img.shields.io/badge/Freqtrade_Discord-4E4E4E?logo=discord)](https://discord.gg/p7nuUNVfP7)

-<!-- Place this tag where you want the button to render. -->
-<a class="github-button" href="https://github.com/freqtrade/freqtrade" data-icon="octicon-star" data-size="large" aria-label="Star freqtrade/freqtrade on GitHub">Star</a>
-<a class="github-button" href="https://github.com/freqtrade/freqtrade/fork" data-icon="octicon-repo-forked" data-size="large" aria-label="Fork freqtrade/freqtrade on GitHub">Fork</a>
-<a class="github-button" href="https://github.com/freqtrade/freqtrade/archive/stable.zip" data-icon="octicon-cloud-download" data-size="large" aria-label="Download freqtrade/freqtrade on GitHub">Download</a>
+<!-- GitHub action buttons -->
+[:octicons-star-16: Star](https://github.com/freqtrade/freqtrade){ .md-button .md-button--sm }
+[:octicons-repo-forked-16: Fork](https://github.com/freqtrade/freqtrade/fork){ .md-button .md-button--sm }
+[:octicons-download-16: Download](https://github.com/freqtrade/freqtrade/archive/stable.zip){ .md-button .md-button--sm }

 ## Introduction

@@ -31,7 +32,6 @@ Freqtrade is a free and open source crypto trading bot written in Python. It is
 - Optimize: Find the best parameters for your strategy using hyperoptimization which employs machine learning methods. You can optimize buy, sell, take profit (ROI), stop-loss and trailing stop-loss parameters for your strategy.
 - Select markets: Create your static list or use an automatic one based on top traded volumes and/or prices (not available during backtesting). You can also explicitly blacklist markets you don't want to trade.
 - Run: Test your strategy with simulated money (Dry-Run mode) or deploy it with real money (Live-Trade mode).
- Run using Edge (optional module): The concept is to find the best historical [trade expectancy](edge.md#expectancy) by markets based on variation of the stop-loss and then allow/reject markets to trade. The sizing of the trade is based on a risk of a percentage of your capital.
 - Control/Monitor: Use Telegram or a WebUI (start/stop the bot, show profit/loss, daily summary, current open trades results, etc.).
 - Analyze: Further analysis can be performed on either Backtesting data or Freqtrade trading history (SQL database), including automated standard plots, and methods to load the data into [interactive environments](data-analysis.md).

@@ -39,8 +39,11 @@ Freqtrade is a free and open source crypto trading bot written in Python. It is

 Please read the [exchange specific notes](exchanges.md) to learn about eventual, special configurations needed for each exchange.

+### Supported Spot Exchanges
+
 - [X] [Binance](https://www.binance.com/)
 - [X] [BingX](https://bingx.com/invite/0EM9RX)
+- [X] [Bitget](https://www.bitget.com/)
 - [X] [Bitmart](https://bitmart.com/)
 - [X] [Bybit](https://bybit.com/)
 - [X] [Gate.io](https://www.gate.io/ref/6266643)
@@ -51,13 +54,15 @@ Please read the [exchange specific notes](exchanges.md) to learn about eventual,
 - [X] [MyOKX](https://okx.com/) (OKX EEA)
 - [ ] [potentially many others through <img alt="ccxt" width="30px" src="assets/ccxt-logo.svg" />](https://github.com/ccxt/ccxt/). _(We cannot guarantee they will work)_

-### Supported Futures Exchanges (experimental)
+### Supported Futures Exchanges

 - [X] [Binance](https://www.binance.com/)
+- [X] [Bitget](https://www.bitget.com/)
 - [X] [Bybit](https://bybit.com/)
 - [X] [Gate.io](https://www.gate.io/ref/6266643)
 - [X] [Hyperliquid](https://hyperliquid.xyz/) (A decentralized exchange, or DEX)
 - [X] [OKX](https://okx.com/)
+- [X] [Kraken](https://www.kraken.com/features/futures)

 Please make sure to read the [exchange specific notes](exchanges.md), as well as the [trading with leverage](leverage.md) documentation before diving in.

@@ -88,7 +93,7 @@ To run this bot we recommend you a linux cloud instance with a minimum of:

 Alternatively

- Python 3.10+
+- Python 3.11+
 - pip (pip3)
 - git
 - TA-Lib
@@ -9,22 +9,32 @@ The freqtrade documentation describes various ways to install freqtrade
 * [Manual Installation](#manual-installation)
 * [Installation with Conda](#installation-with-conda)

-Please consider using the prebuilt [docker images](docker_quickstart.md) to get started quickly while evaluating how freqtrade works.
+Please consider using the prebuilt [docker images](docker_quickstart.md) to get started quickly.
+
+!!! Note "Updating"
+    Keeping freqtrade updated is important to [ensure ongoing compatibility](updating.md#why-update) with exchange API's.
+    Please refer to the [updating guide](updating.md) for details on how to update your installation.
+
+!!! Note "Windows users"
+    We **strongly** recommend that Windows users use [Docker](docker_quickstart.md) as this will work much easier and smoother (also more secure).
+
+    If that is not possible, try using the Windows Linux subsystem (WSL) - for which the Ubuntu/Linux instructions will work.
+    If you really want to install freqtrade natively on Windows, best use the [`./setup.ps1` installation script](#use-setupps1-windows).
+
+    Please also make sure to use the 64bit version of Python, as 32bit versions have severe memory limitations, which can negatively impact your experience with backtesting/hyperopt.

 ------

 ## Information

-For Windows installation, please use the [windows installation guide](windows_installation.md).
-
-The easiest way to install and run Freqtrade is to clone the bot Github repository and then run the `./setup.sh` script, if it's available for your platform.
+The easiest way to install and run Freqtrade is to clone the bot Github repository and then run the `./setup.sh` (`./setup.ps1` for Windows) script, if it's available for your platform.

 !!! Note "Version considerations"
    When cloning the repository the default working branch has the name `develop`. This branch contains all last features (can be considered as relatively stable, thanks to automated tests).
    The `stable` branch contains the code of the last release (done usually once per month on an approximately one week old snapshot of the `develop` branch to prevent packaging bugs, so potentially it's more stable).

 !!! Note
-    Python3.10 or higher and the corresponding `pip` are assumed to be available. The install-script will warn you and stop if that's not the case. `git` is also needed to clone the Freqtrade repository.  
+    Either [uv](https://docs.astral.sh/uv/), or Python3.11 or higher and the corresponding `pip` are assumed to be available. The install-script will warn you and stop if that's not the case. `git` is also needed to clone the Freqtrade repository.  
    Also, python headers (`python<yourversion>-dev` / `python<yourversion>-devel`) must be available for the installation to complete successfully.

 !!! Warning "Up-to-date clock"
@@ -42,11 +52,10 @@ These requirements apply to both [Script Installation](#script-installation) and

 ### Install guide

-* [Python >= 3.10](http://docs.python-guide.org/en/latest/starting/installation/)
+* [Python >= 3.11](http://docs.python-guide.org/en/latest/starting/installation/)
 * [pip](https://pip.pypa.io/en/stable/installing/)
 * [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
 * [virtualenv](https://virtualenv.pypa.io/en/stable/installation.html) (Recommended)
-* [TA-Lib](https://ta-lib.github.io/ta-lib-python/) (install instructions [below](#install-ta-lib))

 ### Install code

@@ -54,7 +63,7 @@ We've included/collected install instructions for Ubuntu, MacOS, and Windows. Th
 OS Specific steps are listed first, the common section below is necessary for all systems.

 !!! Note
-    Python3.10 or higher and the corresponding pip are assumed to be available.
+    Python3.11 or higher and the corresponding pip are assumed to be available.

 === "Debian/Ubuntu"
    #### Install necessary dependencies
@@ -153,20 +162,9 @@ If you are on Debian, Ubuntu or MacOS, freqtrade provides the script to install
 ./setup.sh -i
 ```

-### Activate your virtual environment
+#### Other options of /setup.sh script

-Each time you open a new terminal, you must run `source .venv/bin/activate` to activate your virtual environment.
-
-```bash
-# activate virtual environment
-source ./.venv/bin/activate
-```
-
-[You are now ready](#you-are-ready) to run the bot.
-
-### Other options of /setup.sh script
-
-You can as well update, configure and reset the codebase of your bot with `./script.sh`
+You can also update, configure and reset the codebase of your bot with `./setup.sh`

 ```bash
 # --update, Command git pull to update.
@@ -179,7 +177,7 @@ You can as well update, configure and reset the codebase of your bot with `./scr
 ** --install **

 With this option, the script will install the bot and most dependencies:
-You will need to have git and python3.10+ installed beforehand for this to work.
+You will need to have git and python3.11+ installed beforehand for this to work.

 * Mandatory software as: `ta-lib`
 * Setup your virtualenv under `.venv/`
@@ -195,41 +193,40 @@ This option will pull the last version of your current branch and update your vi
 This option will hard reset your branch (only if you are on either `stable` or `develop`) and recreate your virtualenv.
 ```

+#### Activate your virtual environment
+
+Each time you open a new terminal, you must run `source .venv/bin/activate` to activate your virtual environment.
+
+```bash
+# activate virtual environment
+source ./.venv/bin/activate
+```
+
+### Use ./setup.ps1 (Windows)
+
+The script will ask you a few questions to determine which parts should be installed.
+
+```powershell
+Set-ExecutionPolicy -ExecutionPolicy Bypass
+cd freqtrade
+. .\setup.ps1
+```
+
+#### Activate your virtual environment (Windows)
+
+```powershell
+# activate virtual environment
+. .\.venv\Scripts\Activate.ps1
+```
+
+[You are now ready](#you-are-ready) to run the bot.
+
 -----

 ## Manual Installation

 Make sure you fulfill the [Requirements](#requirements) and have downloaded the [Freqtrade repository](#freqtrade-repository).

-### Install TA-Lib
-
-#### TA-Lib script installation
-
-```bash
-sudo ./build_helpers/install_ta-lib.sh
-```
-
-!!! Note
-    This will use the ta-lib tar.gz included in this repository.
-
-##### TA-Lib manual installation
-
-[Official installation guide](https://ta-lib.github.io/ta-lib-python/install.html)
-
-```bash
-wget http://prdownloads.sourceforge.net/ta-lib/ta-lib-0.4.0-src.tar.gz
-tar xvzf ta-lib-0.4.0-src.tar.gz
-cd ta-lib
-sed -i.bak "s|0.00000001|0.000000000000000001 |g" src/ta_func/ta_utility.h
-./configure --prefix=/usr/local
-make
-sudo make install
-# On debian based systems (debian, ubuntu, ...) - updating ldconfig might be necessary.
-sudo ldconfig  
-cd ..
-rm -rf ./ta-lib*
-```
-
 ### Setup Python virtual environment (virtualenv)

 You will run freqtrade in separated `virtual environment`
@@ -332,16 +329,6 @@ python3 -m pip install -r requirements.txt
 python3 -m pip install -e .
 ```

-Patch conda libta-lib (Linux only)
-
-```bash
-# Ensure that the environment is active!
-conda activate freqtrade
-
-cd build_helpers
-bash install_ta-lib.sh ${CONDA_PREFIX} nosudo
-```
-
 [You are now ready](#you-are-ready) to run the bot.

 ### Important shortcuts
@@ -377,7 +364,7 @@ conda deactivate

 Happy trading!

-----
+------

 ## You are ready

@@ -434,3 +421,15 @@ open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10
 ```

 If this file is inexistent, then you're probably on a different version of MacOS, so you may need to consult the internet for specific resolution details.
+
+### Windows Installation error
+
+```bash
+error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": http://landinghub.visualstudio.com/visual-cpp-build-tools
+```
+
+Unfortunately, many packages requiring compilation don't provide a pre-built wheel. It is therefore mandatory to have a C/C++ compiler installed and available for your python environment to use.
+
+You can download the Visual C++ build tools from [the Visual Studio website](https://visualstudio.microsoft.com/visual-cpp-build-tools/) and install "Desktop development with C++" in it's default configuration. Unfortunately, this is a heavy download / dependency so you might want to consider WSL2 or [docker compose](docker_quickstart.md) first.
+
+![Windows installation](assets/windows_install.png)
--- a/Show More
+++ b/Show More