Skip to main content

A high-performance algorithmic trading platform and event-driven backtester

Project description

codecov codspeed pythons pypi-version pypi-format Downloads Discord

Branch Version Status
master version build
nightly version build
develop version build
Platform Rust Python
Linux (x86_64) 1.86.0+ 3.11-3.13
Linux (ARM64) 1.86.0+ 3.11-3.13
macOS (ARM64) 1.86.0+ 3.11-3.13
Windows (x86_64) 1.86.0+ 3.11-3.13

Introduction

NautilusTrader is an open-source, high-performance, production-grade algorithmic trading platform, providing quantitative traders with the ability to backtest portfolios of automated trading strategies on historical data with an event-driven engine, and also deploy those same strategies live, with no code changes.

The platform is AI-first, designed to develop and deploy algorithmic trading strategies within a highly performant and robust Python-native environment. This helps to address the parity challenge of keeping the Python research/backtest environment consistent with the production live trading environment.

NautilusTrader's design, architecture, and implementation philosophy prioritizes software correctness and safety at the highest level, with the aim of supporting Python-native, mission-critical, trading system backtesting and live deployment workloads.

The platform is also universal, and asset-class-agnostic — with any REST API or WebSocket feed able to be integrated via modular adapters. It supports high-frequency trading across a wide range of asset classes and instrument types including FX, Equities, Futures, Options, Crypto and Betting, enabling seamless operations across multiple venues simultaneously.

nautilus-trader

Features

  • Fast: Core is written in Rust with asynchronous networking using tokio.
  • Reliable: Type safety and thread safety through Rust. Redis-backed performant state persistence (optional).
  • Portable: OS independent, runs on Linux, macOS, and Windows. Deploy using Docker.
  • Flexible: Modular adapters mean any REST API or WebSocket feed can be integrated.
  • Advanced: Time in force IOC, FOK, GTC, GTD, DAY, AT_THE_OPEN, AT_THE_CLOSE, advanced order types and conditional triggers. Execution instructions post-only, reduce-only, and icebergs. Contingency orders including OCO, OUO, OTO.
  • Customizable: Add user-defined custom components, or assemble entire systems from scratch leveraging the cache and message bus.
  • Backtesting: Run with multiple venues, instruments and strategies simultaneously using historical quote tick, trade tick, bar, order book and custom data with nanosecond resolution.
  • Live: Use identical strategy implementations between backtesting and live deployments.
  • Multi-venue: Multiple venue capabilities facilitate market-making and statistical arbitrage strategies.
  • AI Training: Backtest engine fast enough to be used to train AI trading agents (RL/ES).

Alt text

nautilus - from ancient Greek 'sailor' and naus 'ship'.

The nautilus shell consists of modular chambers with a growth factor which approximates a logarithmic spiral. The idea is that this can be translated to the aesthetics of design and architecture.

Why NautilusTrader?

  • Highly performant event-driven Python: Native binary core components.
  • Parity between backtesting and live trading: Identical strategy code.
  • Reduced operational risk: Enhanced risk management functionality, logical accuracy, and type safety.
  • Highly extendable: Message bus, custom components and actors, custom data, custom adapters.

Traditionally, trading strategy research and backtesting might be conducted in Python using vectorized methods, with the strategy then needing to be reimplemented in a more event-driven way using C++, C#, Java or other statically typed language(s). The reasoning here is that vectorized backtesting code cannot express the granular time and event dependent complexity of real-time trading, where compiled languages have proven to be more suitable due to their inherently higher performance, and type safety.

One of the key advantages of NautilusTrader here, is that this reimplementation step is now circumvented - as the critical core components of the platform have all been written entirely in Rust or Cython. This means we're using the right tools for the job, where systems programming languages compile performant binaries, with CPython C extension modules then able to offer a Python-native environment, suitable for professional quantitative traders and trading firms.

Why Python?

Python was originally created decades ago as a simple scripting language with a clean straightforward syntax. It has since evolved into a fully fledged general purpose object-oriented programming language. Based on the TIOBE index, Python is currently the most popular programming language in the world. Not only that, Python has become the de facto lingua franca of data science, machine learning, and artificial intelligence.

The language out of the box is not without its drawbacks however, especially in the context of implementing large performance-critical systems. Cython has addressed a lot of these issues, offering all the advantages of a statically typed language, embedded into Python's rich ecosystem of software libraries and developer/user communities.

What is Rust?

Rust is a multi-paradigm programming language designed for performance and safety, especially safe concurrency. Rust is "blazingly fast" and memory-efficient (comparable to C and C++) with no garbage collector. It can power mission-critical systems, run on embedded devices, and easily integrates with other languages.

Rust’s rich type system and ownership model guarantees memory-safety and thread-safety deterministically — eliminating many classes of bugs at compile-time.

The project increasingly utilizes Rust for core performance-critical components. Python language binding is handled through Cython and PyO3, with static libraries linked at compile-time before the wheel binaries are packaged, so a user does not need to have Rust installed to run NautilusTrader.

This project makes the Soundness Pledge:

“The intent of this project is to be free of soundness bugs. The developers will do their best to avoid them, and welcome help in analyzing and fixing them.”

[!NOTE]

MSRV: NautilusTrader relies heavily on improvements in the Rust language and compiler. As a result, the Minimum Supported Rust Version (MSRV) is generally equal to the latest stable release of Rust.

Integrations

NautilusTrader is modularly designed to work with adapters, enabling connectivity to trading venues and data providers by translating their raw APIs into a unified interface and normalized domain model.

The following integrations are currently supported:

Name ID Type Status Docs
Betfair BETFAIR Sports Betting Exchange status Guide
Binance BINANCE Crypto Exchange (CEX) status Guide
Binance US BINANCE Crypto Exchange (CEX) status Guide
Binance Futures BINANCE Crypto Exchange (CEX) status Guide
Bybit BYBIT Crypto Exchange (CEX) status Guide
Coinbase International COINBASE_INTX Crypto Exchange (CEX) status Guide
Databento DATABENTO Data Provider status Guide
dYdX DYDX Crypto Exchange (DEX) status Guide
Interactive Brokers INTERACTIVE_BROKERS Brokerage (multi-venue) status Guide
OKX OKX Crypto Exchange (CEX) status Guide
Polymarket POLYMARKET Prediction Market (DEX) status Guide
Tardis TARDIS Crypto Data Provider status Guide
  • ID: The default client ID for the integrations adapter clients.
  • Type: The type of integration (often the venue type).

Status

  • building: Under construction and likely not in a usable state.
  • beta: Completed to a minimally working state and in a beta testing phase.
  • stable: Stabilized feature set and API, the integration has been tested by both developers and users to a reasonable level (some bugs may still remain).

See the Integrations documentation for further details.

Versioning and releases

NautilusTrader is still under active development. Some features may be incomplete, and while the API is becoming more stable, breaking changes can occur between releases. We strive to document these changes in the release notes on a best-effort basis.

We aim to follow a bi-weekly release schedule, though experimental or larger features may cause delays.

Branches

We aim to maintain a stable, passing build across all branches.

  • master: Reflects the source code for the latest released version.
  • nightly: Includes experimental and in-progress features, merged from the develop branch daily at 14:00 UTC and also when required.
  • develop: The most active branch, frequently updated with new commits, including experimental and in-progress features.

[!NOTE]

Our roadmap aims to achieve a stable API for version 2.x (likely after the Rust port). Once this milestone is reached, we plan to implement a formal deprecation process for any API changes. This approach allows us to maintain a rapid development pace for now.

Precision mode

NautilusTrader supports two precision modes for its core value types (Price, Quantity, Money), which differ in their internal bit-width and maximum decimal precision.

  • High-precision: 128-bit integers with up to 16 decimals of precision, and a larger value range.
  • Standard-precision: 64-bit integers with up to 9 decimals of precision, and a smaller value range.

[!NOTE]

By default, the official Python wheels ship in high-precision (128-bit) mode on Linux and macOS. On Windows, only standard-precision (64-bit) is available due to the lack of native 128-bit integer support. For the Rust crates, the default is standard-precision unless you explicitly enable the high-precision feature flag.

See the Installation Guide for further details.

Installation

From PyPI

We recommend using the latest supported version of Python and setting up nautilus_trader in a virtual environment to isolate dependencies.

To install the latest binary wheel (or sdist package) from PyPI using Python's pip package manager:

pip install -U nautilus_trader

From the Nautech Systems package index

The Nautech Systems package index (packages.nautechsystems.io) is PEP-503 compliant and hosts both stable and development binary wheels for nautilus_trader. This enables users to install either the latest stable release or pre-release versions for testing.

Stable wheels

Stable wheels correspond to official releases of nautilus_trader on PyPI, and use standard versioning.

To install the latest stable release:

pip install -U nautilus_trader --index-url=https://packages.nautechsystems.io/simple

Development wheels

Development wheels are published from both the nightly and develop branches, allowing users to test features and fixes ahead of stable releases.

Note: Wheels from the develop branch are only built for the Linux x86_64 platform to save time and compute resources, while nightly wheels support additional platforms as shown below.

Platform Nightly Develop
Linux (x86_64)
Linux (ARM64) -
macOS (ARM64) -
Windows (x86_64) -

This process also helps preserve compute resources and ensures easy access to the exact binaries tested in CI pipelines, while adhering to PEP-440 versioning standards:

  • develop wheels use the version format dev{date}+{build_number} (e.g., 1.208.0.dev20241212+7001).
  • nightly wheels use the version format a{date} (alpha) (e.g., 1.208.0a20241212).

[!WARNING]

We don't recommend using development wheels in production environments, such as live trading controlling real capital.

Installation commands

By default, pip installs the latest stable release. Adding the --pre flag ensures that pre-release versions, including development wheels, are considered.

To install the latest available pre-release (including development wheels):

pip install -U nautilus_trader --pre --index-url=https://packages.nautechsystems.io/simple

To install a specific development wheel (e.g., 1.208.0a20241212 for December 12, 2024):

pip install nautilus_trader==1.208.0a20241212 --index-url=https://packages.nautechsystems.io/simple

Available versions

You can view all available versions of nautilus_trader on the package index.

To programmatically fetch and list available versions:

curl -s https://packages.nautechsystems.io/simple/nautilus-trader/index.html | grep -oP '(?<=<a href=")[^"]+(?=")' | awk -F'#' '{print $1}' | sort

Branch updates

  • develop branch wheels (.dev): Are built and published continuously with every merged commit.
  • nightly branch wheels (a): Are built and published daily when develop branch is automatically merged at 14:00 UTC (if there are changes).

Retention policies

  • develop branch wheels (.dev): Only the most recent wheel build is retained.
  • nightly branch wheels (a): Only the 10 most recent wheel builds are retained.

From Source

It's possible to install from source using pip if you first install the build dependencies as specified in the pyproject.toml. We highly recommend installing using uv as below.

  1. Install rustup (the Rust toolchain installer):

    • Linux and macOS:
      curl https://sh.rustup.rs -sSf | sh
      
    • Windows:
    • Verify (any system): from a terminal session run: rustc --version
  2. Enable cargo in the current shell:

    • Linux and macOS:
      source $HOME/.cargo/env
      
    • Windows:
      • Start a new PowerShell
  3. Install clang (a C language frontend for LLVM):

    • Linux:
      sudo apt-get install clang
      
    • Windows:
      1. Add Clang to your Build Tools for Visual Studio 2019:
        • Start | Visual Studio Installer | Modify | C++ Clang tools for Windows (12.0.0 - x64…) = checked | Modify
      2. Enable clang in the current shell:
        [System.Environment]::SetEnvironmentVariable('path', "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\Llvm\x64\bin\;" + $env:Path,"User")
        
    • Verify (any system): from a terminal session run: clang --version
  4. Install uv (see the uv installation guide for more details):

    curl -LsSf https://astral.sh/uv/install.sh | sh
    
  5. Clone the source with git, and install from the project's root directory:

    git clone --branch develop --depth 1 https://github.com/nautechsystems/nautilus_trader
    cd nautilus_trader
    uv sync --all-extras
    

[!NOTE]

The --depth 1 flag fetches just the latest commit for a faster, lightweight clone.

See the Installation Guide for other options and further details.

Redis

Using Redis with NautilusTrader is optional and only required if configured as the backend for a cache database or message bus. See the Redis section of the Installation Guide for further details.

Makefile

A Makefile is provided to automate most installation and build tasks for development. It provides the following targets:

  • make install: Installs in release build mode with all dependency groups and extras.
  • make install-debug: Same as make install but with debug build mode.
  • make install-just-deps: Installs just the main, dev and test dependencies (does not install package).
  • make build: Runs the build script in release build mode (default).
  • make build-debug: Runs the build script in debug build mode.
  • make build-wheel: Runs uv build with a wheel format in release mode.
  • make build-wheel-debug: Runs uv build with a wheel format in debug mode.
  • make clean: Deletes all build results, such as .so or .dll files.
  • make distclean: CAUTION Removes all artifacts not in the git index from the repository. This includes source files which have not been git added.
  • make docs: Builds the documentation HTML using Sphinx.
  • make pre-commit: Runs the pre-commit checks over all files.
  • make ruff: Runs ruff over all files using the pyproject.toml config (with autofix).
  • make pytest: Runs all tests with pytest.
  • make test-performance: Runs performance tests with codspeed.

[!TIP]

Run make build-debug to compile after changes to Rust or Cython code for the most efficient development workflow.

Examples

Indicators and strategies can be developed in both Python and Cython. For performance and latency-sensitive applications, we recommend using Cython. Below are some examples:

Docker

Docker containers are built using the base image python:3.12-slim with the following variant tags:

  • nautilus_trader:latest has the latest release version installed.
  • nautilus_trader:nightly has the head of the nightly branch installed.
  • jupyterlab:latest has the latest release version installed along with jupyterlab and an example backtest notebook with accompanying data.
  • jupyterlab:nightly has the head of the nightly branch installed along with jupyterlab and an example backtest notebook with accompanying data.

You can pull the container images as follows:

docker pull ghcr.io/nautechsystems/<image_variant_tag> --platform linux/amd64

You can launch the backtest example container by running:

docker pull ghcr.io/nautechsystems/jupyterlab:nightly --platform linux/amd64
docker run -p 8888:8888 ghcr.io/nautechsystems/jupyterlab:nightly

Then open your browser at the following address:

http://127.0.0.1:8888/lab

[!WARNING]

NautilusTrader currently exceeds the rate limit for Jupyter notebook logging (stdout output). As a result, the log_level in the examples is set to ERROR. Lowering this level to see more logging will cause the notebook to hang during cell execution. We are investigating a fix, which may involve either raising the configured rate limits for Jupyter or throttling the log flushing from Nautilus.

Development

We aim to provide the most pleasant developer experience possible for this hybrid codebase of Python, Cython and Rust. See the Developer Guide for helpful information.

Testing with Rust

cargo-nextest is the standard Rust test runner for NautilusTrader. Its key benefit is isolating each test in its own process, ensuring test reliability by avoiding interference.

You can install cargo-nextest by running:

cargo install cargo-nextest

[!TIP]

Run Rust tests with make cargo-test, which uses cargo-nextest with an efficient profile.

Contributing

Thank you for considering contributing to NautilusTrader! We welcome any and all help to improve the project. If you have an idea for an enhancement or a bug fix, the first step is to open an issue on GitHub to discuss it with the team. This helps to ensure that your contribution will be well-aligned with the goals of the project and avoids duplication of effort.

Once you're ready to start working on your contribution, make sure to follow the guidelines outlined in the CONTRIBUTING.md file. This includes signing a Contributor License Agreement (CLA) to ensure that your contributions can be included in the project.

[!NOTE]

Pull requests should target the develop branch (the default branch). This is where new features and improvements are integrated before release.

Thank you again for your interest in NautilusTrader! We look forward to reviewing your contributions and working with you to improve the project.

Community

Join our community of users and contributors on Discord to chat and stay up-to-date with the latest announcements and features of NautilusTrader. Whether you're a developer looking to contribute or just want to learn more about the platform, all are welcome on our Discord server.

[!WARNING]

NautilusTrader does not issue, promote, or endorse any cryptocurrency tokens. Any claims or communications suggesting otherwise are unauthorized and false.

All official updates and communications from NautilusTrader will be shared exclusively through https://nautilustrader.io, our Discord server, or our X (Twitter) account: @NautilusTrader.

If you encounter any suspicious activity, please report it to the appropriate platform and contact us at info@nautechsystems.io.

License

The source code for NautilusTrader is available on GitHub under the GNU Lesser General Public License v3.0. Contributions to the project are welcome and require the completion of a standard Contributor License Agreement (CLA).


NautilusTrader™ is developed and maintained by Nautech Systems, a technology company specializing in the development of high-performance trading systems. For more information, visit https://nautilustrader.io.

