ko da je bitno koliko pokazuje miner proxy.
njegov poso je da zakine klejmora za 5% i nista vise, ono sto pokazuje hash-rate je samo statistcki podatak koliko si bacio share/minut ili sat i nista vise....
pool na koma kopate vas placa a miner proxy moze da pokazuje vise ili manje to je nebitno, covek je to stavio samo iz razloga da ljudi koji imaju 5-10 ili 50 rigova imaju uvid u ukupnoj snazi svih rigova i nista vise...
MONERO.RS tim poklanja 100XMR-a za najbolje ideje!
Vise informacija na : https://bitcointalk.org/index.php?topic=764450.0
Hvala na ucestvovanju, top 5 ideja ce u najkracem roku biti implementirana ! Pobednici su : https://bitcointalk.org/index.php?topic=764450.msg8653186#msg8653186
IMPORTANT POOL UPDATES , 4. SEPT 2014
Cryptonote-universal-pool timeout bug fixed! FULL HASH UTILIZATION!
Support for Worker_ID! Monitor your rigs! Aggregate stats SOON, as in, any time now!
Individual workers now supported: -u YOUR_WALLET_ADDRESS.worker_id -p x Worker_id can be any positive integer. Example : -u YOUR_WALLET_ADDRESS.1541 -p x
Pratite nasu glavnu temu : https://bitcointalk.org/index.php?topic=758961
Ja sam mu sinoć postavio isto pitanje na PP i dobio dogovor:Da li može isplata na menjačnicu ili ne?
Mada nije odgovorio na drugi deo pitanja (kolika će biti minimalna isplata pri kopanju direktno na menjačnicu)...Funkcija za isplate direktno na racun menjacnice jos uvek nije dostupna kopacima - kod je 'gotov' i uveliko se testira. Pratite nasu glavnu temu na bitcointalk-u (https://bitcointalk.org/index.php?topic=758961). Funkcija ce biti omogucena u narednih 48h.
Successful attack achieved by including a corrupted block, we're trying to figure out what happened now.
Network is forked. Do not move funds, do not spend, we're likely going to have to apply an emergency patch and roll back to before the corrupted block.
ne šaljite novčiće!
[-]Što se tiče kopanja, možete preći na nešto drugo dok se situacija ne reši jer ko kopa, kopa u prazno[/-]. Navodno su ugrožene sve CN valute.
2014/08/04 Attack: Update 1
Here's what we've ascertained thus far: the "bad block" occurred at 202612. Immediately thereafter there was 202613, which also has oddities, and then at 202614 the network forked. The "A" part of the network has "c29e3dc37d8da3e72e506e31a213a58771b24450144305bcba9e70fa4d6ea6fb" as the block hash on 202614, the "B" part of the network has "ed4eea6109a1b662cf4a3bb372ed4bdee588160b0ac371c2ad78c5e603b8f2ac" as the block hash on 202614. Ultimately the "A" part won, and is the current fork. The "B" part is dead and has not proceeded beyond block 202647.
Thus the good news is that the consensus code works, and only one fork has survived. The bad news is that those on the bad fork are not reorganising back to the fork, and that is something we will need to look at fixing in future - the consensus code is so aggressive that it refuses to believe that the peers on the "good" fork are correct.
To determine if you are on the good or the bad (dead) fork, you can check "diff" in your daemon window. If you are stuck on 202647 or thereabouts, you will need to delete your blockchain and sync from scratch. I strongly suggest using the blockchain bootstrap downloads from the OP, as those are on the correct fork. Please note that the Windows blockchain bootstrap download has not been checked and updated as yet, I will be doing so in the next few hours, so we have rolled back to a Windows blockchain from a few weeks back. The Linux and OS X blockchain bootstraps are fine.
The next step is to determine how, exactly, 202612 & 202613 managed to cause this, which is what we've been doing concurrently and will continue to do. You can use Monero with caution if you are on the main chain, we will continue to update as we proceed.
NB: no funds have been lost, and there will be no blockchain rollback. If you transacted on the dead fork it was only live for about 35 minutes, so chances are little happened of relevance. Once you are on the good fork you can re-sync your wallets and any funds you sent on the dead fork will reappear.
Here's what we've ascertained thus far: the "bad block" occurred at 202612. Immediately thereafter there was 202613, which also has oddities, and then at 202614 the network forked. The "A" part of the network has "c29e3dc37d8da3e72e506e31a213a58771b24450144305bcb a9e70fa4d6ea6fb" as the block hash on 202614, the "B" part of the network has "ed4eea6109a1b662cf4a3bb372ed4bdee588160b0ac371c2a d78c5e603b8f2ac" as the block hash on 202614. Ultimately the "A" part won, and is the current fork. The "B" part is dead and has not proceeded beyond block 202647.
Sad gledam na dwarfu se uopšte ne update-uje statistika?
Mineri kopaju normalno...
I šta sad... kopamo u prazno svi na dwarfu?http://monerochain.info/ se zaglavio na pogresnoj grani fork-a, verovatno se iz istog razloge ne updejtuje. Ta grana je izgubila izbore i sve transakcije na njoj puj-pike-ne-vaze, ali se srecom prekinula i dalje ne raste.
I šta sad... kopamo u prazno svi na dwarfu?
VAZNO OBAVESTENJE!!
Svi MONERO.RS nodovi, eu.monero.rs, usa.monero.rs i asia.monero.rs su updateovani!
Mirrorujemo najnoviji blockchain za LINUX OS na adresi http://monero.rs/blockchain/linux64/blockchain.bin
Po 100ti put, isplata na menjačnicu kada?
Takođe predlog da otvoriš novu temu za tvoj pool, i da odgovaraš na pitanja.
Isplata na menjacnicu - DANAS!
Ukoliko nam moderatori to odobre spremni smo da delegiramo jednu osobu koja bi redovno azurirala temu i odgovarala na pitanja! Moderatori, imamo li dozvolu ?
Ne vidim da je otvorena tema za monero.rs tako da ide pitanje ovde
Daj mi sintaxu tacno sta da ukucam u bat file da zaobidjem Claymora i da imam stats za svakog workera posebno radi pracenja i eto me sa 150k danas kod tebe
Sta me buni,moze li da se stavi NsCpuCNMiner64 -o stratum+tcp://eu.monero.rs:4444 -u YOUR_WALLET_ADDRESS:Claymore.123 -p un1qu3p4sS da obidjem klepanje i da imam stats za minera 123?
Follow along with the video below to see how to install our site as a web app on your home screen.
Napomena: this_feature_currently_requires_accessing_site_using_safari