I've opened the issue on Github. raiden-network/light-client#2710. Anyone have any clue why it's not working?
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.
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:
- 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
- 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
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.FATAL2021-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]
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.
raise ContractSourceManagerVerificationError(
raiden_contracts.contract_source_manager.ContractSourceManagerVerificationError: checksum of ECVerify.sol does not match. got 4f453c3568d3ab07593b84c5f976123e669dc4315820f8f28ff93b64837194a3 != expected {expected_checksum}
7 replies
--network-id, but I had to use RAIDEN_CHAIN_ID to be able to start raiden and connect to goerli
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
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.
[error ] No deployed contracts were found at the default registry contracts_version=NoneNow, 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
raiden-services repo first before trying stuff out with the RSB
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?
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
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?
@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"
./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
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?