Comply with the Google+ page or Twitter for the newest dev information.
We’re happy to launch Litecoin Core 0.17.1. It is a new main model launch, together with new options, varied bugfixes and efficiency enhancements, in addition to up to date translations. It’s endorsed for all customers to improve to this model.
In case you are working an older model, shut it down. Wait till it has utterly shut down (which could take a couple of minutes for older variations), then run the installer (on Home windows) or simply copy over /Purposes/Litecoin-Qt (on Mac) or litecoind/litecoin-qt (on Linux).
In case your node has a txindex, the txindex db will likely be migrated the primary time you run 0.17.1 or newer, which can take up to some hours. Your node won’t be practical till this migration completes.
The primary time you run model 0.15.0 or newer, your chainstate database will likely be transformed to a brand new format. This may take anyplace from a couple of minutes to half an hour relying on the velocity of your machine.
Observe that the block database format additionally modified in model 0.8.0 and there’s no automated improve code from earlier than model 0.8 to model 0.15.0. Upgrading immediately from 0.7.x and earlier with out redownloading the blockchain is just not supported. Nonetheless, as traditional, outdated pockets variations are nonetheless supported.
The chainstate database for this launch is just not suitable with earlier releases, so in the event you run 0.15 after which determine to modify again to any older model, you will want to run the outdated launch with the -reindex-chainstatechoice to rebuild the chainstate knowledge buildings within the outdated format.
In case your node has pruning enabled, it will entail re-downloading and processing the complete blockchain.
Litecoin Core is extensively examined on a number of working programs utilizing the Linux kernel, macOS 10.10+, and Home windows 7 and newer (Home windows XP is just not supported).
Litecoin Core must also work on most different Unix-like programs however is just not steadily examined on them.
From 0.17.1 onwards macOS
Recognized points
- Upgrading from 0.13.2 or older presently ends in reminiscence blow-up through the roll-back of blocks to the SegWit activation level. In these circumstances, a full
-reindexis critical. - The GUI suffers from visible glitches within the new MacOS darkish mode. This has to do with our Qt theme dealing with impacting older variations of Litecoin Core, however is anticipated to be resolved in 0.17.1.
The listtransactions RPC account parameter has been renamed to label.
When litecoin is configured with the -deprecatedrpc=accounts setting, specifying a label/account/dummy argument will return each outgoing and incoming transactions. With out the -deprecatedrpc=accounts setting, it is going to solely return incoming transactions (as a result of it was once doable to create transactions spending from particular accounts, however that is not possiblewith labels).
When -deprecatedrpc=accounts is about, it is doable to move the empty string “” to record transactions that do not have any label. With out -deprecatedrpc=accounts, passing the empty string is an error as a result of returning solely non-labeled transactions is just not usually helpful conduct and might trigger confusion.
-includeconf=can be utilized to incorporate extra configuration recordsdata. Solely works contained in thelitecoin.conffile, not inside included recordsdata or from command-line. A number of recordsdata could also be included. May be disabled from command- line through-noincludeconf. Observe that multi-argument instructions like-includeconfwill override previous-noincludeconf, i.e.
noincludeconf=1
includeconf=relative.conf
as litecoin.conf will nonetheless embody relative.conf.
- Block storage may be restricted underneath Preferences, within the Most important tab. Undoing this setting requires downloading the total blockchain once more. This mode is incompatible with -txindex and -rescan.
The -wallet= choice now accepts full paths as a substitute of requiring wallets to be situated within the -walletdir listing.
If -wallet= is specified with a path that doesn’t exist, it is going to now create a pockets listing on the specified location (containing a pockets.dat knowledge file, a db.log file, and database/log.?????????? recordsdata) as a substitute of simply creating an information file on the path and storing log recordsdata within the guardian listing. This could make backing up wallets extra simple than earlier than as a result of the required pockets path can simply be immediately archived with out having to look within the guardian listing for transaction log recordsdata.
For backwards compatibility, pockets paths which might be names of present knowledge recordsdata within the -walletdir listing will proceed to be accepted and interpreted the identical as earlier than.
Beforehand, wallets might solely be loaded or created at startup, by specifying -wallet parameters on the command line or within the litecoin.conf file. It’s now doable to load, create and unload wallets dynamically at runtime:
- Present wallets may be loaded by calling the
loadwalletRPC. The pockets may be specified as file/listing basename (which should be situated within thewalletdirlisting), or as an absolute path to a file/listing. - New wallets may be created (and loaded) by calling the
createwalletRPC. The supplied identify should not match a pockets file within thewalletdirlisting or the identify of a pockets that’s presently loaded. - Loaded wallets may be unloaded by calling the
unloadwalletRPC.
This characteristic is presently solely obtainable by means of the RPC interface.
Partial spend avoidance
When an tackle is paid a number of occasions the cash from these separate funds may be spent individually which hurts privateness as a consequence of linking in any other case separate addresses. A brand new -avoidpartialspends flag has been added (default=false). If enabled, the pockets will all the time spend present UTXO to the identical tackle collectively even when it ends in larger charges. If somebody have been to ship cash to an tackle after it was used, these cash will nonetheless be included in future coin choices.
The default minimal transaction payment -mintxfee has been lowered to 0.0001 LTC/kB after enjoyable the minimal relay and dirt relay payment charges in prior releases.
It’s now doable for a single configuration file to set totally different choices for various networks. That is finished through the use of sections or by prefixing the choice with the community, corresponding to:
primary.uacomment=litecoin
take a look at.uacomment=litecoin-testnet
regtest.uacomment=regtest
[main]
mempoolsize=300
[test]
mempoolsize=100
[regtest]
mempoolsize=20
If the next choices will not be in a bit, they’ll solely apply to mainnet: addnode=, join=, port=, bind=, rpcport=, rpcbind= and pockets=. The choices to decide on a community (regtest= and testnet=) should be specified outdoors of sections.
A brand new ‘label’ API has been launched for the pockets. That is supposed as a substitute for the deprecated ‘account’ API. The ‘account’ can proceed for use in V0.17 by beginning litecoind with the ‘-deprecatedrpc=accounts’ argument, and will likely be totally eliminated in V0.18.
The label RPC strategies mirror the account performance, with the next practical variations:
- Labels may be set on any tackle, not simply receiving addresses. This performance was beforehand solely obtainable by means of the GUI.
- Labels may be deleted by reassigning all addresses utilizing the
setlabelRPC technique. - There isn’t help for sending transactions from a label, or for figuring out which label a transaction was despatched from.
- Labels shouldn’t have a steadiness.
Listed here are the adjustments to RPC strategies:
