Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Should add support of another IPFS APIs provider other than INFURA #51

Open
naveed-klaytn opened this issue Nov 9, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@naveed-klaytn
Copy link

Is your request related to a problem? Please describe.
INFURA requires credit card info while creating IPFS project (to get IPFS_PROJECT_KEY & IPFS_PROJECT_SECRET required in this project) which I think most of the devs are reluctant to provide. So we should add support for another IPFS APIs provider to enable devs to config provider they want.

Describe the solution you'd like

Describe alternatives you've considered

Additional context
Screenshot attached of infura dashboard requiring credit card info while creating IPFS project.
Screenshot 2022-11-10 at 1 32 32 AM

@naveed-klaytn naveed-klaytn added the enhancement New feature or request label Nov 9, 2022
@praveen-kaia
Copy link
Contributor

praveen-kaia commented Nov 10, 2022

Hi @naveed-klaytn , Please address this as part of #48 . As caver internally supports ipfs which is the reason for plugging IPFS endpoints to it. However as part of sandbox the proposed solution can be used for Metamask and also override the functionality of caver IPFS.

@naveed-klaytn naveed-klaytn self-assigned this Nov 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants