Skip to content
New issue

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

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

Already on GitHub? # to your account

Better code reuse tools #13

Closed
maraoz opened this issue Sep 14, 2016 · 5 comments · Fixed by #158
Closed

Better code reuse tools #13

maraoz opened this issue Sep 14, 2016 · 5 comments · Fixed by #158

Comments

@maraoz
Copy link
Contributor

maraoz commented Sep 14, 2016

Current Solidity code reuse is based on copy-pasting or downloading existing code from other repositories. Mature ecosystems have good code repository management systems such as NodeJS’ npm or Ruby’s gems.
An interesting variation in Ethereum is the possibility of reusing code already deployed to the blockchain. Let's build tools that allow to easily link your contracts to deployed libraries.

@fonzarely
Copy link

Let's build tools that allow to easily link your contracts to deployed libraries.

do you mean to provide a list of public library deployed ?

@maraoz
Copy link
Contributor Author

maraoz commented Sep 28, 2016

@fonzarely more like an index, and easier tools to link contracts in development to those.

For now Zeppelin is using raw npm, and Truffle Beta's integration with npm, which is not ideal. Moving into the future, we should build better tools, but for now we're OK.

@sabr-p
Copy link

sabr-p commented Oct 13, 2016

from what i understood @maraoz , you propose an npm equivalent, a library of public contracts available in the blockchain, that it?
or, npm plays bad with Solidity code?
maybe give some details/examples on snags you hit?

@maraoz
Copy link
Contributor Author

maraoz commented Oct 14, 2016

npm is good enough for now. Eventually, we'll want better ways to link contracts to already deployed code sitting in the blockchain. Not required for now though IMO, never hit a big need for it

@gnidan
Copy link

gnidan commented Dec 19, 2016

Any thought about using the in-development https://github.com/ethpm/epm-spec ?

djvex pushed a commit to djvex/openzeppelin-contracts that referenced this issue Jan 1, 2022
Project setup, formatting, copyright header.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants