https://transport.demo001.env.raiden.network as our matrix server address and this was causing the inconsistencies. However I changed it to transport.transport01.raiden.network and the issues were gone. Still not sure why one address would work and the other doesn't (if someone could explain I'd appreciate it) but for now I have no issues.
1 reply
SecretRegistry has a cumulativeGasUsed of 292942 and TokenNetworkRegistry has a cumulativeGasUsed of 8000000 which is way above the 8000000 gas limit, increasing the gas limit to 8300000 or anything greater that 8000000 throws exceeds block gas limit error which i am still struggling to find a way out
got it! you can also check against what we're doing in our integration test chains and see where your chain differs from ours.
btw, what geth version are you on?
1.9.21
Hello everyone, please what version of raiden is compatible with
raiden-contracts==0.25.0?
Hi all. I have the same question. I am running the raidennetwork/raiden:v0.200.0-rc9 container against the private network created in ethereum/client-go:v1.9.21. I've managed to successfully deploy all the required contracts under the contract version 0.25.0, but when starting the raiden client, I get the following error:
[UserDeposit] Address ... has wrong code. This may happen if Raiden is configured to use an unsupported version of the contracts.
ReturnCode.SMART_CONTRACTS_CONFIGURATION_ERROR
Any help will be appreciated.
oh, can you also try with the previous geth version? we're currently investigating a potential incompatibility with 1.10.x raiden-network/raiden#6872
Am I correct in thinking that I won't be able to use third-party RPC services (infura, alchemy) until raiden-network/raiden#6872 is resolved?
I'm currently getting this error: raiden.exceptions.RaidenError: You need a Byzantium enabled ethereum node. Parity >= 1.7.6 <= 2.7.2 or Geth >= 1.9.7 <= 1.9.11 but you have 1.10.1 EthClient.GETH
Hi everyone,
Please help me to resolve the following problem. I am running Raiden v1.2.0 on Private Network set up via Geth v1.9.21. I have successfully deployed all the required contracts under raiden-contracts version 0.33.0 which I captured by calling grep 'CONTRACTS_VERSION = ' -r env/lib/python3.7/site-packages/raiden_contracts command. While deploying the contracts I have also captured all the addresses returned in the output. When I run the raiden client, it successfully starts and then immediately fails with error:
[UserDeposit]Address 0xF364d2373B54A4E77dc17c85D652Ce3B8A990d4D does not contain code. This may happen if an external ERC20 smart contract selfdestructed, or if the configured address is misconfigured, make sure the used address is not a normal account but a smart contract, and that it is deployed to 4321.
ReturnCode.SMART_CONTRACTS_CONFIGURATION_ERRORThe user deposit contract address reported in the error message is the one that was shown after the contract deployment, and is also written in data_0.33.0/deployment_services_private_net.json file:
"UserDeposit": {
"address": "0xF364d2373B54A4E77dc17c85D652Ce3B8A990d4D",
"transaction_hash": "0x5a40d0767e4254526b33a3d8e390bc0b411432497536f743da79c0212e038209",
"block_number": 53,
"gas_cost": 1899008,
"constructor_arguments": [
"0xD030fB5f2B02aA38c7Ee39A36148B09e1dCacA78",
115792089237316195423570985008687907853269984665640564039457584007913129639935
]
},So at this point I am a little confused, and would really appreciate any help or advice.
web3.eth.getCode() showed all the required contracts has been deployed correctly and has their byte-code returned by the getCode call. As soon as I accomplished it, the error message changed to:[UserDeposit] Address 0x372c0c8894BbCCEFEEd2251Bbd828Ab6207b304d has wrong code. This may happen if Raiden is configured to use an unsupported version of the contracts.
ReturnCode.SMART_CONTRACTS_CONFIGURATION_ERROR
