Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERC-1123 – Revised Ethereum Smart Contract Packaging Standard #1123

gnidan opened this issue May 29, 2018 · 3 comments

ERC-1123 – Revised Ethereum Smart Contract Packaging Standard #1123

gnidan opened this issue May 29, 2018 · 3 comments


Copy link

@gnidan gnidan commented May 29, 2018

Revised Ethereum Smart Contract Packaging Standard

Read: EIP Draft


A data format to describe a single package for distribution with the Ethereum Package Management system (EthPM). This supersedes EIP-190.


Alternate formatting for the EIP submission in corresponding draft PR (#1131) is available hosted on GitHub Pages at

@gnidan gnidan changed the title ERC-1123 – EthPM (Ethereum Package Management) manifest specification, version 2 ERC-1123 – Revised Ethereum Smart Contract Packaging Standard Jun 2, 2018
Copy link

@pipermerriam pipermerriam commented Jun 4, 2018

An explicit 👍 from some of the various teams and projects which have either been involved in the creation of this spec, or who have worked specifically on software that is likely to leverage this spec would be a good signal. Here is a non-exhaustive list.

  • Embark maintainers
  • Remix maintainers
  • Andy or someone from Maker/Dappsys
  • Truffle folks
  • Populus (me, nick, or @davesque)

Please add names/projects/teams that I've missed here. I don't think we have a good "enterprise" representative to speak for the private/consortium chain use case in this list and I'd like to have their view represented.

Copy link

@njgheorghita njgheorghita commented Jul 22, 2020

This ERC has been superseded by ERC 2678 (EthPM v3).

Copy link

@MicahZoltu MicahZoltu commented Jul 23, 2020

@njgheorghita I recommend marking this EIP as abandoned if you have a new one that you plan to push through to final and not this one.

Alternatively, if this is meant to represent a previous version and you don't plan on working further on it, then consider marking this as Last Call and then final so it is no longer a DRAFT and people can start relying on its stability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants