[ANN][DOGE] Dogecoin - very currency many coin - v1.10.0

[Dogecoin]

Mandatory 1.6 update added to OP.

[Ceballos]

Mandatory 1.6 update added to OP.

Fantastic ! 

[devphp]

Mandatory 1.6 update added to OP.

When trying to compile from source on latest debian testing release I get this error:

Code:

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.

[Mikellev]

Updated to 1.6 - running stable. Your choice since day 1 of doge.



Still 0% fee - 9 stratums worldwide - nothing less

http://doge.poolerino.com/

[avw1982]

Shall we try to get DOGE listed at Qoinpro?

[turint]

Doge Plasr pool updated to v.1.6

Vardiff
0% fee
PPLNS

Happy mining!

[mison]

we suggest to fix reward at karmacoin, and they did it, but problem was fix reward was set too high for actual market price and difficulty. Doge is pretty strong market so exactly half of the reward will not hurt the coin like did on karmacoin.

[jdebunt]

http://www.cryptoarticles.com/crypto-news/2014/3/13/pryptos-crypto-scratch-cards-video-redeeming-of-a-dogecoin-card

So much Doge! Very wow!

[salstimda]

Mandatory 1.6 update added to OP.

you should update the block reward specifications in the OP then too

[XbladeX]

Yes, actually would be working with a guarantee, which I am sure that you haven't seen before. It is also very very transparent.

http://cryptoprofit.org/leaf.php

In brackets are shown the the amounts people would get back guaranteed if the system stops and there will be no new deposits. On any other such system, when deposits stops people will loose everything. In this case when the system will stop people will get back at least the part which is in the brackets (distributed from the guarantee fund). So beyond all the jokes and malicious remarks, I think that this is the fairest such system.

Do you agree?

(Not to talk about that rules are transparent and clear).

So you have about 15 millions to give out , and only 6 millions in your guarantee fund? If I read the numbers correctly:)
Wow , such smartness , amazing: a ponzi where you're losing only 50% of your money , is still a ponzi.

Yes, the guarantee fund is limited to 3 times the maximum deposit amount. And yes, you will loose money when it will stop. But compare this to other systems and tell me that you really can't see any difference.

Tell me the difference:
I know this is a ponzi so I'm just putting 100 in.
The other one  is a guarantee ponzi so I'm anyhow getting 100 back so I'm putting 200.

Both cases I lose 100.This is how the things will work in reality.
In the end the people will lose the same amount.

Anyhow , the leaf section is so in red that I suggest ending it

All depends on adoptation and how coin is used.
Doge have community that community is using Doge...
I have sold few things with Doge.
many other pro coins don't have any shop Whatever...
They are just empty...
When you invest in doge 100,200,300 it  means nothing !
When you buy for 100,200,300 then you rise Doge some profit from sells will increase overall Doge infrastructure...
And that make it bigger and bigger...
Price of Doge doesn't matter so much as adaptation and how you can spend it.
Ponzi is when all buying and you can't do anything with that coin...except selling it higher or lower.
I  think in future all alt coins will be tradable to fiat...
You will use something like coins payment multi-platform then you will use option which coin chose from 50 coins with stable market.
Peolple will use Doge becouse they like it...
Some will you BC,Quark because translations are in 5s-10s BC(BC full POS),30s quark...
Some will only use BTC  ,they only belive in BTC.

If i have to acumulate capital i would chose coins with low inflation like NXT, BC,CGB, coins which wasn't pumped in skies.
Doge is good coin for using for sharing with friends like gifts.

[CharityMiningPools]

CharityMiningPools - Donate to Charity while you Mine!

doge.charityminingpools.com

Be a pioneer and help us get started, come mine while making a difference.  

Mandatory 0.5% donation fee goes to the BitGive Foundation this month.  We welcome and encourage you to donate more to a good cause.

SSL, STRATUM, VARDIFF, Datacenter Redundant Server Farm, Load Balanced Servers, Frequent Backups, DDOS Protection
0.5% Mandatory Donation fee to a Good Cause, 0.5% Pool Fees, 0% AP TX Fees

Who Are We?
CharityMiningPools was created to allow miners the ability to mine coins while still knowing that their hashing power is going towards something good.  Our goal is to provide a positive and reliable service while delivering a small portion of the proceeds to a deserving recipient.  Plans are in the works to allow individual miners to choose where they would like to donate to based on a pool of available recipients.

How Does This Work?
All coins minded at CharityMiningPools will require a mandatory 0.5% Donation fee.  This donation fee will be collected and donated to the designated charitable recipient for that given month.  Though we only require a minimum 0.5% Donation fee, we welcome and encourage our miners to raise the stakes and donate more to a good cause.

Cheers!
CharityMiningPools

[Mikellev]

Updated to 1.6 - running stable. Your choice since day 1 of doge.



Still 0% fee - 9 stratums worldwide - nothing less

5,000.00 DOGE Blockfinderbonus running. Get your extra doge now!

http://doge.poolerino.com/

[bitcoindirect]

I would like to thank one of your fellow Doge members, who used his http://Prypto.com scratch card winnings to the cause. Check out his article here! http://www.cryptoarticles.com/crypto-news/2014/3/13/pryptos-crypto-scratch-cards-video-redeeming-of-a-dogecoin-card

And I would like to thank http://peng.poolerino.com for our 15 block find yesterda and donating 150,000 PENG to our donation!

Here is the direct Reddit link where I will have most of the updates.

[http://www.reddit.com/r/Bitcoin/comments/207014/penguin_books_penguin_foundation_charitable/](http://www.reddit.com/r/Bitcoin/comments/207014/penguin_books_penguin_foundation_charitable/)

Thanks again to all those who are helping these kids who don't have the opportunity to have books like we do, and the Penguin Foundation!

Charity Box's so far:

BTC-0.03122
LTC-0.00
DOGE-1,005.60
PENG-200,000.00
AURORA-0.00
FLAP-0.00
RIPPLE-0.00

[Sgm]

http://www.coindesk.com/gocoin-support-dogecoin-following-good-news-miners/

To the Moon!!!

[A1ex]

24/7 MONITORING, ONLINE SUPPORT, AUTOMATED PAYMENTS,
STRATUM, 0% FEE, PPLNS, VARDIFF, SSL, POWERFULL SERVER

DOGE.FORKPOOL.COM - DOGECOIN POOL

[Varvarin]

hmm .. not sure what to make of the update. Yes, the Multipoo shits are responsible for high volatility but also with their 50Ghs ... kept price high. If they don't hash ... great for us miners, but ... price?

DigiByte hardly prospered after the shield, went down 75% .. although it has picked up a bit.

Or it would mean coins to spread more evenly, less selling. Lets hope DOGE can break the tradition of price collapses when things get fixed and Multipoo doesn't exploit it. SMC & Karma didn't do too well.

[ocminer]

Check out https://www.dogepool.net


Stratum
Vardiff
SSL
A very handy separate site optimized for Mobile Phones i.e. IPhone/Android (only visible from phone)
Idle Worker Notifications
Proportional Payout
Manual Cash Out Function
Very fast machine/high availability
NO PPLNS ! Payout immediately after block has found (and is confirmed) in full !
Dogecoind v1.5.2
Constantly over 250 GH/s and finding Blocks on a regular basis.

0 % FEE !

 2500 Block Finder Reward !

This is the pool without downtimes
The pool without users blaming it for stealing
The pool where no coins were stolen or lost
The pool were all (auto-)payments work flawless
The pool with support in minutes !
It's the hassle-free-pool
Search the forums for it !


Visit the Pool at https://www.dogepool.net

We are also on Version 1.6 now !

[boukehj]

I'm surprised to repeatedly the argument that higher network hash rate would imply higher price, while it's the other way around:
higher coin price attracts more miners, resulting in a higher hash rate and lower profitability for existing miners.

If anything, this would result in downward pressure on the coin price. After all, the multipool miners all pump 'n dump, so the supply of the coins go up...

hmm .. not sure what to make of the update. Yes, the Multipoo shits are responsible for high volatility but also with their 50Ghs ... kept price high. If they don't hash ... great for us miners, but ... price?

DigiByte hardly prospered after the shield, went down 75% .. although it has picked up a bit.

Or it would mean coins to spread more evenly, less selling. Lets hope DOGE can break the tradition of price collapses when things get fixed and Multipoo doesn't exploit it. SMC & Karma didn't do too well.

[david1365]

Hi guys
Please someone suggest a good pool for getting better result, my hash power 850 kh/s and after 4h mining on hashfaster i got only 300 DOGE, this is so low

[bitcoindirect]

Thanks for the contributions so far!

http://www.reddit.com/r/Bitcoin/comments/207014/penguin_books_penguin_foundation_charitable/

Charity Box's so far:
BTC-0.03122
LTC-0.00
DOGE-2,006.90
PENG-260,000.00
AURORA-0.00
FLAP-10579.32747051
RIPPLE-0.00
KLONDIKE-0.00
ULTRA-0.00
EARTH-0.00
DARK-0.00
LEAF-0.00
MINT-0.00
BLACK-1234.5678