Litecoin Core v0.14.2 launched

A new major version of Litecoin Core has been released 
01 August 2017   1719
Litecoin

Litecoin features faster transaction confirmation times and improved storage efficiency than the leading math-based currency

Litecoin Core is the Litecoin reference client featuring "full node" capabilities to fully download and validate the Litecoin blockchain as well as wallet functionality to manage transactions. It is the most feature rich client out there and contains all the protocol rules required for the Litecoin network to function. 

Blockchain

Distributed database that is used to maintain a continuously growing list of records, called blocks

Xinxi Wang, director of LTCFoundation and LitecoinCore developer, reports on his Twitter about the brand new release:

As the team claims, Litecoin Core 0.14.2 is a new major version release, including new features, various bug fixes and performance improvements.

What's new?

  • New Multisig Address Prefix - Litecoin Core now supports P2SH addresses beginning with M on mainnet and Q on testnet. P2SH addresses beginning with 3 on mainnet and m or n on testnet will continue to be valid. Old and new addresses can be used interchangeably.
  • miniupnp CVE-2017–8798 - Bundled miniupnpc was updated to 2.0.20170509. This fixes an integer signedness error (present in MiniUPnPc v1.4.20101221 through v2.0) that allows remote attackers (within the LAN) to cause a denial of service or possibly have unspecified other impact. This only affects users that have explicitly enabled UPnP through the GUI setting or through the -upnp option, as since the last UPnP vulnerability (in Litecoin Core 0.10.4) it has been disabled by default.
  • Reset Testnet - Testnet3 has been deprecated and replaced with Testnet4. The server port has been changed to 19335 however the RPC port remains the same (19332).
  • Performance Improvements - Validation speed and network propagation performance have been greatly improved, leading to much shorter sync and initial block download times. 1)The script signature cache has been reimplemented as a “cuckoo cache”, allowing for more signatures to be cached and faster lookups. 2)Assumed-valid blocks have been introduced which allows script validation to be skipped for ancestors of known-good blocks, without changing the security model. See below for more details. 3)In some cases, compact blocks are now relayed before being fully validated as per BIP152. 4)P2P networking has been refactored with a focus on concurrency and throughput. Network operations are no longer bottlenecked by validation. As a result, block fetching is several times faster than previous releases in many cases. 5)The UTXO cache now claims unused mempool memory. This speeds up initial block download as UTXO lookups are a major bottleneck there, and there is no use for the mempool at that stage.
  • Manual Pruning - Manual block pruning can now be enabled by setting -prune=1. Once that is set, the RPC command pruneblockchain can be used to prune the blockchain up to the specified height or timestamp.
  • getinfo Deprecated - The getinfo RPC command has been deprecated. Each field in the RPC call has been moved to another command's output with that command also giving additional information that getinfo did not provide. 
  • ZMQ On Windows - Previously the ZeroMQ notification system was unavailable on Windows due to various issues with ZMQ. These have been fixed upstream and now ZMQ can be used on Windows. 
  • Nested RPC Commands in Debug Console - The ability to nest RPC commands has been added to the debug console. This allows users to have the output of a command become the input to another command without running the commands separately. The nested RPC commands use bracket syntax (i.e. getwalletinfo()) and can be nested (i.e. getblock(getblockhash(1))). Simple queries can be done with square brackets where object values are accessed with either an array index or a non-quoted string (i.e. listunspent()[0][txid]). Both commas and spaces can be used to separate parameters in both the bracket syntax and normal RPC command syntax.
  • Network Activity Toggle - A RPC command and GUI toggle have been added to enable or disable all p2p network activity. The network status icon in the bottom right hand corner is now the GUI toggle. Clicking the icon will either enable or disable all p2p network activity. If network activity is disabled, the icon will be grayed out with an X on top of it. Additionally the setnetworkactive RPC command has been added which does the same thing as the GUI icon. The command takes one boolean parameter, true enables networking and false disables it.
  • Out-of-sync Modal Info Layer - When Litecoin Core is out-of-sync on startup, a semi-transparent information layer will be shown over top of the normal display. This layer contains details about the current sync progress and estimates the amount of time remaining to finish syncing. This layer can also be hidden and subsequently unhidden by clicking on the progress bar at the bottom of the window.

And so on and so forth...

We hope that this tiny peace of information convinced you that the new release is indeed significant and major. We do not aim to retype all the information from the release to the article in order not to overload our readers, so that if you are interested in the full list of changes, go visit Litecoin official blogpost.

Ethereum Scaling Solution Raiden to Launch Last Testnet

As noted by the developers, after implementing the new solution, the Ethereum network will be able to provide more than a million transactions per second
20 July 2018   132

On Thursday, July 19, at the Dappcon developer conference in Berlin, the last test network of Raiden for the Ethereum blockchain was launched, CoinDesk reports.

The release includes a minimal implementation of the scaling solution, which will allow the transfer of Ethereum tokens outside of the main blockchain. This is the last test phase before the introduction of technology into the core network of Ethereum.

It's the first step towards going to the mainnet. We really want people to really test this so we have a user interface, we have an API and we've created an open Github for everything they could find, so if we go hopefully bug-free on the mainnet.
 

Lefteris Karapetsas

Core Developer, Raiden

According to him, the new release represents an early implementation for the core network and contains a new rewritten code of smart contracts and payment channels that can be restored in case of unintended closure.

Also, Karapetsas urged developers to join the test network to help detect possible bugs, adding that a bounty program will be launched to encourage this activity.

The release date for the main network has not yet been assigned, but the developers intend to follow this earlier promise and launch Raiden this summer.

Karapetsas also promised to publish regular updates and code optimizations after the full release, adding that Raiden will complement other Ethereum scaling solutions that are currently being developed.

Raiden is essentially the payment channel network for ethereum, it's supposed to help us scale token transfers. The long term goal would be to have people use Raiden from a mobile device and be able to make off-chain token transfers just from their phone. That would be the long term vision, it would probably work in combination with various scaling solutions, sharding, plasma, a sort of hybrid.
 

Lefteris Karapetsas

Core Developer, Raiden

Raiden is developing from the 2015 and is written mostly on Python. The project is much like the Lightning Network. As noted by the developers, after implementing the new solution, the Ethereum network will be able to provide more than a million transactions per second.