Skip to main content

Chia VDF

Build PyPI PyPI - Format GitHub

CodeQL

What this repository provides

chiavdf implements the Verifiable Delay Function used by Chia's timelord. It builds on Linux (x86_64 and arm64), macOS (Intel and Apple Silicon), and Windows (x64), and produces:

  • vdf_client - the CPU software timelord client.
  • vdf_bench - a CPU benchmark for estimating iterations per second.
  • hw_vdf_client and hw_test - the Chia VDF ASIC client and board test.
  • emu_hw_vdf_client and emu_hw_test - hardware-free emulators for CI and development.
  • The chiavdf Python bindings used by chia-blockchain to validate proofs of time, plus optional chiavdfc shared/static libraries.

CI builds the CPU and ASIC binaries on all of those platforms. The ASIC emulator tests run without a board.

Install a published build

Release binaries are available through Homebrew, winget, and apt. These channels install the same binaries as the GitHub release archives.

macOS

Install through the Chia Homebrew tap:

brew install chia-network/chia/chiavdf

This installs vdf_client, vdf_bench, hw_vdf_client, hw_test, and the emulators. The bundled FTDI libraries are installed under libexec/chiavdf. Install the FTDI D2XX driver before using the ASIC tools with a board; see README_ASIC.md.

Windows

Install through winget:

winget install --id Chia.chiavdf --exact

The winget package is a machine-scope Inno Setup installer. It installs all six tools (vdf_client, vdf_bench, hw_vdf_client, hw_test, emu_hw_vdf_client, and emu_hw_test) under %ProgramFiles%\Chia\chiavdf\bin, adds that directory to the system PATH, and stages the FTDI CDM driver (ftdibus.inf and ftdiport.inf) with pnputil. One install therefore covers software timelords and ASIC hosts. The installer requires x64 Windows 10 version 2004 or newer and will show a UAC prompt. If you cannot elevate, use the portable chiavdf-<version>-windows-amd64.zip from a release instead. The shared FTDI driver is left installed when chiavdf is uninstalled. Open a new terminal after installation so the updated PATH is visible. See README_ASIC.md and assets/windows-installer.md.

Linux

Add the Chia apt repository and install chiavdf:

sudo apt-get update
sudo apt-get install ca-certificates curl gnupg
curl -sL https://repo.chia.net/FD39E6D3.pubkey.asc | sudo gpg --dearmor -o /usr/share/keyrings/chia.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/chia.gpg] https://repo.chia.net/chiavdf/debian/ stable main" | sudo tee /etc/apt/sources.list.d/chiavdf.list
sudo apt-get update
sudo apt-get install chiavdf

The package installs vdf_client, vdf_bench, hw_vdf_client, hw_test, and the emulators under /usr/bin, plus libft4222.so and the udev rule for the ASIC board.

The Python bindings are installed separately with pip install chiavdf; see Building the Python wheel.

Run a timelord

A timelord needs a synced Chia full node and one or more VDF clients connected to the timelord's port 8000. Choose the CPU or ASIC path below.

Software timelord (CPU)

Use vdf_client. The normal installation path is chia-blockchain's install-timelord.sh, which installs the chiavdf package and builds vdf_client from source. Then start the full node, timelord, and launcher:

chia start node timelord

The launcher starts the software vdf_client processes. For full node and timelord setup, see the Chia timelord install guide. To build and test the client directly from this repository, see Building Timelord and related binaries.

Hardware timelord (Chia VDF ASIC)

Use hw_vdf_client with a Chia VDF ASIC board. Hardware support is available on Linux x86_64 and arm64, macOS Intel and Apple Silicon, and Windows x64. chia-blockchain does not start the hardware client, so start the node and timelord without the software launcher, then start the client yourself:

chia start node timelord-only
hw_vdf_client 8000 3

See README_ASIC.md for board and FTDI requirements, packaged and source builds, --device-loc when using multiple boards, timelord allowlisting, service setup, and troubleshooting. emu_hw_vdf_client and emu_hw_test let you exercise the hardware paths without a board.

Building the Python wheel

The published chiavdf wheels contain the native verifier bindings that chia-blockchain uses to validate proofs of time. This lets a node install a prebuilt wheel instead of compiling the C++ library itself.

The Python bindings require Python 3.10 or newer. Building them requires CMake, a C++17 compiler, and GMP (MPIR on Windows). Building the timelord client and tests also requires Boost headers.

python3 -m venv venv
source venv/bin/activate

pip install wheel setuptools_scm pybind11
BUILD_VDF_CLIENT=N pip wheel .

BUILD_VDF_CLIENT=N builds only the Python extension. The next section builds the CPU timelord client and related binaries.

The Python wheel build uses GitHub Actions to build binary wheels for Linux (x86_64 and arm64), macOS (Intel and Apple Silicon), and Windows (x64), and publishes them, plus a source distribution, to PyPI. See .github/workflows/build.yml. CMake uses the installed pybind11 package when available and falls back to FetchContent to download pybind11. cibuildwheel manages the wheel builds. Install a published wheel with pip install chiavdf.

The same source tree also builds the CPU timelord client and benchmark on Linux, macOS, and Windows. vdf_client is the CPU process that computes the Proof of Time requested by the timelord. vdf_bench estimates iterations per second on a given CPU. Try ./vdf_bench square_asm 250000 on x86/x64 for the phased/asm pipeline. On non-x86 architectures, use ./vdf_bench square 250000 (NUDUPL).

Set CHIAVDF_LOG_AVX=1 to emit AVX feature detection logs during startup.

For the ASIC client, hw_vdf_client, see README_ASIC.md.

For direct CMake builds, the following options are available:

  • BUILD_VDF_CLIENT - build vdf_client
  • BUILD_VDF_BENCH - build vdf_bench
  • BUILD_VDF_TESTS - build test binaries (1weso_test, 2weso_test, prover_test) and CTest/GoogleTest targets (for example vdf_client_session_test)
  • BUILD_HW_TOOLS - build the ASIC timelord tools (hw_vdf_client, hw_test, emulators, and hw_proof_wait_test)
  • ENABLE_GNU_ASM - enable GNU-style asm pipeline on x86/x64 (enabled by default)
  • GENERATE_ASM_TRACKING_DATA - enable track_asm() instrumentation in generated asm (off by default to avoid hot-loop overhead)

Example:

cmake -S src -B build \
  -DBUILD_PYTHON=OFF \
  -DBUILD_CHIAVDFC=OFF \
  -DBUILD_VDF_CLIENT=ON \
  -DBUILD_VDF_BENCH=ON \
  -DBUILD_VDF_TESTS=ON
cmake --build build --target vdf_client vdf_bench 1weso_test 2weso_test prover_test vdf_client_session_test

For the ASIC tools, add -DBUILD_HW_TOOLS=ON and follow README_ASIC.md for FTDI libraries and the Windows clang-cl/Ninja setup used by CI.

The legacy setup.py + Makefile.vdf-client flow runs make for native binaries when either BUILD_VDF_CLIENT=Y (the default) or BUILD_VDF_BENCH=Y is set. Set both to N to skip native binaries. The Makefile's default target builds vdf_client, vdf_bench, and the integration test binaries; for selective builds, call make -f Makefile.vdf-client <target> directly.

For direct CMake builds, use -DBUILD_* flags instead.

AVX runtime flags:

  • CHIAVDF_LOG_AVX=1: emit AVX detection logs at startup
  • CHIA_DISABLE_AVX2=1: disable AVX2 path even when supported
  • CHIA_FORCE_AVX2=1: force AVX2 path
  • CHIA_DISABLE_AVX512_IFMA=1: disable AVX-512 IFMA path
  • CHIA_ENABLE_AVX512_IFMA=1: enable AVX-512 IFMA path when CPUID support is present
  • CHIA_FORCE_AVX512_IFMA=1: force AVX-512 IFMA path

The chia-blockchain install-timelord.sh script automates the software timelord installation and builds the vdf_client binary from the chiavdf package.

The following tests are available, depending on which type of timelord you are running:

  • ./1weso_test for sanitizer_mode.
  • ./2weso_test for a timelord that extends the chain with the slow algorithm.
  • ./prover_test for a timelord that extends the chain with the fast algorithm.

Those tests simulate vdf_client and verify that the produced proofs are correct.

Note: ./prover_test defaults to a long soak/stress run. Set CHIAVDF_PROVER_TEST_FAST=1 to run a short, CI-friendly correctness check.

Regression tests for specific bugs use GoogleTest and run via CTest. Example:

cmake -S src -B build \
  -DBUILD_PYTHON=OFF \
  -DBUILD_CHIAVDFC=OFF \
  -DBUILD_VDF_CLIENT=OFF \
  -DBUILD_VDF_BENCH=OFF \
  -DBUILD_VDF_TESTS=ON \
  -DBUILD_HW_TOOLS=OFF
cmake --build build --target vdf_client_session_test
ctest --test-dir build --output-on-failure -R '^regression\.'

Blockchain proof corpus

verify_vdf_corpus is a standalone Unix tool that validates binary VDF proof corpora independently of a blockchain database. Supply one or more files on the command line; there is no default sample or environment-variable configuration. The existing ReferenceGoldenRegressionTest retains the arithmetic regression coverage.

Export more proofs with export-vdf-proofs in the chia_rs repository:

cargo run --release -p chia-tools --bin export-vdf-proofs -- \
  /path/to/blockchain.sqlite mainnet-proofs.bin

The tool opens the database read-only, includes orphan blocks, reports progress, and resolves partial-proof inputs using ancestor records. It refuses to overwrite an existing output file. If extraction fails, discard the partial output.

The file is a sequence of independently serialized Streamable records. There is no file header or record count. The Rust CorpusEntry layout is:

struct CorpusEntry {
    height: u32,
    input: ClassgroupElement,
    info: VDFInfo,
    proof: VDFProof,
}

Streamable integers are big-endian. The 100 raw bytes of input follow the four-byte height immediately. The discriminant size is a fixed 1024 bits in the verifier and is not stored in the corpus. Witness bytes have a u32 byte length prefix. VDFInfo contains the 32-byte challenge, u64 iteration count, and output element. VDFProof contains the u8 witness type, length-prefixed witness, and one-byte normalized flag. input and info.number_of_iterations are the resolved verifier arguments, including adjustments for partial proofs. The C++ reader does not reapply the normalized flag. Block hashes and proof field names are omitted; failures identify the file, height and record number.

Exports can be combined with cat mainnet-proofs.bin testnet11-proofs.bin testneta-proofs.bin > proofs.bin. The corpus omits version, network and proof field metadata. No compression is required.

Build and run from the chiavdf repository (GoogleTest is not required):

cmake -S src -B build -DCMAKE_BUILD_TYPE=Release \
  -DBUILD_PYTHON=OFF -DBUILD_VDF_TESTS=OFF
cmake --build build --config Release --target verify_vdf_corpus -j 4
./build/verify_vdf_corpus mainnet-proofs.bin testnet11-proofs.bin testneta-proofs.bin
./build/verify_vdf_corpus --start-height 1000000 mainnet-proofs.bin

For multi-configuration generators such as Xcode, run the executable from build/Release/ instead.

Files are processed in argument order. Verification uses one worker per hardware thread reported by std::thread::hardware_concurrency() (with a fallback of one worker), maps each corpus file and parses records as workers need them. With --start-height, the verifier still scans every record because the corpus has no height index and sorting proofs by challenge can move heights out of order. It validates only proofs at or above the specified height. Decoded proof memory is bounded by the worker count. Progress is printed every 10,000 proofs, followed by per-file and overall totals. Failures include the filename, block height and record number. Empty, truncated, unreadable or malformed corpora cause a nonzero exit status. A malformed record stops that file, and the tool continues with subsequent files. Invalid proofs are reported while checking the remaining records. Exit status is 0 when every file passes, 1 on failure, or 2 if no files were supplied. Use --help for usage. The tool checks VDF validity, not block consensus.

