10**8 WEI. See the webui-related instructions from https://github.com/raiden-network/microraiden#quick-start
receiverrole needs to run the uRaiden Python proxy server and it has to be online, otherwise it cannot receive offchain payments.
senderto use the web interface, see the link to the Readme quick start from above regarding the webui. You can run the proxy examples shown here: http://microraiden.readthedocs.io/en/docs-develop/applications/pyserver/usage.html (wikipaydia, demo_proxy) to see the paywall web interface.
Thanks for the quick response, the proxy is up and running. I connected 2 accounts via the uraiden openChannel function and added some balance to open the channel. the channel block is the same for both accounts. This means they're in the same channel right?
I don't really understand the sender/receiver part. A sender can also be a receiver right? I created a image to clear things up.
sender(e.g. A) to a
receiver(e.g.) B, so : A -> B. Raiden Network has bidirectional channels and you can send A <-> B (even if you don't have a channel opened directly between A and B).
" But just merging an EIP doesn't do anything. This EIP doesn't require a hard fork. It just proposes a convention.
You have to convince client developers to implement the proposed convention.
store microraiden signatures on chain?