Cryptomining:
Did you get your wallet fixed yet?
Did you get your wallet fixed yet?
no, i started a new one, exported the keys on old one. was going to wait for the new client to import and see if that will do it.
Topic: [ANN][GRA] Graincoin - New PoW/PoS coin | Fast, secure | Version 1.5 Released! - page 89. (Read 177059 times)
January 08, 2014, 09:44:01 PM
no, i started a new one, exported the keys on old one. was going to wait for the new client to import and see if that will do it.
January 08, 2014, 08:00:39 PM
Cryptomining:
Did you get your wallet fixed yet?
Did you get your wallet fixed yet?
January 08, 2014, 06:36:02 PM
looked at this coin a week ago and it seems like it didnt died at all but i must ask is the diff still so low or did something happen? im now thinking about where to place second miner on gift or grain ?!
diff is 30.5k right now, still very mineable, get in before the train takes off, all aboard!
January 08, 2014, 06:20:26 PM
looked at this coin a week ago and it seems like it didnt died at all but i must ask is the diff still so low or did something happen? im now thinking about where to place second miner on gift or grain ?!
January 08, 2014, 06:16:12 PM
Congrats to nullu, nice superblock 
Thanks.
thats a 5%er nice going.
It's nice to know even with my modest 275khash/sec I can still get decent payouts from this coin.
the superblocks make this real interesting to solo.
I totally agree. The current difficulty makes it just right for solo mining, and it's a lot more exciting waiting to hit a block than pool mining.
January 08, 2014, 05:58:50 PM
thats a 5%er nice going.
It's nice to know even with my modest 275khash/sec I can still get decent payouts from this coin.
the superblocks make this real interesting to solo.
January 08, 2014, 05:58:31 PM
Congrats to nullu, nice superblock
January 08, 2014, 05:55:39 PM
thats a 5%er nice going.
It's nice to know even with my modest 275khash/sec I can still get decent payouts from this coin.
January 08, 2014, 05:53:06 PM
thats a 5%er nice going.
January 08, 2014, 05:49:23 PM
Did I just hit a superblock?
If I did it was a small one, but still; sweet.
If I did it was a small one, but still; sweet.
January 08, 2014, 05:30:58 PM
Hi , I've been mining GRA for a week now, got a few friends into it,
looks promising, i really like the PoS part and the fact that it's not in an exchange it.
I read through some concerns of people who say there are not enough miners,
but GRA has a PoS system too, shouldn't you consider the open unlocked wallets too as a factor stabilizing the grain network?
Isn't PoW useless compared to PoS? (i was thinking of mining for another week, and then just leave my wallet open)
What do you think could make Grain more likable compared to other coins?
And i was wondering - i noticed the network retargets the difficulty every block, doesn't that cause some overhead and loss of performance?
happy mining
, I've been mining GRA for a week now, got a few friends into it,looks promising, i really like the PoS part and the fact that it's not in an exchange it.
I read through some concerns of people who say there are not enough miners,
but GRA has a PoS system too, shouldn't you consider the open unlocked wallets too as a factor stabilizing the grain network?
Isn't PoW useless compared to PoS? (i was thinking of mining for another week, and then just leave my wallet open)
What do you think could make Grain more likable compared to other coins?
And i was wondering - i noticed the network retargets the difficulty every block, doesn't that cause some overhead and loss of performance?
happy mining
I wasn't aware you had to leave your wallet open to receive the PoS.
January 08, 2014, 05:26:34 PM
Hi , I've been mining GRA for a week now, got a few friends into it,
looks promising, i really like the PoS part and the fact that it's not in an exchange it.
I read through some concerns of people who say there are not enough miners,
but GRA has a PoS system too, shouldn't you consider the open unlocked wallets too as a factor stabilizing the grain network?
Isn't PoW useless compared to PoS? (i was thinking of mining for another week, and then just leave my wallet open)
What do you think could make Grain more likable compared to other coins?
And i was wondering - i noticed the network retargets the difficulty every block, doesn't that cause some overhead and loss of performance?
happy mining
, I've been mining GRA for a week now, got a few friends into it,looks promising, i really like the PoS part and the fact that it's not in an exchange it.
I read through some concerns of people who say there are not enough miners,
but GRA has a PoS system too, shouldn't you consider the open unlocked wallets too as a factor stabilizing the grain network?
Isn't PoW useless compared to PoS? (i was thinking of mining for another week, and then just leave my wallet open)
What do you think could make Grain more likable compared to other coins?
And i was wondering - i noticed the network retargets the difficulty every block, doesn't that cause some overhead and loss of performance?
happy mining
January 08, 2014, 05:12:40 PM
Thanks everyone and all that sent me encouragements.
I found the issue of pos, why it is stopped. It related to the issue that network time sometimes messed up.
For pos, the last pos block (block 62235) has a network time before the previous pos block (block 62234), this messed everything and caused the pos generation does not meet the criteria so it is rejected:
I have a fix for that, and it works in my test (generated pos block again). But this is a hard fork. I will provide a new version of the client, and it is a mandatory upgrade. I will give about 3 days before the switch over happens. Before the switch over happens, the coin will generate only the pow blocks (as it is now).
The same issue seems occur at pow block, that's why sometimes in block explorer you will see the time messed up. I do notice that this occurs in many other coins. In general this will not cause much problems, but sometimes it could cause diff behave strangely (usually transient). The network time issue is a broader issue which may need some revisit on the fundamentals of the cryptocoin, which I will not address now (this will require a lot more work and maybe a team work).
With my fix, the next time network time issue in pos should not cause a stop in pos generation.
A new version of the client will be provided some time later today or tomorrow.
I found the issue of pos, why it is stopped. It related to the issue that network time sometimes messed up.
For pos, the last pos block (block 62235) has a network time before the previous pos block (block 62234), this messed everything and caused the pos generation does not meet the criteria so it is rejected:
Quote
>> Height = 62235, fProofOfStake = 1, nActualSpacing = -575
>> pindexPrev->GetBlockTime() = 1388562077, pindexPrev->nHeight = 62235
>> pindexPrevPrev->GetBlockTime() = 1388562652, pindexPrevPrev->nHeight = 62234
>> pindexPrev->GetBlockTime() = 1388562077, pindexPrev->nHeight = 62235
>> pindexPrevPrev->GetBlockTime() = 1388562652, pindexPrevPrev->nHeight = 62234
I have a fix for that, and it works in my test (generated pos block again). But this is a hard fork. I will provide a new version of the client, and it is a mandatory upgrade. I will give about 3 days before the switch over happens. Before the switch over happens, the coin will generate only the pow blocks (as it is now).
The same issue seems occur at pow block, that's why sometimes in block explorer you will see the time messed up. I do notice that this occurs in many other coins. In general this will not cause much problems, but sometimes it could cause diff behave strangely (usually transient). The network time issue is a broader issue which may need some revisit on the fundamentals of the cryptocoin, which I will not address now (this will require a lot more work and maybe a team work).
With my fix, the next time network time issue in pos should not cause a stop in pos generation.
A new version of the client will be provided some time later today or tomorrow.
Great work. I'll be pointing my shiny new R9 280x at Grain tomorrow when it arrives.
January 08, 2014, 05:03:51 PM
nice work, thanks bosian.
January 08, 2014, 05:02:30 PM
Very, very good, sir!
January 08, 2014, 05:02:16 PM
Thanks everyone and all that sent me encouragements.
I found the issue of pos, why it is stopped. It related to the issue that network time sometimes messed up.
For pos, the last pos block (block 62235) has a network time before the previous pos block (block 62234), this messed everything and caused the pos generation does not meet the criteria so it is rejected:
I have a fix for that, and it works in my test (generated pos block again). But this is a hard fork. I will provide a new version of the client, and it is a mandatory upgrade. I will give about 3 days before the switch over happens. Before the switch over happens, the coin will generate only the pow blocks (as it is now).
The same issue seems occur at pow block, that's why sometimes in block explorer you will see the time messed up. I do notice that this occurs in many other coins. In general this will not cause much problems, but sometimes it could cause diff behave strangely (usually transient). The network time issue is a broader issue which may need some revisit on the fundamentals of the cryptocoin, which I will not address now (this will require a lot more work and maybe a team work).
With my fix, the next time network time issue in pos should not cause a stop in pos generation.
A new version of the client will be provided some time later today or tomorrow.
I found the issue of pos, why it is stopped. It related to the issue that network time sometimes messed up.
For pos, the last pos block (block 62235) has a network time before the previous pos block (block 62234), this messed everything and caused the pos generation does not meet the criteria so it is rejected:
Quote
>> Height = 62235, fProofOfStake = 1, nActualSpacing = -575
>> pindexPrev->GetBlockTime() = 1388562077, pindexPrev->nHeight = 62235
>> pindexPrevPrev->GetBlockTime() = 1388562652, pindexPrevPrev->nHeight = 62234
>> pindexPrev->GetBlockTime() = 1388562077, pindexPrev->nHeight = 62235
>> pindexPrevPrev->GetBlockTime() = 1388562652, pindexPrevPrev->nHeight = 62234
I have a fix for that, and it works in my test (generated pos block again). But this is a hard fork. I will provide a new version of the client, and it is a mandatory upgrade. I will give about 3 days before the switch over happens. Before the switch over happens, the coin will generate only the pow blocks (as it is now).
The same issue seems occur at pow block, that's why sometimes in block explorer you will see the time messed up. I do notice that this occurs in many other coins. In general this will not cause much problems, but sometimes it could cause diff behave strangely (usually transient). The network time issue is a broader issue which may need some revisit on the fundamentals of the cryptocoin, which I will not address now (this will require a lot more work and maybe a team work).
With my fix, the next time network time issue in pos should not cause a stop in pos generation.
A new version of the client will be provided some time later today or tomorrow.
Nice investigating Bosian
January 08, 2014, 04:53:57 PM
Thanks everyone and all that sent me encouragements.
I found the issue of pos, why it is stopped. It related to the issue that network time sometimes messed up.
For pos, the last pos block (block 62235) has a network time before the previous pos block (block 62234), this messed everything and caused the pos generation does not meet the criteria so it is rejected:
I have a fix for that, and it works in my test (generated pos block again). But this is a hard fork. I will provide a new version of the client, and it is a mandatory upgrade. I will give about 3 days before the switch over happens. Before the switch over happens, the coin will generate only the pow blocks (as it is now).
The same issue seems occur at pow block, that's why sometimes in block explorer you will see the time messed up. I do notice that this occurs in many other coins. In general this will not cause much problems, but sometimes it could cause diff behave strangely (usually transient). The network time issue is a broader issue which may need some revisit on the fundamentals of the cryptocoin, which I will not address now (this will require a lot more work and maybe a team work).
With my fix, the next time network time issue in pos should not cause a stop in pos generation.
A new version of the client will be provided some time later today or tomorrow.
I found the issue of pos, why it is stopped. It related to the issue that network time sometimes messed up.
For pos, the last pos block (block 62235) has a network time before the previous pos block (block 62234), this messed everything and caused the pos generation does not meet the criteria so it is rejected:
Quote
>> Height = 62235, fProofOfStake = 1, nActualSpacing = -575
>> pindexPrev->GetBlockTime() = 1388562077, pindexPrev->nHeight = 62235
>> pindexPrevPrev->GetBlockTime() = 1388562652, pindexPrevPrev->nHeight = 62234
>> pindexPrev->GetBlockTime() = 1388562077, pindexPrev->nHeight = 62235
>> pindexPrevPrev->GetBlockTime() = 1388562652, pindexPrevPrev->nHeight = 62234
I have a fix for that, and it works in my test (generated pos block again). But this is a hard fork. I will provide a new version of the client, and it is a mandatory upgrade. I will give about 3 days before the switch over happens. Before the switch over happens, the coin will generate only the pow blocks (as it is now).
The same issue seems occur at pow block, that's why sometimes in block explorer you will see the time messed up. I do notice that this occurs in many other coins. In general this will not cause much problems, but sometimes it could cause diff behave strangely (usually transient). The network time issue is a broader issue which may need some revisit on the fundamentals of the cryptocoin, which I will not address now (this will require a lot more work and maybe a team work).
With my fix, the next time network time issue in pos should not cause a stop in pos generation.
A new version of the client will be provided some time later today or tomorrow.
January 08, 2014, 04:17:30 PM
Hi all,
Bosian is working on the PoS issue.
Talked to him yesterday, he is inspecting the whole codebase.
Give him some More Time to get it fixed.
Bosian is working on the PoS issue.
Talked to him yesterday, he is inspecting the whole codebase.
Give him some More Time to get it fixed.
January 08, 2014, 04:13:22 PM
my wallet wont sync and locks up, gets to about 2500 blocks left and stops, anyone got any ideas.
stop the wallet, remove the peers.dat file and add these nodes to the Grain.conf:
addnode=61.23.187.93:11054
addnode=146.185.150.184:11054
addnode=84.202.182.12:11054
addnode=95.85.26.11:11054
addnode=83.212.121.113:11054
addnode=198.245.51.98:11054
hope that helps
update but client is still locking up.
is it possible to have to many grain in one address?
YES it is completely possible. Send me half and see if it fixes it
thats the problem i cant send anything. if i get it fixed ill send you some.
Try this.
Go offline and open the wallet, that way it won't try to sync.
Backup your wallet.
Uninstall it completely (get rid of everything the %Appdata% as well)
Reinstall with the current version
Make sure you have all the nodes in place
Import your wallet
January 08, 2014, 02:58:51 PM
I really like Grain, but what made it interesting for me was the PoS element, and the main motivator for me to mine it.
Without it I feel the coin loses what made it interesting.
Without it I feel the coin loses what made it interesting.
dont give up, bosian will probably get it fixed. pos is what got me interseted aswell.
I'll keep mining for a few days in the hope we get some updates on this. My incentive to mine is the PoS stake, and with so many altcoins out there I think the coins with something more unique to offer will survive.
Jump to: