Quick Start
Compile Solidity contracts.
Dependencies
- python3 version 3.9 up to 3.12.
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:
- Deploy the library.
- Call
add_library()using the Solidity compiler plugin, which will also re-compile contracts that need the library. - 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))
1 maintainer
Release files for ape-solidity 0.8.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ape_solidity-0.8.6.tar.gz | 422.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ape_solidity-0.8.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 452.6 kB
Release files / ape_solidity-0.8.6.tar.gz
| Download URL | ape_solidity-0.8.6.tar.gz |
|---|---|
| Size | 422.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b0450e845982f1e1eaa132e7c307339f857e9c79bf5e608ed6fd0277bffb18e
|
|
BLAKE2b-256 checksum How to use checksums |
285cc729079f980eb3dbcbe3f8acbbdcd4764b85422228880b19670259290a0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.12.1.2 readme-renderer/44.0 requests/2.34.2 requests-toolbelt/1.0.0 urllib3/2.7.0 tqdm/4.67.3 importlib-metadata/9.0.0 keyring/25.7.0 rfc3986/2.0.0 colorama/0.4.6 CPython/3.10.20
|
Release files / ape_solidity-0.8.6-py3-none-any.whl
| Download URL | ape_solidity-0.8.6-py3-none-any.whl |
|---|---|
| Size | 30.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f03b2bcdcb9c0e894e58ea15d0b27ed09e191b54fa815215a59fc745b57c772
|
|
BLAKE2b-256 checksum How to use checksums |
8fcd41663de8ba1d2a2c219f329f0efaa1c797634fe0a0d459f69f884f20a51c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.12.1.2 readme-renderer/44.0 requests/2.34.2 requests-toolbelt/1.0.0 urllib3/2.7.0 tqdm/4.67.3 importlib-metadata/9.0.0 keyring/25.7.0 rfc3986/2.0.0 colorama/0.4.6 CPython/3.10.20
|
