Arseniy Klempner

Huge barrier to user on-boarding of decentralized applications is paying for gas. Let's add another version of the `performStateChange` method that accepts two additional parameters: `bytes32 hash, bytes sig` and...

Inspired by TrueBit's incentive layer contracts that use a state machine with [timeout restrictions](https://github.com/TrueBitFoundation/incentive-layer/blob/3b9ce16c35471c991d17ad72ec7c79a7c2b013a8/contracts/IncentiveLayer.sol#L55)

Flagging a transition as `networked` does not specify the details of the transition (which builder, machine, process, and state), it only requires that a transition is successfully performed.

Setup a documentation build system

2

I'm leaning towards using the [Ethereum Natural Specification Format](https://github.com/ethereum/wiki/wiki/Ethereum-Natural-Specification-Format) in the code and generating docs with Digix's [Doxity](https://github.com/DigixGlobal/doxity) (example [here](https://hitchcott.github.io/doxity-demo/docs/ConvertLib/) ) Another option is [Read the Docs](https://readthedocs.org)

Solium's [repo](https://github.com/duaraghav8/Solium) and [Getting Started](http://solium.readthedocs.io/en/latest/user-guide.html#quickstart) guide

Create a `CONTRIBUTING.md` file that outlines the contribution process Good examples: - [OpenZeppelin](https://github.com/OpenZeppelin/zeppelin-solidity/blob/master/CONTRIBUTING.md) - [Gitcoin](https://github.com/gitcoinco/web/blob/master/docs/CONTRIBUTING.md) - [Atom](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#your-first-code-contribution)

Aragon uses very sophisticated [Access Control List](https://github.com/aragon/aragonOS/tree/dev/contracts/acl) contracts for aragonOS. Let's explore the possibility of implementing these same contracts (perhaps with modifications) for managing our permissions system.

feat(telemetry)_: send peer count metric

1

When peer count timer is fired and peer count has changed, send a message to telemetry service indicating the node's peer count at the current timestamp. Also logs decoded error...

feat_: call telemetry upon error pushing envelope

1

Sends request to telemetry upon error publishing envelope. If telemetry is enabled and the publish function set in `func (w *Waku) broadcast()` fails, then the envelope details and resulting error...

feat: abstraction over filter and store for subscriptions with message recovery

6

This is a **bug report/feature request/support request/change request** ## Problem If you run a filter subscription and go offline, any missed messages while offline will not be recovered. There can...