This repository has been archived by the owner on Sep 27, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
To provide a resource for developers, tooling, protocols, etc. to have a trusted, content-addressed, machine-readable, accessible source for ENS contract assets & deployment data.
What's Included?
3 packages. 1 for each of
ensdomains/ens
,ensdomains/ethregistrar
,ensdomains/resolvers
. "pretty" versions of each package have been included for readability (note: these "pretty" versions are NOT valid ethPM packages - which must be tightly packed.)It's not necessary to store these JSON files in a repository - since they live on IPFS. There is an ethPM scraping service that backs up all published packages and their assets hosted on IPFS. However, it's a good idea to keep a copy of the json files on github for backup.
[email protected]
_ethpm_packages/ens.json
_ethpm_packages/ens_pretty.json
[email protected]
_ethpm_packages/ethregistrar.json
_ethpm_packages/ethregistrar_pretty.json
[email protected]
_ethpm_packages/resolvers.json
_ethpm_packages/resolvers_pretty.json
Registry
These packages been published to this registry. I'm currently the owner of the registry, but I'd love to hand ownership over to someone on your team. Only the owner is allowed to release packages on a registry. Just ping me with an address, and I'll transfer ownership. I'll also point the ENS name
ens.ethpm.eth
to the registry address once ownership is transferred, to make it more accessible for users.Maintenance
I encourage you to carefully look through these packages, before taking ownership. AFAIK everything is accurate, but I could've missed something, or you might want to extend a package (i.e. add a deployment).
Currently, the easiest way to generate/consume/publish packages is with the
ethpm-cli
orweb3.py
. Truffle support for ethPM v2 is being actively implemented, and should be available within the coming months.I'm sure some questions might arise, and I'm always happy to help answer questions. Just ping me on github or
@njgheorghita
on gitter.Resources
Docs
Spec
ethpm-CLI