mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 07:01:50 PM Last edit: May 20, 2013, 08:51:29 PM by mullick |
|
Okay So I have been solo mining bitgems on and off for a few days here. I went out and bought a 7870 today and got home and installed it. Then I go to open my bitgem wallet to receive some coins I'm trading. It hangs on out of sync even though I have 14 connections. Odd thing is the 50BTg I was sent popped up instantly but now wont get any confirms!. Yes I know btg confirms take forever but It has been 38 minutes and not one confirm. If I close the wallet and re open it they are still there just no confirms Any Ideas as to what is going on? I thought maybe I messed something up in my .conf so I backed up my wallet and installed bitgem on another account and copied my .dat over. Same exact issue. EDIT: Others are having the same problem. Bitgem has been attacked?!
|
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 07:17:37 PM |
|
It appears to be stuck at block 5126
Catching up...... Downloaded 5126 blocks of transaction histrory Last received block was generated 4 hours ago
|
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 07:49:15 PM |
|
BUMP Bitgem blockchain dead at block 5126
|
|
|
|
coinerd
|
|
May 20, 2013, 07:50:22 PM |
|
all my peers locked at 5126
|
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 07:53:44 PM |
|
all my peers locked at 5126
It appears to be the same across the network. This sucks I just bought 6 LTC worth
|
|
|
|
LiteBit
Legendary
Offline
Activity: 1133
Merit: 1050
|
|
May 20, 2013, 07:57:09 PM |
|
|
|
|
|
baritus
Legendary
Offline
Activity: 966
Merit: 1052
|
|
May 20, 2013, 07:57:51 PM |
|
Rookie dev mistakes are funny.
|
Digitalcoin - Sha256, Scrypt, x11 Mining - Multi-algorithm & One Click Masternodes - Founded in 2013
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 08:03:23 PM |
|
Rookie dev mistakes are funny.
What do you mean by this? Do you know for a fact it was a error in the code?
|
|
|
|
baritus
Legendary
Offline
Activity: 966
Merit: 1052
|
|
May 20, 2013, 08:08:35 PM |
|
Not sure what else it could possibly be that could make all the clients do that. It's hard to mess up all the network, unless it's something in the code, or something I've never heard of before..
|
Digitalcoin - Sha256, Scrypt, x11 Mining - Multi-algorithm & One Click Masternodes - Founded in 2013
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 08:16:40 PM |
|
Not sure what else it could possibly be that could make all the clients do that. It's hard to mess up all the network, unless it's something in the code, or something I've never heard of before..
Arent you just as new as me maybe a few months? Could it be a 51% attack? I'm still not quite sure how one of those would play out
|
|
|
|
baritus
Legendary
Offline
Activity: 966
Merit: 1052
|
|
May 20, 2013, 08:18:38 PM |
|
Nope, I've been around longer than that, just stayed a lurker for a long time, . A 51% attack would allow someone to double spend transactions, I've never heard of it freezing the network at a block.
|
Digitalcoin - Sha256, Scrypt, x11 Mining - Multi-algorithm & One Click Masternodes - Founded in 2013
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 08:21:48 PM |
|
Nope, I've been around longer than that, just stayed a lurker for a long time, . A 51% attack would allow someone to double spend transactions, I've never heard of it freezing the network at a block. I have heard talk about a 51% invalidating everyone else's blocks maybe thats what happened. No one had a valid block to continue the chain? I dont really understand what i'm talking about I guess lol
|
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 08:28:06 PM |
|
Nope, I've been around longer than that, just stayed a lurker for a long time, . A 51% attack would allow someone to double spend transactions, I've never heard of it freezing the network at a block. As someone who has actually killed an alt coin or two with 51% attacks I can tell you this isn't a 51% attack. You would still get confirms with a 51% attack. Could be a "chain bloat" attack but like Baritus I suspect it is rookie coding error. ~BCX~ Thanks for clearing that up. All I know is I just pissed 6 ltc down the drain unless it somehow comes back to life and it somehow doesn't affect the price.
|
|
|
|
Petr1fied
|
|
May 20, 2013, 08:33:08 PM |
|
It will affect the price. If no blocks can be mined, no transactions can be sent so until such times as it's fixed the value becomes zero.
|
|
|
|
sumantso
Legendary
Offline
Activity: 1050
Merit: 1000
|
|
May 20, 2013, 08:37:03 PM |
|
Rookie dev mistakes are funny.
The best was with Gamecoin. Though the community took over and it is great making it work.
|
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 08:37:26 PM |
|
It will affect the price. If no blocks can be mined, no transactions can be sent so until such times as it's fixed the value becomes zero.
I do have a brain. I was being extremely optimistic
|
|
|
|
|
Magic8Ball
Legendary
Offline
Activity: 1050
Merit: 1000
|
|
May 20, 2013, 08:44:32 PM |
|
Rookie dev mistakes are funny.
The best was with Gamecoin. Though the community took over and it is great making it work. Is it possible to do the same with Bitgems? It would be mice see this keep on chugging.
|
|
|
|
mullick (OP)
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
May 20, 2013, 08:50:59 PM |
|
ALL IS well the network seemed to work it out only 3 blocks un accounted for but I may have missed those while the wallet was closed
|
|
|
|
Petr1fied
|
|
May 20, 2013, 08:53:51 PM |
|
GameCoin is not saved yet, it's certainly in a better state than it was but until we hit block 20160 and the difficulty comes down it's still on the edge of a precipice. I personally have no stake in Bitgem but I'd like to hope someone would be prepared to do something similar try and get it back on track.
|
|
|
|
|