OpenZeppelin
Upload files to IPFS
🧐 Motivation
I am an EIP editor. One of the requirements for something to be included in an EIP is that its behavior won't change, and another one is that the resource will never go offline (1 of n).
I find a lot of people trying to use OpenZeppelin contracts in EIPs. I would like to let them use OZ contracts, as they are indeed extremely useful.
📝 Details
The source code of every tag would have to be pinned to IPFS, and be linked to in the release description. I also cannot recommend adding IPFS DNSLink to the documentation enough.
Hello @Pandapip1
That is an interesting proposal. We could add that to the release workflow, but we would have to rely on a specific IPFS host (or run our own node).
@frangio what do you think ?
or run our own node
That would be my personal preference here. Do you think it would be possible for ConsenSYS to run one?
@Pandapip1 You may be mistaken, this is not a ConsenSys project. :slightly_smiling_face:
I also cannot recommend adding IPFS DNSLink to the documentation enough.
This is not something you would use for EIPs though, right? As a DNS record is centralized and may go offline.
I'm interested in the proposal, but I'd only pursue it after we implement an automated release process, which we've been planning for a while and should happen soon. Otherwise it will add an additional step to our releases which I'd rather avoid until automated.
this is not a ConsenSys project
🤦 not sure where I got that idea. Anyways, what you said sounds good.
@JulissaDantes This isn't resolved. We are not uploading to IPFS yet.
You are right, that might have been for another issue.