Skip to content
This repository was archived by the owner on May 13, 2022. It is now read-only.

Commit a6bfa5e

Browse files
Merge pull request #406 from loredanacirstea/readme-0.2.0
Update main Readme, remove outdated docs for 0.2.0
2 parents a44ea31 + ca5a597 commit a6bfa5e

File tree

2 files changed

+8
-337
lines changed

2 files changed

+8
-337
lines changed

README.md

Lines changed: 8 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@
55

66
µRaiden is an off-chain, cheap, scalable and low-latency micropayment solution.
77

8+
[µRaiden documentation](http://microraiden.readthedocs.io/en/latest/)
9+
810

911
## Smart Contract
1012

@@ -54,17 +56,15 @@ The main differences between the Raiden Network and µRaiden are:
5456

5557
µ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.
5658

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.
5860

5961
### Off-chain transactions
6062

61-
A visual description of the process can be found [here](/docs/dev_overview.md#off-chain-messages).
62-
6363
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.
6464

6565
### Closing and settling channels
6666

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).
6868

6969
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.
7070

@@ -79,15 +79,12 @@ Try out the µRaiden demo and build your own customized version, following our i
7979

8080
## Quick Start
8181

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)):
8383

8484
```bash
8585
virtualenv -p python3 env
8686
. env/bin/activate
87-
git clone git@github.com:raiden-network/microraiden.git
88-
cd microraiden/microraiden
89-
pip install -r requirements-dev.txt
90-
pip install -e .
87+
pip install microraiden
9188
```
9289

9390
* install the WebUI component for the paywall examples
@@ -99,35 +96,16 @@ cd microraiden/microraiden/webui/microraiden
9996
npm i && npm run build
10097
```
10198

102-
* run the Proxy component (more details [here](/microraiden/README.md)):
99+
* run the Proxy component:
103100

104101
For an overview of parameters and default options check https://github.com/raiden-network/microraiden/blob/master/microraiden/microraiden/click_helpers.py
105102

106103
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.
108104

109105
```
110106
cd microraiden
111107
python -m microraiden.examples.demo_proxy --private-key <private_key_file> start
112108
```
113109

114110
* Go to the paywalled resource pages:
115-
- http://localhost:5000/doggo.jpg
116-
117-
118-
## How To
119-
120-
You can use the configuration for the above default example for creating your own payment channel service.
121-
122-
* µRaiden Paywall Tutorial:
123-
- Proxy: [/docs/proxy-tutorial.md](/docs/proxy-tutorial.md)
124-
- Web Interface: soon
125-
* Various paywall [examples](/microraiden/microraiden/examples)
126-
127-
128-
## Development Documentation
129-
130-
* Components Overview: [/docs/dev_overview.md](/docs/dev_overview.md)
131-
* µRaiden Service Setup: [/microraiden/README.md](/microraiden/README.md)
132-
* Smart Contracts Setup: [/contracts/README.md](/contracts/README.md)
133-
* JS/TS client library: [NPM package README.md](/microraiden/microraiden/webui/microraiden/README.md)
111+
- http://localhost:5000/teapot

contracts/README.md

Lines changed: 0 additions & 307 deletions
This file was deleted.

0 commit comments

Comments
 (0)