I have a version of the old wallet running on an old laptop ... this gives the current network hashrate accurately.
Current Network Hash Rate: 1055 MH/s
Lets get it up to 2000 ... starting in 15 mins?
Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1278. (Read 3058816 times)
August 27, 2014, 02:33:03 PM
I have a version of the old wallet running on an old laptop ... this gives the current network hashrate accurately.
Current Network Hash Rate: 1055 MH/s
Lets get it up to 2000 ... starting in 15 mins?
August 27, 2014, 01:53:58 PM
I have a version of the old wallet running on an old laptop ... this gives the current network hashrate accurately.
Current Network Hash Rate: 1055 MH/s
Lets get it up to 2000 ... starting in 15 mins?
August 27, 2014, 12:00:35 PM
I just want to know what is the total DGB network hashrate now. Before the update, it was available with the command 'getmininginfo' but since the last update, it is always 0. And when multi algo will be available, I would like to know the total DGB network hashrate for each algo.
Multipool.US has a graph of difficulty and network hashrate.
The Network Hashrate is labelled wrong though - I think it's actually GHash/s instead of MHash/s
https://www.multipool.us/my_stats.php?curr=dgb
August 27, 2014, 11:34:36 AM
Throwing some hash your way, its not much but I am in until the block hits! 
I have more GPU's than Asics so once the magic block hits, Ill be all in.
I have more GPU's than Asics so once the magic block hits, Ill be all in. August 27, 2014, 04:42:45 AM
I just want to know what is the total DGB network hashrate now. Before the update, it was available with the command 'getmininginfo' but since the last update, it is always 0. And when multi algo will be available, I would like to know the total DGB network hashrate for each algo.
Oh right, I did misunderstand. Not sure right now....
August 27, 2014, 04:28:28 AM
As some people ask, how can we now get the scrypt hashrate ? I think it is really important to coordinate efforts.
https://www.nicehash.com/index.jsp
https://www.westhash.com/index.jsp
I mean the scrypt hashrate of DGB.
Thats what he means... for approx. 0.4 btc per GH/day you can rent Scrypt hash from NiceHash/Westhash... and point it at wherever you want...
But this is not the DGB network hashrate, I think.
It's generic Scrypt hashrate available for whatever you want. When you rent it and point it at a DGB pool it becomes DGB network hashrate....
Perhaps I am misunderstanding your question?
I just want to know what is the total DGB network hashrate now. Before the update, it was available with the command 'getmininginfo' but since the last update, it is always 0. And when multi algo will be available, I would like to know the total DGB network hashrate for each algo.
August 27, 2014, 04:15:03 AM
As some people ask, how can we now get the scrypt hashrate ? I think it is really important to coordinate efforts.
https://www.nicehash.com/index.jsp
https://www.westhash.com/index.jsp
I mean the scrypt hashrate of DGB.
Thats what he means... for approx. 0.4 btc per GH/day you can rent Scrypt hash from NiceHash/Westhash... and point it at wherever you want...
But this is not the DGB network hashrate, I think.
It's generic Scrypt hashrate available for whatever you want. When you rent it and point it at a DGB pool it becomes DGB network hashrate....
Perhaps I am misunderstanding your question?
August 27, 2014, 04:11:04 AM
As some people ask, how can we now get the scrypt hashrate ? I think it is really important to coordinate efforts.
https://www.nicehash.com/index.jsp
https://www.westhash.com/index.jsp
I mean the scrypt hashrate of DGB.
Thats what he means... for approx. 0.4 btc per GH/day you can rent Scrypt hash from NiceHash/Westhash... and point it at wherever you want...
But this is not the DGB network hashrate, I think.
August 27, 2014, 04:04:01 AM
I mean the scrypt hashrate of DGB.
Go to this pool and check static: http://p2pool.e-pool.net:8922/static/
Now is
Quote
Global Pool Hashrate: 91.45 MH/s (Rejected 2.23 MH/s / 2.44%)
That's the global DGB P2Pool hashrate, not the total DGB network hashrate.
August 27, 2014, 04:01:16 AM
I mean the scrypt hashrate of DGB.
Go to this pool and check static: http://p2pool.e-pool.net:8922/static/
Now is
Quote
Global Pool Hashrate: 91.45 MH/s (Rejected 2.23 MH/s / 2.44%)
August 27, 2014, 04:00:57 AM
As some people ask, how can we now get the scrypt hashrate ? I think it is really important to coordinate efforts.
https://www.nicehash.com/index.jsp
https://www.westhash.com/index.jsp
I mean the scrypt hashrate of DGB.
Thats what he means... for approx. 0.4 btc per GH/day you can rent Scrypt hash from NiceHash/Westhash... and point it at wherever you want...
August 27, 2014, 03:57:22 AM
As some people ask, how can we now get the scrypt hashrate ? I think it is really important to coordinate efforts.
https://www.nicehash.com/index.jsp
https://www.westhash.com/index.jsp
I mean the scrypt hashrate of DGB.
August 27, 2014, 03:37:16 AM
As some people ask, how can we now get the scrypt hashrate ? I think it is really important to coordinate efforts.
https://www.nicehash.com/index.jsp
https://www.westhash.com/index.jsp
August 27, 2014, 03:20:17 AM
As some people ask, how can we now get the scrypt hashrate ? I think it is really important to coordinate efforts.
August 27, 2014, 02:45:55 AM
Nice to see difficulty has dropped again from 1300+ back down to 316. But still too high for the current block discovery rate... but hopefully we can get things coordinated for this evening. 6PM UTC... for us in the EU we're on summer time now so it's actually 7PM GMT and 8PM for Western Europe.
Hopefully we'll get some help from Josh @ Gawminers.
Hopefully we'll get some help from Josh @ Gawminers.
August 26, 2014, 08:18:49 PM
Quote
The 3.0.1b wallet only included language translation updates. No changes were made other than that. If your an English speaker you wont notice a difference. When we ported the code we had some pretty wild foreign translations for the word "DigiByte." Smiley
So far so good. Wallet updated with the older wallet.data file perfectly. I have shut it down and opened it 5 times. Synced up quickly
August 26, 2014, 07:03:15 PM
I am running the v3.0.1.0-g354c0f3-MultiAlgo (64-bit) which I downloaded from the main site. I tried deleting the "blockchain" & "chainstate" folders. Even with a fresh install (all traces of the digibtye data removed) it still will hang with the v3.0.1.0-g354c0f3-MultiAlgo (64-bit) version. I had no issue prior to this version wallet. If that helps any
I think what I will do for now since I currently only have one ATI 7850 (tiny 345Kh/s) is wait for block 145,000. Then I can add 38Gh/s with my USB miners.
I think what I will do for now since I currently only have one ATI 7850 (tiny 345Kh/s) is wait for block 145,000. Then I can add 38Gh/s with my USB miners.
Interesting. Can you provide a screenshot & debug.log info? We have 5 Windows 7 x64 bit machines running 3.0.1 in the office & at home with no issues.
It started reindexing again =/
EDIT- shut it down and brought it back up and now it's at the 5 hour behind mark again. I tried adding the debug info and the forum won't allow me to post it. Is there a specific part you need to look at?
Edit 2- I think I found the issue... maybe. I went to the main and downloaded the wallet for Windows 64bit. I noticed the file name was different than the version I had before. I may have install a previous wallet version. I installed the current wallet from the site. Hopefully this works.
August 26, 2014, 06:55:00 PM
I am running the v3.0.1.0-g354c0f3-MultiAlgo (64-bit) which I downloaded from the main site. I tried deleting the "blockchain" & "chainstate" folders. Even with a fresh install (all traces of the digibtye data removed) it still will hang with the v3.0.1.0-g354c0f3-MultiAlgo (64-bit) version. I had no issue prior to this version wallet. If that helps any
I think what I will do for now since I currently only have one ATI 7850 (tiny 345Kh/s) is wait for block 145,000. Then I can add 38Gh/s with my USB miners.
I think what I will do for now since I currently only have one ATI 7850 (tiny 345Kh/s) is wait for block 145,000. Then I can add 38Gh/s with my USB miners.
Interesting. Can you provide a screenshot & debug.log info? We have 5 Windows 7 x64 bit machines running 3.0.1 in the office & at home with no issues.
This sounds as if it is just the slow block issue ... ie because a block has not been found for 4+ hours the wallet shows out of sync (even though it is up to date) because it has taken so long. If you hover over the information and look at the latest block received and it matches the last one shown in a block explorer all should be good.
I imagine this will not be a problem once we get to block 145,000 and we hopefully return to a block a minute average.
I'm hoping that's the issue or I just screwed something up myself rather than it be a wallet issue.
August 26, 2014, 06:40:14 PM
@Digibyte
Thanks, that makes much more sense now.
Bit of a long shot, but I will drop josh a line and see if he is feeling generous ... failing that I think we should go with a coordinated push, do you have an idea for a start time/date so everyone can get involved?
Thanks, that makes much more sense now.
Bit of a long shot, but I will drop josh a line and see if he is feeling generous ... failing that I think we should go with a coordinated push, do you have an idea for a start time/date so everyone can get involved?
How does 6 PM UTC time sound tomorrow? Thats 2 PM Eastern, 11 AM Pacific?
Checking into the hash reporting issue with 3.0.1. According to the digi.morecoins pool (2.9.1 wallet) we are currently at 1121 MH net hash. http://digi.morecoins.org/index.php?page=dashboard
We had an issue with the 3.0.0 wallet where it would crash when you ran "getinfo" or "getmininginfo." This may be related.
That is good for me, I will start adding hash shortly after 6pm UTC
August 26, 2014, 06:38:21 PM
I am running the v3.0.1.0-g354c0f3-MultiAlgo (64-bit) which I downloaded from the main site. I tried deleting the "blockchain" & "chainstate" folders. Even with a fresh install (all traces of the digibtye data removed) it still will hang with the v3.0.1.0-g354c0f3-MultiAlgo (64-bit) version. I had no issue prior to this version wallet. If that helps any
I think what I will do for now since I currently only have one ATI 7850 (tiny 345Kh/s) is wait for block 145,000. Then I can add 38Gh/s with my USB miners.
I think what I will do for now since I currently only have one ATI 7850 (tiny 345Kh/s) is wait for block 145,000. Then I can add 38Gh/s with my USB miners.
Interesting. Can you provide a screenshot & debug.log info? We have 5 Windows 7 x64 bit machines running 3.0.1 in the office & at home with no issues.
This sounds as if it is just the slow block issue ... ie because a block has not been found for 4+ hours the wallet shows out of sync (even though it is up to date) because it has taken so long. If you hover over the information and look at the latest block received and it matches the last one shown in a block explorer all should be good.
I imagine this will not be a problem once we get to block 145,000 and we hopefully return to a block a minute average.
Jump to: