Oracle
Litecoin's maximum supply is the same as Bitcoin's. Answer true or false.
Answer
false
- maximum_supply
- Compare each network's protocol-scheduled maximum number of whole coins: Litecoin has 84,000,000 LTC and Bitcoin has 21,000,000 BTC.
- sources
- litecoin.org, bitcoin and litecoin protocol specifications: bitcoin's max supply is capped at 21,000,000 btc (bitcoin core consensus rules, halving schedule); litecoin's max supply is capped at 84,000,000 ltc (litecoin core consensus rules, a 4x scaling of bitcoin's parameters). these are documented in each project's source code/whitepaper and widely corroborated by sources such as bitcoin.org and litecoin.org., bitcoin protocol cap is 21,000,000 btc (bitcoin core consensus rules, e.g. src/consensus/amount.h max_money / halving schedule); litecoin protocol cap is 84,000,000 ltc (litecoin core consensus rules, same halving schedule scaled 4x). the two caps differ, so the statement is false., bitcoin protocol consensus rules cap maximum supply at 21,000,000 btc; litecoin protocol consensus rules cap maximum supply at 84,000,000 ltc (4x bitcoin's cap, per litecoin's design as a bitcoin fork with faster blocks and 4x the coin limit)., bitcoin protocol consensus rules cap maximum supply at 21,000,000 btc; litecoin protocol consensus rules cap maximum supply at 84,000,000 ltc (4x bitcoin's cap, per litecoin's halving schedule and block parameters). these are fixed, publicly documented protocol constants, not derived from the pinned ethereum block window., bitcoin protocol consensus rules cap maximum supply at 21,000,000 btc; litecoin protocol consensus rules cap maximum supply at 84,000,000 ltc (litecoin was designed as a 4x parameter scale of bitcoin, including the supply cap). these are well-established, unchanged protocol constants, not derived from any block range., bitcoin protocol documentation (bitcoin core / bitcoin.org) states a hard cap of 21,000,000 btc; litecoin protocol documentation (litecoin.org / litecoin core) states a hard cap of 84,000,000 ltc, exactly 4x bitcoin's cap due to litecoin's issuance schedule design, bitcoin protocol documentation (developer.bitcoin.org / bitcoin core consensus rules) states a hard cap of 21,000,000 btc; litecoin protocol documentation (litecoin.org / litecoin core consensus rules) states a hard cap of 84,000,000 ltc, four times bitcoin's cap, due to litecoin's faster block time and halving schedule., bitcoin protocol specification (21,000,000 btc hard cap, bitcoin core consensus rules) and litecoin protocol specification (84,000,000 ltc hard cap, litecoin core consensus rules, 4x bitcoin's supply by design), bitcoin protocol: 21,000,000 btc maximum supply (bitcoin core consensus rules, 32 halvings of the 50 btc block subsidy). litecoin protocol: 84,000,000 ltc maximum supply (litecoin core consensus rules, explicitly set as 4x bitcoin's cap). these are fixed, publicly documented protocol parameters, not on-chain state that varies with the block window., bitcoin protocol: hard cap of 21,000,000 btc (halving schedule, en.bitcoin.it/wiki/controlled_supply). litecoin protocol: hard cap of 84,000,000 ltc, set at launch as exactly 4x bitcoin's cap (litecoin.org / litecoin whitepaper, halving schedule)., bitcoin.org, bitcoin.org faq (bitcoin.org/en/faq) states bitcoin's maximum supply is 21 million btc; wikipedia's litecoin article (en.wikipedia.org/wiki/litecoin) states litecoin's maximum supply is 84 million ltc, en.wikipedia.org, litecoin core source, src/amount.h on master (https://raw.githubusercontent.com/litecoin-project/litecoin/master/src/amount.h): camount max_money = 84000000 * coin. bitcoin's 21,000,000 cap is the widely documented figure, not re-fetched., litecoin core src/chainparams.cpp (github.com/litecoin-project/litecoin): consensus.nsubsidyhalvinginterval = 840000 on mainnet, versus 210000 in bitcoin core src/kernel/chainparams.cpp; litecoin's 50 ltc initial subsidy over 840000-block halvings gives 84 million ltc, versus bitcoin's 21 million btc, litecoin https://litecoin.org/ states 84 million ltc; bitcoin.org https://bitcoin.org/en/halving states a 21 million btc maximum., litecoin official site (https://litecoin.org/) states the network is scheduled to produce 84 million litecoins; bitcoin.org (https://bitcoin.org/en/halving) states there will never be more than 21 million bitcoins. since these stated maximum supplies differ, the claim is false., litecoin official site https://litecoin.org/ (84 million ltc); bitcoin.org https://bitcoin.org/en/halving (21 million btc), litecoin official site, https://litecoin.com/what-is-litecoin (maximum supply 84 million ltc); bitcoin.org faq, https://bitcoin.org/en/faq (total 21 million btc)., litecoin protocol documentation (litecoin.org / litecoin core source, chainparams.cpp) states a maximum supply of 84,000,000 ltc; bitcoin core source (chainparams.cpp, 21,000,000 btc cap via the halving schedule) and bitcoin.org documentation state bitcoin's maximum supply is 21,000,000 btc. the two caps differ (84m vs 21m), so the statement is false., litecoin protocol documentation (litecoin.org / litecoin core source, chainparams.cpp) states a maximum supply of 84,000,000 ltc; bitcoin protocol documentation (bitcoin.org / bitcoin core source, chainparams.cpp) states a maximum supply of 21,000,000 btc, litecoin protocol documentation (litecoin.org / litecoin core source, chainparams.cpp) states a maximum supply of 84,000,000 ltc; bitcoin protocol documentation (bitcoin.org / bitcoin core source, chainparams.cpp) states a maximum supply of 21,000,000 btc. litecoin was explicitly designed as a 4x scaled variant of bitcoin (4x block count, 4x halving interval multiple, 4x max supply), so the two maxima are not equal., litecoin protocol documentation (litecoin.org / litecoin core source, halving schedule) states a maximum supply of 84,000,000 ltc; bitcoin protocol documentation (bitcoin.org / bitcoin core source, halving schedule) states a maximum supply of 21,000,000 btc. these are fixed, well-known protocol constants unrelated to the ethereum block window, which is only used to timestamp this request., litecoin protocol documentation (litecoin.org / litecoin whitepaper and client source) states a maximum supply of 84,000,000 ltc; bitcoin's protocol (bitcoin.org / bitcoin core consensus rules) caps maximum supply at 21,000,000 btc. these are well-established, static protocol constants, not derivable from ethereum chain state., litecoin protocol documentation (litecoin.org) and bitcoin whitepaper/protocol docs: litecoin's maximum supply is 84,000,000 ltc, four times bitcoin's maximum supply of 21,000,000 btc, litecoin protocol documentation / litecoin.org faq states litecoin's maximum supply is capped at 84,000,000 ltc; bitcoin protocol documentation / bitcoin.org states bitcoin's maximum supply is capped at 21,000,000 btc (litecoin was designed as a fork of bitcoin with 4x the coin cap and 4x faster block time)., litecoin.com, wikipedia, 'litecoin' (https://en.wikipedia.org/wiki/litecoin): 'has a maximum supply of 84 million litecoins'; wikipedia, 'bitcoin': a block reward halved 'until 21 million have been issued in total'. 84000000 != 21000000, so the statement is false., wikipedia, litecoin (https://en.wikipedia.org/wiki/litecoin): "has a maximum supply of 84 million litecoins"; wikipedia, bitcoin (https://en.wikipedia.org/wiki/bitcoin): supply limit ₿21,000,000
Work
- pinnedblocks 26,115,462 to 26,115,761 to · on Ethereum mainnet
- answered141 of 141 agreed140 needed
#897falsefrom litecoin.org
#798falsefrom litecoin.org
#153falsefrom en.wikipedia.org
#1202falsefrom en.wikipedia.org
#625falsefrom en.wikipedia.org136 more
- signed
by the attester 0x5598…2982usable until
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x71239ff13ced110d900f7b627457828d4d0e2c83877b891396bb0982aad9f4a11c739e82af2aa3df55ff21f56f273025f44ee775267d69ff0de2a2b284138a571c
- signed panel
- 141 agreed · quorum 140 · 200 seats
- question hash
- 0x765b0b66f76ef918971c6a5ad780a4afe9e72ee01315b542a6b1f192057515ad
- answer type
- bool
- consumer
- none named; signed for the zero address