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
Harry Harrold
@HarryHarrold2_twitter
Hi - are there any significant marketing plans for the Raiden Network on the near horizon? I've been surprised by the lack of attention the project's had by 'influencers' (and buyers) given the super-bullish L2 narrative at the moment.
Sagato
@Sagato
heeelo
I have a question. If I were a smart contract developer, how would raiden network support me in that, are there any SDK's or how does it actually work? What is different to for example matic? Are there any comparisons? Greets
Jacob Stenum Czepluch
@czepluch
@Sagato It's a bit unclear to me what you mean exactly. But in general, Raiden is an offchain payment solution that works out of the box and offers an API for interaction.
Jason Smythe
@JasoonS
image.png
I'm getting errors when running a raiden node (see image above). Any ideas?
Jason Smythe
@JasoonS
How easy is it to run your own pathfinding service and run raiden against something like ganache? (running against goerli is expensive because raiden makes lots of rpc requests, and rpc endpoint providers like infura and alchemy have limited free plans if you are doing lots of development)
Ulrich Petri
@ulope
@JasoonS Thanks for bringing this to our attention. The dev PFS should be coming back online in a few minutes.
As for running one yourself, that's pretty straight forward. The documentation should get you started: https://raiden-services.readthedocs.io/en/latest/
We don't recommend (and don't support) running against ganache / eth-tester etc. since they behave quite differently than "real" blockchains.
But running your own goerli node is quite easy. A fresh sync only takes an hour or two.
Jason Smythe
@JasoonS
Why is the address I get when I use the raiden light client dapp (https://lightclient.raiden.network/) different to the address that I use on metamask? How is the address that I have in that app linked to my controlling eth address (from metamask)?
34 replies
Jason Smythe
@JasoonS
hub-is-offline.gif
^ it seems like the hub or monitoring service is down for the goerli lightclient.
Jason Smythe
@JasoonS
image.png
agatsoh
@agatsoh
@JasoonS might mostly be because of the disjoint transport servers which do not communicate with each other
1 reply
Could you open the network tab and on any transport request tell which server it is querying ?
It either would be transport.demo001.env.raiden.network or transport.transport0X.raiden.network(where X is a number)
Jason Smythe
@JasoonS

Hi @andrevmatos , I've started integrating the raiden-ts library into my frontend, I installed version 0.15 from npm. But I'm having issues with the bundler. I have added both of these babel plugins ("@babel/plugin-proposal-nullish-coalescing-operator", "@babel/plugin-syntax-optional-chaining") and this preset ("@babel/preset-typescript"), but the error persists:

(I can't seem to paste nicely formatted code into gitter - I'd swear it was a chat made for non-programmers... )

image.png
Jason Smythe
@JasoonS
I also tried the plugin @babel/plugin-proposal-optional-chaining, it doesn't seem to help though unfortunately
Jason Smythe
@JasoonS
I have created an issue in the repo with steps to reproduce: raiden-network/light-client#2540
André Vitor de Lima Matos
@andrevmatos
Hi, @JasoonS . Our codebase is bundled targeting whatever is supported by latest NodeJS LTS and stable browser versions. Currently, it targets ES2020 (which is quite new) and have ESM (not usable directly due to issues on TypeScript implementation, but importable and tree-shakeable by TS and Webpack projects) and CommonJS builds (usable directly on NodeJS projects, like raiden-cli). We used to have a legacy ES5 build as well, but decided to ditch it in order to push for the end-user projects to customize their build options and adapt to the latest and most efficient language syntaxes whenever possible. We'll be looking in your issue, but seems like your babel project isn't properly being able to recognize these newish syntax.
Meanwhile, you should be able to do a legacy ES6 build by updating the target at raiden-ts/tsconfig.cjs.json and rebuilding. With a single-line patch, the codebase can also be made compatible with ES5 target if needed, but I'd say it'd be worth it to get your project compatible with more modern dependencies, as you'll get goodies by transpiling whatever needed at the end, instead of using legacy libs builds which may end up bundled in a non-optimized manner.
Jason Smythe
@JasoonS
Hi @andrevmatos , thanks, it might be worth checking out the issue - it will severely impact who can use the library. I'm using the latest react-scripts from create-react-app, and they have had ES2020 support for some time and is a very well maintained project. It is the first library npm library that I've ever come across that doesn't work with react-scripts. Anyway, I'll try bundle it myself
André Vitor de Lima Matos
@andrevmatos
@JasoonS this should fix your problem. Please, let me know if there's anything else we can help you.
wynstrol
@wynstrol
Hi guys, I've been enjoying learning how raiden works. Last week everything was going smoothly however this morning I've been unable to start my nodes correctly. Is the pathfinding service down by any chance? I took a screenshot of the error and will post it below.
RaidenPathfindingError.png
Tunji Abioye
@Tunji17
Hi guys, i ran into some issues creating a payment where raiden just keeps retrying endlessly even as the second node is online
Tunji Abioye
@Tunji17
image.png
Jason Smythe
@JasoonS
Hi, I'm also trying to get the pathfinding service working locally but running into the following error with the monitoring service (will post an image). The monitoring service keeps crashing. I am using the docker-compose from here (just removing things unrelated to goerli and making sure all the keystores are setup correctly) - https://github.com/raiden-network/raiden-services/blob/master/deployment/docker-compose.yml .
image.png
1 reply
How do I register an address in the service registry for the monitoring service?
Karl Bartel
@karlb
There is the service-registry script in the raiden-services repo. Use that to register your service.
service-registry register --help
Jason Smythe
@JasoonS
Ah, amazing, I'll try that, thank you @karlb :)
Jason Smythe
@JasoonS
Hi guys, a friendly reminder that hosted testnet pathfinding service is still down for some reason
Tunji Abioye
@Tunji17
image.png

Hi guys, please i am getting this error when i try to create a channel using axios with this payload, Any Idea what could be wrong?

{
"reveal_timeout": "50",
"partner_address": "0xF62561B1edE126Da1dc7110154415706b9314e12",
"token_address": "0xbf9be54Df2001E6Bd044cED0E508d936A9d38b1D",
"total_deposit": "1000",
"settle_timeout": "500"
}

André Vitor de Lima Matos
@andrevmatos
@JasoonS the PFSs aren't down. You probably are experiencing raiden-network/light-client#2521 , which is caused by us currently having two disjoint transport test networks, one stable (older, on demo001.env) and one bleeding edge (on transport0x servers), and depending on the launch options and what's persisted in state, you may end up on a transport network and trying to communicate with PFSs in the other and failing to do so, since the transport networks don't talk with each other. We're currently actively working on that issue in order to properly split the networks, so you only the correct transport/pfss are picked up on each, but current workaround is to explicitly state the MATRIX_SERVER and PFS through client options and envvars you want to use. Please, refer to raiden-dapp/.env* files for examples on how to do so with the dApp, and --help on raiden-cli/raiden-py for the full clients.
André Vitor de Lima Matos
@andrevmatos
@Tunji17 that error should only happen if you either already have a non-settled channel with that partner, or don't have enough of that token to deposit. What's the raiden address from which you're trying to open that channel? Here is the TokenNetwork contract for that token, which probably is the contract on which that tx is failing.
Tunji Abioye
@Tunji17
@andrevmatos thanks for the response, I have not created any channel with that partner previously also i confirmed i have about 20,000 token in the raiden address i am using 0x187838A3e79440eAc1546301cEBEE73CAD051A53
Jacob Stenum Czepluch
@czepluch
@Tunji17 Did you manage to get it to work yet?
Tunji Abioye
@Tunji17
@czepluch Yeah i realized i was calling create channel with an array of addresses in a loop, if the address occurs more than once in the array, the raiden server throws that error. i have a check for if the channel already exists but it seems to not catch it cos create channel is a long running task i think.
Santos Caminiti
@Santos_332_twitter
Im not sure which is the best chat to talk with the team.. but is there any chance they could lock some of their coins in a liquidity pool on uniswap? They have 50% of the supply unlocked which is troubling and their isnt much liquidity. Being a LP on uniswap would solve both problems
Jacob Stenum Czepluch
@czepluch
@Santos_332_twitter I will bring it up
wynstrol
@wynstrol
Hey everyone. I'm currently working on the raiden node and light client stuff and I just have a couple of questions I need a bit of clarification with. Any help would be much appreciated. Will space them out so its a bit easier to reply to.
I want to confirm that I am using the correct raiden node version. Currently I use raidennetwork/raiden:develop. Is this version the correct one to use for ongoing development? Should I remove the locally cached version to get the latest develop version?
When setting up the nodes I use https://pfs.demo001.env.raiden.network for my pathfinding service address and https://transport.demo001.env.raiden.network for my matrix server. I got theses addresses from the .env.production file in the light client. Are these addresses usable?
When starting up my light client I can only seem to choose 1 of my raiden nodes as a hub and the other 2 which I have running do not show up. Is there any thing I am unaware of that would cause this? I currently run the nodes locally on ports 5001, 5002, and 5003.
8 replies
The other problem I get when choosing hubs in the light client is that semi regularly it will say that the hub I want is currently offline but I have it running so not sure how it could be offline? Clearing my storage history on the port I use for the light client sometimes fixes it but its not consistent and doesn't seem like a viable solution. I also have no idea why this would resolve the problem.
1 reply
wynstrol
@wynstrol
Just an update on what I was struggling with. It was a matrix server issue. Basically I was using 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.