Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 26 2017 14:34
    @LefterisJP banned @poojasingh940_twitter
  • Dec 12 2017 13:36
    @LefterisJP banned @Nedu_Onyeanuna_twitter
  • Oct 10 2017 21:40
    @LefterisJP banned @etherchamp1_twitter
  • Aug 11 2016 13:48
    @heikoheiko banned @primehat23
ali06han
@ali06han
What about this rdn / btc case? I trust the coin but I'm afraid it will fall.
Jacob Stenum Czepluch
@czepluch
@ali06han I am not sure what you are talking about. Could you be a bit more specific?
Kris
@drselump14
Do I need my own raiden node to run light-client?
Jacob Stenum Czepluch
@czepluch
@drselump14 no
Or rather the Light Client is a node in it self
Kris
@drselump14
I'm wondering if there is still a use case for using Raiden client (python) if we have the light-client ?
1 reply
Kris
@drselump14
Hi guys, it seems that the https://lightclient.raiden.network/ and master branch of dApp is not working on current metamask browser.
I've opened the issue on Github. raiden-network/light-client#2710. Anyone have any clue why it's not working?
Jacob Stenum Czepluch
@czepluch
Thanks for opening the issue :)
Felix
@flxhbl

hi guys, I was trying to deploy a contract following this tutorial: https://docs.raiden.network/using-raiden-on-testnet/use-custom-token/compile-imported-token-code

I have 0.1 ETH on goerli but if I want to transact from my account to "New Contract" there is the "inssuficient balance" aleart.

Could anyone give me a hint what to try next?
tried different versions of the git contract also
Felix
@flxhbl
'fixed my fault ;)
Diego Ferrer
@Ferret-san
Hello, for testing purposes, can the RSB be run locally with localhost or my inet IP address?
4 replies
Diego Ferrer
@Ferret-san
Mainly curios as to which parts of the configuration can be omitted or skipped in the .env file if it's all run locally
Diego Ferrer
@Ferret-san

Hi guys, I'm trying to run the RSB (mainly looking to have the PFS and MS) locally to test something out (I ported the raiden contracts to Optimism for a hackathon), and I have a couple blockers:

  1. Seems like specifying the server name to localhsot makes it so that it runs as transport.localhost, which it seems incorrect to me. What would be the setting to run things locally? I want to test things out before deploying the dapp to Optimism Kovan
  2. I'm getting the following error for the PFS even though the chainId provided is correct, as well as the address for the ServiceRegistry contract in OE Kovan: "No deployed contracts were found at the default registry contracts_version=None"

Any idea/feedbak is highly appreciated!

10 replies
Diego Ferrer
@Ferret-san
Another question, after looking at the RSB, if I'm trying to run the PFS and MS services for the raiden-contracts I deployed to Optismim, should the RSB work as long as it is provided the right information even if it is not technically a set of contracts deployed on Ethereum, or should I be looking at modifying the raiden-services first to "include" my set of contracts?
Raphael Lullis
@raphael:communick.com
[m]
hey guys... I am trying to run raiden alpha (2.0.0a1) but I am not sure if there is any thing in the configuration that needs to change. If I run with the same matrix server and PFS address I had for 1.2, I am getting the following:
raiden_1             | Traceback (most recent call last):
raiden_1             |   File "/usr/local/lib/python3.8/site-packages/raiden/ui/cli.py", line 724, in _run
raiden_1             |     run_services(kwargs)
raiden_1             |   File "/usr/local/lib/python3.8/site-packages/raiden/ui/runners.py", line 18, in run_services
raiden_1             |     raiden_service = run_raiden_service(**options)
raiden_1             |   File "/usr/local/lib/python3.8/site-packages/raiden/ui/app.py", line 457, in run_raiden_service
raiden_1             |     raiden_service.start()
raiden_1             |   File "/usr/local/lib/python3.8/site-packages/raiden/raiden_service.py", line 480, in start
raiden_1             |     self._start_transport()
raiden_1             |   File "/usr/local/lib/python3.8/site-packages/raiden/raiden_service.py", line 598, in _start_transport
raiden_1             |     self.transport.start(raiden_service=self, prev_auth_data=None)
raiden_1             |   File "/usr/local/lib/python3.8/site-packages/raiden/network/transport/matrix/transport.py", line 582, in start
raiden_1             |     self._initialize_first_sync()
raiden_1             |   File "/usr/local/lib/python3.8/site-packages/raiden/network/transport/matrix/transport.py", line 865, in _initialize_first_sync
raiden_1             |     for room in self._client.rooms.values():
raiden_1             | RuntimeError: dictionary changed size during iteration
raiden_1             | FATAL: An unexpected exception occurred. A traceback has been written to /tmp/raiden-exception-2021-05-19T06-52zkzkk6kw.txt
raiden_1             | dictionary changed size during iteration
raiden_1             | ReturnCode.FATAL
The weird thing is that this error is not always reproducible.
Raphael Lullis
@raphael:communick.com
[m]
Also worthy of note: 2021-05-19 08:04:36.070175 [warning ] Unsupported Ethereum client version "Geth/v1.10.3-stable-991384a7/linux-amd64/go1.16.3" [raiden.network.rpc.client]
What version of geth is supported?
Karl Bartel
@karlb
That version should work: raiden-network/raiden@d7d1a41
We're using 1.10.1 in our CI tests.
Raphael Lullis
@raphael:communick.com
[m]
Okay, great. So the message is only because of patch version?

