Follow our Twitter for the latest dev news.
We are pleased to release Litecoin Core 0.18.1. This is a new major version release, including new features, various bugfixes and performance improvements, as well as updated translations. It is recommended for all users to upgrade to this version.
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, 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:
e0bdd4aa81502551a0c5abcfaae52c8bbaf4a980548aa6c91053643d81924b51 litecoin-0.18.1-aarch64-linux-gnu.tar.gz59b73bc8f034208295634da56a175d74668b07613cf6484653cb467deafb1d52 litecoin-0.18.1-arm-linux-gnueabihf.tar.gz0a2788d58bd22c3754927e216bf18c64145b9fdc0d709f3f49ba3040b876a066 litecoin-0.18.1-i686-pc-linux-gnu.tar.gz4ce590ecbaecaced7253473bc574a2b70527c9aeb3a3ab33a843ea1c9caf0c86 litecoin-0.18.1-osx64.tar.gzb81d9101c6ecb38b7699cf3d05ab57df7922f40f23c8a3377750c335d7102266 litecoin-0.18.1-osx.dmge5585eaff887b9d3de9f14230db0375b858e5cccc571bdb909dfc337d5bd357c litecoin-0.18.1-riscv64-linux-gnu.tar.gz6dfa71ccf059463f0a304f85ff1ca8b88039d63e93269d6f056ab24915be936d litecoin-0.18.1.tar.gz778eac92953d82a3b2e0cdc925e7da9103edd0d9a9ffa151c3c7cc79b9814091 litecoin-0.18.1-win32-setup.exe39d02e463893c970f92ed5ffcb603a1a7b2e2dacdaea306e8526414af841d247 litecoin-0.18.1-win32.zipbd38a1d5d4ac1ca4246f9534032a369b0f3cd38fb2aa82c66010642fa72e65f7 litecoin-0.18.1-win64-setup.exe9ff1f552f8ed3f058a56332defa7c61cfb345848428d7b419182096eca2ac99a litecoin-0.18.1-win64.zipca50936299e2c5a66b954c266dcaaeef9e91b2f5307069b9894048acf3eb5751 litecoin-0.18.1-x86_64-linux-gnu.tar.gz
Thanks to everyone who directly contributed to this release:
- The Bitcoin Core Developers
- Adrian Gallagher
- Martin Smith
Solana, Polkadot, Algorand: What is the Bitcoin effect on these altcoins
With the market trading in red today pretty much all coins including Bitcoin and Ethereum are falling. However, there are some coins that made excellent gains in the last 2 months which are now facing huge price falls as well.
Which alts though?
Solana, Polkadot, and Algorand were three altcoins that successfully rallied between July and August. Polkadot rose from $12.34 all the way to $34.45 registering a 214.33% growth. Similar gains were observed for Algorand as the coin breached $2 and marked a 230.26% rise.
The most gains were seen by Solana holders though mainly because the altcoin shot up 713.94%. An increase this high was the result of the NFT hype which took it up from $26.68 to $191.07
In fact, Solana and Algorand even registered new all-time highs during this time period. But each of these coins is now observing significant price falls as well.
In the last 24 hours ALGO fell by 15.26%, DOT came down by 14.37% and SOL lost 16.8% of its price as of press time.
A huge reason behind this fall is also their exhausted momentum since even after the September 7 fall, DOT and ALGO witnessed another price rise before they finally hit a slowdown.
Owing to this investors are possibly getting rid of their holdings in both spot and derivatives markets. Sell volumes at the time of this report have increased and liquidations rose to millions for all 3 altcoins. Since SOL gained the most, it lost the most as well and its liquidations touched $25 million.
Can Bitcoin save them?
Well since Bitcoin’s price movement commands the market’s movement it is obvious that BTC needs to reduce losses first. But more importantly, these assets’ correlation to Bitcoin will determine how much they will be affected by BTC. Right now Algorand is at the lowest at 0.57, followed by Solana at 0.7, and at the highest is Polkadot (0.88)
However, surprisingly, investors are most positive about Algorand of all three hoping for a recovery soon.
Once Bitcoin and Ethereum change their movement, other coins would follow suit. And that’s when some recovery can be expected.
Where to Invest?
Subscribe to our newsletter
PlatoAi. Web3 Reimagined. Data Intelligence Amplified.
Kraken Daily Market Report for September 19 2021
- Total spot trading volume at $598.4 million, the 30-day average is $1.36 billion.
- Total futures notional at $223.4 million.
- The most traded coins were, respectively, Bitcoin (-2.2%), Ethereum (-3.1%), Tether (0%), Solana (-9.9%), and Cosmos (+8.8%).
- Cosmos continues its hot streak, up 8.8%. Also strong returns from OMG (+10%).
|September 19, 2021
$598.4M traded across all markets today
Crypto, EUR, USD, JPY, CAD, GBP, CHF, AUD
#####################. Trading Volume by Asset. ##########################################
Trading Volume by Asset
The figures below break down the trading volume of the largest, mid-size, and smallest assets. Cryptos are in purple, fiats are in blue. For each asset, the chart contains the daily trading volume in USD, and the percentage of the total trading volume. The percentages for fiats and cryptos are treated separately, so that they both add up to 100%.
Figure 1: Largest trading assets: trading volume (measured in USD) and its percentage of the total trading volume (September 20 2021)
Figure 2: Mid-size trading assets: (measured in USD) (September 20 2021)
###########. Daily Returns. #################################################
Daily Returns %
Figure 3: Returns over USD and XBT. Relative volume and return size is indicated by the size of the font. (September 20 2021)
###########. Disclaimer #################################################
The values generated in this report are from public market data distributed from Kraken WebSockets api. The total volumes and returns are calculated over the reporting day using UTC time.
PlatoAi. Web3 Reimagined. Data Intelligence Amplified.
Taker Protocol Raises $3M to Transform NFT Liquidity and Utilization
New York, United States, 20th September, 2021,
Taker Protocol, a crypto liquidity protocol for NFTs, has raised $3 million from a number of reputable investors to build new financial primitives into the burgeoning NFT market.
Taker Protocol focuses on improving the liquidity available in the NFT market. Due to the unique non-fungible structure of NFTs, existing DeFi primitives are difficult to integrate into the market, resulting in significant issues in terms of overall liquidity. The value of an NFT is extremely volatile and often effectively becomes zero as no buyers can be found at any reasonable price. Furthermore, NFTs are difficult to use productively after purchase and often end up forgotten in the user’s wallet.
Taker Protocol aims to solve the worst of the liquidity issues. Allowing lenders and borrowers to liquidate and rent assets that aren’t cryptocurrencies creates new liquidity streams and opportunities. For Taker, these assets will include NFTs, financial papers, synthetic assets, and much more.
The TKR token defines membership in the Taker DAO, which has several key functions in the system. In addition to setting loan-to-value rates and other parameters in the protocol, the DAO will also contribute in fairly appraising a particular NFT or NFT collection. This means that each asset supported by Taker will have a guaranteed fair floor price. In return, TKR holders will be able to obtain rewards and receive a portion of platform income.
The funds received will help Taker launch the full version of the protocol across multiple chains, including Ethereum, Polygon, Solana, BSC and Near. The support of major stakeholders and participants in the NFT ecosystem will also help further development of the project.
Taker DAO contains many different Curator DAOs (Sub-DAOs), each sub-DAO will manage their own whitelist and a floor price for any NFT on their whitelist if the borrower defaults on the loan. We believe that it is best to mitigate the risks for our lenders by carefully selecting the NFT assets that our community desires and trusts the most. Aligning the interest of the DAOs with that of the lenders, we will mitigate the risk exposure for the lenders and optimize the profits for the DAOs. Moreover, each sub-DAO will have its own funds and can choose to focus exclusively on a specific type of NFT assets. For example, it could be artworks-only or Metaverse-only.
Taker Co-Founder Angel Xu comments:
“We are absolutely thrilled to welcome so many well-established investment funds to the team. Their participation heralds an exciting new phase for the protocol as we seek to address persistent problems in the NFT lending market for the benefit of end-users. This investment will enable us to further optimize liquidation of NFT assets across multiple blockchains, removing the barriers to entry that prevent new players from entering the market.”
“Taker Protocol is using an innovative approach to solve the biggest problem in the NFT space — lack of liquidity. With Taker, we are one step closer to the world where anyone anywhere can use their NFT assets to take out a loan.” (Maria Shen, Partner at Electric Capital)
NFT DeFi: Taker is the first protocol to provide liquidity to the NFT market through a DAO. It is a multi-strategy, cross-chain lending protocol for lenders and borrowers to liquidate and rent all kinds of crypto assets, including financial papers, synthetic assets, and more. Taker provides ensured liquidity via our lenderDao infrastructure and extensions that could be integrated into NFT marketplaces.
PlatoAi. Web3 Reimagined. Data Intelligence Amplified.
Wicked Craniums are now Nifty Gateway!
Acorns Hires Former Amazon Executive as President, Hints at Crypto Options
Swissquote Confirms European Expansion Plan, Focusing on Crypto
Biggest Crypto Adoption Rumours: Apple, Amazon, and Walmart
Massive NFT and Token Giveaway from Polker as Staking is Announced!
Head of Australian Crypto Exchange Says Regulations Are Beneficial
The Signal and the Noise
Evaluating Credit Card Debt Relief Options
Bingbon Launches its Carbon Free and Afforestation Project
Nickelodeon All-Star Brawl will include DLC fighters post-launch
Gods Unchained and Guild of Guardians Layer 2 Solution Immutable Raises $60 Million
What’s Behind Elrond (EGLD) Daily Surges?
Public.com Inks Deal with NFL Star to Advise on Financial Literacy Programs
Over 40 days after Ethereum’s EIP-1559, here’s where it stands
This needs to happen before Peter Schiff will buy Bitcoin (BTC)
Opensea NFT marketplace Accuses Senior Employee of Insider Trading
Grab a spot in Tomi’s presale by bagging an NFT – 260+ ETH raised!
Venture Firm Raises $350 Million to Double Down on Its Cryptocurrency Involvement
Kanga Exchange Partners with Tenset for an Exclusive Public Sale of KNG Token
Cardano Sees an Influx in Smart Contracts ! But There’s a Twist
Uncategorized1 week ago
How to watch the Wild Rift Japan Cup 2021: Teams, format, and more
Uncategorized1 week ago
How to fix NBA 2K21, 2K22 error code 4b538e50
Uncategorized1 week ago
How to scan your face in NBA 2K22
Blockchain1 week ago
SBI-acquired TaoTao exchange in Japan relists XRP
Uncategorized1 week ago
Fortnite says goodbye to season 7 with an alien ship, explosions, and a cliffhanger
News1 week ago
PUBG Mobile becomes the most earning game in August 2021
Uncategorized1 week ago
Best Limited Green Common and Uncommon Innistrad: Midnight Hunt cards
Blockchain1 week ago
Cardano Finally Ousting Ethereum? — Expect The Unexpected As Alonzo Hard Fork Kicks Off