raiden-contracts
raiden-contracts copied to clipboard
Raiden Network Smart Contracts
Currently `raiden_contracts` repository contains many, many `data_x.y.z` directories. When somebody is looking for other files, the view is annoying. This issue keeps track of sweeping all `data_x.y.z` under a directory.
Currently, in `raiden-contracts` addresses are always 0x-prefixed hex string, but this doesn't fit the sandwitching principle https://github.com/raiden-network/raiden/blob/82daa8998a10c8e12fb77e0e40daded2b1090840/CONTRIBUTING.md#encoding
After a while, when `block.number` is big enough, the following addition in TokenNetwork might overflow. ``` channel.settle_block_number += uint256(block.number); ```
When one channel is in the settlement period, the same pair of users should be able to create a new channel. Currently, a new channel can be created only after...
The secret registry currently only supports a single query per secrethash, because of this the token network has to do one `CALL` per lock, which has a non negligible cost...
This issue keeps track of creating a contract that calls the old TokenNetwork to shutdown a channel and then calls the new TokenNetwork to create a channel and sets up...
In many functions, the argument `contracts_version` is optional (and it defaults to `None`). However, it's dangerous when people forget putting `contracts_version`. The call might succeed and people would be talking...
We are using a list to remember service providers and @LefterisJP says it's weird. I also think lists require more care (like never to iterate over them, lest you hit...
This issue keeps track of deciding whether to implement a transaction batch contract that can execute multiple transactions on behalf of the caller. The idea came about during a chat...