Topic: ANN : Rainbowcoin (LGBT) - page 7. (Read 31937 times)
FYI all the pools listed in the top of the thread have been closed down. You can still mine Rainbowcoins at http://rainbowcoin.securepayment.cc
I am not sure if anyone realizes this or not. But this coin (either through a bug or on purpose) has been nearly mined out. The difficulty appear to be set at 1024 and does not change. As a result, blocks are being found about every second instead of every minute.
Code:
static const int64 nTargetTimespan = 3456000;
static const int64 nTargetSpacing = 60;
static const int64 nTargetSpacing = 60;
I don't think it's broken, the spec seems correct:
4 days = 960 * 60 * 60 = 3456000
Diff changes every 57600 blocks. Last change was at #288000, next is: #345600
The Dev's never mined the coin at all
What we hold have been purchased at a fair price from supporters
I suppose you are correct. Still doesn't change the fact that 987,312,883 of the 1,000,000,000 coins (98.7%) have already been mined in only two weeks of the coin's existence.
That is what happens when you release a SHA-256 coin without proper diff adjustment in today's world full of 2TH miners.
This coin is crap. Diff adjustment algo is busted, wallet throws errors half the time when you send large transactions. Wallet does not report network hashrate so there's no way you can tell how many people are mining. The big 10,000-coin blocks are gone, block rewards are something tiny now like 156 coins per block.
The dev owns many, many millions of these coins from weeks (months?) ago when he offered to buy everyone's supply at some ridiculously low price in QRK. Now he is trying to re-ignite the coin so he can dump his acquired at 100x profit.
I am not sure if anyone realizes this or not. But this coin (either through a bug or on purpose) has been nearly mined out. The difficulty appear to be set at 1024 and does not change. As a result, blocks are being found about every second instead of every minute.
Code:
static const int64 nTargetTimespan = 3456000;
static const int64 nTargetSpacing = 60;
static const int64 nTargetSpacing = 60;
I don't think it's broken, the spec seems correct:
4 days = 960 * 60 * 60 = 3456000
Diff changes every 57600 blocks. Last change was at #288000, next is: #345600
I suppose you are correct. Still doesn't change the fact that 987,312,883 of the 1,000,000,000 coins (98.7%) have already been mined in only two weeks of the coin's existence.
That is what happens when you release a SHA-256 coin without proper diff adjustment in today's world full of 2TH miners.
This coin is crap. Diff adjustment algo is busted, wallet throws errors half the time when you send large transactions. Wallet does not report network hashrate so there's no way you can tell how many people are mining. The big 10,000-coin blocks are gone, block rewards are something tiny now like 156 coins per block.
The dev owns many, many millions of these coins from weeks (months?) ago when he offered to buy everyone's supply at some ridiculously low price in QRK. Now he is trying to re-ignite the coin so he can dump his acquired at 100x profit.
Nice coin, going for it
Good for gambling and widly spread because in china it's year of the horse , i'll go for this one, this will be rather "stable"
Let's pray
What does this coin have to do with horses and gambling? Good for gambling and widly spread because in china it's year of the horse , i'll go for this one, this will be rather "stable"
Let's pray
Can the OP please add http://rainbowcoin.securepayment.cc to the list of pools.
why isnt pool paying up?
? It says that I got paid and I receive nothing for quite some time>??PM me your address and I will look into it.
Can the OP please add http://rainbowcoin.securepayment.cc to the list of pools.
why isnt pool paying up?
? It says that I got paid and I receive nothing for quite some time>?? I am not sure if anyone realizes this or not. But this coin (either through a bug or on purpose) has been nearly mined out. The difficulty appear to be set at 1024 and does not change. As a result, blocks are being found about every second instead of every minute.
Code:
static const int64 nTargetTimespan = 3456000;
static const int64 nTargetSpacing = 60;
static const int64 nTargetSpacing = 60;
I don't think it's broken, the spec seems correct:
4 days = 960 * 60 * 60 = 3456000
Diff changes every 57600 blocks. Last change was at #288000, next is: #345600
I suppose you are correct. Still doesn't change the fact that 987,312,883 of the 1,000,000,000 coins (98.7%) have already been mined in only two weeks of the coin's existence.
Yeah, I suppose that the power of ASIC's was greatly underestimated here.
I am not sure if anyone realizes this or not. But this coin (either through a bug or on purpose) has been nearly mined out. The difficulty appear to be set at 1024 and does not change. As a result, blocks are being found about every second instead of every minute.
Code:
static const int64 nTargetTimespan = 3456000;
static const int64 nTargetSpacing = 60;
static const int64 nTargetSpacing = 60;
I don't think it's broken, the spec seems correct:
4 days = 960 * 60 * 60 = 3456000
Diff changes every 57600 blocks. Last change was at #288000, next is: #345600
I suppose you are correct. Still doesn't change the fact that 987,312,883 of the 1,000,000,000 coins (98.7%) have already been mined in only two weeks of the coin's existence.
How many coins did the development team acquire from miners? I read you bought back at a rate of about $1.50/million coins. Must have made a pretty penny.
I am not sure if anyone realizes this or not. But this coin (either through a bug or on purpose) has been nearly mined out. The difficulty appear to be set at 1024 and does not change. As a result, blocks are being found about every second instead of every minute.
Code:
static const int64 nTargetTimespan = 3456000;
static const int64 nTargetSpacing = 60;
static const int64 nTargetSpacing = 60;
I don't think it's broken, the spec seems correct:
4 days = 960 * 60 * 60 = 3456000
Diff changes every 57600 blocks. Last change was at #288000, next is: #345600
I am not sure if anyone realizes this or not. But this coin (either through a bug or on purpose) has been nearly mined out. The difficulty appear to be set at 1024 and does not change. As a result, blocks are being found about every second instead of every minute.
Can the OP please add http://rainbowcoin.securepayment.cc to the list of pools.
It dont shows my lgbt in the pool Why?and I mine lgbt in the pool:http://172.245.183.41/lgbt/public/ some days ago but it closed now. and I mine in the official pool now ,It shows nothing in the unconfirmed account or the confirmed account , and I checked the transactions there was nothing too . If the admin stole them all or other problem?
This coin has got to be broken.
Why does the current coin count show 987,070,739 but max coins is supposedly 1,000,000,000.
What am I missing?
What am I missing?
"Rainbowcoin is a bitcoin-based cryptocurrency to be proud of ="
Do I get it right?
Do I get it right?
yes
"Rainbowcoin is a bitcoin-based cryptocurrency to be proud of ="
Do I get it right?
Do I get it right?
Careful guys dont do that Leancy let their hosting company on their dedicated server and had major scammer issues.
There is major scammers out there making alot of money they may of even stole GOX BTC and want more.
There is major scammers out there making alot of money they may of even stole GOX BTC and want more.
Recently The DEV's of Rainbowcoin allowed third-party users to access the Rainbowcoin central compter mainframe.
those individuals helped themselves to 41M LGBT and sent them off to Cryptorush.in to wash them
After some investigation www.cryptorush.in transfered back all the stolen coins
We, the DEV's of RAINBOWCOIN (LGBT), would like to say thank-you to CRYPTORUSH.IN team for their help and support
those individuals helped themselves to 41M LGBT and sent them off to Cryptorush.in to wash them
After some investigation www.cryptorush.in transfered back all the stolen coins
We, the DEV's of RAINBOWCOIN (LGBT), would like to say thank-you to CRYPTORUSH.IN team for their help and support
Jump to: