Connect with us

Litecoin Core v0.16.0 Release Candidate

Published

on

Adrian Gallagher

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

We are pleased to release Litecoin Core 0.16.0 release candidate. This is a new major version release, including new features, various bugfixes and performance improvements, as well as updated translations.

It is recommended for power users to upgrade to this version. After sufficient testing, Litecoin Core v0.16.0 final will be released and is recommended for all users to upgrade.

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:

  • 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 if it becomes unavailable during operation, funds may be lost.

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/dependencies.md 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/rpcuser.py script was renamed to share/rpcauth/rpcauth.py. 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:

70c8530b957110ba6eaa4794d28b667ecff7e59d0e306e5899236aab5dd84e0b litecoin-0.16.0-aarch64-linux-gnu.tar.gz
b0a5ee56f89fcdb74b580ec5de0ff054b3b7dbb0a2cf6384f066e2217d6830a8 litecoin-0.16.0-arm-linux-gnueabihf.tar.gz
e5dab0814efdad4e0ae61b76d7b859e6fda6224c9fbe5d5fc6807fb7e13a05b1 litecoin-0.16.0-i686-pc-linux-gnu.tar.gz
90fcabe4627aa8c822a9ce7eb8fa55eb8a497c31513369bd8078c8401bf8583c litecoin-0.16.0-osx64.tar.gz
1d3a0ebb0b5c32f36f2157c252b8623c3152d318e7a40c8726e572b4e013ed17 litecoin-0.16.0rc1-osx.dmg
32ab7a80215092b02bc800e9c5d4bc7c0df2da693876f6ebd7e4a6277a812e05 litecoin-0.16.0rc1-win32-setup.exe
35572a215f034eb7c23e4c73c146e631087acf928a3b76113bc70fead3585052 litecoin-0.16.0rc1-win64-setup.exe
7dc4d72a40ec175bc00c464f626f8ffbff8a583e2105da1365662dceff138736 litecoin-0.16.0.tar.gz
f6d2f55f7f02f49bb6764e560d82cece7a8a598cf895af5c6947334b1e5ff7b2 litecoin-0.16.0-win32.zip
ae068caf852de47fb649f9002a440b57386ea88e5a6347287af15a8e2532d27e litecoin-0.16.0-win64.zip
2ca17e763d08ef621ea137519117234dd20db4be58cd3db317e40fe85b13fe4e 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
  • ultragtx
  • VKoskiv
  • voidmain
  • xinxi

Source: https://blog.litecoin.org/litecoin-core-v0-16-0-release-candidate-e1ac751d7f33?source=rss—-d41bceeb173b—4

Blockchain

Robinhood Testing New Cryptocurrency Wallet as Demand Rises

Published

on

The millennial-focused trading portal is edging closer to launching a long-awaited app that will enable its growing user-base to send and receive cryptocurrencies.

A beta version of Robinhood’s iPhone app showed the company’s latest upgrades on the new digital asset features, according to Bloomberg.

There is a hidden image showing a waiting list for users eager to get their hands on the app and code referring to crypto transfers, it added.

Delving Deeper into Crypto

Robinhood users can already buy and sell cryptocurrencies on the platform but they need to convert them to and from USD. With a native app, users will be able to send crypto assets to each other directly and set up two-factor authentication for additional security.

Robinhood Chief Executive Officer Vlad Tenev stated that adding crypto wallets is a priority for the company’s developers and they are actively working on such.


ADVERTISEMENT

“The ability to deposit and withdraw cryptocurrencies is tricky to do with scale, and we want to make sure it’s done correctly and properly.”

He did not specify a launch date, but the beta app leak suggests it is not too far away. Users of the new functions will need to activate crypto sending and receiving and the registration page will require an identity check, the report added.

On Sept. 11, CryptoPotato reported that Robinhood had launched incentives to promote longer-term cryptocurrency investing. The zero-fee recurring purchase feature enables users to schedule digital asset purchases for regular intervals with buys as low as a dollar.

This will encourage customers to build their cryptocurrency portfolios over time and “become a whole coiner,” stated Robinhood.

Robinhood Users Hungry For Crypto

Cryptocurrency trading has been one of the biggest drivers of revenue for Robinhood this year. Dogecoin has been the crown jewel, according to the company. It reported that 62% of its $233 million in second-quarter crypto income came from DOGE trading.

It added that more than half of all transaction-based revenue on the platform came from digital asset trading. The firm did warn that Q3 would not be as prosperous due to “seasonal headwinds and lower trading activity across the industry.”

Robinhood share prices have already fallen 43% since their all-time high of a little over $70 in early August. They are currently trading down 1.68% since Monday’s open at $40.70 according to Yahoo! Finance.

SPECIAL OFFER (Sponsored)

