Skip to content
Python Other
  1. Python 99.0%
  2. Other 1.0%
Branch: develop
Clone or download

Latest commit

ulope Use local synapse server in cli tests
The CLI integration tests implicitly used the matrix servers defined
in the RSB known servers list.
This caused the tests to be dependent on external services and therefore
be flaky.

This now uses the existing infrastructure to run a local Synapse server
thereby removing this dependency.

Fixes: #4642
Latest commit dcbda52 May 22, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci fex test Mar 24, 2020
.github re-add paul May 6, 2020
docker Installing wheel additionally Feb 13, 2020
docs bumpversion to 0.200.0-rc9 May 19, 2020
nix Remove unnecessary comment Sep 20, 2018
raiden Use local synapse server in cli tests May 22, 2020
requirements bumpversion to 0.200.0-rc9 May 19, 2020
snap Add the packaging metadata to build the raiden snap Dec 8, 2017
stubs Make `latest` and `pending` proper literal types Mar 20, 2020
tools Added checks for necessary binaries May 12, 2020
.bumpversion_client.cfg bumpversion to 0.200.0-rc9 May 19, 2020
.dockerignore Fix docker based nightly builds Jun 27, 2019
.editorconfig Fix .editorconfig for Makefiles Jun 19, 2019
.gitattributes Enable python specific hunk-header Oct 29, 2019
.gitignore Switch to pip-tools for dependency management Jun 19, 2019
.pre-commit-config.yaml Require newer pip-tools May 11, 2020
.unittest-coveragerc Exclude runtime typechecks from unit tests Jun 5, 2019
CONTRIBUTING.md Document the new restart_node fixture Feb 4, 2020
LICENSE Changed LICENSE date from 2018 to 2019 Feb 6, 2019
MANIFEST.in Bundle synapse config template Mar 12, 2020
Makefile Update to latest pip Jan 21, 2020
README.md fix typos [skip tests] Apr 16, 2020
codecov.yml Less codecov noise on github Jan 17, 2020
config_sample.toml Cleanup occurances for UDP May 22, 2019
pylintrc Lint: gevent.joinall(raise_error=False) and gevent.wait May 6, 2020
pyproject.toml Add configuration file for `black` defaults May 6, 2019
raiden.spec Fixed nightly binary build Feb 12, 2020
raiden_errors_key.gpg Add RaidenErrors@brainbot.li pgp key Dec 19, 2018
readthedocs.yml Readthedocs does not support python 3.7 Feb 5, 2019
requirements.txt Switch to pip-tools for dependency management Jun 19, 2019
setup.cfg Enable mypy's renundant-casts check Mar 30, 2020
setup.py bumpversion to 0.200.0-rc9 May 19, 2020

README.md

Raiden

Fast, cheap, scalable token transfers for Ethereum

Quicklinks

Python 3.7 Chat on Gitter

The Raiden Network is an off-chain scaling solution, enabling near-instant, low-fee and scalable payments. It's complementary to the Ethereum Blockchain and works with any ERC20 compatible token. The Raiden project is work in progress. Its goal is to research state channel technology, define protocols and develop reference implementations.

INFO: The Raiden client and smart contracts have been released for Mainnet with a limited alpha release of the Raiden Network in December 2018.

The Raiden Network is an infrastructure layer on top of the Ethereum Blockchain. While the basic idea is simple, the underlying protocol is quite complex and the implementation non-trivial. Nonetheless the technicalities can be abstracted away, such that developers can interface with a rather simple API to build scalable decentralized applications based on the Raiden Network.

Raiden in a Nutshell

Table of Contents

Getting Started

Learn about Raiden

If you haven't used Raiden before, you can

Use Raiden

If you want to use Raiden:

Specification

Read the tentative specification for the Raiden Network to understand in detail how Raiden works. It is maintained within this repository.

Repositories

The Raiden Network is getting created with a set of tools, which are maintained in different repositories.

Core

  • The solidity smart contracts, libraries and deployment tools are used to bootstrap a Raiden Network on an Ethereum Chain.

  • The Raiden Python client within the current repository is used to manage payment channels and to make token transfers.

  • A configured matrix server joins a federation of Matrix servers which is used as the transport layer for the Raiden Network.

  • The Service repository contains the code for following services:

    • The Monitoring Service watches open payment channels when the user is not on-line.
    • The Pathfinding service supports users in finding the cheapest or shortest way to route a payment through the network.
  • The Light Client repository contains the code for following applications:

    • The Raiden Light Client SDK is a Raiden Network compatible client written in JavaScript/Typescript.
    • The Raiden DApp is a reference implementation of the Raiden Light Client SDK.

Tools

  • The Raiden WebUI is Raiden Web User Inteface to manage channels and make token transfers.

  • The Raiden Explorer visualizes the nodes of the Raiden Networks and shows more statistical information.

  • The Raiden Wizard makes it easy to install a Raiden client and join the Raiden Network.

  • The Scenario Player is an integration testing tool for the Raiden contracts, the Raiden client and the services.

  • The Workshop Scripts enable workshop facilitators to easily host a Raiden Workshop.

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

Also have a look at the Raiden Development Guide and the Raiden Developer On-boarding Guide for more info.

License

Distributed under the MIT License.

Contact

Dev Chat: Gitter

Twitter: @raiden_network

Website: Raiden Network

Blog: Medium

Mail: contact@raiden.network

The Raiden project is led by brainbot labs Est.

Disclaimer: Please note, that even though we do our best to ensure the quality and accuracy of the information provided, this publication may contain views and opinions, errors and omissions for which the content creator(s) and any represented organization cannot be held liable. The wording and concepts regarding financial terminology (e.g. “payments”, “checks”, “currency”, “transfer” [of value]) are exclusively used in an exemplary way to describe technological principles and do not necessarily conform to the real world or legal equivalents of these terms and concepts.

You can’t perform that action at this time.