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
cdinto it - Run
git fetch --tags git@github.com:vyperlang/vyper.gitto get the tags necessary for version inference - Run
uv sync - Run
source .venv/bin/activateto activate the virtual environment - Run
vyper --versionto verify the setup - (optional) Run
git config blame.ignoreRevsFile .git-blame-ignore-revsto improvegit blame
pip
Make sure you have pip (version 25.1 or above), setuptools, and pytest installed
- Clone this repo and
cdinto it - Run
git fetch --tags git@github.com:vyperlang/vyper.gitto get the tags necessary for version inference - Run
python -m venv .venvto create a virtual environment - Run
source .venv/bin/activateto activate it - Run
make initto install the main dependencies - Run
make dev-initto install the dev dependencies - Run
vyper --versionto verify the setup - (optional) Run
git config blame.ignoreRevsFile .git-blame-ignore-revsto improvegit blame
Commands
vyper path/to/file.vyto run your local copy of the compilerpytestto 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 testsmake mypyto type check your changesmake lintto check your files are correctly formatted (also runs mypy)
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".
2 maintainers
Metadata
2 maintainers
Release files for vyper 0.5.0a2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vyper-0.5.0a2.tar.gz | 1.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vyper-0.5.0a2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.9 MB
Release files / vyper-0.5.0a2.tar.gz
| Download URL | vyper-0.5.0a2.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c92629dc80490eafd008ef9b6b969ced60545c27000d9862a3489a6d1d537cba
|
|
BLAKE2b-256 checksum How to use checksums |
b50c171e9f717225f3f8f5d25e15ccce9bc1031b1622eb7145fa46f09c3c7996
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 29, 2026.
Transparency logRelease files / vyper-0.5.0a2-py3-none-any.whl
| Download URL | vyper-0.5.0a2-py3-none-any.whl |
|---|---|
| Size | 580.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fce90ee21a85ca487a8abc20ac90e25b2fbc4dc441433bb23fb698eed20aa1e8
|
|
BLAKE2b-256 checksum How to use checksums |
142f3aa5431c47a0f58e4790f77158eee014ebce9d0b9a9272dc52e0ff76dc5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 29, 2026.
Transparency log
