Hi Any possibility to give the opportunity to the miner/worker to set the diff or maybe réajust the vardiff server side ? up and down all the time :/ 32/64/128 etc ... 32 calculation is too fast , have 4 rejects when a new block is found sometimes  96 or 128 is nice for 700kh/s |
|
|
|
Hi, I've try to ping the pool server with no result :/ Where is located the pool server plz ? I'm in EU don't want a server located in US  Hey currently there are only servers in the US. With stratum it wont make much of a difference on the location. The Eu servers are currently beign upgraded (been right for time so its taking longer then expected). I will give it a try, hope not too high amount of stale |
|
|
|
Hi, I've try to ping the pool server with no result :/ Where is located the pool server plz ? I'm in EU don't want a server located in US |
|
|
|
merci de ta réponse, j'utilise déjà une pool variable :/ |
|
|
|
Bonjour, J'aurais voulu savoir si il était possible de réduire le nombre de stale share lorsqu'un nouveau block est trouvé sur le reseau. J'ai fait quelque recherche avant de venir poster ici mais malgré le faite que le serveur auquel je me connect à un ping relativement bon je ne sais pas trop sur quelle valeur jouer dans le fichier de conf ? Mon % de rejet est entre 1% et 1.2% sur une période de 24h ca dépend des jours... [2013-07-13 21:24:05] Stratum from pool 0 detected new block
[2013-07-13 21:24:06] Pool 0 stale share detected, submitting as user requested
[2013-07-13 21:24:06] Pool 0 stale share detected, submitting as user requested
[2013-07-13 21:24:06] Rejected 068d2de2 OCL 0 Diff 0/0 (prevhash-stale)
[2013-07-13 21:24:06] Rejected 070f2024 OCL 0 Diff 0/0 (prevhash-stale) L'intensity pourrait-elle jouer un role la dedans ? le faite de poussé un peu trop le hardware ? Merci d'avance |
|
|
|
Nice touch for the hardware pooler  I've lowered the Intensivity 2013-07-10 647 kH/s 503,488 2,688 (0.53%) 0 (0.00%) 0.421893741696 LTC
2013-07-09 649 kH/s 841,784 14,162 (1.65%) 1 (0.00%) 0.705366168528 LTC
but I have changed too the pool server from nl2 to stratum+tcp://litecoinpool.org:3333/ I assume .org redirect to random nl nl1 or nl2 server How can I found the server I'm related ? Thanks in advance for you help  |
|
|
|
it was the question, what do I need to check on the conf  That depends on your software and GPU. It's hard to say what needs to be tweaked. As some like to say, fine-tuning scrypt GPU mining is an art, and experimentation is often the key to a successful setup. I gave you a hint, though, when I mentioned intensity as a possible cause; generally speaking, anything that pushes the hardware too hard can cause latency. ty I will try to play with the conf so but I'm still disappointed because is only happening when a new block is detected |
|
|
|
In my experience, stale shares can be caused by the following:
- Network latency. This is the most obvious cause. If a share takes too much time to get to the server it can easily turn stale.
- Block frequency. The more frequently the network is finding blocks, the more frequent the stales. This means that if the network difficulty is going up the stales will be higher.
- Server inefficiency. If the server is slow at handling submissions, some shares will turn stale. A high load can of course cause slowdowns.
- Software latency. Latency can also occur before the share leaves the miner, especially in the case of GPU mining. For example, if the intensity/aggressiveness parameter is set too high.
@dermo, in your case it seems that the first cause is not the problem, as your ping time to the server is low. The difficulty is currently rising but not dramatically, so I wouldn't consider cause #2 either. As regards cause #3, the average stale rate for the nl2 server is just 1%. The occurrence of stales is subject to probability, of course, but your 2% seems pretty high when compared to the average, so I would suggest that you check your miner's configuration. it was the question, what do I need to check on the conf |
|
|
|
hi, I'm new on the pool and I have an issue with stale share When a new block is detected I have 1 or 2 stale share not all the time but my ratio is going up since I'm mining on the pool 2013-07-09 643 kH/s 370,784 7,808 (2.06%) 1 (0.00%) 0.310695486528 LTC
2013-07-08 650 kH/s 845,768 10,528 (1.23%) 0 (0.00%) 0.694366868784 LTC
2013-07-07 650 kH/s 846,272 10,272 (1.20%) 0 (0.00%) 0.681653478016 LTC
2013-07-06 514 kH/s 671,504 6,368 (0.94%) 3 (0.00%) 0.540881698912 LTC Any idea ? Pinging nl2.litecoinpool.org [80.69.77.111] with 32 bytes of data:
Reply from 80.69.77.111: bytes=32 time=23ms TTL=56
Reply from 80.69.77.111: bytes=32 time=22ms TTL=56
Reply from 80.69.77.111: bytes=32 time=24ms TTL=56
Reply from 80.69.77.111: bytes=32 time=23ms TTL=56
Ping statistics for 80.69.77.111:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 24ms, Average = 23ms |
|
|
|
Just switched to bfgminer from cgminer and have an issue? with the reported diff on accepted share
Bug ?
diff was set auto by the pool on 96 when I'm used cgminer You're probably used to Ldiff (Litecoin difficulty). BFGMiner uses pdiff (pool difficulty) for everything to remain consistent. so nothing to modify in my conf everything is normal ? |
|
|
|
Just switched to bfgminer from cgminer and have an issue? with the reported diff on accepted share Bug ? diff was set auto by the pool on 96 when I'm used cgminer  thanks in advance |
|
|
|
Il ne lit pas ce fil et ne comprend probablement pas le français.
un lien vers sont topic de vente ? |
|
|
|
J'attend les futures commande groupé, parce que je me vois pas en acheter mille d'un coup ...  En Europe plus besoin de commande groupée, yxt va vendre à l'unité. yxt, peux tu donné plus d'infos stp ? merci d'avance |
|
|
|
|
@CoinBomb
you really need doing something on the site, change something .... all players are gone
@actual players/futur players
Don't bet atm, the only things you will won is losing your btc/ltc
|
|
|
|
no affiliate Payout this week ?  |
|
|
|
I am running Electrum 1.8 (Python sources) on Windows Vista. It initially took a long time to connect and then to synchronize but nothing compared to how long a full node would. I restarted the client several times, finally it is displaying my balance.
use electrum.coinwallet.me server, fast and great uptime |
|
|
|
All my balance has 20+ confirm but I get this when trying to send a transaction:  Any idea what is happening? Using Electrum 1.8 EDIT: Realised those are newly generated coins... Maybe I need more than 20+ confirm. "Coins generated aren't considered confirmed by the Bitcoin protocol for 100 blocks. It is advisable to wait some additional time for a better chance that the transaction will be propogated by all nodes. The classic bitcoin client won't show generated coins as confirmed until the 120th block." https://en.bitcoin.it/wiki/ConfirmationOk now I sent 20 BTC to my wallet but can't spend 18 BTC (same error code). I have 1.36 newly generated coins with less than 100 confirm in the same wallet but on another address. Is it possible to chose wich input I spend? edit: nvm |
|
|
|
|
Show Posts
