I have a question for tech-savvy folks around here. Is Myriadcoin more tolerant to 51% attack and especially selfish mining issue due to its 5 independent algos/difficulties. Mostly selfish mining. 51% not so much I believe, but still. Anyone willing to give a good technical explanation? I am not that familiar with all mining details and may be wrong here, but I think selfish mining would be more difficult to perform with Myriadcoin compared to Bitcoin, and that would be a big improvement over Bitcoin. I may be totally wrong though. Anyone? |
|
|
|
As the saying goes: buy the rumor, sell the fact. El Dude, I hope you managed to offload your overvalued LTCs to the suckers while you were mouth-pumping it and it bounced a la dead-cat style. Too late now if you didn't  |
|
|
|
Huobi and Btcchina put pressure on other exchanges like Coinbase to accept litecoin. It's still hard for people in the US to buy Litecoin , Coinbase will change all that.
It's a chicken and egg problem. Why would they buy it if they can't spend it anywhere? Especially so, if they could buy bitcoin which they can spend. People buy something when they can use it (spend it if we talk about a currency) or for speculation. Most people like to buy when the price is growing. Well, the alts are all trending down right now with tiny dead-cat bounces here and there, but the general trend is down. What are the reasons to buy bitcoin now? I see 3 reasons, more or less: To preserve wealth, for speculation, spend it. What are the reasons to buy altcoins now? The only reason is for speculation at this point in time. But since the trend is down, you won't see a lot of speculative interest either, which means you really have to think of all possible factors not to lose your shirt within a few weeks/months. That's what I am trying to do here, and that's what the OP intended: to weigh all pros and cons. We don't need to tout the same old from a few months ago, times change quickly in crypto currencies scene. |
|
|
|
A coin needs to be easy to buy before big stores can accept it . Now that litecoin will be on all the big exchanges it's a matter of time before Overstock and tigerdirect also start accepting litecoin.
Huobi and Btcchina exchanges are irrelevant for that, because a) Chinese stores can't accept cryptos as legal tender, and b) Chinese customers wouldn't be buying at overseas stores, that's why Huobi and Btcchina introducing Litecoin trading won't bring in a lot of new buyers, and are a purely speculating factor. Some buying is possible, but those who wanted to buy into Litecoin have had other options for a long time, there is no shortage of exchanges for that matter, both in China and US/EU. |
|
|
|
|
El Dude,
2013 was the year when exchanges and speculators were the main driving force of the price. This is not sustainable, as you can't shuffle air indefinately, pumping and dumping.
2014 will be the year when who creates more infrastructure and actually allows to use the currency in any meaningful way will be leading the herd. Thus, adding to just another exchange or two doesn't bring it to the next level, at best it only gives some buying support, which can as easily vanish if the currency lacks infrastructure and shops to spend it.
|
|
|
|
You need to factor in the real world relationships that will drive adoption- in the case of Litecoin, Charlie Lee is well positioned in his relationship with Coinbase and obviously BTC China via his brother. You can bet that these ties will count for something as mass adoption begins. I don't know about the developers of Dodge- so I can't comment, but I do know that despite being decentralised, the people inherently connected with cryptos will count for something.
I hear you, but 1) btcchina is no longer the exchange with largest volume, 2) they missed the chance to take Litecoin to the next level back in November, when Max Keiser made his tweet on Litecoin to reach $50. If btcchina introduced Litecoin trading back then, in sync with Max's tweet and general enthusiasm for Litecoin, Litecoin would probably go to 0.1 ltc/btc and stay there and truely become the only second alt and gain a lot of user base. But that opportunity is now lost, there is a bunch of some innovative, some not, alts now that are taking capital away from Litecoin. Whereas back a few months ago Litecoin was attracting most new users of altcoins, it's different now. New users of altcoins have been scattered over a bunch of altcoins like cockroaches over the kitchen table, seeing benefits of other alts. Its very doubtful they can now get together into just 1 altcoin. I found the pic I looked for, yearly inflation for 2015-2020 |
|
|
|
|
The OP forgot to add another positive aspect to the Dogecoin list.
Dogecoin has never been portrayed in the media as the money of criminals: money launderers, drug dealers, etc. Do you know why? Exactly! Because Dogecoin is not used for those purposes, that's why. On the contrary, Dogecoin has been receiving a lot of good press for funding a number of charity projects, this gives tremendous value to the coin. I don't think Litecoin can boast of that. Do you realize how positive press is helpful for marketing something? People are not afraid to use Dogecoin, because they will not be associated with criminals, ever, because Dogecoin is what, a joke.
No journalist in their right mind would write an article that Dogecoin is used illegally, it would sound so ridiculous, that the editor wouldn't let publish this article, or it'd be the end of that media outlet for being so stupid as to even conceive of that. This Dogecoin being a joke is turning into Dogecoin's strongest point and helps attract masses. Without masses no wider adoption is possible. Dogecoin has achieved in months what took Litecoin years to achieve.
|
|
|
|
|
You've summarized it pretty good.
One thing is missing though, that is, current valuation assessment and how it can change in the future.
Litecoin and Dogecoin, all pros and cons weighted are at least equal to each other, but look at their market cap.
Let's say, we look one year from now when 100 bln doges are mined,
by that time, about 30 mln LTCs will have been mined,
assuming they are equal to each other, which they are, both technically, infrastructure wise, community wise, some aspects are better, some worse, but all in all they are about the same,
100 bln doges = 30 mln LTC, which sets the weighted exchange rate at 1 LTC : 3333 DOGEs (current biased exchange rate is 1 LTC = ~ 21 450 DOGEs).
If we sum up the current market caps of both $460 mln + $48 mln = $508 mln and devide it by 2 (because both coins are equal), that puts 1 LTC at $256 mln / 30 mln = $8,53 and that puts 1 DOGE at $256 mln / 100 bln = $0.00256 - quarter of a cent ($0.0008 at the time of this writing).
Summary: LTC should go down ~50%, DOGE should go up 3-fold from current valuations, based on their weighted pros and cons and being about equal.
Oh, and one more, last time I checked, Litecoin didn't have a lightweight wallet application, Dogecoin has 2 lightweight wallet apps (multidoge - ported from bitcoin multibit and wowdoge), that testifies to how more active dogecoin developers are and how more convenient it is for users.
I'd suggest splitting your scrypt coin investments 50:50 LTC:DOGE and see which one wins.
On inflation.
Bitcoin, Litecoin, Dogecoin - all are inflationary. Inflation means money supply grows. Well, it grows for all of them, all of them have new coins mined each day. The difference between Bitcoin/Litcoin and Dogecoin is, the latter mines the core coin supply within 1 year and then inflates each year at 5%. Whereas bitcoin/litecoin will be inflating at 10-15% for the next 3-4 years, then less than that, but still more than 5% till at least 2020. There was a table somewhere, someone posted exact numbers on bitcoin/litecoin/dogecoin yearly inflation.
But one thing you need to remember. Inflation may or may not raise prices of goods and services. It will raise them if there is not enough demand for coins, it will not raise them and can even push them lower if demand for those coins is high. So if there are enough people who are interested to buy Dogecoin, or Bitcoin/Litecoin likewise, their price will be going up, regardless of more coins being sold each day on the market. That's a little bit on the inflation topic.
For the past few weeks we see that there is not much new demand both for bitcoin and altcoins, that's why prices are stagnating or even falling. Cryptos need a wider adoption to see the jump to the next level.
The only non-inflationary coin is a 100% pre-mined coin or proof-of-stake coin like NXT, where no new coins are mined each day. All coins already exist.
|
|
|
|
|
FUD everywhere. Keep calm and carry on, guys and gals.
|
|
|
|
You have to trust employees, unfortunate for him. If my wife wanted to rob my BTC, she could do it easily as well because I trust her.
Is your wife your employee? |
|
|
|
I am not talking about the community or anything , just the coin.
Dogecoin in my opinion is among the worst.
It gives a bad name to cryptocurrency and moves it from something serious to a joke.
Well, ok, strictly as a coin Dogecoin beats Litecoin, because faster transactions and undervalued compared to it. You're asking your questions because you want to know which coin has more chance to appreciate from current rate, aren't you? Joke name helps attract new users, who are scared to touch more 'serious' coins because they have this illegal use stigma attached to them. Nobody can say that Dogecoin is used to launder money or something like that because it'd sound ridiculous, and that's the reason exactly why it will be popular, because there is no fear using them and media doesn't portray Dogecoin as the money of criminals. So no, I don't agree that Dogecoin gives a bad name to crypto currencies, on the contrary, it makes the whole crypto currency scene look agreeable to the public eyes. |
|
|
|
|
Haha, that's a $128k question.
Dogecoin, because different algo (Scrypt) = large GPU miners network, faster transactions, larger infrastructure and community than LTC (also Scrypt) and significantly undervalued compared to LTC by the way.
NXT, because decentralized exchange, not relying on the slow bitcoin network (like XCP and MSC, but have a little bit of these too) and other cool features coming soon.
Maybe protoshares/bitshares as a small part of portfolio. No other worth investing as of now.
|
|
|
|
Help! Has anyone successfully compiled Dogecoin 1.6 on debian jessie (testing release) 64-bit? Here is the crap I get from compiler. 1.5, 1.5.2 branches never had a problem. In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:290:8: error: reference to ‘intmax_t’ is ambiguous
extern intmax_t imaxabs (intmax_t __n) __THROW __attribute__ ((__const__));
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:290:8: error: ‘intmax_t’ does not name a type
extern intmax_t imaxabs (intmax_t __n) __THROW __attribute__ ((__const__));
^
/usr/include/inttypes.h:293:27: error: reference to ‘intmax_t’ is ambiguous
extern imaxdiv_t imaxdiv (intmax_t __numer, intmax_t __denom)
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:293:45: error: reference to ‘intmax_t’ is ambiguous
extern imaxdiv_t imaxdiv (intmax_t __numer, intmax_t __denom)
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from /usr/include/features.h:360:0,
from /usr/include/x86_64-linux-gnu/c++/4.8/bits/os_defines.h:39,
from /usr/include/x86_64-linux-gnu/c++/4.8/bits/c++config.h:426,
from /usr/include/c++/4.8/cstddef:41,
from /usr/include/boost/foreach.hpp:27,
from src/script.cpp:6:
/usr/include/inttypes.h:294:7: error: expected ‘,’ or ‘;’ before ‘throw’
__THROW __attribute__ ((__const__));
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:297:8: error: reference to ‘intmax_t’ is ambiguous
extern intmax_t strtoimax (const char *__restrict __nptr,
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:297:8: error: ‘intmax_t’ does not name a type
extern intmax_t strtoimax (const char *__restrict __nptr,
^
/usr/include/inttypes.h:301:8: error: reference to ‘uintmax_t’ is ambiguous
extern uintmax_t strtoumax (const char *__restrict __nptr,
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:135:27: note: candidates are: typedef long unsigned int uintmax_t
typedef unsigned long int uintmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:307:42: note: typedef boost::ulong_long_type boost::uintmax_t
typedef ::boost::ulong_long_type uintmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:301:8: error: ‘uintmax_t’ does not name a type
extern uintmax_t strtoumax (const char *__restrict __nptr,
^
/usr/include/inttypes.h:305:8: error: reference to ‘intmax_t’ is ambiguous
extern intmax_t wcstoimax (const __gwchar_t *__restrict __nptr,
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:305:8: error: ‘intmax_t’ does not name a type
extern intmax_t wcstoimax (const __gwchar_t *__restrict __nptr,
^
/usr/include/inttypes.h:310:8: error: reference to ‘uintmax_t’ is ambiguous
extern uintmax_t wcstoumax (const __gwchar_t *__restrict __nptr,
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:135:27: note: candidates are: typedef long unsigned int uintmax_t
typedef unsigned long int uintmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:307:42: note: typedef boost::ulong_long_type boost::uintmax_t
typedef ::boost::ulong_long_type uintmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:310:8: error: ‘uintmax_t’ does not name a type
extern uintmax_t wcstoumax (const __gwchar_t *__restrict __nptr,
^
/usr/include/inttypes.h:323:17: error: reference to ‘intmax_t’ is ambiguous
__extern_inline intmax_t
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:323:17: error: ‘intmax_t’ does not name a type
__extern_inline intmax_t
^
/usr/include/inttypes.h:335:17: error: reference to ‘uintmax_t’ is ambiguous
__extern_inline uintmax_t
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:135:27: note: candidates are: typedef long unsigned int uintmax_t
typedef unsigned long int uintmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:307:42: note: typedef boost::ulong_long_type boost::uintmax_t
typedef ::boost::ulong_long_type uintmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:335:17: error: ‘uintmax_t’ does not name a type
__extern_inline uintmax_t
^
/usr/include/inttypes.h:347:17: error: reference to ‘intmax_t’ is ambiguous
__extern_inline intmax_t
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:347:17: error: ‘intmax_t’ does not name a type
__extern_inline intmax_t
^
/usr/include/inttypes.h:361:17: error: reference to ‘uintmax_t’ is ambiguous
__extern_inline uintmax_t
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:135:27: note: candidates are: typedef long unsigned int uintmax_t
typedef unsigned long int uintmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:307:42: note: typedef boost::ulong_long_type boost::uintmax_t
typedef ::boost::ulong_long_type uintmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:361:17: error: ‘uintmax_t’ does not name a type
__extern_inline uintmax_t
^
In file included from src/main.h:13:0,
from src/script.cpp:16:
src/scrypt.h:30:21: error: reference to ‘uint64_t’ is ambiguous
size_t saltlen, uint64_t c, uint8_t *buf, size_t dkLen);
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:55:27: note: candidates are: typedef long unsigned int uint64_t
typedef unsigned long int uint64_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:311:42: note: typedef boost::ulong_long_type boost::uint64_t
typedef ::boost::ulong_long_type uint64_t;
^
In file included from src/main.h:13:0,
from src/script.cpp:16:
src/scrypt.h:30:21: error: ‘uint64_t’ has not been declared
size_t saltlen, uint64_t c, uint8_t *buf, size_t dkLen);
^
In file included from src/script.cpp:16:0:
src/main.h:2254:24: error: template argument 1 is invalid
std::vector<int64_t> vTxFees;
^
src/main.h:2254:24: error: template argument 2 is invalid
src/main.h:2255:24: error: template argument 1 is invalid
std::vector<int64_t> vTxSigOps;
^
src/main.h:2255:24: error: template argument 2 is invalid
make: *** [build/script.o] Error 1
|
|
|
|
I have absolutely no clue what you are going on about. None of what you said makes sense.
haha, that's priceless!  Anyway, this all has been summed up long ago by Benjamin Franklin in his famous "They who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." quote. Still applies. |
|
|
|
But that was the time between the last peaks. We should be on the rise already. Today was not a bad day actually. I just see that from the jag on the 25th of February we are already up almost 50%. OK, from tomorrow on we will officially switch to bubble mode, everybody join the ride and make sure to fasten your seat belts.
Well, have a look at that low back in July 2013, we just had the same one 2-3 weeks ago, and after that bottom the price was sort of stagnant and it really started taking off only at the end of October, which still leaves 3 months from now to wait for the same outcome. |
|
|
|
Mandatory 1.6 update added to OP.
When trying to compile from source on latest debian testing release I get this error: In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:290:8: error: reference to ‘intmax_t’ is ambiguous
extern intmax_t imaxabs (intmax_t __n) __THROW __attribute__ ((__const__));
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:290:8: error: ‘intmax_t’ does not name a type
extern intmax_t imaxabs (intmax_t __n) __THROW __attribute__ ((__const__));
^
/usr/include/inttypes.h:293:27: error: reference to ‘intmax_t’ is ambiguous
extern imaxdiv_t imaxdiv (intmax_t __numer, intmax_t __denom)
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:293:45: error: reference to ‘intmax_t’ is ambiguous
extern imaxdiv_t imaxdiv (intmax_t __numer, intmax_t __denom)
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from /usr/include/features.h:360:0,
from /usr/include/x86_64-linux-gnu/c++/4.8/bits/os_defines.h:39,
from /usr/include/x86_64-linux-gnu/c++/4.8/bits/c++config.h:426,
from /usr/include/c++/4.8/cstddef:41,
from /usr/include/boost/foreach.hpp:27,
from src/script.cpp:6:
/usr/include/inttypes.h:294:7: error: expected ‘,’ or ‘;’ before ‘throw’
__THROW __attribute__ ((__const__));
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:297:8: error: reference to ‘intmax_t’ is ambiguous
extern intmax_t strtoimax (const char *__restrict __nptr,
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:297:8: error: ‘intmax_t’ does not name a type
extern intmax_t strtoimax (const char *__restrict __nptr,
^
/usr/include/inttypes.h:301:8: error: reference to ‘uintmax_t’ is ambiguous
extern uintmax_t strtoumax (const char *__restrict __nptr,
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:135:27: note: candidates are: typedef long unsigned int uintmax_t
typedef unsigned long int uintmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:307:42: note: typedef boost::ulong_long_type boost::uintmax_t
typedef ::boost::ulong_long_type uintmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:301:8: error: ‘uintmax_t’ does not name a type
extern uintmax_t strtoumax (const char *__restrict __nptr,
^
/usr/include/inttypes.h:305:8: error: reference to ‘intmax_t’ is ambiguous
extern intmax_t wcstoimax (const __gwchar_t *__restrict __nptr,
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:305:8: error: ‘intmax_t’ does not name a type
extern intmax_t wcstoimax (const __gwchar_t *__restrict __nptr,
^
/usr/include/inttypes.h:310:8: error: reference to ‘uintmax_t’ is ambiguous
extern uintmax_t wcstoumax (const __gwchar_t *__restrict __nptr,
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:135:27: note: candidates are: typedef long unsigned int uintmax_t
typedef unsigned long int uintmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:307:42: note: typedef boost::ulong_long_type boost::uintmax_t
typedef ::boost::ulong_long_type uintmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:310:8: error: ‘uintmax_t’ does not name a type
extern uintmax_t wcstoumax (const __gwchar_t *__restrict __nptr,
^
/usr/include/inttypes.h:323:17: error: reference to ‘intmax_t’ is ambiguous
__extern_inline intmax_t
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:323:17: error: ‘intmax_t’ does not name a type
__extern_inline intmax_t
^
/usr/include/inttypes.h:335:17: error: reference to ‘uintmax_t’ is ambiguous
__extern_inline uintmax_t
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:135:27: note: candidates are: typedef long unsigned int uintmax_t
typedef unsigned long int uintmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:307:42: note: typedef boost::ulong_long_type boost::uintmax_t
typedef ::boost::ulong_long_type uintmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:335:17: error: ‘uintmax_t’ does not name a type
__extern_inline uintmax_t
^
/usr/include/inttypes.h:347:17: error: reference to ‘intmax_t’ is ambiguous
__extern_inline intmax_t
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:134:19: note: candidates are: typedef long int intmax_t
typedef long int intmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:306:50: note: typedef boost::long_long_type boost::intmax_t
typedef ::boost::long_long_type intmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:347:17: error: ‘intmax_t’ does not name a type
__extern_inline intmax_t
^
/usr/include/inttypes.h:361:17: error: reference to ‘uintmax_t’ is ambiguous
__extern_inline uintmax_t
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:135:27: note: candidates are: typedef long unsigned int uintmax_t
typedef unsigned long int uintmax_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:307:42: note: typedef boost::ulong_long_type boost::uintmax_t
typedef ::boost::ulong_long_type uintmax_t;
^
In file included from src/uint256.h:12:0,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/inttypes.h:361:17: error: ‘uintmax_t’ does not name a type
__extern_inline uintmax_t
^
In file included from src/main.h:13:0,
from src/script.cpp:16:
src/scrypt.h:30:21: error: reference to ‘uint64_t’ is ambiguous
size_t saltlen, uint64_t c, uint8_t *buf, size_t dkLen);
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/include/stdint.h:9:0,
from /usr/include/inttypes.h:27,
from src/uint256.h:12,
from src/key.h:13,
from src/crypter.h:9,
from src/keystore.h:9,
from src/script.h:15,
from src/script.cpp:12:
/usr/include/stdint.h:55:27: note: candidates are: typedef long unsigned int uint64_t
typedef unsigned long int uint64_t;
^
In file included from /usr/include/boost/math_fwd.hpp:12:0,
from /usr/include/boost/math/common_factor_ct.hpp:13,
from /usr/include/boost/variant/variant.hpp:43,
from /usr/include/boost/variant.hpp:17,
from src/script.h:13,
from src/script.cpp:12:
/usr/include/boost/cstdint.hpp:311:42: note: typedef boost::ulong_long_type boost::uint64_t
typedef ::boost::ulong_long_type uint64_t;
^
In file included from src/main.h:13:0,
from src/script.cpp:16:
src/scrypt.h:30:21: error: ‘uint64_t’ has not been declared
size_t saltlen, uint64_t c, uint8_t *buf, size_t dkLen);
^
In file included from src/script.cpp:16:0:
src/main.h:2254:24: error: template argument 1 is invalid
std::vector<int64_t> vTxFees;
^
src/main.h:2254:24: error: template argument 2 is invalid
src/main.h:2255:24: error: template argument 1 is invalid
std::vector<int64_t> vTxSigOps;
^
src/main.h:2255:24: error: template argument 2 is invalid
make: *** [build/script.o] Error 1 never had a problem with compiling 1.5, 1.5.2, so clearly something is broken in the 1.6 release. |
|
|
|
...why are we not yet bubbling up again?   coz if you look at the graph you yourself provided, it takes at least 6 months between bubbling-ups, not 3 which assumption should make June-August period interesting. |
|
|
|
Nope.
Yes, it is. There is no shortage of exchanges, including chinese, that offer LTC for trading, another one won't make a difference. Whoever wanted to buy LTC has already bought it. They (btcchina, huobi) could have brought it to higher exchange rate back in October/November when it was ripe for picking, but now it's simply too late. There are other alt cryptos where capital is pouring into right now. LTC had an advantage of slightly larger infrastrustructure sites over other alt coins back in 2013, but even that advantage is now lost. Dead-cat bounce, imho. |
|
|
|
If you take time to find out why people buy futures in the first place at all (and this is not for speculation, to begin with), this question will be a trifle for you. People buy currency futures since they don't need currency right now, but in the future (when they actually need it), the price may change disadvantageously... I guess you just don't know that the futures price is not the same as the price it allows (gives a right) to sell or buy the underlying currency (commodity) at... I know what hedging is. I also know that there is a) nothing to hedge in bitcoin compared to forex exchange risks, b) no bailout of bitcoin exchanges makes any future disadvantageous price fluctuation not such a big risk compared to the case when bitcoin exchanges goes under, which is not so rare. In practise it means that nobody in their right mind will buy a bitcoin futures contract with one exception: Do you mean bitcoin miners would sell their future bitcoin production? That'd be interesting, but that requires much heavier levels of regulation than now, having them registered as companies, etc. In that case, yeah, futures contracts might have a chance.
and even this wouldn't be practical or popular as miners would have to offer a very attractive discount to entice someone to risk losing money due to the exchange bankruptcy. |
|
|
|
|
Show Posts
