Chia VDF
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_clientandhw_test- the Chia VDF ASIC client and board test.emu_hw_vdf_clientandemu_hw_test- hardware-free emulators for CI and development.- The
chiavdfPython bindings used by chia-blockchain to validate proofs of time, plus optionalchiavdfcshared/static libraries.
CI builds the CPU and ASIC binaries on all of those platforms. The ASIC emulator tests run without a board.
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.11 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.
Building Timelord and related binaries
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- buildvdf_clientBUILD_VDF_BENCH- buildvdf_benchBUILD_VDF_TESTS- build test binaries (1weso_test,2weso_test,prover_test) and CTest/GoogleTest targets (for examplevdf_client_session_test)BUILD_HW_TOOLS- build the ASIC timelord tools (hw_vdf_client,hw_test, emulators, andhw_proof_wait_test)ENABLE_GNU_ASM- enable GNU-style asm pipeline on x86/x64 (enabled by default)GENERATE_ASM_TRACKING_DATA- enabletrack_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 startupCHIA_DISABLE_AVX2=1: disable AVX2 path even when supportedCHIA_FORCE_AVX2=1: force AVX2 pathCHIA_DISABLE_AVX512_IFMA=1: disable AVX-512 IFMA pathCHIA_ENABLE_AVX512_IFMA=1: enable AVX-512 IFMA path when CPUID support is presentCHIA_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_testforsanitizer_mode../2weso_testfor a timelord that extends the chain with the slow algorithm../prover_testfor 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\.'
Testing matrix
- Binary integration tests:
1weso_test,2weso_test,prover_test; these simulatevdf_clientand validate proof correctness. - Regression tests: GoogleTest targets executed via CTest (for example
vdf_client_session_test, typically filtered withctest -R '^regression\.'). - Hardware tests: standalone binaries such as
hw_test,emu_hw_test, andhw_proof_wait_test; build and run instructions are inREADME_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.0
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 |
|---|---|---|---|---|
| chiavdf-1.2.0.tar.gz | 964.7 kB | With provenance | Details for chiavdf-1.2.0.tar.gz |
Built distributions (wheels)
Total release size: 15.7 MB
Release files / chiavdf-1.2.0.tar.gz
| Download URL | chiavdf-1.2.0.tar.gz |
|---|---|
| Size | 964.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b290569182d95adff1d9a0ddbf8a7a8fc0adca80e3e084535ec92105a1c50778
|
|
BLAKE2b-256 checksum How to use checksums |
83fa9c59a0ddfb24c7d3c11f941b931f0f9974bb6cb4cc627b4609d209f307e5
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp314-cp314-win_amd64.whl
| Download URL | chiavdf-1.2.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f2152f4b5666e32a99e0707276905914d87c39073b9198467ac0659be17e7fde
|
|
BLAKE2b-256 checksum How to use checksums |
d152875b7e37bc8689425997a2c93eb819d64897c375511bf107e1e760d6de56
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | chiavdf-1.2.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 487.9 kB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
5cd7e4c24d548c50d9f2c2486fe062db927f06a8a2b841a091b4c85130d93063
|
|
BLAKE2b-256 checksum How to use checksums |
caf1d02b8b2198438e24d28d455638c80258c56698107cb22c50365d87ba5b37
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | chiavdf-1.2.0-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 401.5 kB |
| Tags | CPython 3.14 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
23f9beb66b4821abc7e8259452219c49f571ffa4d373fa66438cb5a5071ed3a6
|
|
BLAKE2b-256 checksum How to use checksums |
fa974b152c71ee41aaf3e9d31a61b7b498b6a59b994be70beab41179ee1697bd
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp314-cp314-macosx_15_0_x86_64.whl
| Download URL | chiavdf-1.2.0-cp314-cp314-macosx_15_0_x86_64.whl |
|---|---|
| Size | 354.7 kB |
| Tags | CPython 3.14 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
51c160fa5b91a286cf672599f650dd56ef81030775befa51f0e5faa5eb137aab
|
|
BLAKE2b-256 checksum How to use checksums |
bf38d4b421a2a69615aeb8617fa24d612d710ad0c5fd09255d53901cbb328229
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp314-cp314-macosx_15_0_arm64.whl
| Download URL | chiavdf-1.2.0-cp314-cp314-macosx_15_0_arm64.whl |
|---|---|
| Size | 328.0 kB |
| Tags | CPython 3.14 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c05273a095782822a531bfe25b199ffce3a8e5f5b3f02c1d9c02f7afe2dfa2c7
|
|
BLAKE2b-256 checksum How to use checksums |
c81e2f6221392045d69f9f50aac7e27cb286b75539750cd09417cb39710847b1
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp313-cp313-win_amd64.whl
| Download URL | chiavdf-1.2.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
aff70dc04b66b0a12613f567185b5d38bb7c07f826275933278e65f50629eaa5
|
|
BLAKE2b-256 checksum How to use checksums |
eac36894c56923650db1fca5889a0bce8af722d1878e6f5d656cfcf594824a0a
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | chiavdf-1.2.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 487.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 |
ebdebb65846facada11e6734db0ec692a36b196abf817da2a74b7984d1bc0903
|
|
BLAKE2b-256 checksum How to use checksums |
84a4ec49bd5535d088bda59ea3386a3e4be9ab369d8e959cd8881b60744037f2
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | chiavdf-1.2.0-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 401.2 kB |
| Tags | CPython 3.13 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
0b275110ad17c991c5e2255761455d99596d20a326f279b9ed1c8802ade55cc5
|
|
BLAKE2b-256 checksum How to use checksums |
d546bb932997c103ecc627b108d0402aac61bac34dc393dd4b364842e7e729a4
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp313-cp313-macosx_15_0_x86_64.whl
| Download URL | chiavdf-1.2.0-cp313-cp313-macosx_15_0_x86_64.whl |
|---|---|
| Size | 354.7 kB |
| Tags | CPython 3.13 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
1ca582c05a4ccf17e828a47d92012211e9979e67e482d2698245120e796bce70
|
|
BLAKE2b-256 checksum How to use checksums |
7e228c1e9305eb2214f43e2c1caa317ec76e082c1f44b3032943915c94d1bda0
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp313-cp313-macosx_15_0_arm64.whl
| Download URL | chiavdf-1.2.0-cp313-cp313-macosx_15_0_arm64.whl |
|---|---|
| Size | 327.8 kB |
| Tags | CPython 3.13 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
37b27a19762f2c7fd9d9886d0de4ea0e111d9b759888be913d4107046d0230dc
|
|
BLAKE2b-256 checksum How to use checksums |
4829c5194050cdbb7b1533a55b2f918c057512c4cbcb207e84f48d72d2d8e1cf
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp312-cp312-win_amd64.whl
| Download URL | chiavdf-1.2.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9ad6f5130c7a031d7a0cb98de6a61f46374f184873acca5bf19a392b095d2c2a
|
|
BLAKE2b-256 checksum How to use checksums |
a3a371a0cc8b5ad5bb26c380434e802b182e237bfc7044f733ce65c031684192
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | chiavdf-1.2.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 487.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 |
271888dc4d5bf12e9dd9243f961369378a33e9fe63b5df45261b3c0589ce41d2
|
|
BLAKE2b-256 checksum How to use checksums |
88af4e47e1b909f5a0a8690b72dd340e0178097df210e3a4a694175c534fb638
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | chiavdf-1.2.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 401.2 kB |
| Tags | CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
e84a507125ff665a37b3299056cbfbf5039fc52c2f167ad6954f04b9a4a60695
|
|
BLAKE2b-256 checksum How to use checksums |
c1fd264a5c2ec59904b397fe6f5eb5c38b81ea5c4d3f1468d03fedceaa7a6a27
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp312-cp312-macosx_15_0_x86_64.whl
| Download URL | chiavdf-1.2.0-cp312-cp312-macosx_15_0_x86_64.whl |
|---|---|
| Size | 354.6 kB |
| Tags | CPython 3.12 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
3ce368991dc15634134370642c5418b73d53d23f61e3042af1c96ccce7028086
|
|
BLAKE2b-256 checksum How to use checksums |
13af11d9ec78a2e71e477aa4aaacdd46d893259bd4dc5aa996208b54531c1f75
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp312-cp312-macosx_15_0_arm64.whl
| Download URL | chiavdf-1.2.0-cp312-cp312-macosx_15_0_arm64.whl |
|---|---|
| Size | 327.8 kB |
| Tags | CPython 3.12 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0dbc58ab4a7d5e2e6f336976a19a47d3b5d85c5cb66665ad5c881612bb090389
|
|
BLAKE2b-256 checksum How to use checksums |
64bdc7d6d5ff48026980150ed54211cf80ac59dc522cf0c54c79ce211dafdc54
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp311-cp311-win_amd64.whl
| Download URL | chiavdf-1.2.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8850d37685caa921c61d016ec4c6636ecb3b958e86370d215b867a155e5520cb
|
|
BLAKE2b-256 checksum How to use checksums |
3fcf9b8977acbfbd59eadb00603a8a8ae2cee7c12495c4e50a04859cc1f0a1d2
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | chiavdf-1.2.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 486.0 kB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
c11b321b490d338454f2006ed56ec3745d0fe7c82373bd0bd246d814e7c3ff7d
|
|
BLAKE2b-256 checksum How to use checksums |
aefdc14deb491bff954692f406d3854b05232f86b59ed5c4cf52dc0a2ccab6ac
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | chiavdf-1.2.0-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 400.3 kB |
| Tags | CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
e6ff70a4e0bc039e42c4d3249051cbc78859424f4da62156ccb6bb0b6d69209b
|
|
BLAKE2b-256 checksum How to use checksums |
011ea44f0e42cd1a857f0fdc1aaaf6993411b90c4b06b9e36527a484aae617b8
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp311-cp311-macosx_15_0_x86_64.whl
| Download URL | chiavdf-1.2.0-cp311-cp311-macosx_15_0_x86_64.whl |
|---|---|
| Size | 353.7 kB |
| Tags | CPython 3.11 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
3407216bf74eeb358d1d695563655d7f3f180227c58ac2a83c5cf21fe71b6df8
|
|
BLAKE2b-256 checksum How to use checksums |
b5acf6e9e29717cf44024c3d0916fabbec5561b568d50616f1bd693f4dc2d2fa
|
| 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 Oct 22, 2026.
Transparency logRelease files / chiavdf-1.2.0-cp311-cp311-macosx_15_0_arm64.whl
| Download URL | chiavdf-1.2.0-cp311-cp311-macosx_15_0_arm64.whl |
|---|---|
| Size | 327.5 kB |
| Tags | CPython 3.11 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6948edd8d1649cfd3900e15c575143234454f4e66fda3ef0504c007e6aa0cbcf
|
|
BLAKE2b-256 checksum How to use checksums |
be59c953dc2dd374c024642becff8497770b97a72e41b62516e535e1b6d55d76
|
| 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 Oct 22, 2026.
Transparency logSecurity for chiavdf 1.2.0
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 21 files in this release have been uploaded with provenance metadata.
Attestation for chiavdf-1.2.0.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 Oct 22, 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.