Add EIP190 for ERC190 Smart Contract Packaging Standard

[pipermerriam]

Preamble

EIP: Ideally [EIP190](https://github.com/ethereum/EIPs/issues/190) to be historically consistent.
Title: Ethereum Smart Contract Packaging Standard
Authors: Piper Merriam, Tim Coulter, Denis Erfurt (mhhf), RJ Catalano (VoR0220), Iuri Matias (iurimatias)
Type: Standard Track
Category: ERC 
Status: Draft
Created: 2017-01-10

Simple Summary

This ERC proposes a specification for Ethereum smart contract packages.

Abstract / Motivation

Packaging is a core piece of modern software development which is missing from the Ethereum ecosystem. The lack of packaging limits the ability for developers to reuse code which negatively affects productivity and security.

A key example of this is the ERC20 standard. There are a few well audited reusable token contracts available but most developers end up writing their own because of the difficulty in finding and reusing existing code.

A packaging standard should have the following positive effects on the ecosystem:

• Greater overall productivity caused by the ability to reuse existing code.
• Increased security caused by the ability to reuse existing well audited implementations of common patterns (ERC20, crowdfunding, etc).

Smart contract packaging should also have a direct positive effect on the end user. Wallet software will be able to consume a released package and generate an interface for interacting with any deployed contracts included within that package. With the advent of ENS all of the pieces will be in place for a wallet to take a human readable name and present the user with an interface for interacting with the underlying application.

Specification

The full specification for this standard is maintained separately in the repository epm/epm-spec.

This EIP refers to the 1.0.0 version of the specification: https://github.com/ethpm/epm-spec/tree/v1.0.0

The specification contains details for a single document referred to as a "Release Lockfile".

• Release Lockfile Specification: https://github.com/ethpm/epm-spec/blob/v1.0.0/release-lockfile.spec.md.
• JSON Schema for Release Lockfile: https://github.com/ethpm/epm-spec/blob/v1.0.0/spec/release-lockfile.spec.json

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

This specification covers the following types of smart contract packages.

1. Packages with contracts intended to be used as base contract such as the common owned pattern.
2. Packages with contracts that are ready to use as-is such as an ERC20 token contract.
3. Packages with deployed contracts such as libraries or services.

Full explanations and examples of these use cases can be found in the README.md from the epm/epm-spec repository.

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

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

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.

Multi-chain deploys

Supports deployments across multiple chains, allowing a package to define addresses on both the public mainnet and testnet.

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.

Implementation

Implementations are implemented in the following frameworks.

• Truffle
• Populus

Implementations are underway for the following frameworks.

• Dapple
• Eris PM

Implementation has not yet begun in the following frameworks but is on the roadmap.

• Embark

Copyright

Copyright and related rights waived via CC0.

[Souptacular]

A grammar error and other minor fixes. Oh and change the EIP line at the top to EIP: 190

[Souptacular]

Go ahead and remove rationale since you explained it sufficiently in Motivation.

[Souptacular]

it's should be its

[Souptacular]

You can go ahead and and say "Implementations are complete or in progress for the following frameworks." Then list all of the frameworks.

[Arachnid]

Implementations are implemented?

[Souptacular]

Hm. Maybe "EIP 190 is implemented in the following frameworks."

[pipermerriam]

Will get these tips addressed soon. Thx for the review.

…

On Fri, Feb 10, 2017, 3:58 AM Hudson Jameson ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In EIPS/eip-190-smart-contract-packaging-standard.md <#203>: > +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. + + +### Multi-chain deploys + +Supports deployments across multiple chains, allowing a package to define addresses on both the public mainnet and testnet. + + +### 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. + + +# Implementation + +Implementations are implemented in the following frameworks. Hm. Maybe "EIP 190 is implemented in the following frameworks." — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#203>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAyTgv8Xsq-SSXcRQqApFbpVF_Hrlvcrks5rbEK8gaJpZM4L1s30> .

[pipermerriam]

I believe I've addressed the handful of comments/feedback.

[Souptacular]

Thanks @pipermerriam. Approved!