Binance Futures 50 USDT FREE Voucher: Use this link to register & get 10% off fees and 50 USDT when trading 500 USDT (limited offer).

PrimeXBT Special Offer: Use this link to register & enter POTATO50 code to get 50% free bonus on any deposit up to 1 BTC.

You Might Also Like:


PlatoAi. Web3 Reimagined. Data Intelligence Amplified.

Click here to access.

Source: https://cryptopotato.com/robinhood-testing-new-cryptocurrency-wallet-as-demand-rises/

Continue Reading

Blockchain

Snoop Dogg Reveals His Connection With Twitter Account on NFTs

Snoop Dogg Twitter

Rate this post American rapper Snoop Dogg tweeted on Monday that he’s the owner of a Twitter account that talks about nonfungible tokens (NFTs). The account, named @CozomoMedici, shares “insights and tales from the wild world of NFTs” and has 27.7K followers at the moment. Snoop Dog Claims to Be Popular NFT Advocate on Twitter Snoop Dogg left the crypto community stunned this week after he revealed himself as the owner of a Twitter account dedicated to NFTs.  The account Cozomo de’ Medici, named after an Italian banker, is only a month old. However, it has already garnered attention from industry watchers and even a mention from crypto-focused news outlet The Block.   According to The Verge, the person behind the Medici account had been creating hype around their real identity for “at least a few days” and even conducted a poll for their followers to take a guess. The poll featured Democratic congresswoman Alexandria Ocasio-Cortez and Matt Bellamy, the lead singer of the rock band Muse. Snoop, however, was not mentioned in the poll. On September 20, @CozomoMedici tweeted that they were about to reveal their identity from their account. Shortly after, Snoop Dogg tweeted “I am @CozomoMedici.”   Interestingly, after making this revelation, the Medici account bought two weed-themed collectibles from an artist named NyanDogg, The Verge reported. Additionally, Snoop’s alleged OpenSea account has been sent  “a cloud of blunt and Snoop-themed NFTs” following the reveal. Is Medici Account an Elaborate Prank? The Medici account could likely turn out to be an elaborate prank, one that Snoop might have engineered himself or just participated in. Many reactions to Medici’s reveal have also expressed skepticism about Snoop’s involvement. “I have a hard time accepting that this account is Snoop Dogg. Like seriously Snoop Dogg muted his live stream for a week (?) by accident. And he is that deep into NFTs out here owning crypto punks… Owning Eth using OpenSea. Would love that to be true but I can’t believe it,” Twitter user @Brandolf485 wrote in the comments. Nonetheless, the crypto community will have to continue looking for concrete proof till Snoop’s involvement with the account is confirmed. 

The post Snoop Dogg Reveals His Connection With Twitter Account on NFTs appeared first on Cryptoknowmics-Crypto News and Media Platform.

Published

on

American rapper Snoop Dogg tweeted on Monday that he’s the owner of a Twitter account that talks about nonfungible tokens (NFTs). The account, named @CozomoMedici, shares “insights and tales from the wild world of NFTs” and has 27.7K followers at the moment.

Snoop Dog Claims to Be Popular NFT Advocate on Twitter

Snoop Dogg left the crypto community stunned this week after he revealed himself as the owner of a Twitter account dedicated to NFTs. 

The account Cozomo de’ Medici, named after an Italian banker, is only a month old. However, it has already garnered attention from industry watchers and even a mention from crypto-focused news outlet The Block.  

According to The Verge, the person behind the Medici account had been creating hype around their real identity for “at least a few days” and even conducted a poll for their followers to take a guess. The poll featured Democratic congresswoman Alexandria Ocasio-Cortez and Matt Bellamy, the lead singer of the rock band Muse. Snoop, however, was not mentioned in the poll.

On September 20, @CozomoMedici tweeted that they were about to reveal their identity from their account. Shortly after, Snoop Dogg tweeted “I am @CozomoMedici.”

Interestingly, after making this revelation, the Medici account bought two weed-themed collectibles from an artist named NyanDogg, The Verge reported. Additionally, Snoop’s alleged OpenSea account has been sent  “a cloud of blunt and Snoop-themed NFTs” following the reveal.

Is Medici Account an Elaborate Prank?

The Medici account could likely turn out to be an elaborate prank, one that Snoop might have engineered himself or just participated in. Many reactions to Medici’s reveal have also expressed skepticism about Snoop’s involvement.

“I have a hard time accepting that this account is Snoop Dogg. Like seriously Snoop Dogg muted his live stream for a week (?) by accident. And he is that deep into NFTs out here owning crypto punks… Owning Eth using OpenSea. Would love that to be true but I can’t believe it,” Twitter user @Brandolf485 wrote in the comments.

Nonetheless, the crypto community will have to continue looking for concrete proof till Snoop’s involvement with the account is confirmed. 

PlatoAi. Web3 Reimagined. Data Inteligence Amplifed.
Click here for Free Trial.

Source: https://www.cryptoknowmics.com/news/snoop-dogg-reveals-his-connection-with-twitter-account-on-nfts/

Continue Reading

Blockchain

TA: Ethereum Breaking This Confluence Resistance Could Spark a Recovery

Published

on

Ethereum started a major decline below the $3,200 support zone against the US Dollar. ETH price traded as low as $2,807 and it is now attempting a recovery wave.

  • Ethereum started a fresh decline below the $3,300 and $3,200 support levels.
  • The price is now trading below $3,200 and the 100 hourly simple moving average.
  • There is a key bearish trend line forming with resistance near $3,020 on the hourly chart of ETH/USD (data feed via Kraken).
  • The pair could a steady recovery wave if there is a close above $3,050 in the near term.

Ethereum Price Corrects Losses

Ethereum started a major decline from the $3,500 resistance zone. ETH traded below many important support zones near $3,300 and the 100 hourly simple moving average, similar to bitcoin.

The bears gained strength below the $3,200 support zone. Finally, ether spiked below $3,000 and extended its decline. A low is formed near $2,807 and the price is now correcting losses. There was a break above the $2,920 and $2,950 resistance levels.

The price recovered above the 23.6% Fib retracement level of the recent decline from the $3,455 swing high to $2,807 low. An immediate resistance on the upside is near the $3,020 level. There is also a key bearish trend line forming with resistance near $3,020 on the hourly chart of ETH/USD.

Ethereum Price

Source: ETHUSD on TradingView.com

A close above the $3,020 and $3,050 levels could start a decent recovery. The next major resistance might be near the $3,130 level. It is near the 50% Fib retracement level of the recent decline from the $3,455 swing high to $2,807 low. A clear break and close above the $3,130 level could start a steady increase. The next major resistance sits near $3,300.

More Losses in ETH?

If ethereum fails to correct higher above the $3,020 and $3,050 resistance levels, it could start another decline. An initial support on the downside is near the $2,960 level.

The next major support seems to be forming near the $2,900 level. A downside break below the $2,900 support zone could lead the price towards the $2,800 zone. The next major support is near the $2,750 level, below which ether price might decline towards the $2,640 support zone.

Technical Indicators

Hourly MACDThe MACD for ETH/USD is slowly losing pace in the bearish zone.

Hourly RSIThe RSI for ETH/USD is still well below the 50 level.

Major Support Level – $2,960

Major Resistance Level – $3,050

PlatoAi. Web3 Reimagined. Data Intelligence Amplified.

Click here to access.

Source: https://www.newsbtc.com/analysis/eth/ethereum-confluence-resistance-3050/

Continue Reading
Uncategorized5 days ago

Swissquote Confirms European Expansion Plan, Focusing on Crypto

Blockchain5 days ago

Massive NFT and Token Giveaway from Polker as Staking is Announced!

Uncategorized5 days ago

Bingbon Launches its Carbon Free and Afforestation Project

Uncategorized5 days ago

Nickelodeon All-Star Brawl will include DLC fighters post-launch

News4 days ago

Gods Unchained and Guild of Guardians Layer 2 Solution Immutable Raises $60 Million

Blockchain3 days ago

Over 40 days after Ethereum’s EIP-1559, here’s where it stands

Blockchain5 days ago

Opensea NFT marketplace Accuses Senior Employee of Insider Trading

Blockchain5 days ago

Grab a spot in Tomi’s presale by bagging an NFT – 260+ ETH raised!

Blockchain5 days ago

Kanga Exchange Partners with Tenset for an Exclusive Public Sale of KNG Token

Blockchain3 days ago

Cardano Sees an Influx in Smart Contracts ! But There’s a Twist

Blockchain4 days ago

If Shiba Inu is a ‘shitcoin,’ why are exchanges still listing it

Blockchain5 days ago

Ethereum, NEO, Dogecoin Price Analysis: 16 September

Uncategorized2 days ago

NBA 2K22 Limitless Spot-Up and Chef Badges Explained

News5 days ago

MicroStrategy Issues a Response to FASB’s 2021 ‘Invitation to Comment’

Blockchain5 days ago

Over $1B Worth of ETH Burned in the Aftermath of Ethereum’s London Upgrade

Uncategorized4 days ago

Laos Green-Lights Cryptocurrency Trials

Blockchain5 days ago

Bitcoin Cash: A 40% hike may be incoming from this setup

Uncategorized5 days ago

Tether Claims to Hold no Commercial Paper From Struggling Evergrande

Uncategorized4 days ago

DeFi comes to Cardano (ADA) as EMURGO announces ‘Astarter’

Blockchain4 days ago

Bitdefender Releases Tool To Decrypt Files Affected by REvil/Sodinokibi Ransomware

Trending