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

Replacing Infura with IN3 Client. #7868

Open
chirag-parmar opened this issue Jan 20, 2020 · 4 comments
Open

Replacing Infura with IN3 Client. #7868

chirag-parmar opened this issue Jan 20, 2020 · 4 comments

Comments

@chirag-parmar
Copy link

Description:
Slock.it just released the first stable version of its blockchain client, INCUBED (IN3). INCUBED unlike Infura connects to the Ethereum Blockchain via an INcentivized Node Network which incentivizes and distributes the trust on remote nodes while still keeping the bandwidth and storage requirements low. Such a client fits the requirements of wallets like metamask.

Problem:
The codebase is huge and the project structure is new to me. If someone could explain the architecture in detail and point out the important sections of code that is responsible for the RPC communication it would be great. Also a brief explanation of the project structure would be a cherry on the top.

Sidenote:
Please feel free to voice your views on using IN3 with metamask. All suggestions are welcome.

Links:

@cerealkill
Copy link

@CJentzsch
Copy link

CJentzsch commented Mar 5, 2020

@whymarrh continuing the discussion here.
As asked here #8117 (comment)
Where would you place an option regarding the RPC provider? Where people could choose between the local node, infura, etherscan, incubed or others?
Do you want to offer this at all or is MetaMask Infura only?

@whymarrh
Copy link
Contributor

whymarrh commented Mar 9, 2020

Do you want to offer this at all or is MetaMask Infura only?

We want to offer a way for people to have alternatives to Infura, yes. We don't have a good way of doing this right now. We would like to introduce a way that offers our users choice without us having to pick a select few options.

Where would you place an option regarding the RPC provider? Where people could choose between the local node, infura, etherscan, incubed or others?

This question presumes a fixed list. We're early enough in these discussions that I don't think this is a fair assumption. It might be possible to offer a dynamic list.

@bschorchit
Copy link

It's now possible to add a new RPC provider for Ethereum Mainnet by adding it as a custom network. Does this solve this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants