|
[2017-03-10 13:46:57] GPU #2: GeForce GTX 1070: 34603008 hashes, 1596.13 kh/s
[2017-03-10 13:46:57] accepted: 19/20 (95.00%), 4255 khash/s (yay!!!)
[2017-03-10 13:47:08] GPU #2: GeForce GTX 1070: 16777216 hashes, 1595.91 kh/s
[2017-03-10 13:47:08] accepted: 20/21 (95.24%), 4255 khash/s (yay!!!)
[2017-03-10 13:47:12] GPU #1: GeForce GTX 1070: 57671680 hashes, 1595.77 kh/s
[2017-03-10 13:47:12] accepted: 21/22 (95.45%), 4782 khash/s (yay!!!)
[2017-03-10 13:47:16] GPU #1: GeForce GTX 1070: 6291456 hashes, 1596.09 kh/s
[2017-03-10 13:47:16] accepted: 22/23 (95.65%), 4783 khash/s (yay!!!)
[2017-03-10 13:47:31] GPU #2: GeForce GTX 1070: 36700160 hashes, 1595.99 kh/s
[2017-03-10 13:47:31] accepted: 23/24 (95.83%), 4783 khash/s (yay!!!)
[2017-03-10 13:47:37] GPU #0: GeForce GTX 1070: 95420417 hashes, 1592.41 kh/s
TDP 100W.
slight code modification.
|
|
|
|
Is XCN listed on poloniex guys?
It is, but trading is suspended. We will provide them a fixed wallet and, hopefully, they will re-enable it. |
|
|
|
Yesterday I made a withdrawal of some coins from Poloniex, it's a shame that they have removed XCN from the trade
Do you think there is any possibility that they will re-include XCN in their trade?
I will try to convince them when the fixed wallet is ready. I already have a modified wallet that can sync from scratch flawlessly, I will test it further to be sure there are no issues, then we will release it :-) |
|
|
|
euhhh sure, but which one ? :p ive all the ones on yiimp  here are some : BOAT BFpW7pXravMzXggsgYWWnTwWkhFjL5eQQ9
I just sent you all my doubloons there, ma captn! :-) |
|
|
|
|
Tanguy, have you got an altcoin donation address? To send you a BTC beer, I need to pay 15% fee :-(
|
|
|
|
Daily volume 15 BTC :-)
Ready to skyrocket, when the fix is done? ;-)
Where can i buy Cryptonite sir??? Thank you  On bter and on BTC38, but the latter currently has disabled deposits and withdrawals, because they can't start their wallet. |
|
|
|
Just as a FYI, the BBR kernels that are available are so old that 970s are faster then 1070s. They haven't even been updated for Pascal. Please for the love of god someone fix the miner and update it.
there is something weird about 1070 memory accesses, I've seen that on the m7 miner as well. and bbr is all random memory access. And because your XCN miner is so awesome, you figured out a way of dealing with it, right? XD Unfortunately, not. I just reduced the number of read and writes to the memory. I couldn't find another way. |
|
|
|
|
Daily volume 15 BTC :-)
Ready to skyrocket, when the fix is done? ;-)
|
|
|
|
Just as a FYI, the BBR kernels that are available are so old that 970s are faster then 1070s. They haven't even been updated for Pascal. Please for the love of god someone fix the miner and update it.
there is something weird about 1070 memory accesses, I've seen that on the m7 miner as well. and bbr is all random memory access. |
|
|
|
|
Great release Tpruvot! Thumbs up for your work which is keeping nvidia mining afloat :-)
|
|
|
|
|
We will provide a new windows wallet binary when the sync bug is fixed.
|
|
|
|
|
Updated node list (to be put into your cryptonite.conf file):
addnode=106.186.126.57
addnode=118.174.153.195
addnode=137.189.91.64
addnode=137.189.91.71
addnode=158.69.27.82
addnode=178.26.208.109
addnode=180.253.248.218
addnode=182.71.181.102
addnode=188.252.239.235
addnode=193.106.171.8
addnode=24.246.60.145
addnode=46.105.118.15
addnode=68.193.116.54
addnode=77.111.163.71
addnode=77.233.244.74
addnode=82.116.52.170
addnode=85.14.250.2
addnode=86.127.154.22
addnode=89.99.27.94
addnode=91.152.122.132
addnode=92.52.46.192
addnode=93.33.170.142
addnode=96.127.136.18
|
|
|
|
I'd also like to describe my Win Wallet behavior. After it stopped crashing a couple of months ago, it's been working pretty flawlessly apart from some minor issues:
1. The wallet regularly micro-freezes for a few seconds.
I've seen that on the headless client on linux as well. 2. When I open it to sync, the wallet can not establish a stable connection with peers, meaning that it looses connection to them every 20-30 sec (shows 0 connections). Once the wallet is synced, it has a stable 5-8 connected peers (once I've even seen 10 peers ) If you open your ports for incoming connections, you will get more that 30 :-) Sending-receiving works fine.
Well, that is the important thing ;-) Besides, we are now 3 devs working on the fix, will keep you all posted, on this thread! |
|
|
|
Meanwhile, the 24-volume of coin trading ESP/LTC on the novaexch is very small. And the rate has not changed for the better. Very sadly ...
Don't worry, you should buy now not if the chain is forked. you should never buy a coin with forks in its chain. there is no way of guaranteeing that you are buying coins on the right chain You can check the block height on nova to see if it matches your wallet and/or the block explorer. It always did. |
|
|
|
My wallet corrupted again. Bit it's not wallet.dat itself but the content of trie.dat now being empty so I just had to use an older backup of it. Assertion failed!
Program: cryptonite-qt.exe
File: trieview.cpp, Line 30
Expression: fread(buf,sz,1,filein)>0 Interesting: trie.dat is part of the blockchain, not of the wallet. So you replaced that file and it's working fine again? If that is the issue, we could trigger trie download when such a situation is detected. |
|
|
|
Hi
i got a request
I want to mine quark on my GPU. i have Geforce 840M...download link here doesnt work...please can somebody help me with downlod a miner and set it to my pool?
thank you so much
1 - don't use this software, it's old and there are much better sgminer versions around. 2 - don't mine quark with your gpu, there are ASICs for that. |
|
|
|
cheers , if this one syncing now doesn't work , will do ^^ . upon further inspection of this situation of mine , i do conclude that i did in fact fork off from the main chain at some point . i could provide a few screenshots of my scrambled transactions in the wallet if it helps , it appears every transaction after 3 blocks i mined solo (payouts from suprnova) was there in the transaction list but the dates were in the wrong order lol and they were not confirmed . The wierdest thing about this whole thing is that i had my wallet open this morning like 6 hours ago , it was synced and everything seemed to be fine ...... for some reason the wallet auto closed itself (it was there open and then it wasnt) ... i was like huh wtf wierd and didnt think much of it , but yeah sincethat moment BAM when i reopen wallet it did this 3 days headers behind thing . im at 4090 blocks behind now on this resync fingers crossed .
ps. If i did fork from main chain , how the hell does that happen im only mining with 24 megahash .
cheers .
You may fork with just one block, but it should reorganize itself automatically, unless you have problems syncing. Let me know how it goes. |
|
|
|
thanks heaps , it rly was a wierd thing , i tried a few diff blockchain snapshots i backed up myself and BOTH of em would basically sync backwards and end up at 3 days behind on headers (both snapshots were more recent than 3 days tho!) . ive now tried a backup from the 2nd this month (one from longer than 3 days ago) and it seems to be syncing from about 5500 blocks behind now , what i did notice tho is that transactions in my transaction list had weird dates that wernt even in the right order when id sort it by date (everything past a point was not verified by a green tick but was just a blue block in that section that would have the green tick . I think i may have possibly forked on my solo mining attempt the last few days? , it seemed to be working fine and i had been switching from solo to pool....and all working good.... i mined in pool overnight and opened wallet this morning tho and it was broken like this .... i could see my most recent transaction showing was from 6am this morning , but it said 3 days behind on headers . true wigout this one , totally new issue . ill let you know if it finishes its sync successfully or if it wigs again . I have a feeling theres a chasnce it will cause the last snapshot i tried seemed to be syncing at bout 3000 blocks to go then i looked at it 2 mins later and it say 3 days behind on headers lol , ahhhhhh ><
You may also try the new snapshot I just posted. Please keep reporting your findings: we are working on fixing the sync bug and every piece of information may be useful. |
|
|
|
about the hash: looks suspicious, I will look thru it, time permitting :-)
please share the block height and hash.
the error in debug.log while syncing: 2017-03-06 06:50:24 UpdateTip: new best=000000017ec0449e4ebc1e2bc7d0cc5836490048169d4ab01801dd7d5dc7ebdc height=160 log2_work=35.256255 tx=161 date=2014-07-28 01:24:2 0 progress=1.000000
2017-03-06 06:50:24 Cannot fastforward chain because of missing data: 000000044c4e5c82cf3c93a3019f09ecd9005a30f5eeba2ff6952b349c7324ae
Cannot fastforward chain because of missing data: 000000044c4e5c82cf3c93a3019f09ecd9005a30f5eeba2ff6952b349c7324ae 2
2017-03-06 06:50:24 Activate 000000017ec0449e4ebc1e2bc7d0cc5836490048169d4ab01801dd7d5dc7ebdc however putting a fully sync'd chain into place, running 'getblockhash 161', we get: 000000044c4e5c82cf3c93a3019f09ecd9005a30f5eeba2ff6952b349c7324ae james "Cannot fastforward chain because of missing data" means it can't find block data, which is normal for such an old block. Miniblockchain should go ahead and keep the header only. There must be something else. |
|
|
|
|
Show Posts
