The function arguments to core.NewBlockChain got way out of hand. We need a config structure instead.

While ccxt does a great job unifying most functions / settings, not everything is or can be unified.
I think it would be good to provide a separate wiki/documentation page which documents exchange-specific properties.

The behavior is there now and all is working well - but to find it users need to search through issues (which are not easy to navigate) to find certain exchange-specifics - and o

Expected behavior

The path defined for example in the tsconfig file of the web3-providers-http package is misleading and should get corrected if possible in a non-breaking manner.

Actual behavior

The defined path is web3-providers instead of web3-providers-http.

Steps to reproduce the behavior

1. Open a tsconfig file from one of the provider packag

Issue

The "Full Example" of using @truffle/contract to interact with contracts should include an example of listening to an event with a filter.

In the past, it used to be possible to pass a filter object on indexed event parameters when listening to an event, as seen for example [here](https://ethereum.

These contracts' functions don't have explanations:

https://docs.openzeppelin.com/contracts/2.x/api/token/erc20#ERC20Pausable
https://docs.openzeppelin.com/contracts/2.x/api/token/erc20#SafeERC20
https://docs.openzeppelin.com/contracts/2.x/api/token/erc20#TokenTimelock

The type checker contains multiple occurrences of

		if (noErrors)
			for (Source const* source: m_sourceOrder)
				if (source->ast)
					for (ASTPointer<ASTNode> const& node: source->ast->nodes())
						if (ContractDefinition* contract = dynamic_cast<ContractDefinition*>(node.get()))

These should be extracted into some helper "forAllContracts" or something like that, which takes

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

See openethereum/openethereum#11542 (comment).

After we migrate all wiki to OpenEthereum org, we need to update all the links in README.md and CONTRIBUTING.md here.

Env:

• python 3.8
• capstone 4.0.1
• ubuntu 18.04 (WSL)

Repro:

import capstone
md = capstone.Cs(capstone.CS_ARCH_X86, capstone.CS_MODE_32)
md.detail = True

# case 1
# expected: fstcw  WORD PTR [ebp-0x4] (based on Objdump disassembly which round-trips with GNU as)
for insn in md.disasm(b"\x9B\xD9\x7D\xFC", 0):
    print(insn.address, insn.mnemonic, insn.op_str)

print(

The section on style guides is quite short at the moment.
A more extensive description with examples would be better.

This can be highly valuable for newcomers and for the community as a whole!

There are some good style guides already out there that could be incorporated like this one:
https://github.com/0xcert/solidity-style-guide

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

Describe the bug
QR Code Scanner fails to scan input fields on Send Transaction view when scanning QR Code contains an EIP-681 URI

Example URI

ethereum:0x46c69f4424043e720a704330748cf3c593656b9c

To Reproduce
Steps to reproduce the behavior:

1. Go to Send Transaction view
2. Click on QR Code scanner
3. Position QR Code in front of Webcam
4. QR Code scanner closes

Had a hard time building both Aleth and Solidity, which were getting stuck on make.

Realized I should upgrade my GCC to a more current version, I had the initial configuration of:

• Ubuntu 16.04
• GCC/G++ 5.4.0
• clang version 3.8.0
• Boost 1.71

I then upgraded to G++ 6.5.0 and it is building successfully.

Ironically I wanted to contribute so I think this is a good starting po

For a university school project I will be making some edits to your documentation which will aim to make writing more technical

Please add edits if you would like :)

Feature Request

Add more configuration options for storage (IPFS). Command line arguments, for example.

Summary

For example, I want to develop my apps using IPFS. But I do not need to use it online. For example, running with --offline flag.

There two main ways to make it:

• Creating a variable called args in config/storage.js that would store extra argumens for the IPFS i

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

Description

Golem Version: 0.1

Golem-Messages version (leave empty if unsure):

Electron version (if used):

OS [e.g. Windows 10 Pro]: Ubuntu 19.04

Branch (if launched from source):

Mainnet/Testnet:

Priority label is set to the lowest by default. To setup higher priority please change the label
_P0 label is set for Severity-Critical/Effort-easy

We need to create our own docker image with git, sphinx-build and gradle to create the documentation and commit it into github.

The default docker image doesn't accept the html tags.

We should expand the contribution guide:

• Installing test / documentation dependencies
• Running the tests
• Detailed explanation of the VIP process
• Team calls

The Atom contribution guide is an excellent example - some of the content isn't valid for Vyper, but it's a great reference point for what a contribution guide can look

Maybe we rethink the whole flow here. Or maybe we just need to have a modal asking "Would you really like to switch workspace?".

Or maybe we can just rename the button "shutdown"

Related to #1726, fixing this one may be sufficient.

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

When I instruct the WebUI to join a token network with 5 TDAI, I get the message

TestDAI network was joined successfully with 5 TDAI

but in my case, only a single channel with a deposit of 1 TDAI has been created. The actual behavior is an expected result of our code for joining a TN. The behavior is already surprising enough, but with this message it clearly looks like a bug to the unsus