status-im
/
EIPs
mirror of https://github.com/status-im/EIPs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

update PR for feedback

This commit is contained in:
Piper Merriam 2017-02-14 09:30:26 -07:00
parent 837d368dec
commit 888bb039ee
1 changed files with 10 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
EIPS/eip-190-smart-contract-packaging-standard.md
View File

@ -47,9 +47,7 @@ The specification contains details for a single document referred to as a *"Rele
> These documents have not been inlined into this ERC to ensure that there is a single source of truth for the specification. > These documents have not been inlined into this ERC to ensure that there is a single source of truth for the specification.
# Rationale # Use Cases
## Use Cases
This specification covers the following types of smart contract packages. This specification covers the following types of smart contract packages.
@ -60,43 +58,38 @@ This specification covers the following types of smart contract packages.
Full explanations and examples of these use cases can be found in the [`README.md`](https://github.com/ethpm/epm-spec/blob/v1.0.0/README.md#use-cases) from the `epm/epm-spec` repository. Full explanations and examples of these use cases can be found in the [`README.md`](https://github.com/ethpm/epm-spec/blob/v1.0.0/README.md#use-cases) from the `epm/epm-spec` repository.
## Package Managers # Package Managers
The *Release Lockfile* is intended for consumption by package management software. Specific care was made to ensure that all of the following functionality can be implemented by package managers. The *Release Lockfile* is intended for consumption by package management software. Specific care was made to ensure that all of the following functionality can be implemented by package managers.
### Deterministic builds ## Deterministic builds
Ensures that a package will always resolve to the same set of dependencies and source files. Both source files and dependencies are content addressed to ensure that the referenced resources cannot change. Ensures that a package will always resolve to the same set of dependencies and source files. Both source files and dependencies are content addressed to ensure that the referenced resources cannot change.
### Bytecode verification ## Bytecode verification
Contains the appropriate information for a package manager to inspect a deployed contract and verify that it's bytecode matches the bytecode that results from compilation and linking of the package source code. Contains the appropriate information for a package manager to inspect a deployed contract and verify that its bytecode matches the bytecode that results from compilation and linking of the package source code.
### Multi-chain deploys ## Multi-chain deploys
Supports deployments across multiple chains, allowing a package to define addresses on both the public mainnet and testnet. Supports deployments across multiple chains, allowing a package to define addresses on both the public mainnet and testnet.
### Trusted packages ## Trusted packages
Allows for packages which exclude source code or other elements which would be needed for verification of the contract bytecode. This allows for minimalistic packages to be created for special situations where the package manager will not be performing verification. Allows for packages which exclude source code or other elements which would be needed for verification of the contract bytecode. This allows for minimalistic packages to be created for special situations where the package manager will not be performing verification.
# Implementation # Framework support and integration
Implementations are implemented in the following frameworks. Support for ERC190 is either implemented or in progress for the following:
* [Truffle](http://truffleframework.com/) * [Truffle](http://truffleframework.com/)
* [Populus](http://populus.readthedocs.io/en/latest/) * [Populus](http://populus.readthedocs.io/en/latest/)
Implementations are underway for the following frameworks.
* [Dapple](http://dapple.readthedocs.io/en/master/) * [Dapple](http://dapple.readthedocs.io/en/master/)
* [Eris PM](https://github.com/eris-ltd/eris-cli) * [Eris PM](https://github.com/eris-ltd/eris-cli)
Implementation has not yet begun in the following frameworks but is on the roadmap.
* [Embark](https://github.com/iurimatias/embark-framework) * [Embark](https://github.com/iurimatias/embark-framework)
* [Browser Solidity](https://github.com/ethereum/browser-solidity/issues/386)