Use Raiden to enrich your dApp with nearly instant, low-fee and scalable payments. It comes with an easy-to-use API and is compatible with the Ethereum ERC20 token standard.
The WebUI allows users to easily access the main functionalities of the Raiden Network via a web interface.
Look at the codeWith Raiden it's easy to build an accountless pay-per-use paywall infrastructure.
Look at the codeRaiden can be used for making instant IoT machine-to-machine (M2M) micropayments.
Look at the codeIncentivized, decentralized P2P live streaming with micropayments using Raiden, introducing “Proof-of-Stream-Payment”.
WiFi internet sharing/ WiFi access on-the-go (paid in 100kb chunks) using Raiden, inspired by the Freifunk project.
Decentralized streaming and tipping platform with a pay-as-you-go model using Raiden payments through a BurnerWallet integration.
Rock-paper-scissors game with robots and micropayments on the Raiden Network.
A client library to interact with the Raiden API, written in Golang.
LED matrix display controlled by ESP8266 to display messages paid for through Raiden.
Race between four characters, which can be moved forward by receiving tokens.
The Raiden API helps you to easily access the Raiden Network's functionalities, such as joining a token network, opening and closing channels, depositing tokens and executing payments.
Learn more about it in the API walkthrough→
Example Request
GET /api/V1/channels HTTP/1.1
Host: localhost:5001
Example Response
HTTP/1.1 200 OK
Content-Type: application/json
[
{
"token_network_identifier":"0xE5637F0103794C7e05469A9964E4563089a5E6f2",
"channel_identifier": 20,
"partner_address": "0x61C808D82A3Ac53231750daDc13c777b59310bD9",
"token_address": "0xEA674fdDe714fd979de3EdF0F56AA9716B898ec8",
"balance": 25000000,
"total_deposit": 35000000,
"state": "opened",
"settle_timeout": 100,
"reveal_timeout": 30
}
]
Example Request
POST /api/V1/payments/(token_address)/(target_address) HTTP/1.1
Host: localhost:5001
Content-Type: application/json
{
"amount": 200
}
Example Response
HTTP/1.1 200 OK
Content-Type: application/json
{
"initiator_address":
"0xEA674fdDe714fd979de3EdF0F56AA9716B898ec8",
"target_address": "0x61C808D82A3Ac53231750daDc13c777b59310bD9",
"token_address": "0x2a65Aca4D5fC5B5C859090a6c34d164135398226",
"amount": 200,
"identifier": 42
}
Example Request
GET /api/V1/payments/(token_address)/(target_address) HTTP/1.1
Host: localhost:5001
Example Response
HTTP/1.1 200 OK
Content-Type: application/json
[
{
event:"EventPaymentReceivedSuccess",
amount: 5,
initiator: "0x82641569b2062B545431cF6D7F0A418582865ba7",
identifier: 1
},
{
event:"EventPaymentSentSuccess",
amount: 35,
target:"0x82641569b2062B545431cF6D7F0A418582865ba7",
identifier: 2
},
{
event:"EventPaymentSentSuccess",
amount: 20,
target: "0x82641569b2062B545431cF6D7F0A418582865ba7"
identifier: 3
}
]
The Beta/Stable release is the latest tested and most mature version of the Raiden client. When following the safety instructions, it can be used on the mainnet.
Download StableRelease Candidates (RC) are untested releases. They usually come with new features and bug fixes to the current stable release, but may still have glitches and issues to be fixed. Release Candidates should not be used on the mainnet.
Want to learn more about the basics of Raiden Network? Have a look at the Raiden 101 or check out one of the technical deep dives below.