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.

Sign up for GitHub

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

Jump to bottom

Endpoint in API to indicate ChainId #7483

Open
lullis opened this issue Dec 16, 2021 · 0 comments
Open

Endpoint in API to indicate ChainId #7483

lullis opened this issue Dec 16, 2021 · 0 comments
Labels
Tag / Good First Issue

Comments

@lullis
Copy link
Contributor

lullis commented Dec 16, 2021

Abstract

The API provides a way for to know the raiden address, but it does not indicate what chain (or chains?) it is connected to. This is not so much of an issue when Raiden was only deployed on ethereum mainnet, but with the plans to deploy it on Arbitrum it might be important

Motivation

One can think of applications that need to interact with multiple instances of Raiden nodes, and quickly figure out through the REST API what chain a particular instance is connected to.

Examples:

  • a payment gateway or centralized exchange that wants to give the ability to make payouts to its users via Raiden
  • Someone providing a mainnet -> arbitrum token bridge.

Specification

There should be an endpoint in the REST API that responds with the id of the chain that the raiden node is connected to. This can be a simple relay of the chainId value provided by the ethereum client.
lullis added a commit to mushroomlabs/hub20.backend that referenced this issue Feb 24, 2022
@lullis
Refactor relationship betweeen raiden <-> wallet (account) model
0745465 
With the idea that a raiden can be deployed on multiple chains, we
needed to revisit the concept of having Raiden as a type of ethereum
account, given that the same address can have raiden nodes connected
to different chains.

A Raiden node is now represented only by its URL, the underlying
account address and the chain that is connected to. Given that there
is not yet a reliable way to [get chain information from Raiden's
API](raiden-network/raiden#7483), the
operator needs to include this information when creating the
entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Tag / Good First Issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lullis @karlb