[ANN][GHOST] GhostCoin | Roadmap | Thread Redesign | Bittrex | Bter | 400GH+ - page 16.

AllCoinedUp

member

Activity: 201

Merit: 10

Quote from: godda04 on October 09, 2014, 03:27:00 PM

why does ghost keep popping up on bittrex, one minute its there, next its gone

Maybe they are testing it, which means they are working on it right? Wink

kleineaap

hero member

Activity: 532

Merit: 500

https://github.com/GhostCoinOfficial/ghostcoin/pull/1

Quote

+/* Left for transparency. No longer needed as we're forking into POS.
+ * This code was not in the original launch. Some coins got minted
+ * improperly. In order to save everyones coins, some bad blocks had
+ * to be allowed.

muddafudda

legendary

Activity: 1008

Merit: 1022

Quote from: HoldTheLine on October 09, 2014, 07:51:30 PM

Quote from: esotericizm on October 09, 2014, 03:47:21 PM

Quote from: BTHECREATOR on October 09, 2014, 03:38:47 PM

One thing is for sure. The dev is obviously not some idiot who doesn't know his head from a hole in the ground as some have suggested. He appears to be working hard to correct the issues, and by all accounts seems to have a high degree of competency in both coding and crypto.

If that were true miners would not be in this current situation. If the dev were competant than a fix would have been rolled out in under 24 hours.

You are assuming it is something that could simply be 'fixed' within 24 hours.

It can be fixed in under an hour.

sly5am

hero member

Activity: 582

Merit: 500

move along nothing to see here.. any day now..

HoldTheLine

member

Activity: 112

Merit: 10

Quote from: provenceday on October 09, 2014, 08:18:05 PM

Ghostcoin Chinese community QQ group: 398618659 (if you are a miner or investor,you can join us, thanks)

Ghostcoin 中国社区交流群: 398618659(如果你是矿工或者投资人，你可以加入我们，谢谢！)

Good stuff!

provenceday

legendary

Activity: 1148

Merit: 1000

Ghostcoin Chinese community QQ group: 398618659 (if you are a miner or investor,you can join us, thanks)

Ghostcoin 中国社区交流群: 398618659(如果你是矿工或者投资人，你可以加入我们，谢谢！)

HoldTheLine

member

Activity: 112

Merit: 10

Quote from: esotericizm on October 09, 2014, 03:47:21 PM

Quote from: BTHECREATOR on October 09, 2014, 03:38:47 PM

One thing is for sure. The dev is obviously not some idiot who doesn't know his head from a hole in the ground as some have suggested. He appears to be working hard to correct the issues, and by all accounts seems to have a high degree of competency in both coding and crypto.

If that were true miners would not be in this current situation. If the dev were competant than a fix would have been rolled out in under 24 hours.

You are assuming it is something that could simply be 'fixed' within 24 hours.

infazan

hero member

Activity: 538

Merit: 502

when he returns to bittrex ?

esotericizm

hero member

Activity: 750

Merit: 500

Quote from: BTHECREATOR on October 09, 2014, 03:38:47 PM

One thing is for sure. The dev is obviously not some idiot who doesn't know his head from a hole in the ground as some have suggested. He appears to be working hard to correct the issues, and by all accounts seems to have a high degree of competency in both coding and crypto.

If that were true miners would not be in this current situation. If the dev were competant than a fix would have been rolled out in under 24 hours.

BTHECREATOR

member

Activity: 67

Merit: 10

Quote from: godda04 on October 09, 2014, 03:27:00 PM

why does ghost keep popping up on bittrex, one minute its there, next its gone

I think the fact that GHOST is still popping up on Bittrex at all is a great sign for us bagholders. I for one can't wait to dump all over the heads of newbs the second this goes live. I'm gonna splatter those little shitheads with this slime.

Jk, I still think this is going to the moon. It's going to be a beautiful redemption story, kind of like a movie about the sexual awakening of a thin, nubile, rural college-age girl transplanted for the first time to the big city. All the heartbreak, the drugs and the lost lovers interspersed with erotic scenes of sensual awakening. The abortions, rehab, the liason with the Professor. And then she finds herself in all the chaos, truly finds herself, and it is glorious.

That's what's going to happen to GHOST.

BTHECREATOR

member

Activity: 67

Merit: 10

Quote from: c_e_d on October 09, 2014, 12:06:29 PM

Wasn't POW supposed to end at block 5000?

Block 9323

Hash 00000000121d5b80127d52592b84fe2fba277b170e6438d3259a7e108e7d26c1
Previous Block 3e7550f94dfa15ccef2ebac672dc81b91a6501a7a362ce9f147443f31e5ab6bd
Next Block 00000000143859492ae97276517ba3c034990b9096339dab9eee26f98471cc3d
Height 9323
Version 6
Transaction Merkle Root 9fec23a9b26e74bc8b3dfb07070421b1ea26a4f97ebfc89d416a468a001db1b6
Time 1412755652 (2014-10-08 08:07:32)
Difficulty 8.344 (Bits: 1c1eadd1)
Cumulative Difficulty 3 594 801.926
Nonce 12996936
Transactions 1
Value out 4000
Transaction Fees 0
Average Coin Age 0.925654 days
Coin-days Destroyed 0
Cumulative Coin-days Destroyed 35.21%
Transaction Fee Size (kB) From (amount) To (amount)
9fec23a9b2... 0 0.13 Generation: 4000 + 0 total fees GfH6xoSRDLkP8rHqmKcaANhrZQfMzaPgRr: 4000

There is more wrong with this code than only the missing check for the POW block reward.

So your chances to get a working coin again are:
a) fix that max POW block check too and hope there are no more surprises in the code
b) get a serious code review from a well known trusted coin dev so you know what else to fix
c) start again with a fresh copy from the clean(?), original source (not! the compromised code) and put your params and mods in

One thing is for sure. The dev is obviously not some idiot who doesn't know his head from a hole in the ground as some have suggested. He appears to be working hard to correct the issues, and by all accounts seems to have a high degree of competency in both coding and crypto.

What cracks me up, though, is all the people who are here saying this situation is marred beyond redemption. Have you people saying these things been in crypto for longer than a month? PRO is still listed and has good moments. URO, the most bizarre freak show of them all, still pumps. LIBRE, remember the FUD that almost wrecked that one? Coin after bozo coin gets blown away with fud, real or imagined, and comes back singing like a bird.

But on a deeper level, I have a news flash for you people: CRYPTO IS A SCAM. This stuff is almost entirely, to a coin, 100% useless. Have fun while you can, and stop hating on your neighbor.

BTHECREATOR

member

Activity: 67

Merit: 10

Quote from: ?? on ??

Quote from: baxto on October 09, 2014, 11:48:16 AM

Quote from: PANDiNSKi on October 09, 2014, 11:42:33 AM

It's nice to see the dev attempting to fix this mess, But you've repeatedly avoided the most important question - When are you going to do POD? I'm not going anywhere near this coin again until you address POD. Nobody will trust you, even remotely, until this has been done.

Not true its been proven time and time again POD doesnt mean shit anymore. Anyone can submit fake ids and 4+ stars

Agreed, I've seen a ton of shitcoins get away with being 4+ stars. The fact that the dev is still around is probably more important than anything PoD.

Is it possible the dev has not done PoD because he's concerned about liability for the previous issues as there's still a pall of suspicion over him? Perhaps he's trying to prove he's legit before revealing his identity.

And yet, if this is the case, why has he not revealed the identity of the scammers?

godda04

sr. member

Activity: 476

Merit: 500

why does ghost keep popping up on bittrex, one minute its there, next its gone

muddafudda

legendary

Activity: 1008

Merit: 1022

Quote from: Jookly on October 09, 2014, 01:39:32 PM

Quote from: muddafudda on October 09, 2014, 01:37:20 PM

Code:

static const int LAST_POW_BLOCK = 5000;

is available in main.h but is pointless when not used. Usually you would add this in main.ccp but they didn't and POW goes on.

Code:

map::iterator mi = mapBlockIndex.find(hashPrevBlock);
    if (mi == mapBlockIndex.end())
        return DoS(10, error("AcceptBlock() : prev block not found"));
    CBlockIndex* pindexPrev = (*mi).second;
    int nHeight = pindexPrev->nHeight+1;
    int nPowHeight = GetPowHeight(pindexPrev)+1;
+        if (IsProofOfWork() && nHeight > CUTOFF_POW_BLOCK)
+        return DoS(100, error("AcceptBlock() : No proof-of-work allowed anymore (height = %d)", nHeight));

Very amateur, foolish mistake.

get a fucking clue man.

I just pointed out one of a series of fuck ups and you tell me to get a clue? Are you fucktarded?

DonQuijote

legendary

Activity: 1551

Merit: 1002

♠ ♥ ♣ ♦ < ♛♚&#

Quote from: BTHECREATOR on October 09, 2014, 01:08:54 PM

Haha, GHOST #1 in 24-hr. Vol. on Bittrex!

No, ghost market is disable on bittrex:
https://bittrex.com/Market/Index?MarketName=BTC-GHOST

Jookly

legendary

Activity: 1131

Merit: 1007

Quote from: muddafudda on October 09, 2014, 01:37:20 PM

Code:

static const int LAST_POW_BLOCK = 5000;

is available in main.h but is pointless when not used. Usually you would add this in main.ccp but they didn't and POW goes on.

Code:

map::iterator mi = mapBlockIndex.find(hashPrevBlock);
    if (mi == mapBlockIndex.end())
        return DoS(10, error("AcceptBlock() : prev block not found"));
    CBlockIndex* pindexPrev = (*mi).second;
    int nHeight = pindexPrev->nHeight+1;
    int nPowHeight = GetPowHeight(pindexPrev)+1;
+        if (IsProofOfWork() && nHeight > CUTOFF_POW_BLOCK)
+        return DoS(100, error("AcceptBlock() : No proof-of-work allowed anymore (height = %d)", nHeight));

Very amateur, foolish mistake.

get a fucking clue man.

muddafudda

legendary

Activity: 1008

Merit: 1022

Code:

static const int LAST_POW_BLOCK = 5000;

is available in main.h but is pointless when not used. Usually you would add this in main.ccp but they didn't and POW goes on.

Code:

map::iterator mi = mapBlockIndex.find(hashPrevBlock);
    if (mi == mapBlockIndex.end())
        return DoS(10, error("AcceptBlock() : prev block not found"));
    CBlockIndex* pindexPrev = (*mi).second;
    int nHeight = pindexPrev->nHeight+1;
    int nPowHeight = GetPowHeight(pindexPrev)+1;
+        if (IsProofOfWork() && nHeight > CUTOFF_POW_BLOCK)
+        return DoS(100, error("AcceptBlock() : No proof-of-work allowed anymore (height = %d)", nHeight));

Very amateur, foolish mistake.

BTHECREATOR

member

Activity: 67

Merit: 10

Haha, GHOST #1 in 24-hr. Vol. on Bittrex!

sdmathis

hero member

Activity: 546

Merit: 500

AKA The Rubber Monkey

Quote from: c_e_d on October 09, 2014, 12:06:29 PM

Wasn't POW supposed to end at block 5000?

Block 9323

Hash 00000000121d5b80127d52592b84fe2fba277b170e6438d3259a7e108e7d26c1
Previous Block 3e7550f94dfa15ccef2ebac672dc81b91a6501a7a362ce9f147443f31e5ab6bd
Next Block 00000000143859492ae97276517ba3c034990b9096339dab9eee26f98471cc3d
Height 9323
Version 6
Transaction Merkle Root 9fec23a9b26e74bc8b3dfb07070421b1ea26a4f97ebfc89d416a468a001db1b6
Time 1412755652 (2014-10-08 08:07:32)
Difficulty 8.344 (Bits: 1c1eadd1)
Cumulative Difficulty 3 594 801.926
Nonce 12996936
Transactions 1
Value out 4000
Transaction Fees 0
Average Coin Age 0.925654 days
Coin-days Destroyed 0
Cumulative Coin-days Destroyed 35.21%
Transaction Fee Size (kB) From (amount) To (amount)
9fec23a9b2... 0 0.13 Generation: 4000 + 0 total fees GfH6xoSRDLkP8rHqmKcaANhrZQfMzaPgRr: 4000

There is more wrong with this code than only the missing check for the POW block reward.

So your chances to get a working coin again are:
a) fix that max POW block check too and hope there are no more surprises in the code
b) get a serious code review from a well known trusted coin dev so you know what else to fix
c) start again with a fresh copy from the clean(?), original source (not! the compromised code) and put your params and mods in

No, it was supposed to end after 5000 POW blocks. The total block count that you are looking at includes POS blocks.

c_e_d

member

Activity: 100

Merit: 10

Wasn't POW supposed to end at block 5000?

Block 9323

Hash 00000000121d5b80127d52592b84fe2fba277b170e6438d3259a7e108e7d26c1
Previous Block 3e7550f94dfa15ccef2ebac672dc81b91a6501a7a362ce9f147443f31e5ab6bd
Next Block 00000000143859492ae97276517ba3c034990b9096339dab9eee26f98471cc3d
Height 9323
Version 6
Transaction Merkle Root 9fec23a9b26e74bc8b3dfb07070421b1ea26a4f97ebfc89d416a468a001db1b6
Time 1412755652 (2014-10-08 08:07:32)
Difficulty 8.344 (Bits: 1c1eadd1)
Cumulative Difficulty 3 594 801.926
Nonce 12996936
Transactions 1
Value out 4000
Transaction Fees 0
Average Coin Age 0.925654 days
Coin-days Destroyed 0
Cumulative Coin-days Destroyed 35.21%
Transaction Fee Size (kB) From (amount) To (amount)
9fec23a9b2... 0 0.13 Generation: 4000 + 0 total fees GfH6xoSRDLkP8rHqmKcaANhrZQfMzaPgRr: 4000

There is more wrong with this code than only the missing check for the POW block reward.

So your chances to get a working coin again are:
a) fix that max POW block check too and hope there are no more surprises in the code
b) get a serious code review from a well known trusted coin dev so you know what else to fix
c) start again with a fresh copy from the clean(?), original source (not! the compromised code) and put your params and mods in

Topic: [ANN][GHOST] GhostCoin | Roadmap | Thread Redesign | Bittrex | Bter | 400GH+ - page 16. (Read 117135 times)