Skip to main content

Quick Start

Compile Solidity contracts.

Dependencies

Installation

via pip

You can install the latest release via pip:

pip install ape-solidity

via setuptools

You can clone the repository and use setuptools for the most up-to-date version:

git clone https://github.com/ApeWorX/ape-solidity.git
cd ape-solidity
python3 setup.py install

Quick Usage

In your project, make sure you have a contracts/ directory containing Solidity files (.sol).

Then, while this plugin is installed, compile your contracts:

ape compile

The byte-code and ABI for your contracts should now exist in a __local__.json file in a .build/ directory.

Solidity Versioning

By default, ape-solidity tries to use the best versions of Solidity by looking at all the source files' pragma specifications. However, it is often better to specify a version directly. If you know the best version to use, set it in your ape-config.yaml, like this:

solidity:
  version: 0.8.14

EVM Versioning

By default, ape-solidity will use whatever version of EVM rules are set as default in the compiler version that gets used. Sometimes, you might want to use a different version, such as deploying on Arbitrum or Optimism where new opcodes are not supported yet. If you want to require a different version of EVM rules to use in the configuration of the compiler, set it in your ape-config.yaml like this:

solidity:
  evm_version: paris

Dependency Mapping

By default, ape-solidity knows to look at installed dependencies for potential remapping-values and will use those when it notices you are importing them. For example, if you are using dependencies like:

dependencies:
  - name: openzeppelin
    github: OpenZeppelin/openzeppelin-contracts
    version: 4.4.2

And your source files import from openzeppelin this way:

import "@openzeppelin/contracts/token/ERC721/ERC721.sol";

Ape knows how to resolve the @openzeppelin value and find the correct source.

If you want to override this behavior or add new remappings that are not dependencies, you can add them to your ape-config.yaml under the solidity: key. For example, let's say you have downloaded openzeppelin somewhere and do not have it installed in Ape. You can map to your local install of openzeppelin this way:

solidity:
  import_remapping:
    - "@openzeppelin=path/to/openzeppelin"

Library Linking

To compile contracts that use libraries, you need to add the libraries first. Use the add_library() method from the ape-solidity compiler class to add the library. A typical flow is:

  1. Deploy the library.
  2. Call add_library() using the Solidity compiler plugin, which will also re-compile contracts that need the library.
  3. Deploy and use contracts that require the library.

For example:

import pytest


@pytest.fixture
def contract(accounts, project, compilers):
    # Deploy the library.
    account = accounts[0]
    library = project.Set.deploy(sender=account)

    # Add the library to Solidity (re-compiles contracts that use the library).
    compilers.solidity.add_library(library)

    # Deploy the contract that uses the library.
    return project.C.deploy(sender=account)

Compiler Settings

When using ape-solidity, your project's manifest's compiler settings will include standard JSON output. You should have one listed compiler per solc version used in your project. You can view your current project manifest, including the compiler settings, by doing:

from ape import project

manifest = project.extract_manifest()

for compiler_entry in manifest.compilers:
    print(compiler_entry.version)
    print(compiler_entry.settings)

NOTE: These are the settings used during contract verification when using the Etherscan plugin.

--via-IR Yul IR Compilation Pipeline

You can enable solc's --via-IR flag by adding the following values to your ape-config.yaml

solidity:
  via_ir: True

Contract Flattening

ape-solidity has contract-flattening capabilities. If you are publishing contracts using Ape, Ape automatically detects and uses the flattened-contract approach if needed.

To manually flatten a contract for your own benefit, use the following code:

from ape import compilers, project

source_path = project.source_paths[0]  # Replace with your path.
flattened_src = compilers.flatten_contract(source_path)
print(str(flattened_src))

Metadata

Release files for ape-solidity 0.8.7

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

Source distribution (sdist)

Source distribution for ape-solidity 0.8.7
File Size Uploaded Provenance Actions
ape_solidity-0.8.7.tar.gz 421.7 kB With provenance Details for ape_solidity-0.8.7.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ape-solidity 0.8.7
File Interpreter ABI Platform Actions
ape_solidity-0.8.7-py3-none-any.whl Python 3 none any Details for ape_solidity-0.8.7-py3-none-any.whl

Total release size: 451.1 kB

Release files / ape_solidity-0.8.7.tar.gz

Download URL ape_solidity-0.8.7.tar.gz
Size 421.7 kB
Tags Source
SHA-256 checksum
How to use checksums
dff931f29dcdbb67b0654b486510a99543be210f039647158ab4322337bd5f0e
BLAKE2b-256 checksum
How to use checksums
91252b8d448222da59cd9bc298cfe6f17207f88c2f91a2a23426e928baaa707f
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 27, 2026.

Transparency log

Release files / ape_solidity-0.8.7-py3-none-any.whl

Download URL ape_solidity-0.8.7-py3-none-any.whl
Size 29.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
571fd5de30b659587cbf103c9e0e98699201822cbab0fff8415ea59ed7fdcd39
BLAKE2b-256 checksum
How to use checksums
ac24953367ca285e3ec63b7a3148358de620bcb364650a4cd2b24c8b6b1ed912
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 27, 2026.

Transparency log

Security for ape-solidity 0.8.7

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 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for ape_solidity-0.8.7.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 27, 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

0.8.7 This release

2 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