main.js is demo code, so it's part of the documentation. Nonetheless, these details are in all the extensive µRaiden documentation, both the server, m2m client, microraiden-js lib and demo documentation, but of course we're always open to PRs to improve it
@andrevmatos I got the 'hello' the first time! Cool! Thank you very very much! :) But I have the next problem: Trying it again I get the error "TypeError: this.channel.proof.balance.plus is not a function". This comes from the function incrementBalanceAndSign within the TS library. Do you know whats the point here?
the closing signature is the one by the receiver, saying it agrees with a given BP, iff the sender requested it because it wanted to do a cooperative close. without closing signature from receiver, it's a uncooperative close, which will start the settle timeout, after when the sender will be able to settle
wait for the settle timeout to expire and do the settling
you need to wait for the settle timeout, then call
settleChannel. You're always able to load the channel as much times as needed. loadChannelFromBlockchain is just a helper (as I said), which do some smart checks to avoid you loading a channel which is inside the settle timeout (as you can't do anything with it anyway), allowing you to e.g. open a new channel and interact with it. If you forget the new channel and call this function again after settle timeout expires, it'll pick the old, to-be-settled channel again so you can settle it
"server won't accept this channel.
Please, close+settle+forget, and open a new channel"
this message is displayed on both chrome and firefox with metamask on the ropsten test network while accessing demo https://wikidemo.micro.raiden.network/wiki/Main_Page . it appears after depositing the TKN tokens and trying to sign them. Please suggest.
@rajjha10_twitter as I answered in your opened issue (#489), it was caused by the ropsten constantinople consensus issue between parity and geth. resync is underway, and everything should be working again soon. As it was stated in the log messages, despite an issue as big as a consensus issue in the ethereum node, the user's money (both client and server) were in their own hands, no custody involved, so the users, through a synced node in whichever fork they were, would be able to close the channel and reclaim their tokens, demonstrating the power of µRaiden and Raiden payment channels technology
@rajjha10_twitter yes, that should be about it. The documentation holds on these matters, and the error you're seeing locally is caused by these chainsplits/setup/deploy issues, not codewise (FYI
demo site is running exactly the setup you see in the docker folder in repository)
what is the current status of raiden, does it have its own mainnet, is it on the eth mainnet? i try to write proof of concept micropayment thesis and would like to use either lightning btc or raiden, but your raidos raidex raidn-netw and uradien, is overwhelming, could you shed light into what i would use now and which chains/testnets it tackles?
@LefterisJP you seem to be at the core of dev
hey @hivemall for raiden questions please go to the raiden channel: https://gitter.im/raiden-network/raiden
this is only for uRaiden.
You can use Raiden right now on public or private testnets. It's completely functional
There is simply no mainnet deployment yet. For that I can't give a date.
You can ofcourse use Raiden in your thesis. Our specification is online: https://raiden-network-specification.readthedocs.io/en/latest/
and the docs on how to get started are also online: https://raiden-network.readthedocs.io/en/latest/
and the docs on how to get started are also online: https://raiden-network.readthedocs.io/en/latest/
Hello Community, can you guys please look at my specific problem with the uRaiden Example: raiden-network/microraiden#491
Thanks in advance.
I tried on Mac and then switched to Ubuntu, but the pip install requirements keeps on getting errors.
Hi, @phzietsman . If you look into the repository, you'll see a
You may want to adapt it a little, to remote e.g. SSL from nginx, etc, but it's a fully working solution to get the dependencies and environment right for µRaiden
docker folder containing our exact in-production environment at demo.micro.raiden.networkYou may want to adapt it a little, to remote e.g. SSL from nginx, etc, but it's a fully working solution to get the dependencies and environment right for µRaiden
Continue with the good work!
@1nfinite Hi. Infura is already used by the web/js client, through Metamask. About the server, it requires filters, which infura doesn't support currently. You could look into Raiden's implementation of
StatelessFilters, and try to port the idea to µRaiden, but right now it's not an usecase we support
I would love to know if you have any updates for MicroRaiden since the last release of 0.2.5? Given that I am mostly interested on unidirectional payment scenarios, just wondering if we can base our development efforts out of MicroRaiden or will Ithaca provide more capabilities in this unidirectional payment situation. Can someone clarify? Thanks in advance.