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

It would be helpful (especially for non techie folk) if the entry point for the book was more obvious.

Only because I read the Mastering Bitcoin book did I know to enter at book.asciidoc

Needs something like this: https://github.com/bitcoinbook/bitcoinbook/blob/develop/README.md#reading-this-book

• 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

Hello,
Actually I would like to increase a dependency version of url and dotenv crate only, as I have duplicates versions in my Cargo.lock. But I have collect also which other dependency could be increased:

diesel/diesel/Cargo.toml

[dependencies]
url = "2.1.0"
quickcheck = "0.9.0"
uuid = "0.8.1"
[dev-dependencies]
dotenv = "0.15.0"
quickcheck = "

Once #3655 is merged, lnd will support the option_upfront_shutdown_address feature which allows nodes to specify an address that a channel should be paid out to upon cooperative close. If the peer we open a channel with supports the feature and we choose to set this address, the peer will not cooperatively close out to an address other than the one provided on channel open.
Further details are

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

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

@shekhar-shubhendu pointed out that a Google search for bigchaindb docker or similar returns search results where some of the first results are old and out-of-date docs. Anyone clicking on those search results will quickly get confused or in a dead end. Here's a screenshot of one such search (done in incognito mode):

![screenshot from 2018-09-20 11-18-30](https://user-images.githubusercontent

Problem

Currently when a user receives a PN, we show a very generic message (no indication of sender, body, etc). This will change in the future (e.g. with status-im/status-react#7043), so it would be good to be more explicit about the fact that we are showing a generic PN message due to the db being locked. Also, since we may receive PNs from users we've since removed