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.

The first link in gsoc.md file is being redirected to Error Page (404) Not found.
Please fix this!!

Line : #29
Link on how to prepare for gsoc.
Thank you

• I've asked for help in the Truffle Gitter before filing this issue.

https://gitter.im/ConsenSys/truffle?at=5de5c3d91659720ca8eb0c4c

Issue

I'm seeing the failure reported here: https://ethereum.stackexchange.com/questions/15101/how-to-use-the-testrpc-evm-increasetime-parameter-from-truffle-console#comment89683_21

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.

Background

Restoring an older wallet takes a long time right now.

@mandelmonkey posted this on lnd slack:

I just tried mainnet with a passphrase made about 4 months ago and one made just now, the one made 4 months ago is taking around 30mins the one made now in a just a couple of mins to recover

Right now there is no way to know if restoring is completed or how long it might still

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

Actual docs (https://www.getmonero.org/resources/developer-guides/wallet-rpc.html#get_transfer_by_txid) tells us what get_transfer_by_txid return only transfer object, and did not mention what it return a transfers array too.

example (testnet):

• `curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfer_by_txid","params":{"txid":"a5447204b

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 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.

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

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

Issue Description

The usage statement does list the manifest and validator_info commands, added by #3197.

Steps to Reproduce

Print the usage statement:

rippled -h

Expected Result

The result should list all supported commands.

Actual Result

The usage statement does not list either manifest or validator_info.

Environment

Arch Linux, x86_64, self

Feature Request

Make Vyper development a first-class citizen

Summary

There a few quality of life things that should be added to make it easier to develop with Vyper. Specifically:

1. Correct color formatting of .vy files & error highlighting
2. Comment shortcut (cmd+/) should use # instead of //
3. Integration of Vyper-debug

I am sure there are more but these are the first

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