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

Raiden Client not compatible with Infura #2027

Closed
BCsRock opened this issue Aug 1, 2018 · 4 comments · Fixed by #2092
Closed

Raiden Client not compatible with Infura #2027

BCsRock opened this issue Aug 1, 2018 · 4 comments · Fixed by #2092
Assignees

Comments

@BCsRock
Copy link

BCsRock commented Aug 1, 2018

Problem Definition

I am considering the possiblity of using a 3rd-party hosted Ethereum Full Node and decided to go with Infura. This allows a small IoT Device to run the Raiden Client and interact with 3rd-party node.

Reason is: not everybody has infrastructure to host an own full node, ensure it's 24/7 uptime, maintaining security updates and so on.

The infura documentation regarding the available API Endpoints is shown here.

It covers a variety of methods of rpcapis: eth_*, net_*, web3_*

The problem is: when calling raiden with --eth-rpc-endpoint https://ropsten.infura.io/<myToken>:<myPort> it produces the error message:

Could not contact the ethereum node through JSON-RPC.
Please make sure that JSON-RPC is enabled for these interfaces:

    eth_*, net_*, web3_*

geth: https://github.com/ethereum/go-ethereum/wiki/Management-APIs

It would now be interesting to identify if there are actually necessary methods which are not provided by Infura's API endpoints.

System Description

Ubuntu 16.04 LTS
Raiden-0.4.1-linux
Geth on Infura: Geth/v1.8.3-stable/linux-amd64/go1.10

@LefterisJP LefterisJP added this to the Red Eyes Testnet 4 milestone Aug 6, 2018
err508 added a commit to err508/raiden that referenced this issue Aug 7, 2018
After raiden-network#2066 the function is unused and superfluous.
Additionally, raiden-network#2066 implicitly resolved raiden-network#2027 by
replacing `eth-endpoint_to_hostport`.
The helper had a bug resolving tls rpc-endpoints.

Closes raiden-network#2027
LefterisJP pushed a commit that referenced this issue Aug 7, 2018
After #2066 the function is unused and superfluous.
Additionally, #2066 implicitly resolved #2027 by
replacing `eth-endpoint_to_hostport`.
The helper had a bug resolving tls rpc-endpoints.

Closes #2027
@BCsRock
Copy link
Author

BCsRock commented Aug 13, 2018

Guys, you are awesome! Tested with version 0.5.0 today in our VM on our cloud server. It works like a charm. Using Infura Account as RPC interface, I was able to´establish a channel between two accounts, send tokens off-chain, close the channel. Everything without any failure.

I really appreciate your development strength and I am sure this feature will make a lot of users happy in the future too (^_^)b

@palango
Copy link
Contributor

palango commented Aug 13, 2018

@czepluch Should we mention this more prominently in the docs? I think this might be nice to know for people who just want to test raiden.

@czepluch
Copy link
Contributor

That's a good idea.

@err508
Copy link
Contributor

err508 commented Aug 21, 2018

A description of the how to use Raiden with the Infura endpoint has been added to the docs here.

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

Successfully merging a pull request may close this issue.

5 participants