-
Notifications
You must be signed in to change notification settings - Fork 43
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
Direct Channel Checks (Updated) #1027
Comments
This adds logic to check that we have a direct channel with a peer before enabling trading for a given Raiden token. Currently multi-hop Raiden payments are not well supported, and this will prevent any attempts to swap Raiden tokens without a direct channel. Closes #1027.
This adds logic to check that we have a direct channel with a peer with sufficient balance for raiden currencies before accepting or proposing a swap. Currently multi-hop Raiden payments are not well supported, and failed payments are not handled well in Raiden. This will prevent any attempts to swap Raiden tokens without a direct channel. Closes #1027.
This adds logic to check that we have a direct channel with a peer with sufficient balance for raiden currencies before accepting or proposing a swap. Currently multi-hop Raiden payments are not well supported, and failed payments are not handled well in Raiden. This will prevent any attempts to swap Raiden tokens without a direct channel. Closes #1027.
This adds logic to check that we have a direct channel with a peer with sufficient balance for raiden currencies before accepting or proposing a swap. Currently multi-hop Raiden payments are not well supported, and failed payments are not handled well in Raiden. This will prevent any attempts to swap Raiden tokens without a direct channel. Closes #1027.
This adds logic to check that we have a direct channel with a peer with sufficient balance for raiden currencies before accepting or proposing a swap. Currently multi-hop Raiden payments are not well supported, and failed payments are not handled well in Raiden. This will prevent any attempts to swap Raiden tokens without a direct channel. Closes #1027.
This adds logic to check that we have a direct channel with a peer with sufficient balance for raiden currencies before accepting or proposing a swap. Currently multi-hop Raiden payments are not well supported, and failed payments are not handled well in Raiden. This will prevent any attempts to swap Raiden tokens without a direct channel. Closes #1027.
As just discussed in the call we want to have the check on receiving an order if we have a direct channel with raiden. Issue raised by @offerm |
Let's discuss this more today, some thoughts I have:
|
How about we store the "direct" channel info as peer property and discard orders which involve tokens, where this property is And yes, I think it makes sense to periodically hit https://raiden-network.readthedocs.io/en/latest/rest_api.html#get--api-(version)-channels-(token_address) and see if there is a new channel. |
This commit attempts to ensure that we have a direct channel with peers for raiden currencies before exchanging orders with that peer for any pairs involving that currency. When a peer advertises a trading pair, either via initial handshake or on a node state update, we check that we have a direct channel for any raiden currencies before activating advertised pairs. If the trading pair is not activated, then we do not send or accept orders for that pair with the peer. An existing timer with an interval of one minute is used for each peer to periodically check if inactive currencies and pairs can be activated by performing the same checks described above, including the direct channel check for raiden currencies. Closes #1027.
Some new thoughts: #1347 (comment) |
This commit attempts to ensure that we have a direct channel with peers for raiden currencies before exchanging orders with that peer for any pairs involving that currency. When a peer advertises a trading pair, either via initial handshake or on a node state update, we check that we have a direct channel for any raiden currencies before activating advertised pairs. If the trading pair is not activated, then we do not send or accept orders for that pair with the peer. An existing timer with an interval of one minute is used for each peer to periodically check if inactive currencies and pairs can be activated by performing the same checks described above, including the direct channel check for raiden currencies. Closes #1027.
This commit attempts to ensure that we have a direct channel with peers for raiden currencies before exchanging orders with that peer for any pairs involving that currency. When a peer advertises a trading pair, either via initial handshake or on a node state update, we check that we have a direct channel for any raiden currencies before activating advertised pairs. If the trading pair is not activated, then we do not send or accept orders for that pair with the peer. An existing timer with an interval of one minute is used for each peer to periodically check if inactive currencies and pairs can be activated by performing the same checks described above, including the direct channel check for raiden currencies. Closes #1027.
This commit attempts to ensure that we have a direct channel with peers for raiden currencies before exchanging orders with that peer for any pairs involving that currency. When a peer advertises a trading pair, either via initial handshake or on a node state update, we check that we have a direct channel for any raiden currencies before activating advertised pairs. If the trading pair is not activated, then we do not send or accept orders for that pair with the peer. An existing timer with an interval of one minute is used for each peer to periodically check if inactive currencies and pairs can be activated by performing the same checks described above, including the direct channel check for raiden currencies. Closes #1027.
This commit attempts to ensure that we have a direct channel with peers for raiden currencies before exchanging orders with that peer for any pairs involving that currency. When a peer advertises a trading pair, either via initial handshake or on a node state update, we check that we have a direct channel for any raiden currencies before activating advertised pairs. If the trading pair is not activated, then we do not send or accept orders for that pair with the peer. An existing timer with an interval of one minute is used for each peer to periodically check if inactive currencies and pairs can be activated by performing the same checks described above, including the direct channel check for raiden currencies. Closes #1027.
The text was updated successfully, but these errors were encountered: