Cryptocurrency Exchange Feed Handler
Handles multiple cryptocurrency exchange data feeds and returns normalized and standardized results to client registered callbacks for events like trades, book updates, ticker updates, etc. Utilizes websockets when possible, but can also poll data via REST endpoints if a websocket is not provided.
Supported exchanges
- Bitfinex
- bitFlyer
- Bithumb
- Bitstamp
- Bybit
- Binance
- Binance Delivery
- Binance Futures
- Binance US
- Bitget
- Coinbase
- Crypto.com
- Deribit
- Gate
- Gate Futures
- dYdX v4
- Gemini
- Hyperliquid
- HTX (formerly Huobi)
- HTX Swap (Coin-M and USDT-M)
- Independent Reserve
- Kraken
- MEXC (spot)
- Kraken Futures
- KuCoin
- OKX
- Phemex
- Poloniex
- Upbit
Basic Usage
Create a FeedHandler object and add subscriptions. For the various data channels that an exchange supports, you can supply callbacks for data events, or use provided backends (described below) to handle the data for you. Start the feed handler and you're done!
from cryptofeed import FeedHandler
# not all imports shown for clarity
fh = FeedHandler()
# ticker, trade and book are user defined coroutine functions, each taking the
# normalized object and the timestamp cryptofeed received the message at:
#
# async def trade(t, receipt_timestamp):
# print(f'{t.exchange} {t.symbol} {t.side} {t.amount} @ {t.price}')
#
# a callback must be async - wrap a synchronous one in cryptofeed.callback.ExecutorCallback
ticker_cb = {TICKER: ticker}
trade_cb = {TRADES: trade}
gemini_cb = {TRADES: trade, L2_BOOK: book}
fh.add_feed(Coinbase(symbols=['BTC-USD'], channels=[TICKER], callbacks=ticker_cb))
fh.add_feed(Bitfinex(symbols=['BTC-USD'], channels=[TICKER], callbacks=ticker_cb))
fh.add_feed(Poloniex(symbols=['BTC-USDT'], channels=[TRADES], callbacks=trade_cb))
fh.add_feed(Gemini(symbols=['BTC-USD', 'ETH-USD'], channels=[TRADES, L2_BOOK], callbacks=gemini_cb))
fh.run()
National Best Bid/Offer (NBBO)
Cryptofeed also provides a synthetic NBBO (National Best Bid/Offer) feed that aggregates the best bids and asks from the user specified feeds.
from cryptofeed import FeedHandler
from cryptofeed.exchanges import Coinbase, Gemini, Kraken
async def nbbo_update(symbol, bid, bid_size, ask, ask_size, bid_feed, ask_feed):
print(f'Pair: {symbol} Bid Price: {bid:.2f} Bid Size: {bid_size:.6f} Bid Feed: {bid_feed} Ask Price: {ask:.2f} Ask Size: {ask_size:.6f} Ask Feed: {ask_feed}')
def main():
f = FeedHandler()
f.add_nbbo([Coinbase, Kraken, Gemini], ['BTC-USD'], nbbo_update)
f.run()
Supported Channels
Cryptofeed supports the following public data channels from exchanges
- L1_BOOK - Top of book
- L2_BOOK - Price aggregated sizes. Some exchanges provide the entire depth, some provide a subset.
- L3_BOOK - Price aggregated orders. Like the L2 book, some exchanges may only provide partial depth.
- TRADES - Note this reports the taker's side, even for exchanges that report the maker side.
- TICKER
- FUNDING
- OPEN_INTEREST - Open interest data.
- LIQUIDATIONS
- INDEX
- CANDLES - Candlestick / K-Line data.
Normalized data
Every callback receives two arguments: a normalized object and receipt_timestamp, the time (float epoch seconds)
cryptofeed received the message that produced the callback. The objects are defined in cryptofeed/types.pyx (Trade,
Ticker, OrderBook, L1Book, Candle, Funding, OpenInterest, Liquidation, Index) and share these rules:
exchangeis the venue id andsymbolthe normalized name:BASE-QUOTEfor spot,BASE-QUOTE-PERPfor perpetuals,BASE-QUOTE-<expiry>for dated futures with the expiry as a two-digit year, a futures month code and a zero-padded day (BTC-USD-26H05), andBASE-QUOTE-<strike>-<expiry>-CALL|PUTfor options.- Prices, sizes, rates and volumes are
Decimal.numeric_typeon a backend orto_dict()converts them. timestampis the venue's event time in float epoch seconds.timestampisNonewhen the venue does not provide a timestamp and backends then store the receipt time in its place.Trade.sideis the taker's side.Trade.idis the venue's id orNone.OrderBook.bookholds the full local book (.bids,.asks).deltaisNonefor a snapshot and otherwise lists the levels that changed as(price, size)with size 0 for a removed level.sequence_numberandchecksumare set when the venue provides them.Candle.closedisTrueonce the bar is final, by default only closed candles are delivered. (candle_closed_only=Falsealso delivers each update of the open bar).trade_history,candle_historyandliquidation_historycontrol whether the batch of recent trades, candles or liquidations some venues send on subscribe is delivered, by default it isFalse.
Backends
Cryptofeed supports backend callbacks that will write directly to storage or other interfaces.
Supported Backends:
- Redis (Sorted Sets, Streams and Keys)
- ZeroMQ
- UDP Sockets
- TCP Sockets
- Unix Domain Sockets
- InfluxDB v2
- MongoDB
- Kafka
- PostgreSQL
- QuestDB
- ClickHouse
Data Capture and Replay
Cryptofeed can record data from data feeds to standard pcap files for later replay
from cryptofeed import FeedHandler
# `record` is a pcap file path or a directory
fh = FeedHandler(record='sample_data/')
fh.add_feed('COINBASE', symbols=['BTC-USD'], channels=[TRADES, L2_BOOK], callbacks=...)
fh.run()
examples/record.py wraps this into a small recording tool. The pcaps are zstandaard compressed by default. Wireshark and tshark open these files natively and playback decompresses transparently. Metadata is stored in .meta.json.
Installation
Note: cryptofeed requires Python 3.13+
Cryptofeed can be installed from PyPi. (It's recommended that you install in a virtual environment of your choosing).
pip install cryptofeed
Cryptofeed has optional dependencies, depending on the backends used. You can install them individually, or all at once. To install Cryptofeed along with all its optional dependencies in one bundle:
pip install cryptofeed[all]
If you wish to clone the repository and work on it (development uses uv), run this from the root of the cloned repository:
uv sync
Alternatively, you can install from source in editable mode with pip:
pip install -e .
Performance
Measured on Python 3.14.6 based on throughput over real recorded exchange traffic.
| Operation | Result |
|---|---|
Trade construct / to_dict / from_dict |
102 ns / 214 ns / 277 ns |
Ticker / Candle / Funding construct |
70 ns / 118 ns / 141 ns |
| Book single level update / delete / top-of-book read | 89 ns / 124 ns / 140 ns |
Book to_dict, 10 / 100 levels per side |
2.4 µs / 22.2 µs |
| Checksum, Kraken / OKX format (200 levels) | 2.0 µs / 6.1 µs |
JSON decode with Decimal (msgspec / stdlib fallback) |
1.39M / 0.60M msg/s |
| JSON encode to str / bytes | 4.65M / 5.25M msg/s |
| Message handler, Kraken / Bybit / KuCoin / Kraken Futures | 161k / 134k / 122k / ~100k frames/s |
Future Work
There are a lot of planned features, new exchanges, etc planned! If you'd like to discuss ongoing development, please join the discord or open a thread in the discussions in GitHub.
Contributing
Issues and PRs are welcomed!
Cryptofeed wouldn't be possible without the help of many contributors! I owe them and all other contributors my thanks!
Donations / Support
Support and donations are appreciated but not required. You can donate via GitHub Sponsors, or via the addresses below:
- Bitcoin: bc1qm0kxz8hqacaglku5fjhfe9a5hjnuyfwk02lsyr
- Ethereum: 0x690709FEe13eEce9E7852089BB2D53Ae5D073154
1 maintainer
Metadata
1 maintainer
Release files for cryptofeed 3.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cryptofeed-3.0.4.tar.gz | 169.6 kB | With provenance | Details for cryptofeed-3.0.4.tar.gz |
Built distributions (wheels)
Total release size: 17.6 MB
Release files / cryptofeed-3.0.4.tar.gz
| Download URL | cryptofeed-3.0.4.tar.gz |
|---|---|
| Size | 169.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34843428912dbfe6af6e1a353b5e2f34f45a85d51d2256a48e6a4dd3d035e69a
|
|
BLAKE2b-256 checksum How to use checksums |
e092e0d435fe1c52272c8e1728d373a167efd269f42cfaa511140cff09924797
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315t-win_arm64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315t-win_arm64.whl |
|---|---|
| Size | 301.7 kB |
| Tags | CPython 3.15 CPython 3.15 free-threading Windows ARM64 |
|
SHA-256 checksum How to use checksums |
9d4131709359a4456d7236a288e7f8bc47c89d4a21be765da236d47bc35103dd
|
|
BLAKE2b-256 checksum How to use checksums |
189a26f1d55b8ecd8d0a787612fc020b319acc65ebbdb36756d5ceaac6aaa90f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315t-win_amd64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315t-win_amd64.whl |
|---|---|
| Size | 314.7 kB |
| Tags | CPython 3.15 CPython 3.15 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
283b3f65e0c3f678d5b48357178a23442df429544a4821dc94c4bff8d3e7e5ff
|
|
BLAKE2b-256 checksum How to use checksums |
547787b647eb63666a22fa0f950eafd13a98d34a3693e6de6c9dae07975bd178
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315t-musllinux_1_2_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315t-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
d8f1f15071347f77ee8d777ba16f783b27f1823abb71b26141a7ba1752378ede
|
|
BLAKE2b-256 checksum How to use checksums |
1b40f71043a759c4620801217f91e4ca894505f5b7d3fa3e4131b9c86bfa774e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
526705ad0fa2c058e1d25a8b995c17a4c7bb6a91d5abfbc222b0d64b3e9da030
|
|
BLAKE2b-256 checksum How to use checksums |
01d60aa0cb7b5eb7d925b0fffa9bbddb4b79ce4821a8eafb587c65d16e20be6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315t-macosx_11_0_arm64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315t-macosx_11_0_arm64.whl |
|---|---|
| Size | 348.1 kB |
| Tags | CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
83dea1c0359d0c533ecd83ee0d502802c69575c5cd3097226668655d25882706
|
|
BLAKE2b-256 checksum How to use checksums |
964a47191a0b569dd3b9742783ea9da530b6c3e75bf87a7de2556ce7cc940a43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315-win_arm64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315-win_arm64.whl |
|---|---|
| Size | 290.6 kB |
| Tags | CPython 3.15 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
6e6967edcb6ce288879ccdb7dee43d47140846fcd246cb1131aa12cc1f5c4fcf
|
|
BLAKE2b-256 checksum How to use checksums |
e9c25ed0ba371dda4016bd22a147a46b6cac99ac94023b19013d12b0ab8e3fd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315-win_amd64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315-win_amd64.whl |
|---|---|
| Size | 304.6 kB |
| Tags | CPython 3.15 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
abb9d921b70562061b9f1bcf35cd41b96339dbe1ce1329704891006e1af23723
|
|
BLAKE2b-256 checksum How to use checksums |
1495dfae56f4b4e489eb556814a24091ba6420481b322225647cd693a86bbc89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315-musllinux_1_2_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.15 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
815d91b8b3cda3ea16074761ee61a2ba8b4620bae737afc5783bee44d1dc8617
|
|
BLAKE2b-256 checksum How to use checksums |
0666ee22288b92a557d429894088e299ba384d1c7804518c61cba58080a9bab1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.15 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
add5ee41d0b331e41fb24ba54d3c410babc5c1fe3000bcefe63603362819cb5e
|
|
BLAKE2b-256 checksum How to use checksums |
fc92fee2e5efb3cd4709df47813cf37882518f634b276b8bb07e6709be081646
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | cryptofeed-3.0.4-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 328.6 kB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
bee136e5cb3da8b9ba44bfa41fc13b6cc3ec979c7168fcce8e6afd4de2cbf106
|
|
BLAKE2b-256 checksum How to use checksums |
bf57445f336bb249255c9ccd17772ba8d9230f0659e1d03bc15090f3ae73fe05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314t-win_arm64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314t-win_arm64.whl |
|---|---|
| Size | 302.7 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows ARM64 |
|
SHA-256 checksum How to use checksums |
5144da2d5eb41db55a6635c708140b276e69fe22795aa385857b5b689022b73e
|
|
BLAKE2b-256 checksum How to use checksums |
c62e319f5c20cbd65de4acbc4067c14bf5458c107112e8d268610eaf5e427161
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314t-win_amd64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314t-win_amd64.whl |
|---|---|
| Size | 315.9 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a9de51c0d40aa7b10c02bcf3aba6fbdeeff5a666ac9f80e4c1dfa37703b2a089
|
|
BLAKE2b-256 checksum How to use checksums |
700b6a0322f5a7b5b85f6cdf574b2f4751c668f232dd4eacc646abba43dd75af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314t-musllinux_1_2_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314t-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
c885dc45f88114c89395f6e7ab8b38a3c41ee86650e7264a7e542a9386dbaa5e
|
|
BLAKE2b-256 checksum How to use checksums |
4ebd72ab53d706232e193cb4da6db09b1823c1465877fa369b3f54ecdffdd1a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
27313a81768d6cc38a40304fc06b5e9c6e3761b42ae8bbb29c495200574949cb
|
|
BLAKE2b-256 checksum How to use checksums |
7fc154d3b591f7cfaa719c7ac9ab099325b5057b35592fa3586631991c44e8e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314t-macosx_11_0_arm64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314t-macosx_11_0_arm64.whl |
|---|---|
| Size | 348.6 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
25ffc1d5dd47cfecb6b7f774d05b558a28f4091b9b72a792105656836164de3d
|
|
BLAKE2b-256 checksum How to use checksums |
e54df7c362051334396dcf34abccdca90134fec34a6a566cf92e145f14152712
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314-win_arm64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314-win_arm64.whl |
|---|---|
| Size | 290.8 kB |
| Tags | CPython 3.14 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
0c96111b6cb623d4b7a27ab1ebc470486b4651173dee441aea5263e8b2889534
|
|
BLAKE2b-256 checksum How to use checksums |
6646f6133f772cbb092673224c6aa00166a925c97e2b40c59544a48279f28438
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314-win_amd64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 304.8 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
277bfecabbf572699a67faad45223884965ec55b4d14d0b44f88ef5e6381f0ff
|
|
BLAKE2b-256 checksum How to use checksums |
8064f671146433de3ef5083eb77e0c53347b763d37ab4ab0e50c36f2ea83312c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
f09449e6d4ce4e8a021a1f882d898a5401dc26a5e4f06be18d8659676a2d5d7c
|
|
BLAKE2b-256 checksum How to use checksums |
4a5c617bc19b65b5b15587036a4b186cb3de13a07867abffdd6b0cc0f8af93ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
eafba5a75b29771b3cfb77b1cbb25909969f80abc9777d77e3c12af526644133
|
|
BLAKE2b-256 checksum How to use checksums |
265feb55145784505662e42d72537271d3d1eb2654b5e09ac9fc3fd7d2581a14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | cryptofeed-3.0.4-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 328.9 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2858fe350f1475def75c8f4f7d18afc7b916a2db778f6aa410317ae723754ad4
|
|
BLAKE2b-256 checksum How to use checksums |
967aecb19add4d28b5cd9eb96f6770519c5e20dcd70eb6354806bc07e3b332b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp313-cp313-win_arm64.whl
| Download URL | cryptofeed-3.0.4-cp313-cp313-win_arm64.whl |
|---|---|
| Size | 287.8 kB |
| Tags | CPython 3.13 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
0d789174739a1bc597af53a271327117a32708f33fd9eda36a995b35a3e3e4f3
|
|
BLAKE2b-256 checksum How to use checksums |
9b59f030a2b0dcbdccc8873d7ed0a9cbbf30204e498a5367e5a979b298965fc7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp313-cp313-win_amd64.whl
| Download URL | cryptofeed-3.0.4-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 300.1 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
5ef6ffb1e0c769b59579e503f3375154e8e4113f9191ca6cfcbe2f5abd502358
|
|
BLAKE2b-256 checksum How to use checksums |
163e93c4263ad7b2f6345295fb3fff1c9255ada929c7cc5c8484977cd0182a64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
eab32c829d88070d2f91e2c1b70bca325e37e0fccb13e0caa2bbd2ca1c891d41
|
|
BLAKE2b-256 checksum How to use checksums |
a044876a72e57fb7fe5872491a97747bc1023bf0995487fee8124e089a765a89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | cryptofeed-3.0.4-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b625b3684f6b82cb1b6a9291dbd6722cc43bc19d56cdc2fc58954bc6929a91e8
|
|
BLAKE2b-256 checksum How to use checksums |
9f965e79014dce61234edbb7239e6b82dab8f4332624feaf1c81a2a09d256fae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / cryptofeed-3.0.4-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | cryptofeed-3.0.4-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 327.7 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
db8ad82450a01baf83db27c6f092f29f58e31566bbb373d27bb6b14a2401445b
|
|
BLAKE2b-256 checksum How to use checksums |
f1ff4c4e91067b5642408f00312560324153ac0e12401ad4b1b69fd3d305ae3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logSecurity for cryptofeed 3.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 26 files in this release have been uploaded with provenance metadata.
Attestation for cryptofeed-3.0.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
