Topic: [ANN][DOGE] Dogecoin - very currency many coin - v1.10.0 - page 615. (Read 3100004 times)
Shall we try to get DOGE listed at Qoinpro?
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/
Still 0% fee - 9 stratums worldwide - nothing less
http://doge.poolerino.com/
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::vectorvTxFees;
^
src/main.h:2254:24: error: template argument 2 is invalid
src/main.h:2255:24: error: template argument 1 is invalid
std::vectorvTxSigOps;
^
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.
Mandatory 1.6 update added to OP.
Updated to 1.6 and all my peers are still on 1.51 1.52 I am not using a conf file at all.
Just letting dns find em.
For shame
Catch up man !
Just letting dns find em.
For shame
Catch up man !
I'm glad they are finally doing away with "random" rewards. I might start mining doge again after block 145k.
Hi guys, I just made a pool for Dogecoin. Now with Cryptsy price displayed
Address: doge.p2phash.com
P2Pool benefits:
* No registration required
* Distributed hashrate
* Immediate payouts after a block is found
* Higher payouts with transaction fees paid to miners
* No account hack possible
Fee: only 0.5%
Start mining within seconds! Just point your miner to p2phash.com:9555 and use the Dogecoin address from your wallet for username, the password doesn't matter.
Rob Ford has invested $20,000 of his crack money into Doge
doge to tha moon!
http://www.reddit.com/r/dogecoin/comments/207hfb/ann_dogecoin16_its_ready_all_you_need_to_know
"A huge thanks ... /u/digibytedev - for their contributions with the DigiShield difficulty algorithm; and a huge shout out to their coin, /r/digibyte . In a climate where altcoins often find themselves at eachother's throats, the DigiByte devs stepped forward and gladly offered to assist us with developing v1.6 - not only with the contribution of DigiShield, but also with assisting in testing, and providing a friendly ear, coupled with excellent advice on crypto development. I can't thank you enough. You've been outstanding to us - and I only hope our community can return the favour. "
...you have my vote
"A huge thanks ... /u/digibytedev - for their contributions with the DigiShield difficulty algorithm; and a huge shout out to their coin, /r/digibyte . In a climate where altcoins often find themselves at eachother's throats, the DigiByte devs stepped forward and gladly offered to assist us with developing v1.6 - not only with the contribution of DigiShield, but also with assisting in testing, and providing a friendly ear, coupled with excellent advice on crypto development. I can't thank you enough. You've been outstanding to us - and I only hope our community can return the favour. "
...you have my vote
We are part of the Digibyte community. Awesome to see both communities working together. Would it be possible for the DOGE community to vote for DGB to be added to Crypsty? Would be great!
https://www.cryptsy.com/coinvotes
YC
https://www.cryptsy.com/coinvotes
YC
beautiful picture! bravo!
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).
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
I can not end just like that... they are clear rules about that too. Unfortuntaly LEAF as a coin doesn't do very well, so no wonder that not many are adventuring in it. Maybe DOGE will do better, and the chain will stop (because eventually it will), in a lot later stage, time by probably many people will benefit from it.
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
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).
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
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).
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.
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).
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.
Jump to: