You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 13, 2022. It is now read-only.
@@ -54,17 +56,15 @@ The main differences between the Raiden Network and µRaiden are:
54
56
55
57
µRaiden uses its own token for payments which is both [ERC20](https://github.com/ethereum/EIPs/issues/20) and [ERC223](https://github.com/ethereum/EIPs/issues/223) compliant.
56
58
57
-
In a nutshell, clients (subsequently called "senders") wanting to access a provider's payable resources, will [open a micropayment channel](/contracts#opening-a-transfer-channel) with the provider ("receiver") and fund the channel with a number of tokens. These escrowed tokens will be kept by a third party contract that manages opening and closing of channels.
59
+
In a nutshell, clients (subsequently called "senders") wanting to access a provider's payable resources, will [open a micropayment channel](http://microraiden.readthedocs.io/en/latest/contract/index.html#opening-a-transfer-channel) with the provider ("receiver") and fund the channel with a number of tokens. These escrowed tokens will be kept by a third party contract that manages opening and closing of channels.
58
60
59
61
### Off-chain transactions
60
62
61
-
A visual description of the process can be found [here](/docs/dev_overview.md#off-chain-messages).
62
-
63
63
However, the heart of the system lies in its sender -> receiver off-chain transactions. They offer a secure way to keep track of the last verified channel balance. The channel balance is calculated each time the sender pays for a resource. He is prompted to sign a so-called balance proof, i.e., a message that provably confirms the total amount of transfered tokens. This balance proof is then sent to the receiver's server. If the balance proof checks out after comparing it with the last received balance and verifying the sender's signature, the receiver replaces the old balance value with the new one.
64
64
65
65
### Closing and settling channels
66
66
67
-
A visual description of the process can be found [here](/contracts#closing-a-channel).
67
+
A visual description of the process can be found [here](http://microraiden.readthedocs.io/en/latest/contract/index.html#closing-a-channel).
68
68
69
69
When a sender wants to close a channel, a final balance proof is prepared and sent to the receiver for a closing signature. In the happy case, the receiver signs and sends the balance proof and his signature to the smart contract managing the channels. The channel is promptly closed and the receiver debt is settled. If there are surplus tokens left, they are returned to the sender.
70
70
@@ -79,15 +79,12 @@ Try out the µRaiden demo and build your own customized version, following our i
79
79
80
80
## Quick Start
81
81
82
-
* install the Proxy component (more details [here](/microraiden/README.md)):
82
+
* install the Proxy component (more details [here](http://microraiden.readthedocs.io/en/latest/proxy-tutorial.html)):
* install the WebUI component for the paywall examples
@@ -99,35 +96,16 @@ cd microraiden/microraiden/webui/microraiden
99
96
npm i && npm run build
100
97
```
101
98
102
-
* run the Proxy component (more details [here](/microraiden/README.md)):
99
+
* run the Proxy component:
103
100
104
101
For an overview of parameters and default options check https://github.com/raiden-network/microraiden/blob/master/microraiden/microraiden/click_helpers.py
105
102
106
103
For chain and contract settings change: https://github.com/raiden-network/microraiden/blob/master/microraiden/microraiden/config.py
107
-
This is where you integrate custom contract & token deployments.
0 commit comments