Testing matrix

  • Binary integration tests: 1weso_test, 2weso_test, prover_test; these simulate vdf_client and validate proof correctness.
  • Regression tests: GoogleTest targets executed via CTest (for example vdf_client_session_test, typically filtered with ctest -R '^regression\.').
  • Hardware tests: standalone binaries such as hw_test, emu_hw_test, and hw_proof_wait_test; build and run instructions are in README_ASIC.md.

Fuzzing

Fuzz targets live under rust_bindings/fuzz. The prove target includes an iteration cap to avoid out-of-memory conditions in CI. If you want deeper iteration coverage, raise the cap in rust_bindings/fuzz/fuzz_targets/prove.rs after validating memory usage and exec/s on your runner.

Contributing and workflow

Contributions are welcome. More details are available in chia-blockchain's CONTRIBUTING.md.

main is the default branch. Tagged releases are published to PyPI and consumed by chia-blockchain, so main can be ahead of the version chia-blockchain currently pins. Branch from main, open a pull request against main, and make sure the CI build and CodeQL analysis pass. Merging requires a completed review.

Historical background

The original VDF competition background, attribution, and implementation notes are in README_BACKGROUND_COMPETITION.md.

Metadata

Release files for chiavdf 1.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for chiavdf 1.2.3
File Size Uploaded Provenance Actions
chiavdf-1.2.3.tar.gz 1.0 MB With provenance Details for chiavdf-1.2.3.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for chiavdf 1.2.3
File Actions
chiavdf-1.2.3-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for chiavdf-1.2.3-cp314-cp314-win_amd64.whl
chiavdf-1.2.3-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for chiavdf-1.2.3-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
chiavdf-1.2.3-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 Details for chiavdf-1.2.3-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
chiavdf-1.2.3-cp314-cp314-macosx_15_0_x86_64.whl CPython 3.14 CPython 3.14 macOS 15.0+ x86-64 Details for chiavdf-1.2.3-cp314-cp314-macosx_15_0_x86_64.whl
chiavdf-1.2.3-cp314-cp314-macosx_15_0_arm64.whl CPython 3.14 CPython 3.14 macOS 15.0+ ARM64 Details for chiavdf-1.2.3-cp314-cp314-macosx_15_0_arm64.whl
chiavdf-1.2.3-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for chiavdf-1.2.3-cp313-cp313-win_amd64.whl
chiavdf-1.2.3-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for chiavdf-1.2.3-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
chiavdf-1.2.3-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for chiavdf-1.2.3-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
chiavdf-1.2.3-cp313-cp313-macosx_15_0_x86_64.whl CPython 3.13 CPython 3.13 macOS 15.0+ x86-64 Details for chiavdf-1.2.3-cp313-cp313-macosx_15_0_x86_64.whl
chiavdf-1.2.3-cp313-cp313-macosx_15_0_arm64.whl CPython 3.13 CPython 3.13 macOS 15.0+ ARM64 Details for chiavdf-1.2.3-cp313-cp313-macosx_15_0_arm64.whl
chiavdf-1.2.3-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for chiavdf-1.2.3-cp312-cp312-win_amd64.whl
chiavdf-1.2.3-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for chiavdf-1.2.3-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
chiavdf-1.2.3-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for chiavdf-1.2.3-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
chiavdf-1.2.3-cp312-cp312-macosx_15_0_x86_64.whl CPython 3.12 CPython 3.12 macOS 15.0+ x86-64 Details for chiavdf-1.2.3-cp312-cp312-macosx_15_0_x86_64.whl
chiavdf-1.2.3-cp312-cp312-macosx_15_0_arm64.whl CPython 3.12 CPython 3.12 macOS 15.0+ ARM64 Details for chiavdf-1.2.3-cp312-cp312-macosx_15_0_arm64.whl
chiavdf-1.2.3-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for chiavdf-1.2.3-cp311-cp311-win_amd64.whl
chiavdf-1.2.3-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for chiavdf-1.2.3-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
chiavdf-1.2.3-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 Details for chiavdf-1.2.3-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
chiavdf-1.2.3-cp311-cp311-macosx_15_0_x86_64.whl CPython 3.11 CPython 3.11 macOS 15.0+ x86-64 Details for chiavdf-1.2.3-cp311-cp311-macosx_15_0_x86_64.whl
chiavdf-1.2.3-cp311-cp311-macosx_15_0_arm64.whl CPython 3.11 CPython 3.11 macOS 15.0+ ARM64 Details for chiavdf-1.2.3-cp311-cp311-macosx_15_0_arm64.whl
chiavdf-1.2.3-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for chiavdf-1.2.3-cp310-cp310-win_amd64.whl
chiavdf-1.2.3-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for chiavdf-1.2.3-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
chiavdf-1.2.3-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 Details for chiavdf-1.2.3-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
chiavdf-1.2.3-cp310-cp310-macosx_15_0_x86_64.whl CPython 3.10 CPython 3.10 macOS 15.0+ x86-64 Details for chiavdf-1.2.3-cp310-cp310-macosx_15_0_x86_64.whl
chiavdf-1.2.3-cp310-cp310-macosx_15_0_arm64.whl CPython 3.10 CPython 3.10 macOS 15.0+ ARM64 Details for chiavdf-1.2.3-cp310-cp310-macosx_15_0_arm64.whl

Total release size: 19.6 MB

Release files / chiavdf-1.2.3.tar.gz

Download URL chiavdf-1.2.3.tar.gz
Size 1.0 MB
Tags Source
SHA-256 checksum
How to use checksums
023274f32a96d80aa3e70ba07113470d6c60d658b23c7a2f525a3cc603af5e73
BLAKE2b-256 checksum
How to use checksums
c7c7a21de21eef4e34bc61182c3be7ebd9810a8a06457b3816044a2ad894451e
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp314-cp314-win_amd64.whl

Download URL chiavdf-1.2.3-cp314-cp314-win_amd64.whl
Size 2.2 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
044645993c5cbe9df361c610a9257782616498100b9276214aec3ed474086bfb
BLAKE2b-256 checksum
How to use checksums
5e00389b4c8f07400f871862afe0bb363faac618be005da6dadd7f4f14525fb0
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL chiavdf-1.2.3-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 495.0 kB
Tags CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
ea6e49eb690e1320ed469325a910386fbf156a1d8d6e866a3ef8764a478bfe79
BLAKE2b-256 checksum
How to use checksums
8223d9725c285ef071a01a9ab95e0b773d0e3a4fae75e505011f16402609f436
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL chiavdf-1.2.3-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 406.4 kB
Tags CPython 3.14 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
a356804f61c931d05b9914eadb39c4d6badfb6ceb9da30b742726b5637bcc316
BLAKE2b-256 checksum
How to use checksums
aac0323ee1be6ce5f4b94aa11dfd2c5905497e85a3d974020de5db4f00334b7d
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp314-cp314-macosx_15_0_x86_64.whl

Download URL chiavdf-1.2.3-cp314-cp314-macosx_15_0_x86_64.whl
Size 363.8 kB
Tags CPython 3.14 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
5104d29b8f1100e6ca398c5f215afd43719f219997ed79ea3a5a756005a8533a
BLAKE2b-256 checksum
How to use checksums
f1518e7edb15966809f7dd7dcbe5b1142feaafc7d820e6c6e4bd1c6c016c5072
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp314-cp314-macosx_15_0_arm64.whl

Download URL chiavdf-1.2.3-cp314-cp314-macosx_15_0_arm64.whl
Size 336.2 kB
Tags CPython 3.14 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
093cb86bc77dea7f7229389f65328b32e6fa9973fd5521b3cb81d9eb2806c0b0
BLAKE2b-256 checksum
How to use checksums
550d3e77e20bb15427cd1e0115c3a4143e3d2af90690bfb3f2d3ca87da9ef6be
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp313-cp313-win_amd64.whl

