State-of-the-art, highly opinionated, hyper-optimised, and secure 🐍Vyper smart contract building blocks.
Warning
This is experimental software and is provided on an "as is" and "as available" basis. We do not give any warranties and will not be liable for any losses incurred through any use of this code base.
src
└── snekmate
├── auth
│ ├── Ownable — "Owner-Based Access Control Functions"
│ ├── Ownable2Step — "2-Step Ownership Transfer Functions"
│ ├── AccessControl — "Multi-Role-Based Access Control Functions"
│ └── interfaces
│ └── IAccessControl — "AccessControl Interface Definition"
├── extensions
│ ├── ERC2981 — "ERC-721 and ERC-1155 Compatible ERC-2981 Reference Implementation"
│ ├── ERC4626 — "Modern and Gas-Efficient ERC-4626 Tokenised Vault Implementation"
│ └── interfaces
│ └── IERC2981 — "EIP-2981 Interface Definition"
├── governance
│ └── TimelockController — "Multi-Role-Based Timelock Controller Reference Implementation"
├── tokens
│ ├── ERC20 — "Modern and Gas-Efficient ERC-20 + EIP-2612 Implementation"
│ ├── ERC721 — "Modern and Gas-Efficient ERC-721 + EIP-4494 Implementation"
│ ├── ERC1155 — "Modern and Gas-Efficient ERC-1155 Implementation"
│ └── interfaces
│ ├── IERC20Permit — "EIP-2612 Interface Definition"
│ ├── IERC721Enumerable — "EIP-721 Optional Enumeration Interface Definition"
│ ├── IERC721Metadata — "EIP-721 Optional Metadata Interface Definition"
│ ├── IERC721Permit — "EIP-4494 Interface Definition"
│ ├── IERC721Receiver — "EIP-721 Token Receiver Interface Definition"
│ ├── IERC1155 — "EIP-1155 Interface Definition"
│ ├── IERC1155MetadataURI — "EIP-1155 Optional Metadata Interface Definition"
│ ├── IERC1155Receiver — "EIP-1155 Token Receiver Interface Definition"
│ └── IERC4906 — "EIP-4906 Interface Definition"
└── utils
├── Base64 — "Base64 Encoding and Decoding Functions"
├── BatchDistributor — "Batch Sending Both Native and ERC-20 Tokens"
├── CreateAddress — "`CREATE` EVM Opcode Utility Function for Address Calculation"
├── Create2Address — "`CREATE2` EVM Opcode Utility Functions for Address Calculations"
├── ECDSA — "Elliptic Curve Digital Signature Algorithm (ECDSA) Functions"
├── SignatureChecker — "ECDSA and EIP-1271 Signature Verification Functions"
├── EIP712DomainSeparator — "EIP-712 Domain Separator"
├── Math — "Standard Mathematical Utility Functions"
├── MerkleProofVerification — "Merkle Tree Proof Verification Functions"
├── Multicall — "Multicall Functions"
└── interfaces
└── IERC5267 — "EIP-5267 Interface Definition"
Important
🐍 snekmate uses a ZeroVer-based versioning scheme. This means 🐍 snekmate's major version will never exceed the first and most important number in computing: zero.
We offer three convenient ways to install the 🐍 snekmate contracts:
You can install 🐍 snekmate via submodules using Foundry with:
forge install pcaversaccio/snekmate
If you want to leverage 🐍 snekmate's
VyperDeployer
contract for your own testing, ensure that you compile the Vyper contracts with the same EVM version as configured in yourfoundry.toml
file. TheVyperDeployer
contract offers two overloadeddeployContract
functions that allow the configuration of the target EVM version. Please note that since Vyper version0.3.8
the default EVM version is set toshanghai
.
You can install 🐍 snekmate from PyPI with:
pip install snekmate
You can use
pip install snekmate -t .
to install the contracts directly into the current working directory!
You can install 🐍 snekmate from npm with:
npm install --save-dev snekmate
Or if you are using Yarn:
yarn add --dev snekmate
In case you are using pnpm, invoke:
pnpm add --save-dev snekmate
Caution
It is possible to install the latest versions of main
or any other branch locally via pip install git+https://github.com/pcaversaccio/snekmate.git@<branch>
or forge install pcaversaccio/snekmate && forge update
. Each branch, including the main
branch, must be understood as a development branch that should be avoided in favour of tagged releases. The release process includes security measures that the repository branches do not guarantee.
This repository contains Foundry-based unit tests, property-based tests (i.e. fuzzing), and invariant tests for all contracts, if applicable. All tests are run as part of the CI pipeline test-contracts
.
Note
An invariant is a property of a program that should always hold true. Fuzzing is a way of checking whether the invariant is falsifiable.
Contract | Unit Tests | Property-Based Tests | Invariant Tests |
---|---|---|---|
Ownable |
✅ | ✅ | ✅ |
Ownable2Step |
✅ | ✅ | ✅ |
AccessControl |
✅ | ✅ | ✅ |
ERC2981 |
✅ | ✅ | ✅ |
ERC4626 |
✅ | ✅ | ✅ |
TimelockController |
✅ | ✅ | ✅ |
ERC20 |
✅ | ✅ | ✅ |
ERC721 |
✅ | ✅ | ✅ |
ERC1155 |
✅ | ✅ | ✅ |
Base64 |
✅ | ❌ | ❌ |
BatchDistributor |
✅ | ✅ | ✅ |
CreateAddress |
✅ | ✅ | ❌ |
Create2Address |
✅ | ✅ | ❌ |
ECDSA |
✅ | ✅ | ❌ |
SignatureChecker |
✅ | ✅ | ❌ |
EIP712DomainSeparator |
✅ | ✅ | ❌ |
Math |
✅ | ✅ | ❌ |
MerkleProofVerification |
✅ | ✅ | ❌ |
Multicall |
✅ | ❌ | ❌ |
✅ Test Type Implemented ❌ Test Type Not Implemented
This repository is inspired by or directly modified from many sources, primarily:
- ApeAcademy
- Batch Distributor
CREATE
Factory- Disperse Research
- Multicall
- OpenZeppelin Contracts
- solady
- solmate
🐍 snekmate only exists thanks to its contributors. There are many ways to get involved and contribute to our high-quality and secure smart contracts. Check out our Contribution Guidelines!
I am a strong advocate of the open-source and free software paradigm. However, if you feel my work deserves a donation, you can send it to this address: 0xe9Fa0c8B5d7F79DeC36D3F448B1Ac4cEdedE4e69
. I can pledge that I will use this money to help fix more existing challenges in the Ethereum ecosystem 🤝.