© 2015-2025 Nautech Systems Pty Ltd. All rights reserved.

nautechsystems

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

nautilus_trader-1.216.0.tar.gz (2.0 MB view details)

Uploaded Source

Built Distributions

nautilus_trader-1.216.0-cp313-cp313-win_amd64.whl (37.0 MB view details)

Uploaded CPython 3.13 Windows x86-64

nautilus_trader-1.216.0-cp313-cp313-manylinux_2_35_x86_64.whl (72.7 MB view details)

Uploaded CPython 3.13 manylinux: glibc 2.35+ x86-64

nautilus_trader-1.216.0-cp313-cp313-manylinux_2_35_aarch64.whl (67.8 MB view details)

Uploaded CPython 3.13 manylinux: glibc 2.35+ ARM64

nautilus_trader-1.216.0-cp313-cp313-macosx_14_0_arm64.whl (65.3 MB view details)

Uploaded CPython 3.13 macOS 14.0+ ARM64

nautilus_trader-1.216.0-cp312-cp312-win_amd64.whl (37.0 MB view details)

Uploaded CPython 3.12 Windows x86-64

nautilus_trader-1.216.0-cp312-cp312-manylinux_2_35_x86_64.whl (72.8 MB view details)

Uploaded CPython 3.12 manylinux: glibc 2.35+ x86-64

nautilus_trader-1.216.0-cp312-cp312-manylinux_2_35_aarch64.whl (67.8 MB view details)

Uploaded CPython 3.12 manylinux: glibc 2.35+ ARM64

nautilus_trader-1.216.0-cp312-cp312-macosx_14_0_arm64.whl (65.2 MB view details)

Uploaded CPython 3.12 macOS 14.0+ ARM64

nautilus_trader-1.216.0-cp311-cp311-win_amd64.whl (37.0 MB view details)

Uploaded CPython 3.11 Windows x86-64

nautilus_trader-1.216.0-cp311-cp311-manylinux_2_35_x86_64.whl (73.3 MB view details)

Uploaded CPython 3.11 manylinux: glibc 2.35+ x86-64

nautilus_trader-1.216.0-cp311-cp311-manylinux_2_35_aarch64.whl (68.0 MB view details)

Uploaded CPython 3.11 manylinux: glibc 2.35+ ARM64

nautilus_trader-1.216.0-cp311-cp311-macosx_14_0_arm64.whl (65.3 MB view details)

Uploaded CPython 3.11 macOS 14.0+ ARM64

File details

Details for the file nautilus_trader-1.216.0.tar.gz.

File metadata

  • Download URL: nautilus_trader-1.216.0.tar.gz
  • Upload date:
  • Size: 2.0 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.6.14

File hashes

Hashes for nautilus_trader-1.216.0.tar.gz
Algorithm Hash digest
SHA256 430e45073e813eef0f40a830c2138054a8640fe8b1512eb3c6fedf5be6f9fba8
MD5 58150856d831725f0c19d9bdf95bf494
BLAKE2b-256 2baae665433c26a2799d89b249ea2f5bc9c5177cf9e9609c283eab0c871b8908

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp313-cp313-win_amd64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp313-cp313-win_amd64.whl
Algorithm Hash digest
SHA256 9487889e680b36d6f4edbaf8b56aae9582bced628abf0696dc961d457231ebe8
MD5 73e5f5769585b158b3a4ed33f780f68d
BLAKE2b-256 461300301a25767ea9ef48a9c21b98a59524be612b14707c042d33351527c831

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp313-cp313-manylinux_2_35_x86_64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp313-cp313-manylinux_2_35_x86_64.whl
Algorithm Hash digest
SHA256 788f7c36c1964a32e625b8806590832049371256eb69fed59c5f9aa7e4070971
MD5 3e77f49c06b91cafbbc8dd2463f931aa
BLAKE2b-256 173fad2ad198b69424593cb374c15050fb81f61e6051b73bceb31671ce89414e

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp313-cp313-manylinux_2_35_aarch64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp313-cp313-manylinux_2_35_aarch64.whl
Algorithm Hash digest
SHA256 15d35506ef51732ad8f95da4735fb0d150da16500233149bc2d9cbe58f0df4e0
MD5 4839cb0d97e3ecc8665a90294ebcd94a
BLAKE2b-256 31bb9936a68f797492153635b7a8acdcb2c5bfc2ef8dc116476c6716f3c818be

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp313-cp313-macosx_14_0_arm64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp313-cp313-macosx_14_0_arm64.whl
Algorithm Hash digest
SHA256 811fabbb2b7a180c03c2a8ba8485433a78b075ad22f6a4576f036026a8f81c41
MD5 05d7b6d6539f44cde6029f690a736db5
BLAKE2b-256 e3273c418c4f13d45fefa391eb4be55292747f9e702e89db5418341fd6e5cba0

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp312-cp312-win_amd64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp312-cp312-win_amd64.whl
Algorithm Hash digest
SHA256 6106e74768a6cdb77bb34b4a12c9a1cfd154631754443342be5488d799b70b1d
MD5 89ffd4a15b8fbc54f27448e5a062b650
BLAKE2b-256 756d92badfb7f7bfca7acdcb23d16751042be286ab34238727be67d86a9a9da1

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp312-cp312-manylinux_2_35_x86_64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp312-cp312-manylinux_2_35_x86_64.whl
Algorithm Hash digest
SHA256 2880bb1031990a4e97e46853a60b8054e352cf5089faf82741c13f2a82dd2a3a
MD5 dab1911b919538d228348fce18158225
BLAKE2b-256 5cf14b611c8ab1d1be0990c7062c75f336a87fde1f2ed6c686dccd0a0118f2da

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp312-cp312-manylinux_2_35_aarch64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp312-cp312-manylinux_2_35_aarch64.whl
Algorithm Hash digest
SHA256 13440844b5c44c5e4b4b14886bf5f31deabefe74f364b9277526ef714e8adb81
MD5 c33c9d00f410555d34c2a5ae5bf124e3
BLAKE2b-256 18b243c7482e8d43bfcda5309d1a5cbf8b46eef266cff2908c40f9f01f740b8c

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp312-cp312-macosx_14_0_arm64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp312-cp312-macosx_14_0_arm64.whl
Algorithm Hash digest
SHA256 c305f4ce5befbdffae8cebf7be2e54dbeb34446073932a5ef6d9fa36b554a1bf
MD5 64140c8a85cec7820a1075f1a3741331
BLAKE2b-256 33cb8df0058516f58210b52802525a247b69e33baf1822b655801ff5b5c7ee2e

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp311-cp311-win_amd64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp311-cp311-win_amd64.whl
Algorithm Hash digest
SHA256 877469a74c67364db65b1361e87f71f34f2ff1fc1733f421159034a4f70975c8
MD5 e8d9a1ae27f9e0a52c13a894bc71426b
BLAKE2b-256 49d20a8a7d8153a279066d2e55f20700776073bf4281c0144091cf67b9c7ac08

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp311-cp311-manylinux_2_35_x86_64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp311-cp311-manylinux_2_35_x86_64.whl
Algorithm Hash digest
SHA256 f258205d02da4a340cc297bd17125da709df3aad2cfbb5776f015cfff24a5398
MD5 f8d026fbcc85bf2aa5e85acec4c2786d
BLAKE2b-256 603e59daac17cbe38b8c55f3b5f4652cb185bcfbfad8d29ae2d9fc0a41e678b4

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp311-cp311-manylinux_2_35_aarch64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp311-cp311-manylinux_2_35_aarch64.whl
Algorithm Hash digest
SHA256 abc0dfa6bf5b013265e933225cdfc95eac0c6cb59dbbb1b16782049665632858
MD5 9a49fc47aa8a0c9d4f97cd070689d5d8
BLAKE2b-256 d93ab091ac7baeabf7d00c8cc3079726647b67f995739d862ade2ed963b476a4

See more details on using hashes here.

File details

Details for the file nautilus_trader-1.216.0-cp311-cp311-macosx_14_0_arm64.whl.

File metadata

File hashes

Hashes for nautilus_trader-1.216.0-cp311-cp311-macosx_14_0_arm64.whl
Algorithm Hash digest
SHA256 738b7ffa0e4ec0bcca7e41214f93ad744773e1c6a0ed24331a8a4738346c43ef
MD5 0560ff7833cb4117624da4555c9e6b0c
BLAKE2b-256 3ba75e87385e7ca981e5980fb0fb11b1057caec0911dbbacc9cb48aa549714e5

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page