Follow our Twitter for the latest dev news.
We are pleased to release Litecoin Core 0.18.1 release candidate. This is a new major version release, including new features, various bug fixes, performance improvements and updated translations.
It is recommended for power users to upgrade to this version. After sufficient testing, Litecoin Core 0.18.1 final will be released and is recommended for all users to upgrade.
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over
/Applications/Litecoin-Qt (on Mac) or
litecoin-qt (on Linux).
The first time you run version 0.15.0 or newer, your chainstate database will be converted to a new format, which will take anywhere from a few minutes to half an hour, depending on the speed of your machine.
Note that the block database format also changed in version 0.8.0 and there is no automatic upgrade code from before version 0.8 to version 0.15.0 or later. Upgrading directly from 0.7.x and earlier without redownloading the blockchain is not supported. However, as usual, old wallet versions are still supported.
Litecoin Core is supported and extensively tested on operating systems using the Linux kernel, macOS 10.10+, and Windows 7 and newer. It is not recommended to use Litecoin Core on unsupported systems.
Litecoin Core should also work on most other Unix-like systems but is not as frequently tested on them.
From 0.17.0 onwards, macOS <10.10 is no longer supported. 0.17.0 is built using Qt 5.9.x, which doesn’t support versions of macOS older than 10.10. Additionally, Litecoin Core does not yet change appearance when macOS “dark mode” is activated.
In addition to previously-supported CPU platforms, this release’s pre-compiled distribution also provides binaries for the RISC-V platform.
For advanced users who have both (1) enabled coin control features, and (2) are using multiple wallets loaded at the same time: The coin control input selection dialog can erroneously retain wrong-wallet state when switching wallets using the dropdown menu. For now, it is recommended not to use coin control features with multiple wallets loaded.
- Calls to
getblocktemplatewill fail if the segwit rule is not specified. Calling
getblocktemplatewithout segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
Configuration option changes
- A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are
- Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the “high water mark”) before dropping additional messages. The default value is 1,000, the same as was used for previous releases. See the ZMQ documentation for details.
rpcallowipoption can no longer be used to automatically listen on all network interfaces. Instead, the
rpcbindparameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g.
docker run [...] -p 127.0.0.1:9332:9332(this is an extra
:9332over the normal Docker port specification).
rpcpasswordoption now causes a startup error if the password set in the configuration file contains a hash character (#), as it’s ambiguous whether the hash character is meant for the password or as a comment.
whitelistforcerelayoption is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers. Users can still explicitly enable this behavior with the command line option (and may want to consider contacting the Litecoin Core project to let us know about their use-case, as this feature could be deprecated in the future).
When creating a transaction with a fee above
-maxtxfee (default 0.1 LTC), the RPC commands
fundrawtransaction will now fail instead of rounding down the fee. Beware that the
feeRate argument is specified in LTC per kilobyte, not litoshi per byte.
- A new short document about the JSON-RPC interface describes cases where the results of an RPC might contain inconsistencies between data sourced from different subsystems, such as wallet state and mempool state. A note is added to the REST interface documentation indicating that the same rules apply.
- Further information is added to the JSON-RPC documentation about how to secure this interface.
- A new document about the
litecoin.conffile describes how to use it to configure Litecoin Core.
- A new document introduces Litecoin Core’s BIP174 Partially-Signed Litecoin Transactions (PSBT) interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
- The output script descriptor documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
- A new
--disable-bip70option may be passed to
./configureto prevent Litecoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Litecoin Core to libssl vulnerabilities in the past, builders who don’t need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
- The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddressesreturns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdirreturns a list of wallets in the wallet directory (either the default wallet directory or the directory configured by the
getrpcinforeturns runtime details of the RPC server. At the moment, it returns an array of the currently active commands and how long they’ve been running.
deriveaddressesreturns one or more addresses corresponding to an output descriptor.
getdescriptorinfoaccepts a descriptor and returns information about it, including its computed checksum.
joinpsbtsmerges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all of the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbtexamines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT,
analyzepsbtprovides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and
analyzepsbtwill also list the next role in general needed to complete the PSBT.
analyzepsbtwill also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbtsearches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions,
utxoupdatepsbtwill only add the UTXO for segwit inputs.
Note: some low-level RPC changes mainly useful for testing are described in the Low-level Changes section below.
getpeerinfonow returns an additional
minfeefilterfield set to the peer’s BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
- The mempool RPCs, such as
verbose=true, now return an additional “bip125-replaceable” value indicating whether the transaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfeepreviously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of “0” may still be used to request the minimum value.
getaddressinfonow provides an
ischangefield indicating whether the wallet used the address in a change output.
importmultihas been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional
importmultinow returns an additional
warningsfield for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfonow returns an additional
solvableboolean field when Litecoin Core knows enough about the address’s scriptPubKey, optional redeemScript, and optional witnessScript in order for the wallet to be able to generate an unsigned input spending funds sent to that address.
scantxoutsetRPCs now return an additional
descfield that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The
descfield is only returned for
listunspentwhen the address is solvable.
importprivkeywill preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label “cold wallet” in earlier releases of Litecoin Core, subsequently importing the private key would default to resetting the address’s label to the default empty-string label (“”). In this release, the previous label of “cold wallet” will be retained. If you optionally specify any label besides the default when calling
importprivkey, the new label will be applied to the address.
- See the Mining section for changes to
currentblocktxwhen a block was never assembled via RPC on this node.
getrawtransactionRPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows: 1. If a blockhash is provided, check the corresponding block. 2. If no blockhash is provided, check the mempool. 3. If no blockhash is provided but txindex is enabled, also check txindex.
unloadwalletis now synchronous, meaning it will not return until the wallet is fully unloaded.
importmultinow supports importing of addresses from descriptors. A “desc” parameter can be provided instead of the “scriptPubKey” in a request, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through
importmultiwill have their key origin information stored in the wallet for use with creating PSBTs. More information about descriptors can be found here.
listunspenthas been modified so that it also returns
witnessScript, the witness script in the case of a P2WSH or P2SH-P2WSH output.
createwalletnow has an optional
blankargument that can be used to create a blank wallet. Blank wallets do not have any keys or HD seed. They cannot be opened in software older than 0.18. Once a blank wallet has a HD seed set (by using
sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 0.17.x. Encrypting a blank wallet will also set a HD seed for it.
signrawtransactionis removed after being deprecated and hidden behind a special configuration option in version 0.17.0.
- The ‘account’ API is removed after being deprecated in v0.17. The ‘label’ API was introduced in v0.17 as a replacement for accounts. See the release notes from v0.17 for a full description of the changes from the ‘account’ API to the ‘label’ API.
addwitnessaddressis removed after being deprecated in version 0.16.0.
generateis deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using
generatefor testing purposes should transition to using the
generatetoaddressRPC, which does not require or use the wallet component. Calling
generatetoaddresswith an address returned by the
getnewaddressRPC gives the same functionality as the old
generateRPC. To continue using
generatein this version, restart litecoind with the
- Be reminded that parts of the
validateaddresscommand have been deprecated and moved to
getaddressinfo. The following deprecated fields have moved to
addressesfield has been removed from the
getaddressinfoRPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the
embedded.addressfield for P2SH or P2WSH wrapped addresses, and
pubkeysfor inspecting multisig participants.
- A new
/rest/blockhashbyheight/endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
- A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
- In the Send tab, the checkbox for “pay only the required fee” has been removed. Instead, the user can simply decrease the value in the Custom Feerate field all the way down to the node’s configured minimum relay fee.
- In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the
createwalletRPC and the
disable_private_keysparameter was set to true.
- The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (use CXXFLAGS=”-mmacosx-version-min=10.11″ CFLAGS=”-mmacosx-version-min=10.11″ for setting the deployment sdk version)
- A new
litecoin-wallettool is now distributed alongside Litecoin Core’s other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
This section describes planned changes to Litecoin Core that may affect other Litecoin software and services.
- Since version 0.16.0, Litecoin Core’s built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely-used software. Starting with Litecoin Core 0.20 (expected about a year after 0.18), Litecoin Core will default to native segwit addresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Litecoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Litecoin Core 0.20. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn’t want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the
addresstype=bech32configuration option in any Litecoin Core release from 0.16.0 up.)
- BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v0.17 with the
-enablebip61=0option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
This section describes RPC changes mainly useful for testing, mostly not relevant in production. The changes are mentioned for completeness.
submitblockRPC previously returned the reason a rejected block was invalid the first time it processed that block, but returned a generic “duplicate” rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns “duplicate” for valid blocks it has already accepted.
- A new
submitheaderRPC allows submitting block headers independently from their block. This is likely only useful for testing.
signrawtransactionwithwalletRPCs have been modified so that they also optionally accept a
witnessScript, the witness script in the case of a P2WSH or P2SH-P2WSH output. This is compatible with the change to
- For the
walletcreatefundedpsbtRPCs, if the
bip32derivsparameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
-usehdconfiguration option was removed in version 0.16. From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying
-usehdan invalid configuration option.
- This release allows peers that your node automatically disconnected for misbehavior (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don’t have many other peers). Previously, Litecoin Core banned the IP addresses of misbehaving peers for a period of time (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the
setbanRPC, all connections from that peer will still be rejected.
- The key metadata will need to be upgraded the first time that the HD seed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
- Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
- A sub-project of Litecoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Litecoin Core. See their project page for details.
- This release changes the Random Number Generator (RNG) used from OpenSSL to Litecoin Core’s own implementation, although entropy gathered by Litecoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Litecoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
- On macOS, Litecoin Core now opts out of application CPU throttling (“app nap”) during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
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:
Thanks to everyone who directly contributed to this release:
- The Bitcoin Core Developers
- Adrian Gallagher
- Martin Smith
Increasing Stability of the Utopia P2P Network
The number of full nodes in the Utopia P2P ecosystem has passed the 30,000 mark.
This means that more than 30,000 nodes are working for the security and resilience of the network.
The number of full nodes within the Utopia decentralized ecosystem has reached 30,000 and is moving forward. This number is an indicator of the stability of internal processes and a guarantor of reliability.
Nodes in the blockchain have one of the most important roles – they are responsible for checking the legitimacy of blocks, approving transactions, and ensuring the smooth operation of the network. To a large extent, this responsibility falls squarely on the full nodes. In other words, the more nodes involved in supporting the network, the harder it is to trick, hack or crash the system. As a consequence, better connection quality, safer operations, cleaner and more honest mining.
When you install and run Utopia ecosystem mining bot, you automatically increase the number of nodes, thereby contributing to the stability of the network. Everyone involved in this process receives Crypton Cryptocurrency (CRP).
Crypton is the unique currency of the Utopia peer-to-peer network. Coin mining does not burden your PC and is eco-friendly as it is done through an ecosystem. All you need to mine is a computer and a bot installed.
By launching the app, you start receiving collective rewards every 15 minutes – that’s how long it takes to form a new block. Users also receive a Proof of Stake reward to their minimum monthly balance. CRP is already listed on a number of exchanges and is available for sale.
– Anyone can mine, send and receive Cryptons. Cryptocurrency mining is available to all Utopia ecosystem users. CRPs are provided for being on the network and. Mining participants are rewarded for supporting the ecosystem – forwarding packets and providing RAM for caching purposes,” according to 1984 Group, the developer of the Utopia P2P network.
At the time of writing, 4,672,181.975674 CRPs have already been mined by Utopia network users, with the total number of transactions steadily approaching 300,000.
The creators of Utopia Network have built an independent ecosystem, which doesn’t ask for your personal information even when you register and doesn’t track your activities or geolocation.
The server is basically not involved in data transfer and storage. The Curve25519, XSalsa20, and Poly1305 algorithms are used to encrypt, sign, and authenticate packets, objects, and peer-to-peer connections.
This way, you don’t have to worry about the security of your personal data and are free to use the Utopia ecosystem. In addition to in-network mining there are anonymous messenger, browser, email, and e-wallet. All functionality is focused on user anonymity and is available to all registered in the Utopia P2P decentralized network.
As far as we know, in the near future the developers will release an encrypted anonymous Utopia ecosystem app on IOs and Android.
Click here for Free Trial.
Investors must brace themselves as Bitcoin Cash goes downhill in the coming weeks
Though off to a strong start in September, Bitcoin Cash seemed to have taken its foot off the pedal. Caught between two corrective phases on 7 and 20 September, the price steadily declined after forming a local peak above $800.
Moreover, BCH’s latest drawdown towards 38.2% Fibonacci level identified vulnerabilities in the market which could extend all the way back to July lows. With sentiment also expected to be sour due to a recent death cross, BCH bulls certainly faced a tall mountain to climb. At the time of writing, BCH traded at $549.2, down by 4.8% over the last 24 hours.
BCH Daily Chart
A near 16% decline from the 50% Fibonacci level pushed BCH to the all important 38.2% Fibonacci level. Back in late-June, BCH suffered a 31% sell-off after it pierced below the aforementioned level on the back of a descending triangle. Hence, to dissuade short-sellers from the market, BCH would need to keep its neck above the $540-mark.
However, certain factors in the market could not be overlooked. For instance, each of BCH’s indicators slipped below their equilibrium points for the first time in nearly 2-months, while a negative crossover between the 20-SMA (red) and 200-SMA (green) created some more uncertainties.
Even though corrective phases have been overserved previously in the market, BCH’s RSI held above it mid-line. This was not the case anymore after the RSI shifted below 45 and into bearish territory. In fact, the RSI was yet to touch the oversold territory, which meant that BCH could see some more losses rather than an immediate reversal. Such was the case with the MACD and Awesome Oscillator as well, which slipped below their equilibrium levels. If sentiment continues to be weak, the 23.6% Fibonacci level and $400 would come back into play.
Bitcoin Cash’s long term narrative took quite a hit after prices declined below the 50% Fibonacci mark. In fact, this also negated a bullish setup which was highlighted in an earlier article. BCH’s indicators also fell into bearish zones after this retracement. Considering these factors, BCH was open to a further sell-off towards the $400-mark in the coming weeks.
Where to Invest?
Subscribe to our newsletter
PlatoAi. Web3 Reimagined. Data Intelligence Amplified.
Indian government cautious about crypto-adoption, CBDC is a possibility
Indian traders and exchanges might be bullish about the crypto market, but the Indian government doesn’t seem keen on rushing into the scene. At least, not until studying its homegrown fintech industry and the anti-Bitcoin protests in El Salvador.
Tracking global news
Indian finance minister Nirmala Sitharaman in a recent interview with Hindustan Times explained why the country seemed to be falling behind when it came to crypto adoption.
Though she admitted, El Salvador wasn’t “the best example,” Sitharaman said,
“You’d think common people don’t care about digital currency; but the public took to the streets against the move. It’s not a question of literacy or understanding – it’s also a question of to what extent this is a transparent currency; is it going to be a currency available for everyone?”
Sitharaman referred to CBDCs as a “legitimate” cryptocurrency and admitted there could be a “possibility,” in hat regard. She noted that India held the “strength of the technology” and acknowledged the need to formulate a Cabinet note. However, Sitharaman wondered if India was ready to follow El Salvador’s way.
Facts on the ground
Though accessibility is a pressing concern, more Indians have discovered crypto than perhaps expected.
Nischal Shetty, CEO of the Indian crypto exchange WazirX – a subsidiary of Binance Holdings – has stated that WazirX sign-ups from India’s tier-two and tier-three cities overtook those from tier-one cities this year. Even so, sign-ups from tier-one cities themselves saw a 2,375% rise. Furthermore, WazirX added one million users in April 2021 alone.
Compared to few years ago, today people better understand crypto classification
Crypto is not just a currency but also utility & asset. There are new use cases emerging every day
India has over 20M people in Crypto now. It’s a great time to BUIDL 🚀#IndiaWantsCrypto
— Nischal (WazirX) ⚡️ (@NischalShetty) September 19, 2021
Adding to this, the cost of electricity and Internet data in India are relatively cheaper, which could boost both crypto trading and mining in the future. However, at the last count, there was only one Bitcoin ATM in the whole country.
As per data by Useful Tulips, which combined data from Paxful and LocalBitcoins, India saw transfers worth around $4,502,369 in the last two weeks.
Could anti-Bitcoin protests happen in India?
There is evidence to support both sides. India has a strong history of mass protests, with the farmers’ protests against the government’s agricultural laws being one such example. The 2016 demonetization of part of the country’s paper currency still haunts many, and Internet penetration is yet to cross 50%.
However, India also has the largest diaspora in the world, with approximately 18 million people living outside the country. Crypto innovation could lead to hundreds of millions of dollars being saved on remittance charges as money is sent across borders.
But for the time being, it seems India’s urban residents are more bullish about crypto than its government.
Where to Invest?
Subscribe to our newsletter
PlatoAi. Web3 Reimagined. Data Intelligence Amplified.
Over 40 days after Ethereum’s EIP-1559, here’s where it stands
Gods Unchained and Guild of Guardians Layer 2 Solution Immutable Raises $60 Million
Cardano Sees an Influx in Smart Contracts ! But There’s a Twist
If Shiba Inu is a ‘shitcoin,’ why are exchanges still listing it
NBA 2K22 Limitless Spot-Up and Chef Badges Explained
After Targeting BlockFi, State Regulators Now Set Their Eyes On Celsius
Laos Green-Lights Cryptocurrency Trials
DeFi comes to Cardano (ADA) as EMURGO announces ‘Astarter’
Best Dribble Pull-Up in NBA 2K22: Which to Use
Bitdefender Releases Tool To Decrypt Files Affected by REvil/Sodinokibi Ransomware
What is The Old Gym in NBA 2K22 Next Gen?
NFTs Are the Building Blocks of the Metaverse — Here’s How It’s Being Built
Shiba Inu (SHIB) Rises to Range High
EY Taps Polygon Network to Improve Enterprise Clients’ Experience
Flux Pools autoriza o pagamento de ativos paralelos em mais de 300K Flux!
Matic Price to hit $1.75 in the next leg up! Launch on Bitfinex to be the Catalyst?
The Head of Diem wants you to trust Facebook, but is he fighting a losing battle?
XRP Lawsuit: Here’s Why Experts Think Ripple Could Win the Case Against SEC
All you need to know about MATIC before investing
PetPals, One Of The First Play-To-Earn NFT Web-Based Games Is Out Now
Uncategorized1 week ago
Fortnite says goodbye to season 7 with an alien ship, explosions, and a cliffhanger
Blockchain1 week ago
SBI-acquired TaoTao exchange in Japan relists XRP
News1 week ago
PUBG Mobile becomes the most earning game in August 2021
Uncategorized1 week ago
The best rookies in NBA 2K22
Blockchain1 week ago
Cardano Finally Ousting Ethereum? — Expect The Unexpected As Alonzo Hard Fork Kicks Off
Uncategorized1 week ago
All Maps in Battlefield 2042
Blockchain1 week ago
Polygon invests in Decentral Games to take Play-to-Earn gaming mainstream
Uncategorized1 week ago
Bjergsen reportedly returning to pro play for 2022