Bitcoin core roadmap icons

Choose sending or receiving amount. Choose all available inputs or manual input selection. Make version label clickable and show if new version is available. Only use hidden service btc nodes if Tor is enabled for BitcoinJ and provided nodes are used. Optimize P2P network startup behavior Separate fees in trade complete screen. Show withdrawal btc address only after button click in trade complete screen. Cagecoin, Spectrecoin, Verify Add more provided Bitcoin nodes Add more seed nodes Add more provider nodes market price, miner fee estimation Add second seed node for DASH and LTC Add filter for btc nodes Use domainname instead of IP if both are known for btc nodes Increase connection timeouts Increase timeout for offer availability check Increase time for showing Tor settings at startup to 30 sec.

Increase offer refresh and republish intervals and offer TTL. Decrease maxConnections for btc network from 10 to 9 Remove unneeded broadcast trade fee tx tasks Remove checks for min.

That also avoids the privacy issues with bloom filters. Instead of using bytes as estimation of trade fee tx we create a dummy tx to get the exact size id funds are on the wallet, otherwise we use bytes for maker and bytes for taker deposit and payout tx are larger.

If both already existed if user has run 0. Fix issue with non-english OS Add a reminder to write down the wallet seed and make a backup before setting the wallet password Rename ClearXChange to Zelle Improve build setup auto install protoc Fix date format Only request restart at base currency selection if it has changed from default.

Remove popup at startup for selecting base currency Version 0. More will come in future releases. Use fee estimation service form https: Use dynamic trading fees.

Trading fees are based on trade amount and distance to market price. Make security deposit for buyer customizable at offer creation allowed range: In exceptional situations like at long bank holidays exceeding the period will be tolerated.

Swap input text controls when toggle between fixed price and percentage based price. Hide percentage based inputs if no market price is available. Support for translations of all application display strings User can select preferred language of those which are already translated and default country. German, Spanish, Greek, Portuguese and Serbian still require UI layout adjustments Remove ask and bid market price and use always last price.

Check for market price age on client. Add checks for locked up funds of failed trades. Add shortcut to remove failed trade from pending trades view. Use for Windows build no version nr at jar files to avoid collecting multiple jars at updates.

Prepare the split role of arbitrator in mediator has no MultiSig key and arbitrator 3rd key holder of MultiSig. Would anyone mine it? The answer to all these questions turns out to be yes. So where does Bitcoin Cash go from here? While both technologies would represent and improvement over the status quo, neither delivers any meaningful additional capacity.

Besides that Core has basically bet the house on the lightning network in hopes that it will live up to the hype. Only time will tell. The following are a list of items that appear to me to be more or less on the Bitcoin Cash roadmap. That has now changed with the Bitcoin Cash fork. The difficulty adjustment algorithm designed by Satoshi is pretty naive and not well suited for multiple coins competing for the same hash power and both Bitcoin Cash and Bitcoin are suffering because of it; Bitcoin Cash more so.

So it makes sense to change the algorithm. The result is that Bitcoin Cash will have a modern adjustment algorithm that prevents wild swings in block times.

Bitcoin, on the other hand, will have to continue to muddle through the relative changes in mining profitability.

We were told the reason the Bitcoin community needed to accept such a cumbersome and ugly hack on a multi-billion dollar protocol was that to do it any other way was to risk a chain split. Ironically, that hack ended up being a primary driver of the Bitcoin Cash chain split. Bitcoin Cash is probably better off for forking off when it did because now it can fix malleability the correct way.

Whether that is through a minimal malleability fix, with the transaction format remaining largely unchanged, or by changing the format to be more extensible is TBD. It should be obvious to everyone that the primary use case for a malleability fix, the lightning network, is not ready right now.

Even when it finally becomes ready it will take time for the technology to mature. And even more time to gain consumer acceptance, if it ever does. This could easily take several years to happen.

If Bitcoin Cash takes 12 or 18 months to get a malleability fix out the door I doubt it will miss anything. This prevents the validation from being done in parallel, increasing the time it takes to validate a block and creating a scalability bottleneck. By validating in parallel the work can be split across multiple cores or even multiple machines speeding up validation time.

Since the ordering is no longer important, the merkle tree can be redefined to allow for things like proof-of-absence which would been needed for fraud proofs or sharding down the road. UTXO comittments Committing the root of the UTXO set to each block would improve light client security, support a fast sync mode, and help with sharding down the road.

Ethereum does this with its Patricia tree, so there is at least some precedent but more research into how best to do so is probably still needed. This could even be done without committing anything to the blocks and could be replaced by something better later. This would allow a new node to get fully bootstrapped in like five minutes rather than a couple days and allow all but archival nodes to prune transaction data older than six months or a year.

The first has to do with larger blocks artificially benefiting larger miners at the expense of smaller miners potentially creating mining centralization pressures. The second is the need to validate blocks all at once rather than over time.

If I had a vote I would probably do weak blocks now, see how it works, and then consider ng later on down the road. GetBalance Instantly see your available Bitcoin balance. SendMany Send a single payment to multiple addresses. ListUnspent See what received transactions you can spend.

Notification Be notified of new blocks and transactions. Lightweight wallets usually connect to several random full nodes like Bitcoin Core to send and receive all of their data. In the process they leak private data and make themselves more vulnerable to attacks.

GreenBits is a fast and easy to use wallet.