Download URL chiavdf-1.2.3-cp313-cp313-win_amd64.whl
Size 2.1 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
c7b896ec6cff2e1954ad1fa216a82f60c792241b7f2d07475657ff18f4d65112
BLAKE2b-256 checksum
How to use checksums
2888a5badc5ac8da90e492b2043e9f21fc7d221fb1c04f4bbd836a49c01bad64
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL chiavdf-1.2.3-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 494.8 kB
Tags CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
a1ade169b6dbd1bef2e7317472849fffc4a9cbeedd6d47d8bb17c4ad77c8c995
BLAKE2b-256 checksum
How to use checksums
872f797f9f63959b75cf405429c53e40c935bf194ebd764302b404a2a308a9f3
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL chiavdf-1.2.3-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 406.1 kB
Tags CPython 3.13 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
b419439d16132868a4c7eeaf7df9e1547a129eeea978682433a1b1d482875960
BLAKE2b-256 checksum
How to use checksums
1c109760e2daae8d47730fd0a55ada74b536241c475d494cc797792fdbd34654
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp313-cp313-macosx_15_0_x86_64.whl

Download URL chiavdf-1.2.3-cp313-cp313-macosx_15_0_x86_64.whl
Size 363.8 kB
Tags CPython 3.13 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
d1575662c8cb8a6065bf5f3d28af8b0b85b5e0f97bf7e83c5d6fdedb483ca765
BLAKE2b-256 checksum
How to use checksums
907c6e19c9d362c4ecce5e00b62b81606245be563d53feb45f2d2e0c1116625d
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp313-cp313-macosx_15_0_arm64.whl

Download URL chiavdf-1.2.3-cp313-cp313-macosx_15_0_arm64.whl
Size 336.0 kB
Tags CPython 3.13 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
eeeed938a71a474bb21591dce5877f721890173053ad8897dd4cfbe1c83f80ac
BLAKE2b-256 checksum
How to use checksums
73ef384026a36ff88535e804a7f28da57ff1b15811cf99381fa34c3514ed5ddf
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp312-cp312-win_amd64.whl

Download URL chiavdf-1.2.3-cp312-cp312-win_amd64.whl
Size 2.1 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
e63bd20c6f9a73eb6e3f81e66a50008e09d9364d4c46c4e72cd286306b835559
BLAKE2b-256 checksum
How to use checksums
f776880b785c9904ac47da04458aa270d3fb126e552e6bc5b7534fef017c870d
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL chiavdf-1.2.3-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 494.7 kB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
2fac8da90f00d05b5988396cd9686a4cdcce24f4309aff91d1e668791a94fe4b
BLAKE2b-256 checksum
How to use checksums
db02bb52a524692c3e06e5c49e16d2a9b428fc2943dd8efb4d7d5219a52356ee
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL chiavdf-1.2.3-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 406.1 kB
Tags CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
0aa9564fc87311a9dd8773d75239c4c24e7ffe822a7bb3363a667f9b56b120bb
BLAKE2b-256 checksum
How to use checksums
4d3c9efe76dfd51263c470e37e59e6b10a9cbce08358daf0863e55e5fa38e542
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp312-cp312-macosx_15_0_x86_64.whl

Download URL chiavdf-1.2.3-cp312-cp312-macosx_15_0_x86_64.whl
Size 363.7 kB
Tags CPython 3.12 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
08c780567ec32c70d109cee3a094eed17bb18e589dac88a2a84382ffe6169b37
BLAKE2b-256 checksum
How to use checksums
51b99888a0896ec68cc7500eee5017c303fa26d1f2411d8e55073a464db4a821
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp312-cp312-macosx_15_0_arm64.whl

Download URL chiavdf-1.2.3-cp312-cp312-macosx_15_0_arm64.whl
Size 336.0 kB
Tags CPython 3.12 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
c52bd7ccd75eed574a25e32c65474011ac2ef81365c14137464d33118a491d0f
BLAKE2b-256 checksum
How to use checksums
a90534239d3af6289188ccba47e0ffdfd10bf7638b21bac5203cb972df8864b2
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp311-cp311-win_amd64.whl

Download URL chiavdf-1.2.3-cp311-cp311-win_amd64.whl
Size 2.1 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
cdc96cfad41d4eac9a78f300c518560a79c7b270c5bcec07cce446eebcbcb0aa
BLAKE2b-256 checksum
How to use checksums
910de343379fdb9ad8a599eddd35aeb8f1929b17eb8a04e25c60ca81d7768bfb
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL chiavdf-1.2.3-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 492.8 kB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
90b627542e5b39be98f2ed89ad84140f8d43b6ffedb90922c43ab10224591e16
BLAKE2b-256 checksum
How to use checksums
c97ddce6f69ab904a3bfaf478f5e64e7cc21e66fd98a9d0e2988351408a62e04
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL chiavdf-1.2.3-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 404.7 kB
Tags CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
ddc8367c062e43b0e45625b4bb570077e4d8f9fdaac9e5f0185e62e5b967430c
BLAKE2b-256 checksum
How to use checksums
f42fd1f9344af89cd87e2807dc6707ab4c696b359a88c96ae0de376520b74aab
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp311-cp311-macosx_15_0_x86_64.whl

Download URL chiavdf-1.2.3-cp311-cp311-macosx_15_0_x86_64.whl
Size 363.1 kB
Tags CPython 3.11 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
b3d65a333970b0d2634e5fcdb4ce7612014d6f604291f172033b81a910fa0c3c
BLAKE2b-256 checksum
How to use checksums
926b244de95abe34e8cc9aa8a5f5e44d1c1772dd7a846a6a15e97c130ce13a01
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp311-cp311-macosx_15_0_arm64.whl

Download URL chiavdf-1.2.3-cp311-cp311-macosx_15_0_arm64.whl
Size 335.7 kB
Tags CPython 3.11 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
e0834b68684e83520025bcde89aa5382cbceb31bbdd14d951cc394b7e757905f
BLAKE2b-256 checksum
How to use checksums
7756296d4575ea0550f12578d52478ded334327933650e94d4d4b73d098cdb89
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp310-cp310-win_amd64.whl

Download URL chiavdf-1.2.3-cp310-cp310-win_amd64.whl
Size 2.1 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
fee4ddfa9d81a3bfc0d10512ad365fd0cdcbc111c9e1103d1d720ed9c3b476de
BLAKE2b-256 checksum
How to use checksums
7b2d0e630de2d2889b8c8cdb0c40182b6d57eb2608772409d4347533253aaa79
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL chiavdf-1.2.3-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 491.5 kB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
71da042bfddd42dff67b165034534417cd0f82f75ec6589b6c4e3ae1204a139c
BLAKE2b-256 checksum
How to use checksums
777991a07dc63dd0c9c7352555ef568b9027d7aff971da4c467c623342695850
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL chiavdf-1.2.3-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 403.7 kB
Tags CPython 3.10 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
1d36f3b25ae6423280146cd44a7042721c0221f5f39b054847260642b21ee16d
BLAKE2b-256 checksum
How to use checksums
500218e3cfd2fd06e6aeb4bc699280ec19ac5c90613ebb7e2fb0290138e2cd5a
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp310-cp310-macosx_15_0_x86_64.whl

Download URL chiavdf-1.2.3-cp310-cp310-macosx_15_0_x86_64.whl
Size 361.5 kB
Tags CPython 3.10 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
56352628900f5d1d8a5d8c1d1c38f2475864248294d693a5262d3558a2656081
BLAKE2b-256 checksum
How to use checksums
50414f322f775788df470b23a8ef1f18e4d4ae956e7b10d5fb54543ef3dc62c6
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 9, 2026.

Transparency log

Release files / chiavdf-1.2.3-cp310-cp310-macosx_15_0_arm64.whl

Download URL chiavdf-1.2.3-cp310-cp310-macosx_15_0_arm64.whl
Size 334.5 kB
Tags CPython 3.10 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
9e173570734e80368de6d29154c9c8165703adcf0d61e67a02e6e5d914d19bc0
BLAKE2b-256 checksum
How to use checksums
adb337868bb1c91ae87b56b7aa7bd80360929791bccb0ca6022f1f82e78628e6
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 9, 2026.

Transparency log

Security for chiavdf 1.2.3

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.

Select from 26 files

Attestation for chiavdf-1.2.3.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 9, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

1.2.3 This release

26 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page