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

Deploy Aave Interface in more distributed IPFS network using Crust #1973

Open
wuhaixian1984 opened this issue Mar 1, 2024 · 0 comments
Open
Labels
feature New feature or request new issue This issue has not been triaged by the core team yet

Comments

@wuhaixian1984
Copy link

wuhaixian1984 commented Mar 1, 2024

Is your feature request related to a problem? Please describe.
Aave Interface is only deployed to IPFS Pinata right now, which is not distributed enough.

IPFS as a p2p network, more hosting nodes will ensure more distributed, secure, faster, and stable access experience.

Describe the solution you'd like
Add second IPFS Pin server in github workflow using ipfs-crust-action.

This doesn't have any side impact for the current build process.

A PR would be provided for review.

Describe alternatives you've considered
N/A

Additional context
Crust Network is the world's leading web3 decentralized storage provider, which runs over 1400+ distributed nodes and provides over 650+ PB storage capacity all over the world.

Pin the Aave Interface to Crust IPFS Network will provide faster and more stable access experience for end users.

Crust Network will provide free CRUST_SEEDS for Aave to use, so do not have any additional charge.

@wuhaixian1984 wuhaixian1984 added feature New feature or request new issue This issue has not been triaged by the core team yet labels Mar 1, 2024
wuhaixian1984 added a commit to crustio/aave-interface that referenced this issue Mar 1, 2024
1. Change the 'update-prod-staging.yml' to add secondary ipfs pin server, utilized the crustio/ipfs-crust-action action which is supported by Crust Network.

2. Use the "continue-on-error: true" to make sure this new action would not break the build.

3. Git repo administrator needs to set the secrets.CRUST_SEEDS in the repo setting in order to make this new action function correctly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request new issue This issue has not been triaged by the core team yet
Projects
None yet
Development

No branches or pull requests

1 participant