main.js
carefully, the whole workflow is there, although somehow wrapped in some jQuery callbacks to keep the UI consistent, but with some jquery knowledge/homework, you can follow it there
@andrevmatos
You request it by signing the zero-balance proof and doing the request, it'll then reply with a 402 response, with your last balance proof on headers/cookies, which you then (in the 2nd case) is supposed to load and
verifyProof
My problem is to trigger the server to send me the latest balance proof. So from the very beginning I do this steps: loadChannelFromBlockchain and then request the resource? Requesting the server with which data? With all the 7 RDN-* header? Which value has the RDN-Payment header to have? If I send a number there I get 500 internal server error back with this message in the body "Payment must be an integer". I do not receive my latets balance proof within headers or cookies. Mybe because I never did a persistent transaction between this two parties?
Please, read
main.js
carefully, the whole workflow is there, although somehow wrapped in some jQuery callbacks to keep the UI consistent, but with some jquery knowledge/homework, you can follow it there
I will try this again. Reading code unfortunately isn't the best way for me learning and understanding new technology. Documentation would be much easier for me.
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
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.
demo
site is running exactly the setup you see in the docker
folder in repository)
Hello Community, can you guys please look at my specific problem with the uRaiden Example: raiden-network/microraiden#491
Thanks in advance.
docker
folder containing our exact in-production environment at demo.micro.raiden.network