SPEC

A detailed Spec from the Truffle team can be found here.

1. Finish V2 of the spec, including examples, documentation and basic implementers guide. Remaining to-do this week on the spec:
   1. Examples need to be re-generated, probably from the existing list of example packages. Documentation and implementers guides to this item will be added as well because I think that’s really needed for people to be able to understand the specification.
2. Reference implementation of an ethpm library. To be done in javascript. We already started one in python here: https://github.com/pipermerriam/py-ethpm
   1. This would be a library that *understands* the packaging specification, knows how to do all of the various types of validation that are needed, and has some level of integration with web3. Also, it would implement ways to *install* packages to disk as well as load packages that have already been installed to disk. (see next point for specifying how things get installed to disk)
   2. GitHub
      1. pipermerriam/py-ethpm
      2. py-ethpm - ERC190 package abstraction for python
3. ERC for writing ethpm packages to disk. This should be a really simple spec that outlines how package data is written to disk so that we’re sure to be compatible across different implementations in different languages. (package installed with truffle/js should be able to be loaded with the python implementation).
4. Reference implementation of a package registry. This should be very close to your original implementation of the package registry. Something that is as simple as possible for the use case of a single developer deploying their own package registry.
   1. Integration with #2 would be part of this so that the ethpm-js library could interface with package registries and maybe even deploy a package registry for the user and wire it up to an ENS name.
5. ERC to define the package registry API. This would just be an ERC like ERC20 but for the package registry contract from #4
6. Web3js integration for ethpm-js (#2)

SPEC

Feature-parity with etherscan to be confirmed by advisors - POA to open-source library on March 10th.

1. The explorer open-source code is located here:
   https://github.com/poanetwork/poa-explorer
2. User Stories can be found here:
   https://github.com/poanetwork/poa-explorer/issues
3. Staging Version of Explorer
   https://explorer-sokol.poa.network/en