We are currently thinking about fixing some bugs in the mobile backend.
This issue shall act as an umbrella issue to collect some of the quirks of the backend that could be improved in the future. If you have any suggestions, feel free to add.

• All functions are undocumented
  Maybe we can find a way to insert Javadoc into the generated.aar

• Address.toString() returns {}Address
  In order

In this error message:

Error: There was a timeout while attempting to connect to the network.
       Check to see that your provider is valid.
       If you have a slow internet connection, try configuring a longer timeout in your Truffle config. Use the networks[networ

Not exactly a bug, for for those who have been using Claimable in earlier versions of OZ (for the purpose of transferOwnership followed by claimOwnership) - what are the options in v2.0.0?

Relying solely on Ownable.transferOwnership lacks a safety mechanism for accidentally transferring the ownership to an incorrect address.

At present, the only alternative that I see is copying `Cla

Our error messages are not consistent regarding the use of quotes, e.g. some quote the function name and contract name, others don't.

We should agree on how we want to do that and make it consistent everywhere.

@erak argues for double quotes " around all user defined names.
I tend to agree.

Version: `0.10.0`
OS & Version: linux
Node version: `geth 1.8.2-stable-b8b9f7f4`

It seems that in "Latest transactions" in Ethereum Wallet there are listed pending transactions from all networks (the real network and several test networks) without displaying which network this transaction is of.

So either show it noticeably or l

Alignment for "Restore your Account with Seed Phrase" is off:

Screenshots

Quorum doesn't return a message error clearly specifying the cause of an error (from a user standpoint) when the transaction manager fails to Quorum (e.g: 400 bad request, ...).

System information

Release: 2.2.3

Expected behaviour

Helpful error message

Actual behaviour

invalid argument 0: json: cannot unmarshal non-string into Go value of type common.Hash

The cpp-ethereum homepage is not exactly helpful... http://cpp-ethereum.org/ which just takes you to here: http://www.ethdocs.org/en/latest/ethereum-clients/cpp-ethereum/ which only helps with building and installing.. and the only useful link is the "Running" which is only this: "Running eth without any argument will synchronise your node to the public blockchain. It is also possible to create or

User Story

To be able to see the history of the channels (anonymized though), we need a bot that will listen in to a set of public channels and writes their content in a DB. We also need a full-text search in the archive in the same bot.

Imagine http://offsite.chat/html, but on steroids.

https://github.com/status-im/sta

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the