Pre-release

This release is a pre-release and may not be stable for production use.

Getting Started

See Installing Vyper to install vyper. See Tools and Resources for an additional list of framework and tools with vyper support. See Documentation for the documentation and overall design goals of the Vyper language.

See learn.vyperlang.org for learning Vyper by building a Pokémon game. See try.vyperlang.org to use Vyper in a hosted jupyter environment!

Note: Vyper is constantly evolving, use with care and understand the risks associated with smart contract development.

Installation

See the Vyper documentation for build instructions.

Compiling a contract

To compile a contract, use:

vyper your_file_name.vy

generate bytecode

vyper -f bytecode file-name.vy > file-name.bin

generate abi

vyper -f abi file-name.vy > file-name.abi

There is also an online compiler available you can use to experiment with the language and compile to bytecode and/or IR.

Note: While the vyper version of the online compiler is updated on a regular basis it might be a bit behind the latest version found in the master branch of this repository.

Contributing

See Issues tab, and feel free to submit your own issues
Add PRs if you discover a solution to an existing issue
For further discussions and questions, post in Discussions or talk to us on Discord
For more information, see Contributing

Contributing Code

Setup

uv (recommended)

Make sure you have uv installed

Clone this repo and cd into it
Run git fetch --tags git@github.com:vyperlang/vyper.git to get the tags necessary for version inference
Run uv sync
Run source .venv/bin/activate to activate the virtual environment
Run vyper --version to verify the setup
(optional) Run git config blame.ignoreRevsFile .git-blame-ignore-revs to improve git blame

pip

Make sure you have pip (version 25.1 or above), setuptools, and pytest installed

Clone this repo and cd into it
Run git fetch --tags git@github.com:vyperlang/vyper.git to get the tags necessary for version inference
Run python -m venv .venv to create a virtual environment
Run source .venv/bin/activate to activate it
Run make init to install the main dependencies
Run make dev-init to install the dev dependencies
Run vyper --version to verify the setup
(optional) Run git config blame.ignoreRevsFile .git-blame-ignore-revs to improve git blame

Commands

vyper path/to/file.vy to run your local copy of the compiler
pytest to test your changes Useful pytest flags: * -x: Fail test run on first test failure * --instafail: Show reason for test failure directly, instead of at the end of a test run * --disable-warnings: Hide warnings which occurred during tests
make mypy to type check your changes
make lint to check your files are correctly formatted (also runs mypy)

Docker Setup

Note: This is only useful for contributors, if you just want to use vyper, look here.

Build the image:

docker build . -t vyper -f Dockerfile

Check it runs:

docker run -v $(pwd):/code vyper --help

Run vyper:

It works like vyper locally, with the difference that you should add /code/ before the local path:

docker run -v $(pwd):/code vyper /code/<path to vy file>

Example:

vyper -f abi_python examples/name_registry/name_registry.vy becomes
docker run -v $(pwd):/code vyper -f abi_python /code/examples/name_registry/name_registry.vy

Other Tips

Checking performance

To run a python performance profile (to find compiler perf hotspots):

PYTHONPATH=. python -m cProfile -s tottime vyper/cli/vyper_compile.py "$@"

The utility timer functions timeit, profileit and cumtimeit are available in vyper/utils.py.

Getting call graph

To get a call graph from a python profile, install gprof2dot and xdot, and run it like gprof2dot -f pstats stats | xdot -. (See https://stackoverflow.com/a/23164271/).

Testing with hevm

Install hevm by downloading it from the releases page (https://github.com/ethereum/hevm/releases/latest) and making sure it is in your PATH. hevm tests can be enabled with --hevm flag, and hevm tests can be selected with the -m hevm marker. For instance, pytest -m "hevm" --hevm.

Fuzzing tests

Fuzzing test are very slow, so they are not run by default. To run them, use pytest -m "fuzzing".

Download files

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

Source Distribution

vyper-0.5.0b1.tar.gz (1.5 MB view details)

Uploaded Sep 1, 2026 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

vyper-0.5.0b1-py3-none-any.whl (668.3 kB view details)

Uploaded Sep 1, 2026 Python 3

File details

Details for the file vyper-0.5.0b1.tar.gz.

File metadata

Download URL: vyper-0.5.0b1.tar.gz
Upload date: Sep 1, 2026
Size: 1.5 MB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for vyper-0.5.0b1.tar.gz
Algorithm	Hash digest
SHA256	`c98ed60eaa1c04e079052ef5adf76ab1b5c581107b8dd1031d0d6dea50d0400e`
MD5	`8ac2ab6627950b1de26e9780a2ebe7c1`
BLAKE2b-256	`12b152b494bab667fc27b6ca004eff1c5afd5fa5ab2b56eda1247d707bad7bc3`

See more details on using hashes here.

Provenance

The following attestation bundles were made for vyper-0.5.0b1.tar.gz:

Publisher: release-pypi.yml on vyperlang/vyper

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: vyper-0.5.0b1.tar.gz
- Subject digest: c98ed60eaa1c04e079052ef5adf76ab1b5c581107b8dd1031d0d6dea50d0400e
- Sigstore transparency entry: 2674345981
- Sigstore integration time: Sep 1, 2026
Source repository:
- Permalink: vyperlang/vyper@577d2534356903076bb79b5b15ebd4d772994693
- Branch / Tag: refs/tags/v0.5.0b1
- Owner: https://github.com/vyperlang
- Access: public
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: release-pypi.yml@577d2534356903076bb79b5b15ebd4d772994693
- Trigger Event: release