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

I'm looking at the react tutorial at https://github.com/amark/gun/wiki/React-Tutorial and noticed that the code examples are using depreciated lifecycle methods such as componentWillMount.

Do you have an Interesting Story to share? We are here to listen to your story.

• You don't need to have a high paying job or from a premier institution. If you have done something you worth consider sharing, please write your story here in the comments.

Or, you can also drop a mail at raj.deeepak@gmail.com

Remember your story can inspire thousands of students out there !!

Feel

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.

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.

Given that we support CURRENT_TIMESTAMP, the lack of CURRENT_DATE feels like an omission. While you can hack it with date(now), I keep finding myself wishing there was a direct way to reference this. Given that now means CURRENT_TIMESTAMP, I think there's precedent for today meaning CURRENT_DATE. This is supported by all backends we support (and is in the ISO standard I believe).

What's wrong

@dvf it would be great if you could fix Step 6: Setting up Flask gist, it affects the workflow at the Learn Blockchains by Building One article. Also there is no way to mention someone at the gist comments, so I created this issue instead.

To be done on lbrytech repo probably.
The wallet is currently configured as defined originally in ElectrumX, there are some docs for it already in there.

Keep in mind that we added new configuration keys and should clean up the unused ones at some point, so we need something easy

Background

The binaries are built with most of the build flags already set, but when building from source you must specify which tags are desired. This is an important step to building a usable binary from source.

These flags should be listed in the docs, with what their use is for the entire system, and whether or not excluding it would break the normal function of the system.

A sect

When given a wrong argument, some daemon commands fail with "unknown command" error, instead of a meaningful error message.

Examples of useless error messages:

hard_fork_info abc
unknown command: hard_fork_info abc
Monero 'Carbon Chamaeleon' (v0.15.0.0-57854a3e2)
Commands:
  ...

in_peers abcd
unknown command: in_peers abcd
Monero 'Carbon Chamaeleon' (v0.15.0.0-57854a3e2)
Comm

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

The blockchain v2 reactor utilizes concurrency to saturate the bottleneck of writing blocks to disk. This concurrency is internal to the reactor where the reactor itself will launch and manage internal state machines running as go-routines. This configuration makes testing difficult as we don't know when messages processed by internal state machines will be processed and when we can assert that th

The documentation website needs a major overhaul. Many of the examples and sample code are not up to date with the latest release.

This is definitely affecting users, see #1786 for example.

Describe the bug
Merry Christmas everybody. I have a question regarding BigchainDB. We have a setup of a cluster from 3 nodes where each has a Tendermint and MongoDB and they are connected.When in one of nodes on MongoDB Level a document is deleted, it does not recover itself. Is that possible to solve somehow?

To Reproduce
Install a cluster from several nodes, login to MongoDB direct

Take a look at this call graph. Now look at the source of that function and all the calls to methods of InboundLedger, through the shared_ptr<InboundLedger> named inbound. Notice how the call gra

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

Summary
We have templates for issues, now we need a template for the PR. It is quite similar to the issue template, except that you fill it when you send the PR.

Do you have any solution you want to propose?
Create a PR template for this repository

Where in the software does this update applies to?

• Other: House-keeping

Codecov Report

Merging #10574 into master will decrease coverage by 0.01%.
The diff coverage is 21.42%.

[![Impacted file tree graph](https://codecov.io/gh