problem: should update CHANGELOG for upcoming release

solution: update it

CHANGELOG.md

@@ -5,7 +5,7 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/)
 and this project adheres to [Semantic Versioning](http://semver.org/).
 
 __Legend__:
-```md
+```text
 <Added> for new features.
 <Changed> for changes in existing functionality.
 <Refactored> for improvements to codebase quality not impacting client interface.
@@ -15,9 +15,11 @@ __Legend__:
 <Security> to invite users to upgrade in case of vulnerabilities.
 ```
 
-Releases considered stable may be found on our [Releases Page](https://github.com/ethereumproject/go-ethereum/releases).
+Releases considered __stable__ may be found on our [Releases Page](https://github.com/ethereumproject/go-ethereum/releases).
 
-## [Unreleased]
+Rolling builds for the master branch may be found at [builds.etcdevteam.com](builds.etcdevteam.com).
+
+## [3.5.86] - 2017-07-19 -
 
 #### Added
 - Newly configurable in external `chain.json`:
@@ -27,15 +29,21 @@ Releases considered stable may be found on our [Releases Page](https://github.co
     > See cmd/geth/config/*.json for updated examples.
 
 - Dev mode (`--dev`) made compatible with `--chain`
+- `debug_AccountExist` method added to RPC and web3 extension methods (thanks @sorpaas)
+- Additional Morden testnet bootnodes
+- Add listen for `SIGTERM` to stop more gracefully, if possible
 
 #### Changed
+- Nightly and tagged release distribution builds now available at [builds.etcdevteam.com](builds.etcdevteam.com) (instead of Bintray)
 - _Option_: `--chain <chainIdentifier|mychain.json>` - specify chain identifier or path to JSON configuration file
 
 #### Fixed
 - `geth attach` command uses chain subdirectory schema by default, e.g. `datadir/mainnet/geth.ipc` instead of `datadir/geth.ipc`
-- Sometimes ungraceful stopping on SIGTERM causing corrupted chaindata
+- Sometimes ungraceful stopping on SIGTERM, potentially causing corrupted chaindata
 - PublicKey method for protected transactions with malformed chain id causing SIGSEGV
 - Concurrent map read/writes for State Objects
+- Ignore reported neighbors coming from non-reserved addresses; prevents irrelevant discovery attempts on local and reserved IP's
+- RLP-decoded transactions include EIP155 signer if applicable (thanks @shawdon)
 
 ## [3.5.0] - 2017-06-02 - 402c170