Sberbank
Newbie
Offline
Activity: 42
Merit: 0
|
|
January 28, 2014, 12:22:52 PM |
|
many orphans lately
|
|
|
|
suncoastbuddy
|
|
January 28, 2014, 12:25:22 PM |
|
I am having a lot of trouble running the 1.4 wallet with minting. I am running windows 7 and if I unlock it for minting it goes to non responsive.... Any ideas?
|
|
|
|
groggin
Legendary
Offline
Activity: 1894
Merit: 1001
|
|
January 28, 2014, 12:30:07 PM |
|
I am having a lot of trouble running the 1.4 wallet with minting. I am running windows 7 and if I unlock it for minting it goes to non responsive.... Any ideas?
having same trouble, mostly when another running wallet grabs the focus. try: task manager>processes tab>sort by name, right click [grain]>set priority>DO NOT USE REALTIME usually works for me, the realtime setting freezez my comp.
|
|
|
|
suncoastbuddy
|
|
January 28, 2014, 12:35:11 PM |
|
I am having a lot of trouble running the 1.4 wallet with minting. I am running windows 7 and if I unlock it for minting it goes to non responsive.... Any ideas?
having same trouble, mostly when another running wallet grabs the focus. try: task manager>processes tab>sort by name, right click [grain]>set priority>DO NOT USE REALTIME usually works for me, the realtime setting freezez my comp. Thanks... I will give it a go
|
|
|
|
mkimid
Sr. Member
Offline
Activity: 336
Merit: 250
Have A Nice Day
|
|
January 28, 2014, 03:23:57 PM |
|
I guess, there is a kind of trap, it is very hard to be in, and you and me are in those hole, Anyway, if possible we have to find a way to escape for the others ^^
Has it improved for you? In the past couple of hours I can only see 7 small corrections (one PoW lost) and one slightly larger correction that orphaned 3 blocks. In the 2 hours before that there were 65+ PoS corrections. T-4 to T-2 had 65+ small to medium corrections T-2 to T-0 had 8 small corrections Bit of a difference? I have restarted around hour ago, I have removed all, and started agin from sync. I have to check on tomorrow ^^ good luck... I've been mining, seems the diff now is OK, it was shot up for a while, but now it seems more reasonable. From 11PM to 10AM (for 11 hours), I have found 14 blocks, and 11 blocks have been validated, and 3 blocks have been invalidated due to orphans. I think, after fully restart, it work normal again, Anyway, I do not know why I have been in local(?) fork, But, Maybe, I have found the solution, First Trial [3 hours, Diff 0~1] Remove all file (block information and peer information) from %APPDATA%\Grain and, I have synced all again, But, just orphans only, Second Trial [6 hours, Diff 0~1] I have repair wallet But, just orphans only, Third Trial [11 hours, Diff 0~2(mostly 1)] Move all coins into the other wallet such as coinedup wallet, and, I have remove %APPDATA%\Grain and, I have synced all again and, I have return my coines from the other wallet to local Now, It have been started working again I am not sure the reason (1) wallet.data has some problem ? (2) any squence of records create a problem ? (3) block data in my local computer has problem ? (4) specially diff has affect on my computer ? But, I have a solution, IF GOT JUST ORPHANS FOR LONG TIME, REFRESH ALL Thank you... P/S : between each trial, I have lost some hours, for sync blocks again, and testing and testing,
|
Have a nice day
|
|
|
bosian (OP)
|
|
January 28, 2014, 05:05:25 PM |
|
One more shop accepting Graincoin: Crypto Coin Stuff - Cryptocoin banners, stickers etchttp://www.cryptocoinstuff.comwe now have 14 shops/services accepting Graincoin (listed in OP).
|
|
|
|
bosian (OP)
|
|
January 28, 2014, 05:39:15 PM |
|
I am having a lot of trouble running the 1.4 wallet with minting. I am running windows 7 and if I unlock it for minting it goes to non responsive.... Any ideas?
having same trouble, mostly when another running wallet grabs the focus. try: task manager>processes tab>sort by name, right click [grain]>set priority>DO NOT USE REALTIME usually works for me, the realtime setting freezez my comp. Thanks... I will give it a go Hope this will be fine. Sometimes the CPU usage from pos mining can be extreme, but usually it is fine, like my wallets they mine pos every 1-2 weeks, and do not take much CPU. In most case they do not mine by themself as I guess there's no qualified coin-day available in them.
|
|
|
|
bobbyb
Member
Offline
Activity: 109
Merit: 10
|
|
January 28, 2014, 07:54:44 PM |
|
MPOS (web interface) updating completed on gra.forkpool.com. If you have any problems, contact with me by online chat on site. Hi, Is it possible to get a static share difficulty of 32 or 64? I am mining with 300-400 kH/s and I mostly get nothing from short rounds (<30% of expected shares), because the share difficulty often changes to 128 or 256. It is kinda shitty if you mine the whole 1000% round and in the next short round you just get nothing, because you didnt submit a share fast enough due to the high share difficulty. Kind regards, bobbyb It is a good idea. I think all troubles with shares archive fixed now, and i will try make new settings for vardiff tomorrow. Possible i will try to decrease base target, this is settings increase shares per round. The share difficulty jumps still to 128, this is too high for 330 kH/s and 20 sec. block times (at the moment even 14 sec!) and average round times of 70 sec.
|
|
|
|
bosian (OP)
|
|
January 28, 2014, 08:52:56 PM |
|
MPOS (web interface) updating completed on gra.forkpool.com. If you have any problems, contact with me by online chat on site. Hi, Is it possible to get a static share difficulty of 32 or 64? I am mining with 300-400 kH/s and I mostly get nothing from short rounds (<30% of expected shares), because the share difficulty often changes to 128 or 256. It is kinda shitty if you mine the whole 1000% round and in the next short round you just get nothing, because you didnt submit a share fast enough due to the high share difficulty. Kind regards, bobbyb It is a good idea. I think all troubles with shares archive fixed now, and i will try make new settings for vardiff tomorrow. Possible i will try to decrease base target, this is settings increase shares per round. The share difficulty jumps still to 128, this is too high for 330 kH/s and 20 sec. block times (at the moment even 14 sec!) and average round times of 70 sec. hmm interesting. I took a look at a particular block (block 150314) that you said not received. When I look at the block explorer, it says that the block 150314 is paid 1415 coins and sent to address 9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2R. This address receives it: http://coinblockchain.com/grain/address/9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2Rlooking at the activity of this address, it is a pool address. Then after some time, the coins 1415 are transferred out of the wallet (at block 150377). This is cleared a transfer out, as it paid 0.02 GRA tx fee. I saw a lot small transfer out, is your wallet secure? hope it's not transferred out by a bot. (Note: I looked at it again, it's the pool payout to miners). And it looks like a payout to the miners. So anyway, the block 150314 is fine, you should have received its coins and already paid out to miners.
|
|
|
|
bobbyb
Member
Offline
Activity: 109
Merit: 10
|
|
January 28, 2014, 09:19:05 PM |
|
MPOS (web interface) updating completed on gra.forkpool.com. If you have any problems, contact with me by online chat on site. Hi, Is it possible to get a static share difficulty of 32 or 64? I am mining with 300-400 kH/s and I mostly get nothing from short rounds (<30% of expected shares), because the share difficulty often changes to 128 or 256. It is kinda shitty if you mine the whole 1000% round and in the next short round you just get nothing, because you didnt submit a share fast enough due to the high share difficulty. Kind regards, bobbyb It is a good idea. I think all troubles with shares archive fixed now, and i will try make new settings for vardiff tomorrow. Possible i will try to decrease base target, this is settings increase shares per round. The share difficulty jumps still to 128, this is too high for 330 kH/s and 20 sec. block times (at the moment even 14 sec!) and average round times of 70 sec. hmm interesting. I took a look at a particular block (block 150314) that you said not received. When I look at the block explorer, it says that the block 150314 is paid 1415 coins and sent to address 9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2R. This address receives it: http://coinblockchain.com/grain/address/9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2Rlooking at the activity of this address, it is a pool address. Then after some time, the coins 1415 are transferred out of the wallet (at block 150377). This is cleared a transfer out, as it paid 0.02 GRA tx fee. I saw a lot small transfer out, is your wallet secure? hope it's not transferred out by a bot. (Note: I looked at it again, it's the pool payout to miners). And it looks like a payout to the miners. So anyway, the block 150314 is fine, you should have received its coins and already paid out to miners. I got nothing for this round, because the share difficulty was too high and I didnt submited any shares for this round. Yes it is a pool, its forkpool. A share difficulty of 32 or 64 would be nice. Vardiff jumps to 128 or 256 are too much.
|
|
|
|
bondi
|
|
January 28, 2014, 10:15:04 PM |
|
I guess, there is a kind of trap, it is very hard to be in, and you and me are in those hole, Anyway, if possible we have to find a way to escape for the others ^^
Has it improved for you? In the past couple of hours I can only see 7 small corrections (one PoW lost) and one slightly larger correction that orphaned 3 blocks. In the 2 hours before that there were 65+ PoS corrections. T-4 to T-2 had 65+ small to medium corrections T-2 to T-0 had 8 small corrections Bit of a difference? I have restarted around hour ago, I have removed all, and started agin from sync. I have to check on tomorrow ^^ good luck... I've been mining, seems the diff now is OK, it was shot up for a while, but now it seems more reasonable. From 11PM to 10AM (for 11 hours), I have found 14 blocks, and 11 blocks have been validated, and 3 blocks have been invalidated due to orphans. I think, after fully restart, it work normal again, Anyway, I do not know why I have been in local(?) fork, But, Maybe, I have found the solution, First Trial [3 hours, Diff 0~1] Remove all file (block information and peer information) from %APPDATA%\Grain and, I have synced all again, But, just orphans only, Second Trial [6 hours, Diff 0~1] I have repair wallet But, just orphans only, Third Trial [11 hours, Diff 0~2(mostly 1)] Move all coins into the other wallet such as coinedup wallet, and, I have remove %APPDATA%\Grain and, I have synced all again and, I have return my coines from the other wallet to local Now, It have been started working again I am not sure the reason (1) wallet.data has some problem ? (2) any squence of records create a problem ? (3) block data in my local computer has problem ? (4) specially diff has affect on my computer ? But, I have a solution, IF GOT JUST ORPHANS FOR LONG TIME, REFRESH ALL Thank you... P/S : between each trial, I have lost some hours, for sync blocks again, and testing and testing, So your GPU has to rest a bit...hehe..
|
|
|
|
bosian (OP)
|
|
January 28, 2014, 10:28:53 PM |
|
MPOS (web interface) updating completed on gra.forkpool.com. If you have any problems, contact with me by online chat on site. Hi, Is it possible to get a static share difficulty of 32 or 64? I am mining with 300-400 kH/s and I mostly get nothing from short rounds (<30% of expected shares), because the share difficulty often changes to 128 or 256. It is kinda shitty if you mine the whole 1000% round and in the next short round you just get nothing, because you didnt submit a share fast enough due to the high share difficulty. Kind regards, bobbyb It is a good idea. I think all troubles with shares archive fixed now, and i will try make new settings for vardiff tomorrow. Possible i will try to decrease base target, this is settings increase shares per round. The share difficulty jumps still to 128, this is too high for 330 kH/s and 20 sec. block times (at the moment even 14 sec!) and average round times of 70 sec. hmm interesting. I took a look at a particular block (block 150314) that you said not received. When I look at the block explorer, it says that the block 150314 is paid 1415 coins and sent to address 9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2R. This address receives it: http://coinblockchain.com/grain/address/9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2Rlooking at the activity of this address, it is a pool address. Then after some time, the coins 1415 are transferred out of the wallet (at block 150377 - this is 63 blocks later, should be a payout from the pool). This is cleared a transfer out, as it paid 0.02 GRA tx fee. I saw a lot small transfer out, is your wallet secure? hope it's not transferred out by a bot. (Note: I looked at it again, it's the pool payout to miners). And it looks like a payout to the miners. So anyway, the block 150314 is fine, you should have received its coins and already paid out to miners. I got nothing for this round, because the share difficulty was too high and I didnt submited any shares for this round. Yes it is a pool, its forkpool. A share difficulty of 32 or 64 would be nice. Vardiff jumps to 128 or 256 are too much. But from the blockexplorer, this is the trace of the 1415 coins from block 150314: minted at block 150314, sent to 9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2R. Then later, the 1415 coins are sent from 9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2R to two other addresses: 9Cji8S3hzCmQJUjFfWkoe8XggTkLtrgnKY: 194.553719 9CKy36m54nMYAx66NsgnrKr47J18uzggvM: 1220.426281 The transaction is http://coinblockchain.com/grain/block/000000001ab18da64639ad270f9bea52a108a3d77b9d9707b26712d78c7841bcand you can follow the links to further track where are these coins.
|
|
|
|
bobbyb
Member
Offline
Activity: 109
Merit: 10
|
|
January 28, 2014, 10:52:56 PM Last edit: January 28, 2014, 11:34:08 PM by bobbyb |
|
MPOS (web interface) updating completed on gra.forkpool.com. If you have any problems, contact with me by online chat on site. Hi, Is it possible to get a static share difficulty of 32 or 64? I am mining with 300-400 kH/s and I mostly get nothing from short rounds (<30% of expected shares), because the share difficulty often changes to 128 or 256. It is kinda shitty if you mine the whole 1000% round and in the next short round you just get nothing, because you didnt submit a share fast enough due to the high share difficulty. Kind regards, bobbyb It is a good idea. I think all troubles with shares archive fixed now, and i will try make new settings for vardiff tomorrow. Possible i will try to decrease base target, this is settings increase shares per round. The share difficulty jumps still to 128, this is too high for 330 kH/s and 20 sec. block times (at the moment even 14 sec!) and average round times of 70 sec. hmm interesting. I took a look at a particular block (block 150314) that you said not received. When I look at the block explorer, it says that the block 150314 is paid 1415 coins and sent to address 9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2R. This address receives it: http://coinblockchain.com/grain/address/9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2Rlooking at the activity of this address, it is a pool address. Then after some time, the coins 1415 are transferred out of the wallet (at block 150377 - this is 63 blocks later, should be a payout from the pool). This is cleared a transfer out, as it paid 0.02 GRA tx fee. I saw a lot small transfer out, is your wallet secure? hope it's not transferred out by a bot. (Note: I looked at it again, it's the pool payout to miners). And it looks like a payout to the miners. So anyway, the block 150314 is fine, you should have received its coins and already paid out to miners. I got nothing for this round, because the share difficulty was too high and I didnt submited any shares for this round. Yes it is a pool, its forkpool. A share difficulty of 32 or 64 would be nice. Vardiff jumps to 128 or 256 are too much. But from the blockexplorer, this is the trace of the 1415 coins from block 150314: minted at block 150314, sent to 9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2R. Then later, the 1415 coins are sent from 9Kvkbie3addSc3PGpdcQyKumQBRFKkSV2R to two other addresses: 9Cji8S3hzCmQJUjFfWkoe8XggTkLtrgnKY: 194.553719 9CKy36m54nMYAx66NsgnrKr47J18uzggvM: 1220.426281 The transaction is http://coinblockchain.com/grain/block/000000001ab18da64639ad270f9bea52a108a3d77b9d9707b26712d78c7841bcand you can follow the links to further track where are these coins. Dear Bosian, I didnt say, that the pool steals the coins. I said, that the share difficulty of the pool jumps too high for my miner (300-400 Kh/s), so that I cant compute the shares fast enough for the short rounds. This means, that when the round only takes 10 seconds and my GPU needs 20 seconds to find a share of min. 128 share difficulty, then I get nothing from this round, because i didnt submited any shares. If the share difficulty would stay at 32, then my miner would be able to find those shares faster and get also payed for the short rounds. share diff 32 = 0,00048828125 diff share diff 128 = 0,001953125 diff share diff 256 = 0,00390625 diff Those share difficulties may work for slow miners for 2.5 for 1 minute block target coins, but Grain has at the moment a block target of <20 seconds (pow and pos). Many rounds only take 1-5 seconds on forkpool, this is too fast for my miner to find shares at such high share difficulty. Image if the last round took 1000% of the estimated round time and found a normal block and then the next one only takes 5% of the estimated time and finds a superblock. This would be a nice compensation, but no. The share diff was too high, your miner didnt find any valid shares for this round due to the high share difficulty and you get nothing for the short round. Have fun with the next long round... And you cant solo mine with such a slow miner, because you get >50% orphans. I am only asking the pool operator for a lower and stable share difficulty.
|
|
|
|
bosian (OP)
|
|
January 28, 2014, 11:39:21 PM |
|
Dear Bosian,
I didnt say, that the pool steals the coins. I said, that the share difficulty of the pool jumps too high for my miner (300-400 Kh/s), so that I cant compute the shares fast enough for the short rounds. This means, that when the round only takes 10 seconds and my GPU needs 20 seconds to find a share of min. 128 share difficulty, then I get nothing from this round, because i didnt submited any shares. If the share difficulty would stay at 32, then my miner would be able to find those shares faster and get also payed for the short rounds.
share diff 32 = 0,00048828125 diff share diff 128 = 0,001953125 diff share diff 256 = 0,00390625 diff
Those share difficulties may work for slow miners for 2.5 for 1 minute block target coins, but Grain has at the moment a block target <20 seconds (pow and pos). Many rounds only take 1-5 seconds on forkpool, this is too fast for my miner to find shares at such high share difficulty.
Image if the last round took 1000% of the estimated round time and found a normal block and then the next one only takes 5% of the estimated time and finds a superblock. This would be a nice compensation, but no. The share diff was too high, your miner didnt find any valid shares for this round due to the high share difficulty and you get nothing for the short round. Have fun with the next long round...
And you cant solo mine with such a slow miner, because you get >50% orphans.
I am only asking the pool operator for a lower and stable share difficulty.
OK, thanks for clarifying. Unfortunately we can not fix the diff. The diff is determined from the previous real block time. I am not sure the recent diff increase is due to more hashpower, or if it is due to an algorithm issue. I am more thinking of the former, as the current price of GRA make it possibly one of the most profitable coin. The team is looking at this problem. Again, we can not fix the diff, otherwise you may get every second a block, it will mess up everything. The current block time is about 20 sec, that's why the diff is going up. But if you look at only PoW block, it is about 40-60 sec as block time, which is pretty reasonable. Though there are certain orphans, the minted block count is reasonable and within the designed range. The problem you described is why we need a pool. And the time to find a block is not fixed, it is random.
|
|
|
|
almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
|
January 29, 2014, 02:45:09 AM |
|
Dear Bosian,
I didnt say, that the pool steals the coins. I said, that the share difficulty of the pool jumps too high for my miner (300-400 Kh/s), so that I cant compute the shares fast enough for the short rounds. This means, that when the round only takes 10 seconds and my GPU needs 20 seconds to find a share of min. 128 share difficulty, then I get nothing from this round, because i didnt submited any shares. [...]
OK, thanks for clarifying. Unfortunately we can not fix the diff. The diff is determined from the previous real block time. bobbyb is talking about pool/share diff, not GRA network diff. The shares that the pool is offering are of too high a difficulty for his hashing speed, so his miner is often still working on solving a share when the network (or pool) finds the block solution. He gets paid zero for that block since he didn't submit a completed share, even though his miner has done SOME work on it.
|
|
|
|
bosian (OP)
|
|
January 29, 2014, 02:47:29 AM |
|
Dear Bosian,
I didnt say, that the pool steals the coins. I said, that the share difficulty of the pool jumps too high for my miner (300-400 Kh/s), so that I cant compute the shares fast enough for the short rounds. This means, that when the round only takes 10 seconds and my GPU needs 20 seconds to find a share of min. 128 share difficulty, then I get nothing from this round, because i didnt submited any shares. [...]
OK, thanks for clarifying. Unfortunately we can not fix the diff. The diff is determined from the previous real block time. bobbyb is talking about pool/share diff, not GRA network diff. The shares that the pool is offering are of too high a difficulty for his hashing speed, so his miner is often still working on solving a share when the network (or pool) finds the block solution. He gets paid zero for that block since he didn't submit a completed share, even though his miner has done SOME work on it. I see, this makes sense. Thanks.
|
|
|
|
valley365
|
|
January 29, 2014, 08:46:58 AM |
|
Nice coin, diff a bit high, not sure how profitable the coin is...
|
|
|
|
Nullu
|
|
January 29, 2014, 08:48:34 AM |
|
Nice coin, diff a bit high, not sure how profitable the coin is...
Long-term coin to hold. Stable price and new services weekly.
|
BTC - 14kYyhhWZwSJFHAjNTtyhRVSu157nE92gF
|
|
|
bee7
|
|
January 29, 2014, 08:54:51 AM Last edit: January 29, 2014, 01:34:04 PM by bee7 |
|
Nice coin, diff a bit high, not sure how profitable the coin is...
Long-term coin to hold. Stable price and new services weekly. Actually Grain shows steady price growth with some spikes when somebody decides to get into.
|
|
|
|
bondi
|
|
January 29, 2014, 02:38:14 PM |
|
Nice coin, diff a bit high, not sure how profitable the coin is...
Long-term coin to hold. Stable price and new services weekly. Actually Grain shows steady price growth with some spikes when somebody decides to get into. Seems to be holding pretty well, need just to increase volume...
|
|
|
|
|