In any case, can you share the configuration you have for geth? When I didn't get the transport error message above and it went through, I got another error:

raceback (most recent call last): raiden_1 | File "/usr/local/lib/python3.8/site-packages/raiden/ui/cli.py", line 724, in _run raiden_1 | run_services(kwargs) raiden_1 | File "/usr/local/lib/python3.8/site-packages/raiden/ui/runners.py", line 18, in run_services raiden_1 | raiden_service = run_raiden_service(**options) raiden_1 | File "/usr/local/lib/python3.8/site-packages/raiden/ui/app.py", line 392, in run_raiden_service raiden_1 | check_ethereum_confirmed_block_is_not_pruned( raiden_1 | File "/usr/local/lib/python3.8/site-packages/raiden/ui/checks.py", line 93, in check_ethereum_confirmed_block_is_not_pruned raiden_1 | raise RaidenError( raiden_1 | raiden.exceptions.RaidenError: The ethereum client does not have the necessary data available. The client can not operate because the prunning strategy is too agressive. Please make sure that at very minimum 7 blocks of history are available.

Karl Bartel
@karlb
The warning is there because we were a bit late to increase the known-good max version. The commit above has just been added yesterday and is not in 2.0.0a1.
Diego Ferrer
@Ferret-san
What would be the best way to add custom deployments of the raiden contracts to the raiden-services and subsequently to the RBS?
3 replies
Diego Ferrer
@Ferret-san
Has anybody ran into this issue with the current master branch of raiden-services?:
raise ContractSourceManagerVerificationError( raiden_contracts.contract_source_manager.ContractSourceManagerVerificationError: checksum of ECVerify.sol does not match. got 4f453c3568d3ab07593b84c5f976123e669dc4315820f8f28ff93b64837194a3 != expected {expected_checksum}
7 replies
yoavw
@yoavw:matrix.org
[m]
Is there a way to prove to an L1 contract that a payment was done on Raiden? I'm not talking about closing the channel, but keeping it open and just proving to a contract that it happened. Doesn't matter if it's gas-inefficient, as I only need it for rare dispute resolutions.
Raphael Lullis
@raphael:communick.com
[m]
Hey guys... I'm running raiden (latest alpha) on docker as part of a docker-compose setup and and it seems that the web UI does not honor the "ETH_RPC_ENDPOINT" environment variable. Raiden starts fine, but the web UI shows an error because it is trying to connect to localhost:8545.
I also noticed an inconsistency with the environment variables/cli. The cli parameter to specify the network is --network-id, but I had to use RAIDEN_CHAIN_ID to be able to start raiden and connect to goerli
Jacob Stenum Czepluch
@czepluch

Is there a way to prove to an L1 contract that a payment was done on Raiden? I'm not talking about closing the channel, but keeping it open and just proving to a contract that it happened. Doesn't matter if it's gas-inefficient, as I only need it for rare dispute resolutions.

@yoavw:matrix.org Do you mean for a specific payment?

2 replies
Diego Ferrer
@Ferret-san
Is there a reason as to why the contract_manager looks for the contract data in the script path and not the normal path?
Diego Ferrer
@Ferret-san
Also, is the JSON data for the contracts supposed to be placed inside of the DATA folder for the RSB? seems like the containers are unable to find the files so I'm guessing that I either don't have the files in the right place, or the docker files don't copy + paste the deployment files into the containers when they are being built
Paul Lange
@palango
@Ferret-san What error do you see? some problem with one of the services (MS/PFS) or the matrix server?
Ulrich Petri
@ulope
@Ferret-san The data path of the raiden-contracts package is completely unrelated to the RSB data mount point.
The deployment JSON files are distributed inside the raiden-contracts package and looked up from within that.
The RSB data directory is used to store (among other things) the Postgres database files, PFS / MS databases and logfiles.
But yes, what @palango said. Can you post the error message you're seeing?
Diego Ferrer
@Ferret-san
Ok, so this is the error I get from the PFS and MS containers:
[error ] No deployed contracts were found at the default registry contracts_version=None
Now, I've added some print statements to my fork of raiden-contracts in order to do some debugging, and here's the path in which it is looking for the files:
/usr/local/lib/python3.7/site-packages/raiden_contracts/data/
Still trying to figure out why it can't find the files
Diego Ferrer
@Ferret-san
Could it be that the issue is dependent on the ETH_RPC that's being used by the containers?
Maybe I can try running things locally from the raiden-services repo first before trying stuff out with the RSB
vhcleite
@vhcleite

hi guys! I'm starting with raiden for a project of mine and I'm having an error to make a payment. This is my first payment so I openned a channel with raiden hub on goerli and deposited 1000 WIZ on it. When I use the api endpoint to make the payment the following error happens

{
"errors": "Payment couldn't be completed because: PFS returned an error while trying to fetch user information: \n('Pathfinding Service returned malformed json in response', {'http_code': 404})"
}

so I checked de PFS that I configured and for me it looks ok... I used the following command to run raiden:

./raiden-v2.0.0rc3-linux-x86_64 --pathfinding-service-address=https://pfs.demo001.env.raiden.network --matrix-server=https://transport.demo001.env.raiden.network --eth-rpc-endpoint "https://goerli.infura.io:443/v3/xxxxxxxx" --api-address "http://localhost:5010" --keystore-path ~/.ethereum/keystore --address 0x3FFfbda3CaD6140bc13E65156e97E9583b2f8E20 --network-id goerli --environment-type development --log-file node-949e47-goerli.6thJune2020.log --log-config "raiden:debug" --accept-disclaimer --enable-monitoring

I also tried to run raiden without de PFS with de following command but I got a never ending request when making the payment:

./raiden-v2.0.0rc3-linux-x86_64 --routing-mode=private --matrix-server=https://transport.demo001.env.raiden.network --eth-rpc-endpoint "https://goerli.infura.io:443/v3/xxxxxxxxxxxxxx" --api-address "http://localhost:5010" --keystore-path ~/.ethereum/keystore --address 0x3FFfbda3CaD6140bc13E65156e97E9583b2f8E20 --network-id goerli --environment-type development --log-file node-949e47-goerli.6thJune2020.log --log-config "raiden:debug" --accept-disclaimer --no-enable-monitoring

OBS: I used the last non official version because I'm using infrura and there is the incompatibility with GETH 1.1.9.

Someone could give me a help?

Diego Ferrer
@Ferret-san
Alright, I can't seem to be able to get the RSB to run, is there any way or chance that there's a documentation that explains how to run my local version of raiden-services so that I can at least test things out with the MS/PFS/MSRC? I think it would be simpler and easier to only have to debug a couple of containers for the services instead of everything else that is part of the RSB
Jacob Stenum Czepluch
@czepluch
Hey @Ferret-san and @vhcleite we've been very busy lately. Hopefully we'll have soon to catch up with you guys soon. Do you still experience these problems?
vhcleite
@vhcleite

Hello Guys. I just tried the same command i was using before and got another error.

Message from the Pathfinding Service:
Welcome!
Raiden is running in development mode

You are connected to the 'goerli' network and the DB path is: /home/victor/.raiden/node_3fffbda3/netid_5/network_5a5cf4a6/v27_log.db
Traceback (most recent call last):
File "raiden/ui/cli.py", line 721, in _run
File "raiden/ui/runners.py", line 18, in run_services
File "raiden/ui/app.py", line 457, in run_raiden_service
File "raiden/raiden_service.py", line 480, in start
File "raiden/raiden_service.py", line 598, in _start_transport
File "raiden/network/transport/matrix/transport.py", line 556, in start
File "raiden/network/transport/matrix/transport.py", line 834, in _initialize_first_sync
File "raiden/network/transport/matrix/client.py", line 604, in blocking_sync
File "raiden/network/transport/matrix/client.py", line 796, in _handle_responses
File "raiden/network/transport/matrix/transport.py", line 922, in _reject_invite
File "raiden/network/transport/matrix/transport.py", line 1426, in retry_api_call
File "raiden/network/transport/matrix/transport.py", line 1414, in retry_api_call
File "matrix_client/api.py", line 234, in send_state_event
File "raiden/network/transport/matrix/client.py", line 183, in _send
File "matrix_client/api.py", line 691, in _send
matrix_client.errors.MatrixRequestError: 400: {"errcode":"M_UNKNOWN","error":"Expected UserID string to start with '@'"}
FATAL: An unexpected exception occurred. A traceback has been written to /tmp/raiden-exception-2021-06-10T11-093mu1zu88.txt
400: {"errcode":"M_UNKNOWN","error":"Expected UserID string to start with '@'"}

Should I try to create a new account with raiden wizard to see with this UserID error goes away? Do you know why I haven't experienced this error before when I haven't changed anything from sunday to today?

Jacob Stenum Czepluch
@czepluch
@vhcleite Which version are you using of Raiden?
vhcleite
@vhcleite
@czepluch I was using raiden-v2.0.0rc3-linux-x86_64, but downloaded the release raiden-v2.0.0-linux-x86_64.tar.gz and the same error happened
maybe it's backwards compatibility issue? The account I am using was created by raiden wizard
Jacob Stenum Czepluch
@czepluch
It should still work. When do you experience this error?
vhcleite
@vhcleite

@czepluch I erased the files that raiden wizard created and made a fresh restart with a new account. It initialized OK now. However, I still can't do a payment beacause of the PFS. When I do the "POST payment", raiden logs:

2021-06-12 21:57:51.777257 [warning ] PFS returned an error while trying to fetch user information:
('Pathfinding Service returned malformed json in response', {'http_code': 404}) [raiden.routing]
2021-06-12 21:57:51.779461 [error ] Error processing request [raiden.api.rest_utils] errors=Payment couldn't be completed because: PFS returned an error while trying to fetch user information:
('Pathfinding Service returned malformed json in response', {'http_code': 404}) status_code=<HTTPStatus.CONFLICT: 409>
2021-06-12 21:57:51.783084 [info ] 127.0.0.1 - - [2021-06-12 18:57:51] "POST /api/v1/payments/0x95B2d84De40a0121061b105E6B54016a49621B44/0x1F916ab5cf1B30B22f24Ebf435f53Ee665344Acf HTTP/1.1" 409 405 1.907317 [raiden.api.rest.pywsgi]

Did I configure PFS wrong? I' m using:
matrix-server = "https://transport.demo001.env.raiden.network"
pathfinding-service-address = "https://pfs.demo001.env.raiden.network"

vhcleite
@vhcleite
I started my node with this command:
./raiden-v2.0.0-linux-x86_64 --pathfinding-service-address=https://pfs.demo001.env.raiden.network --matrix-server=https://transport.demo001.env.raiden.network --eth-rpc-endpoint "https://goerli.infura.io:443/v3/xxxxxxxxxxxxxx" --api-address "http://localhost:5010" --keystore-path ~/.ethereum/keystore --network-id goerli --environment-type development --accept-disclaimer --enable-monitoring
3 replies
vhcleite
@vhcleite

I didn't find a solution for the error above so I tried to run raiden in the private routing-mode with the following command:

./raiden-v2.0.0-linux-x86_64 --routing-mode private --matrix-server=https://transport.demo001.env.raiden.network --eth-rpc-endpoint "https://goerli.infura.io:443/v3/xxxxxxxxxxxxxxxxxxxxxxx" --api-address "http://localhost:5001" --keystore-path ~/.ethereum/keystore --network-id goerli --environment-type development --accept-disclaimer

Now, when I make the payment I receive:

{
"errors": "Payment couldn't be completed because: lock expired"
}

This is the channel in which I tried to make the payment:

[
{
"settle_timeout": "500",
"total_withdraw": "0",
"state": "opened",
"token_address": "0x95B2d84De40a0121061b105E6B54016a49621B44",
"token_network_address": "0xF6955f8C75270dfF5E0dBd9F1E5b158f47730fE1",
"channel_identifier": "96",
"partner_address": "0x1F916ab5cf1B30B22f24Ebf435f53Ee665344Acf",
"reveal_timeout": "50",
"total_deposit": "200000000000000000000",
"balance": "200000000000000000000",
"network_state": "unknown"
}
]

According to Raiden documentation my node shouldn't be sending the protocol messages, right?