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

There's no published benchmark for IOPS on S3 storage

Would it be possible to post this alongside the other benchmarks?

S3 storage would be super cheap way to get started because it's serverless (thus more folks would potentially use gun.js)

Thank you for the useful service. I would like to see more Auth/ABAC for startup usage, right now I'm using a centralized database because it's uncle

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

Issue

When sending more gas than the network's current block limit, the error message that comes back is confusing and can/should be clarified.

Steps to Reproduce

In truffle-config, specify a "gas" value which is higher than the block gas limit for the network you are connected to. Attempt to do a basic migration or any other Truffle transaction.

Expected Behavior

The "Block li

@ekpyron and I went a bit over the testcases code (while looking at #8238) and come up with the following ideas for a refactor:

• remove validateSettings and the related variables m_settings and m_validateSettings. Instead add a function void addSetting() that takes a string and a lambda/function pointer that is called for each setting that is found. The lambda can set desired member va

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

• Parity Ethereum version: 2.4.5 or 2.4.6
• Operating system: Linux
• Installation: binary from Github | releases
• Fully synchronized: both, no and yes
• Network: ethereum
• Restarted: yes

Actual behaviour

When starting parity 2.4.5/2.4.6 in archive mode (tracing on, db_compaction ssd, pruning archive, fat_db on) with the default settings for the cache_size

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

see: dvf/blockchain#50

The underlying exploit to tamper with a blockchain is described there

props to: @TimelessP

The fix should be fairly simple:
affected file: blockchain/blockchain.py

https://github.com/dvf/blockchain/blob/4010cf3273e19146a9cd7b37cf355cb751ffef88/blockchain.py#L82

A noted, currently it reads:

if length > max_length and self.valid

Currently the lncli listinvoices --reversed flag has no effect, as it
is of type cli.BoolTFlag https://github.com/lightningnetwork/lnd/blob/ad0a89b844ec9f55b3ca4ddbb4d368dd8e3c0ea9/cmd/lncli/commands.go#L2848
which is true by default.

Correct behavior can be triggered by lncli listinvoices --reversed=True
or lncli listinvoices --reversed=False.

Is this behavior intended? I get th

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

Using latest version 0.15.0.1. (Edit : on Ubuntu 18.04)
After the CLI wallet was locked, the prompt showed the password in clear while typing.
I'm not a big CLI user so this happened only twice so far, but I thought it's worth reporting this issue.
Not sure if a screenshot is useful, but here's one below anyway.

![image](https://user-images.githubusercontent.com/16813929/72224145-2e286100-35

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.

tendermint debug tool can be used to continuously collect data. We haven't written any documentation/tutorials for it.

Write documentation and/or a mini-tutorial on how to collect profiling data continuously

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

Migrated from internal issue RIPD-1031.

By convention, the account_lines method returns booleans for flags that are in their non-default states. In the vast majority of cases, this means it returns flags when the values are true and omits them when the values are false. The NoRipple flags of a trust

The gas is counted incorrect in the first time .send() is invoked, because it also sums the cost of deploy the transaction.

I had to do a workaround (see status-im/account-contracts@291fd9b#diff-8ae90872f0505462a211bc1fa2f5f03eR28 ) to show proper gas, which is a transaction to anywhere before doing the other transactions I want to tes

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

Bug Report

Problem

The amount is the first field in a transaction. When you fill this out, and then add recipient by scanning their QR code, the amount is reset.

Expected behavior

Amount is maintained unless user cancels the Tx.

Actual behavior

Set Tx amount.
Scan recipient QR code.
Amount is cleared and must be re-entered.