Python abstraction for ERC190 packages.
Project description
parse and validate packages
given a web3 instance provide access to contract factory classes
given a web3 instance provide access to all of the deployed contract instances for the chain that web3 is connected to.
validate package bytecode matches compilation output.
validate deployed bytecode matches compilation output
access to packages dependencies
construct new packages
Web3
The Package object will function much like the Contract class provided by web3. Rather than instantiating the base class provided by ethpm, you will instead use a classmethod which generates a new Package class for a given package.
OwnedPackage = BasePackage.factory('/path/to/owned-v1.0.0.json')Then, the OwnedPackage can be instantiated with any web3 intance.
owned_package = OwnedPackage(web3)A Package class can only be directly constructed from the parsed package JSON. It can also be initialized with the package’s URI or the local filesystem path to a package by using Package.from_file(path).
Contract Factories
Contract factories should be accessible from the package class but you must also provide a web3 instance.
Owned = OwnedPackage.get_contract_factory(web3, 'owned')From a package instance, they are also available as properties.
Owned = owned_package.contract_factories.ownedIn cases where a contract uses a library, the contract factory will have unlinked bytecode. The ethpm package ships with its own subclass of web3.contract.Contract with a few extra methods and properties related to bytecode linking
>>> math = owned_package.contract_factories.math
>>> math.has_linkable_bytecode
True
>>> math.is_bytecode_linked
False
>>> linked_math = math.link_bytecode({'MathLib': '0x1234...'})
>>> linked_math.is_bytecode_linked
TrueNote: the actual format of the link data is not clear since library names aren’t a one-size-fits all solution. We need the ability to specify specific link references in the code.
Deployed Contracts
Deployed contracts are only available from package instances. The package instance will filter the deployments based on the chain that web3 is connected to.
Accessing deployments is done with property access
package.deployed_contracts.GreeterIPFS
We’ll need a pluggable backend system for IPFS access. A built-in default one that defaults to using infura should be enough to get off the ground.
Lower priority but important will be ensuring that a user can configure connecting to their own IPFS node.
Verifying Things
The Package class should verify all of the following things.
Package json matches EthPM V2 Manifest Specification
Included bytecode matches compilation output
Deployed bytecode matches compilation output
Dependencies
The Package class should provide access to the full dependency tree.
>>> owned_package.build_dependencies['zeppelin']
<ZeppelinPackage>Testing Strategy
Load and validate packages from disk.
Access package data.
Access contract factories.
EthPM-Spec
EthPM-Spec is referenced inside this repo as a submodule.**
If you clone this repository, you should run this command to fetch the contents of the submodule
git submodule initRegistry URI
The URI to lookup a package from a registry should follow the following format. (subject to change as the Registry Contract Standard makes it’s way through the EIP process)
scheme://authority/package-name?version=x.x.x
URI must be a string type
scheme: ercxxx
authority: Must be a valid ENS domain or a valid checksum address pointing towards a registry contract.
package-name: Must conform to the package-name as specified in the EthPM-Spec.
version: The URI escaped version string, should conform to the semver version numbering specification.
i.e. ercxxx://packages.zeppelinos.eth/owned?version=1.0.0
Release setup
For Debian-like systems:
apt install pandocTo release a new version:
make release bump=$$VERSION_PART_TO_BUMP$$How to bumpversion
The version format for this repo is {major}.{minor}.{patch} for stable, and {major}.{minor}.{patch}-{stage}.{devnum} for unstable (stage can be alpha or beta).
To issue the next version in line, specify which part to bump, like make release bump=minor or make release bump=devnum.
If you are in a beta version, make release bump=stage will switch to a stable.
To issue an unstable version when the current version is stable, specify the new version explicitly, like make release bump="--new-version 4.0.0-alpha.1 devnum"
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file ethpm-0.1.0a22.tar.gz.
File metadata
- Download URL: ethpm-0.1.0a22.tar.gz
- Upload date:
- Size: 14.7 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | a39300321c6534899a4f32bcdb1abd682a44077ad34b7d658e12705fb6c1ec46 |
|
| MD5 | 15154f725e6cc27b4712a9142fbb90c0 |
|
| BLAKE2b-256 | 2147fa05b216fd2182ffc4666196e0402a5e96eaad40af316c9b15b2dbd9fb3c |
File details
Details for the file ethpm-0.1.0a22-py3-none-any.whl.
File metadata
- Download URL: ethpm-0.1.0a22-py3-none-any.whl
- Upload date:
- Size: 15.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | be492faae8bc749808635de819e23b3709f7d4a6a941f33265912098a62392f6 |
|
| MD5 | 7d4e2d1cd47ebe5510963b68e53bc949 |
|
| BLAKE2b-256 | bceb8fc216c9c8b293bdb0f4477b158efb0eb5458a2c6d061891fbab4157fb5e |
