Feinbild-detection-alert.  Rechte, Linke, Reichsbürger, Michel, Aluhutträger, Christen, Islamisten, Renter, Arbeiter, Intellektuelle, Arbeitslose, Frauen, Männer, BTC, Alts, Classic, Core... Die Propaganda des Establishments schafft es immer wieder mit FUD Feinbilder zu installieren und ab geht die Party.  Ja, diese Welt ist schon lange nicht mehr bunt. Aber zwischen Schwarz und Weiß gibt's noch Graustufen. Chillt ein wenig und tanzt mal wieder. Happy Hanukkah! |
|
|
|
Wollte gerade ein paar BTC von Kraken holen und bekomme folgende Meldung:
wollte heute auch meinen BTC von Kraken holen und sehe nun dass es ein Maximum withdrawal von 0,xx BTC gibt obwohl Daily limit und Monthly limit jeweils auf max, da noch nie etwas geholt wurde. Warum kann ich nicht meinen BTC senden?   bzw. wie? thx Evtl. ist es nur eine offene Order. Diese ggf. canceln und das max. withdrawal erneut überprüfen. |
|
|
|
Do you got PoS block in new version?
No, I do not have that much GPL. Will run the wallet again tomorrow and report back in case a PoS block will be mined.  Not sure if it's still interesting, but got a PoS block now with the new version.  Transaction is: a4d6218a5408ca05d65c8250131f12966ecdf9ea5b3713042b6f424074fe6cee |
|
|
|
v5.0 is showing ~ 80 H/s for my card (R7 370) but the pool an average of 55-60 during the last 4h or so. The rejection rate is low (< one per thousand shares). Any idea what might cause the diversity displayed? I've not noticed any differences with v4.0.
I guess a 50% boost displayed by the pool is more realistic than 100% displayed within the miner (have had ~ 40 H/s with v4.0)?
I'm getting about 65H/s with my R7 370 2GB. My settings in Afterburner are 1125 / 1500 with -15% for power limit. Lowering the clocks below 1100 seems to impact performance pretty significantly. Lowering the power limit more made things a bit unstable. It's been running for days with these settings no problem. Every new release, I just stop, reboot (seems to like a reboot for some reason), run the new version, and performance increases. Are yours 4GB? What settings are you using to get 80? Well then, looks like I have a display glitch inside v5.0  I did no really tweak much, 1040/1425, power limit not changed. 2GB card with 15.12 driver on Win 10 64-bit. Your 65 H/s seems to match my displayed 55-60 from the pool, considering your higher clocks. Thanks for sharing your settings and hashrate! Interesting - The only difference I see is that my drivers are 16.9 instead of 15.12. I thought v5 officially made ver 16 drivers cool, but I may have to give it a try when I have time to take down my system. Thanks for the info! Just an update... With v6.0 miner and pool showing the same numbers again, ~ 75 H/s. Glitch gone. |
|
|
|
v5.0 is showing ~ 80 H/s for my card (R7 370) but the pool an average of 55-60 during the last 4h or so. The rejection rate is low (< one per thousand shares). Any idea what might cause the diversity displayed? I've not noticed any differences with v4.0.
I guess a 50% boost displayed by the pool is more realistic than 100% displayed within the miner (have had ~ 40 H/s with v4.0)?
I'm getting about 65H/s with my R7 370 2GB. My settings in Afterburner are 1125 / 1500 with -15% for power limit. Lowering the clocks below 1100 seems to impact performance pretty significantly. Lowering the power limit more made things a bit unstable. It's been running for days with these settings no problem. Every new release, I just stop, reboot (seems to like a reboot for some reason), run the new version, and performance increases. Are yours 4GB? What settings are you using to get 80? Well then, looks like I have a display glitch inside v5.0 I did no really tweak much, 1040/1425, power limit not changed. 2GB card with 15.12 driver on Win 10 64-bit. Your 65 H/s seems to match my displayed 55-60 from the pool, considering your higher clocks. Thanks for sharing your settings and hashrate! |
|
|
|
Hello. I'm getting this: I1115 00:33:24.237930 4344 downloader.go:267] Synchronisation failed: block time is in the future: BlockFutureErr, 1479166467 > 1479166434
I1115 00:33:42.014012 4344 fetcher.go:771] Peer 77b71660f5cb025e: block #1449416 [ffafbbea…] import failed: block time is in the future: BlockFutureErr, 1479166467 > 1479166452
I1115 00:33:42.745260 4344 downloader.go:267] Synchronisation failed: block time is in the future: BlockFutureErr, 1479166467 > 1479166452
I1115 00:33:44.157848 4344 downloader.go:267] Synchronisation failed: block time is in the future: BlockFutureErr, 1479166467 > 1479166454
I1115 00:33:54.008448 4344 downloader.go:267] Synchronisation failed: block time is in the future: BlockFutureErr, 1479166467 > 1479166464 Blocks from the future! My time is synced via time.nist.gov... Any ideas how to receive current/past blocks? Never mind, my system clock is slow. Guess I need a new CMOS battery. |
|
|
|
|
v5.0 is showing ~ 80 H/s for my card (R7 370) but the pool an average of 55-60 during the last 4h or so. The rejection rate is low (< one per thousand shares). Any idea what might cause the diversity displayed? I've not noticed any differences with v4.0.
I guess a 50% boost displayed by the pool is more realistic than 100% displayed within the miner (have had ~ 40 H/s with v4.0)?
|
|
|
|
can some one with 7850 or rx 460 or r7 370 post results with claymore latest build please ? did they got also increase in hr or still stuck at 30 -38 h/s ?
I'll post on Friday I'm getting R7 370 4GB, most likely Hynix of Elpida memory R7 370 with 2GB, 1040/1425 -> 37 - 40 H/s using v3.1 with -i 0. -i 1 does not help and -i 2 crashed. |
|
|
|
Not sure if this was reported before... Looks like the miner will not switch to a failover pool specified in epools.txt if he can connect to the main pool and there is a timeout: 17:37:28:253 920 ZEC: 4 pools are specified
17:37:28:256 920 Main ZCash pool is equihash.eu.nicehash.com:3357
...
17:37:38:550 2390 ZEC: Stratum - connecting to 'equihash.eu.nicehash.com' <5.153.50.217> port 3357
17:37:38:606 2390 send: {"id": 1, "method": "mining.subscribe", "params": ["equihashminer", null, "equihash.eu.nicehash.com", "3357"]}
17:37:38:607 2390 send: {"id": 2, "method": "mining.authorize", "params": ["xxx","z"]}
17:37:38:608 2390 send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
17:37:38:608 2390 ZEC: Stratum - Connected (equihash.eu.nicehash.com:3357)
17:37:41:806 2390 checkread timeout
...
17:38:07:440 2390 checkread timeout
17:38:08:853 920 GPU0 t=52C fan=20%
17:38:08:856 920 em hbt: 30422, fm hbt: 62,
17:38:08:857 920 watchdog - thread 0, hb time 110
17:38:08:857 920 watchdog - thread 1, hb time 94
17:38:10:637 2390 checkread timeout
17:38:10:638 2390 ZEC: Job timeout, disconnect, retry in 20 sec...
17:38:30:642 2390 ZEC: Stratum - connecting to 'equihash.eu.nicehash.com' <5.153.50.217> port 3357
17:38:30:746 2390 send: {"id": 1, "method": "mining.subscribe", "params": ["equihashminer", null, "equihash.eu.nicehash.com", "3357"]}
17:38:30:747 2390 send: {"id": 2, "method": "mining.authorize", "params": ["xxx","z"]}
17:38:30:747 2390 send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
17:38:30:748 2390 ZEC: Stratum - Connected (equihash.eu.nicehash.com:3357)
17:38:33:953 2390 checkread timeout
17:38:37:153 2390 checkread timeout
17:38:39:174 920 GPU0 t=52C fan=20%
17:38:39:177 920 em hbt: 8531, fm hbt: 31,
17:38:39:178 920 watchdog - thread 0, hb time 78
17:38:39:178 920 watchdog - thread 1, hb time 78
17:38:40:347 2390 checkread timeout
...
17:39:02:783 2390 checkread timeout
17:39:02:784 2390 ZEC: Job timeout, disconnect, retry in 20 sec... |
|
|
|
[OT] kann ich da die privatkeys rausholen und sie in die version 0,13.1 importieren?
und wenn ja
wie bekomm ich die privatkeys ? was muss ich da machen ?
Klar, das geht. Vor den folgenden Schritten bitte alle Keylogger und Viren deinstallieren, den Standrechner vom Internetz trennen usw... Öffne die Konsole der alten Wallet: Hilfe -> Debugfenster -> Konsole Dort kannst Du Dir mit alle Adressen der Wallet anzeigen lassen, welche jemals eine Transaktion empfangen haben. Erstelle eine Liste der Adressen (z.B. Copy & Paste in's Notepad). Mit bekommst Du den Private Key zur jeweiligen Adresse ausgegeben. Erstelle eine Liste der Private Keys. Solltest Du die Fehlermeldung "Error: Please enter the wallet passphrase with walletpassphrase first." erhalten, ist die Wallet verschlüsselt. Entsperre sie mit walletpassphrase PASSWORT 667667 Sind alle Private Keys in Deiner Liste, kannst Du sie in der neuen Wallet importieren. Auch hier die Konsole öffnen und Deine Private Keys einzeln importieren via: Sollte Du nach dem Import aller Private Keys einige BTC in der neuen Wallet vermissen... führe den Rescan durch: Erstelle eine Verknüpfung zur neuen Wallet auf Deinem Desktop. Rechtsklick, die Eigenschaften öffnen sich. Unter "Ziel" steht z.B. "C:\Program Files\Bitcoin\bitcoin-qt.exe" ersetze dies durch "C:\Program Files\Bitcoin\bitcoin-qt.exe" -rescan bestätige mit "Übernehmen", "OK". Einen Doppelklick auf die Verknüpfung und einige Kaffee später sollte die neue Wallet Deine BTC wieder anzeigen und für den Versand bereithalten. [/OT] Ob wir die sechste Woche im Wochenchart grün schließen werden, was meint ihr? |
|
|
|
...
Das passt schon zur Theorie das die Banken sich gerade den BTC aufteilen, für die Zukunft, das denke ich wirklich!
 verdammt scheiße 1 Jahr um ...und? glaubste das immernoch? Urbane Mythen sterben augenscheinlich nie. |
|
|
|
Ok, I guessed it will update with a new block but was noch watching the wallet actively. Thank you for the info! No, I do not have that much GPL. Will run the wallet again tomorrow and report back in case a PoS block will be mined. |
|
|
|
You are fast. Just three little findings: 1) My wallet is locked. When I unlocked the wallet and enabled '-staking' as command line option or 'staking=1' in the *.conf file, the little staking information thingy will not switch instantly to green. Staking starts (I guess, because the CPU load increases), but the symbol takes some time to change it's color. Nothing major, just an observation. 2) The 'staking' command does not work via API/RPC console, got an error message: Method not found (code -32601).  3) Might be a good idea to update OpenSSL. Other than that, seems to work. |
|
|
|
Sounds perfect. |
|
|
|
Would be nice to have the switch as well via API and/or *.conf-file - for the Linux-folks. |
|
|
|
And QBT got a new rating. 3.5 of 5 stars, yay! |
|
|
|
Presstab explorer cost 7$ per month and 30$ setup. Minimum 6 month. But now I try make explorer here: http://cryptoguru.tk/ - 0.1BTC per month and no setup fee. Are you sure it's .1 BTC not.01 BTC otherwise the first one seems a much better deal. Sorry, 0.01 BTCcryptoguru.tk sounds like a plan. I will load up two months Premium as soon as QBT is listed. edit: UPD: User with IP 65.50.96.63 and others, use new empty wallet before fully synch. You start minting before synch and overload net.
Current block 495320
I was just wondering who's jamming my upload and Wireshark showed this IP. Just 50k blocks to go, 65.x.x.63 - you will make it!  |
|
|
|
@EpyxZ Nice, slick explorer. Browsing PoW blocks is working fine, but got some errors with PoS blocks.  @vampirus Do you know what the presstab.pw explorer would cost? |
|
|
|
|
Show Posts
