Connect with us

Litecoin Core v0.16.0 Release




Adrian Gallagher

Follow the Google+ page or Twitter for the latest dev news.

We are pleased to release Litecoin Core 0.16.0 release. This is a new major version release, including new features, various bugfixes and performance improvements, as well as updated translations. It is reccomended for all users to upgrade to this version.

Segwit Wallet

Litecoin Core 0.16.0 introduces full support for segwit in the wallet and user interfaces. A new -addresstype argument has been added, which supports legacy, p2sh-segwit (default), and bech32 addresses. It controls what kind of addresses are produced by getnewaddress, getaccountaddress, and createmultisigaddress. A -changetype argument has also been added, with the same options, and by default equal to -addresstype, to control which kind of change is used.

A new address_type parameter has been added to the getnewaddress and addmultisigaddress RPCs to specify which type of address to generate. A change_type argument has been added to the fundrawtransaction RPC to override the -changetype argument for specific transactions.

  • All segwit addresses created through getnewaddress or *multisig RPCs explicitly get their redeemscripts added to the wallet file. This means that downgrading after creating a segwit address will work, as long as the wallet file is up to date.
  • All segwit keys in the wallet get an implicit redeemscript added without it being written to the file. This means recovery of an old backup will work as long as you use new software.
  • All keypool keys that are seen used in transactions explicitly get their redeemscripts added to the wallet files. This means that downgrading after recovering from a backup that includes a segwit address will work

Note that some RPCs do not yet support segwit addresses. Notably, signmessage/verifymessage doesn’t support segwit addresses, nor does importmulti at this time. Support for segwit in those RPCs will continue to be added in future versions.

P2WPKH change outputs are now used by default if any destination in the transaction is a P2WPKH or P2WSH output. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.

BIP173 (Bech32) Address support (“ltc1…” addresses)

Full support for native segwit addresses (BIP173 / Bech32) has now been added. This includes the ability to send to BIP173 addresses (including non-v0 ones), and generating these addresses (including as default new addresses, see above).

A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses. When launched with -addresstype=bech32 it is checked by default. When launched with -addresstype=legacy it is unchecked and disabled.

HD-wallets by default

Due to a backward-incompatible change in the wallet database, wallets created with version 0.16.0 will be rejected by previous versions. Also, version 0.16.0 will only create hierarchical deterministic (HD) wallets. Note that this only applies to new wallets; wallets made with previous versions will not be upgraded to be HD.

Wallets directory configuration (-walletdir)

Litecoin Core now has more flexibility in where the wallets directory can be located. Previously wallet database files were stored at the top level of the litecoin data directory. The behavior is now the following:

  • For new installations (where the data directory doesn’t already exist), wallets will now be stored in a new wallets/subdirectory inside the data directory by default.
  • For existing nodes (where the data directory already exists), wallets will be stored in the data directory root by default. If a wallets/ subdirectory already exists in the data directory root, then wallets will be stored in the wallets/ subdirectory by default.
  • The location of the wallets directory can be overridden by specifying a -walletdir=<path> option where <path> can be an absolute path to a directory or directory symlink.

Care should be taken when choosing the wallets directory location as funds may be lost if it becomes unavailable during operation.

The minimum version of the GCC compiler required to compile Litecoin Core is now 4.8. No effort will be made to support older versions of GCC. See discussion in issue #11732 for more information. The minimum version for the Clang compiler is still 3.3. Other minimum dependency versions can be found in doc/ in the repository.

Pruned nodes can now signal BIP159’s NODE_NETWORK_LIMITED using service bits, in preparation for full BIP159 support in later versions. This would allow pruned nodes to serve the most recent blocks. However, the current change does not yet include support for connecting to these pruned peers.

The SHA256 hashing optimizations for architectures supporting SSE4, which lead to ~50% speedups in SHA256 on supported hardware (~5% faster synchronization and block validation), have now been enabled by default. In previous versions they were enabled using the --enable-experimental-asm flag when building, but are now the default and no longer deemed experimental.

  • The option to reuse a previous address has now been removed. This was justified by the need to “resend” an invoice. But now that we have the request history, that need should be gone.
  • Support for searching by TXID has been added, rather than just address and label.
  • A “Use available balance” option has been added to the send coins dialog, to add the remaining available wallet balance to a transaction output.
  • A toggle for unblinding the password fields on the password dialog has been added.

New rescanblockchain RPC

A new RPC rescanblockchain has been added to manually invoke a blockchain rescan. The RPC supports start and end-height arguments for the rescan, and can be used in a multiwallet environment to rescan the blockchain at runtime.

New savemempool RPC

A new savemempool RPC has been added which allows the current mempool to be saved to disk at any time to avoid it being lost due to crashes / power loss.

Safe mode disabled by default

Safe mode is now disabled by default and must be manually enabled (with -disablesafemode=0) if you wish to use it. Safe mode is a feature that disables a subset of RPC calls – mostly related to the wallet and sending – automatically in case certain problem conditions with the network are detected. However, developers have come to regard these checks as not reliable enough to act on automatically. Even with safe mode disabled, they will still cause warnings in the warnings field of the getneworkinfo RPC and launch the -alertnotify command.

Renamed script for creating JSON-RPC credentials

The share/rpcuser/ script was renamed to share/rpcauth/ This script can be used to create rpcauthcredentials for a JSON-RPC user.

Validateaddress improvements

The validateaddress RPC output has been extended with a few new fields, and support for segwit addresses (both P2SH and Bech32). Specifically:

  • A new field iswitness is True for P2WPKH and P2WSH addresses (“ltc1…” addresses), but not for P2SH-wrapped segwit addresses (see below).
  • The existing field isscript will now also report True for P2WSH addresses.
  • A new field embedded is present for all script addresses where the script is known and matches something that can be interpreted as a known address. This is particularly true for P2SH-P2WPKH and P2SH-P2WSH addresses. The value for embedded includes much of the information validateaddress would report if invoked directly on the embedded address.
  • For multisig scripts a new pubkeys field was added that reports the full public keys involved in the script (if known). This is a replacement for the existing addresses field (which reports the same information but encoded as P2PKH addresses), represented in a more useful and less confusing way. The addresses field remains present for non-segwit addresses for backward compatibility.
  • For all single-key addresses with known key (even when wrapped in P2SH or P2WSH), the pubkey field will be present. In particular, this means that invoking validateaddress on the output of getnewaddress will always report the pubkey, even when the address type is P2SH-P2WPKH.
  • The deprecated RPC getinfo was removed. It is recommended that the more specific RPCs are used:
  • getblockchaininfo
  • getnetworkinfo
  • getwalletinfo
  • getmininginfo
  • The wallet RPC getreceivedbyaddress will return an error if called with an address not in the wallet.
  • The wallet RPC addwitnessaddress was deprecated and will be removed in version 0.17, set the address_type argument of getnewaddress, or option -addresstype=[bech32|p2sh-segwit] instead.
  • dumpwallet now includes hex-encoded scripts from the wallet in the dumpfile, and importwallet now imports these scripts, but corresponding addresses may not be added correctly or a manual rescan may be required to find relevant transactions.
  • The RPC getblockchaininfo now includes an errors field.
  • A new blockhash parameter has been added to the getrawtransaction RPC which allows for a raw transaction to be fetched from a specific block if known, even without -txindex enabled.
  • The decoderawtransaction and fundrawtransaction RPCs now have optional iswitness parameters to override the heuristic witness checks if necessary.
  • The walletpassphrase timeout is now clamped to 2^30 seconds.
  • Using addresses with the createmultisig RPC is now deprecated, and will be removed in a later version. Public keys should be used instead.
  • Blockchain rescans now no longer lock the wallet for the entire rescan process, so other RPCs can now be used at the same time (although results of balances / transactions may be incorrect or incomplete until the rescan is complete).
  • The logging RPC has now been made public rather than hidden.
  • An initialblockdownload boolean has been added to the getblockchaininfo RPC to indicate whether the node is currently in IBD or not.
  • minrelaytxfee is now included in the output of getmempoolinfo
  • -debuglogfile=<file> can be used to specify an alternative debug logging file.
  • litecoin-cli now has an -stdinrpcpass option to allow the RPC password to be read from standard input.
  • The -usehd option has been removed.
  • litecoin-cli now supports a new -getinfo flag which returns an output like that of the now-removed getinfo RPC.
  • The default regtest JSON-RPC port has been changed to 19443 to avoid conflict with testnet’s default of 19332.
  • Segwit is now always active in regtest mode by default. Thus, if you upgrade a regtest node you will need to either -reindex or use the old rules by adding vbparams=segwit:0:999999999999 to your regtest litecoin.conf. Failure to do this will result in a CheckBlockIndex() assertion failure that will look like: Assertion `(pindexFirstNeverProcessed != nullptr) == (pindex->nChainTx == 0)’ failed.

To download, please visit the download page here. Alternatively, you can view the download folder here.

Please use GPG to verify the integrity of the release binaries. This ensures that the binary you have downloaded has not been tampered with. Linux, MacOS and Win32 cygwin command line GPG instructions are available here. Please also note that we GPG sign the binaries as a convenience to you, the ultimate way to verify the integrity of the builds is to build them yourself using Gitian. Instructions on how to perform these builds, can be found here.

For this release, the binaries have been signed with key identifier FE3348877809386C (thrasher’s key).

Despite this version being heavily tested, this version may still contain bugs. Always backup your wallet.dat file before upgrading. If you encounter any issues, please let us know by posting to the bug reporting section below.

The master branch contains the latest commits to the next stable releases of Litecoin Core.

Build instructions for Linux can be found here.

Build instructions for OSX can be found here.

Builds instructions for Windows can be found here.

Submit any issues you encounter here and one of the Litecoin developers will assist you.

Sign up for announcements only or development discussion.

These are the SHA-256 hashes of the released files:

108db1106539f48d3221420d14219177c81019b10b751fa923fe2b2376fe25eb litecoin-0.16.0-aarch64-linux-gnu.tar.gz
e49f8fba90e5c87000d0c8a91ddc305e3cfd3e34861f678f9220337db5fe79db litecoin-0.16.0-arm-linux-gnueabihf.tar.gz
edda17bdbcba596149cd94d9aa58e5d7975955a94ca9eac30892cbdeaea40ea8 litecoin-0.16.0-i686-pc-linux-gnu.tar.gz
d068934a905c3a15a3b32684751f68d7d46e8ce7a540436563659ef8ee4784f1 litecoin-0.16.0-osx64.tar.gz
e33fab8afa3c03eabcd958f4f7c2a4fdfdaf1f65eff7a861135e19fbc68423ad litecoin-0.16.0-osx.dmg
93b451d180b2c60495595df00c303de6b8e135187d0d77bd542b9df917f50286 litecoin-0.16.0-osx.dmg.old
ee13921d34a5fa0c38ca6660514b1ae20f8d66ff366497a3368c7449ab6be541 litecoin-0.16.0.tar.gz
21718c1a60e66fdf55f8d0be0601fa5e7ed7c60bc74e1f08f6e8a470cc2859cd litecoin-0.16.0-win32-setup.exe
629a4133cd6870562915df1da13a3600d559f5c0d3878eb00a4c1e925f4b9cf1 litecoin-0.16.0-win64-setup.exe
5a1dfaea8d70f4d0d61190061631d6ad40cb3662e7718660000c43f564c348e6 litecoin-0.16.0-x86_64-linux-gnu.tar.gz

Thanks to everyone who directly contributed to this release:

  • The Bitcoin Core Developers
  • Adrian Gallagher
  • aunyks
  • coblee
  • cryptonexii
  • gabrieldov
  • Martin Smith
  • NeMO84
  • ppm0
  • romanornr
  • shaolinfry
  • spl0i7
  • stedwms
  • ultragtx
  • VKoskiv
  • voidmain
  • wbsmolen
  • xinxi



EOS, BAT, Dogecoin Price Analysis: 16 January

Republished by Plato



EOS‘s market noted some bearish presence, with the same likely to push the crypto’s price slightly south towards $2.6. Basic Attention Token appeared to break out of a range backed by significant trading volume, while Dogecoin was in a phase of consolidation and traded sideways on the charts with no strong momentum.


EOS, BAT, Dogecoin Price Analysis: 16 January

Source: EOS/USDT on TradingView

The RSI floated just under the neutral 50 value, unable to rise above and likely indicative of a downtrend to come. The price, more importantly, flipped the $2.73-level to support recently and attempted a surge towards the next level of resistance at $3.

This session (cyan) saw the market’s bulls drive prices as high as $2.93, but the bears stepped in and pushed the price down to test the support at $2.6. This highlighted a lack of bullish strength.

Their presence in the market is poised to be highlighted once more. It can be expected that EOS would slowly descend towards $2.6 once more. If it does not hold as support, the price could drop to $2.44 in the coming days.

In other news, Arca CIO Jeff Dorman tweeted that EOS could be undervalued due to its massive BTC holdings.

Basic Attention Token [BAT]

EOS, BAT, Dogecoin Price Analysis: 16 January

Source: BAT/USD on TradingView

The range between $0.27 and $0.2 is one that BAT has traded within since late November. On the 6-hour charts, it appeared that BAT was headed for a breakout above this range. The trading volume for the most recent session before press time was extraordinary, pointing towards market conviction.

The MACD formed a bullish crossover and rose above zero to highlight bullish momentum. However, the $0.292-mark continued to be a thorn in the side of bulls and can be expected to stall the rise of BAT’s price.

Another rejection at $0.292 could see BAT tumble sharply back within the range it was trading within.

Dogecoin [DOGE]

EOS, BAT, Dogecoin Price Analysis: 16 January

Source: DOGE/USDT on TradingView

After its explosive move from $0.0045 to $0.01, DOGE spent the past few weeks in a phase of consolidation. Using the swing high and low of this phase for DOGE, and Gann’s rule of eight, some potential levels of support and resistance (yellow) can be plotted on the charts.

It can be seen that DOGE has respected these levels. The Awesome Oscillator showed a lack of definitive momentum in either direction for DOGE.


Continue Reading


Demand for Ethereum hits rooftop, price could quadruple within 90 days

Republished by Plato



Upcoming ETH Futures And Increased Interest From Institutional Investors Will See Ethereum Hit $10K - Pundit Predicts

Advertisement &  & 

Bitcoin bulls are calling $50,000 for the next rally. Ethereum bulls are also just as optimistic, as fundamental indicators are looking as promising as technical indicators. These key signals imply that a bullish rally, despite price stagnation is imminent and includes the sky-high demand for Ethereum’s ETH, which analysts claim will unseat supply in the coming weeks. To get the point across, analysts noted how Bitcoin’s price quadrupled within a three months period (November 2020 to January 2021) when demand toppled supply.

In the last 48 hours, Ethereum has sustained losses of 8.5%. The drop in prices was triggered by whale activities, reflected in the exit of ETH worth $2.4 billion from the Bitfinex exchange.

DeFi still remains one of Ethereum’s most promising ventures. At press time, locked in value has hit $23.22 billion. But Ethereum’s DeFi industry is still in its early stages, hence market maturation is still at its beginning state. “The DeFi market is still severely undervalued,” says analyst Joseph Young. Making up a large fraction of the entire digital currency market, he touches on DeFi’s astounding market cap.

“The total market cap of all DeFi tokens (even including Chainlink) is $25.7 billion. XRP and LTC and ADA will result in $31 billion.” 

Decentralized futures, still in the early stages but just as bullish is already processing millions of dollars in daily transactions. Young noted this in a preceding tweet as quoted below ;

“Decentralized futures exchanges on Ethereum are also seeing fast growth. Perpetual Protocol, for instance, is processing $50 million PER DAY.”

Meanwhile, on the technical charts, Ethereum seems to be replenishing its 7 days losses with reverse daily gains of 12% at the time of this report. However, the second most valued digital asset may need more to break above the $1,350 resistance level. Within the last few days, it has become evident that the strong price rejection around said resistance is still ongoing. 

Advertisement &  & 
Demand for Ethereum hits rooftop, price could quadruple within 90 days
ETHUSD Chart By TradingView

Ethereum bulls have been knocked back down on several occasions. And the bearish momentum had successfully managed to suppress ETH to a low of $994. At press time price of $1,209, ETH bulls will need to build enough momentum to retest $1,350 resistance or risk testing $880 support levels.

A bullish price reversal is still being anticipated by analysts who opine that LINK, DOT, and ETH will pioneer the altcoin season.

Get Daily Crypto News On Facebook | Twitter | Telegram | Instagram


The views expressed in the article are wholly those of the author and do not represent those of, nor should they be attributed to, ZyCrypto. This article is not meant to give financial advice. Please carry out your own research before investing in any of the various cryptocurrencies available.


Continue Reading


Polkadot surpasses XRP to grab the 4th slot

TL; DR Breakdown Polkadot (DOT) is now the 4th largest crypto by market cap XRP could suffer a catastrophic blow if ruled a security The crypto market is shifting again, and this time, the charts are re-arranging as Polkadot moves up by one position. The top 10 largest cryptos (by market cap) have always been […]

Republished by Plato



TL; DR Breakdown

  • Polkadot (DOT) is now the 4th largest crypto by market cap
  • XRP could suffer a catastrophic blow if ruled a security

The crypto market is shifting again, and this time, the charts are re-arranging as Polkadot moves up by one position. The top 10 largest cryptos (by market cap) have always been a good point of reference when it comes to market movements. Now, it seems like XRP is getting stripped of its position, a spot now occupied by Polkadot (DOT).

The last few days have been a huge challenge for XRP as it battles the negative effects resulting from the current lawsuit facing its creator company, Ripple. A quick glance at the running market placements reveals that XRP price has been losing ground while other cryptos like Polkadot have been scoring gains each day.

Polkadot (DOT) has been thriving

In the past 7 days, Polkadot has surged by over 64%, putting the price at around $15 – according to information on CoinMarketCap. Over the same period, XRP has dropped by 10% to put the price at around $0.28. As a result, Polkadot has been gaining traction both in popularity and relative acceptance as an interoperability protocol designed to facilitate multi-chain operations. The network uses DOT as its native crypto token which users can use to vote on issues concerning the network’s governance.  

Polkadot surpasses XRP to grab the 4th slot 1

Currently, DOT has posted an impressive Market Cap totaling $13.4 billion as opposed to XRP’s $12.7 billion, effectively making it the 4th largest crypto by market cap. That’s after Tether (3rd place at $24.29 billion), Ethereum (second place at $135.3 billion), and Bitcoin (first place at $681.6 billion).

XRP facing an existential threat

For some years, Ripple has been lobbying to get XRP ratified as a cryptocurrency as opposed to the views of some who see it as a security. These efforts seem to have somehow back-fired as the US SEC moved to file a suit against Ripple and its top management back in December 2020. According to SEC, Ripple has been illegally transacting with XRP, which SEC sees as a security. The accused include Ripple’s CEO Brad Garlinghouse, co-founder and Executive Chairman Chris Larsen, and Ripple Labs itself.

The suit has led to investors like Grayscale ditching XRP. Some crypto exchanges suspending XRP from their trading platforms, while others have moved to delist it altogether. The latest to take action is Kraken.

These developments are in no way in favor of XRP, and they could cause a lasting effect on its market standings. If XRP is ruled a security, it will cease to exist as a crypto and ultimately end its streak as one of the most popular digital tokens backed by the might of a global company.

Continue Reading
Blockchain4 days ago

Ethereum Whale Addresses With Over 10,000 ETH Continue to Grow In Numbers, Price Holds Above $1000

Blockchain4 days ago

‘Crypto is exactly like dot com bubble; Bitcoin, Ethereum can survive it’

Blockchain4 days ago

As Bitcoin Regains Lost Ground, Options Traders Bet on $52K Move By Late January

Blockchain4 days ago

Ethereum Price Analysis: 12 January

Blockchain4 days ago

Shanghai Government Invests $5M in Blockchain Startup Conflux

Blockchain4 days ago

Brian Brooks, Crypto-Friendly OCC Leader, Steps Down

Blockchain4 days ago

Coinbase Custody Lists DeFi Project BarnBridge

Blockchain4 days ago

How the OCC Is Building Crypto America (and Saving Banks From Extinction)

Blockchain3 days ago

SolidX Sues VanEck Over Bitcoin ETF Plagiarism

Blockchain4 days ago

Bitcoin ‘real’ daily trading volume tops $22B as BTC price recovers

Blockchain3 days ago

Trader comforts the market’s traumatized first timers amid falling prices

Blockchain4 days ago

Crypto Community Expects Bitcoin to Surge Amid Biden’s $3 Trillion Stimulus Plan

Blockchain4 days ago

Gensler Said to Be Named SEC Chairman: Reuters

Blockchain4 days ago

Bakkt to Become a Publicly Traded Company worth $2.1 Billion Via New Merger

Blockchain4 days ago

IMVU’s new blockchain-backed stablecoin goes live

Blockchain4 days ago

Is China Poised to Nationalize Alibaba?

Blockchain3 days ago

Uniswap’s growth lead bites back over Yearn Finance’s SushiSwap merger

Blockchain4 days ago

Singapore-based Zipmex closes $6M funding round led by Jump Capital

Blockchain3 days ago

Crypto Lawyer Sees Incoming SEC Chair as a Win for Bitcoin, Not XRP

Blockchain4 days ago

Blockstream expands Liquid Federation, but LBTC adoption remains slow