what did I do by suggesting getmininginfo :-D
sorry guys I wasn't aware of that, I'm almost new to hodlcoin.
Topic: [ANN] Ħ [HODL] 5% Interest. No Staking Req. Term Deposits 10%. Solo Mining. - page 229. (Read 472878 times)
March 06, 2016, 06:56:10 AM
March 06, 2016, 06:43:58 AM
17:41:26

{
"blocks" : 18036,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00150986,
"errors" : "",
"genproclimit" : 8,
"networkhashps" : 42428,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false
}
SLOW ?

{
"blocks" : 18036,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00150986,
"errors" : "",
"genproclimit" : 8,
"networkhashps" : 42428,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false
}
SLOW ?
March 06, 2016, 04:06:25 AM
Finally, the 1989 contest!
https://bitcointalksearch.org/topic/hodl-1989-twitter-contest-68000-hodl-in-prizes-1386329
bumping for sake of all future squirrels, get your bag of nuts. 12 days to go!!!! https://bitcointalksearch.org/topic/hodl-1989-twitter-contest-68000-hodl-in-prizes-1386329
until now 16 participants, getting hot in HOdl California. Some nice tweets to enjoy
https://twitter.com/HOdlcoin/status/705686960006832128
March 06, 2016, 03:28:34 AM
Hope this chart makes the term deposit rates clear -
HODL Early, HODL Long.
ooooo fancy HODL Early, HODL Long.
March 06, 2016, 03:15:45 AM
Hope this chart makes the term deposit rates clear -
HODL Early, HODL Long.
HODL Early, HODL Long.
March 06, 2016, 01:40:51 AM
Friendly reminded Please back up your wallet before upgrading to a new one
March 06, 2016, 01:38:33 AM
I think everyone agrees, we're very lucky to have Fuzz on our nuts.
lol...nohomo
March 06, 2016, 01:22:49 AM
Thanks to Fuzzbawls for his tireless work in putting together the 1.0.0 and making trusted binaries -
https://github.com/HOdlcoin/HOdlcoin/releases/tag/v1.0.0
I'm already seeing an 8% improvement in hashing using the Windows 64 bit version as compared to the previous 32bit release.
Many thanks Fuzz. I think everyone agrees, we're very lucky to have Fuzz on our nuts.
https://github.com/HOdlcoin/HOdlcoin/releases/tag/v1.0.0
I'm already seeing an 8% improvement in hashing using the Windows 64 bit version as compared to the previous 32bit release.
Many thanks Fuzz. I think everyone agrees, we're very lucky to have Fuzz on our nuts.
March 05, 2016, 11:36:16 PM
very strange I just checked the old laptop with the same settings and its at like 40280 ( this was in the mininginfo) better than my desktop? I dont see how that is possible I must have something wrong in my bios. this laptop is like 4 or 5 years old thing is junk. My desktop is maybe year and a half old 4ghz. what do you guys think? debug says 17 hash. I guess I dont know what Im looking at.
AES-NI maybe
March 05, 2016, 10:25:22 PM
Now is good?

{
"blocks" : 17792,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00128231,
"errors" : "",
"genproclimit" : 8,
"networkhashps" : 39830,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true
}
very strange I just checked the old laptop with the same settings and its at like 40280 ( this was in the mininginfo) better than my desktop? I dont see how that is possible I must have something wrong in my bios. this laptop is like 4 or 5 years old thing is junk. My desktop is maybe year and a half old 4ghz. what do you guys think? debug says 17 hash. I guess I dont know what Im looking at.
Think you're both looking at 'networkhashps' which doesn't really tell you anything about your own personal hashing speed. I take it both of you are on windows using the previously released windows binary? In which case the line in 'getmininginfo' that Pallas is referring to is not present, it was added later.
March 05, 2016, 09:19:44 PM
Now is good?

{
"blocks" : 17792,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00128231,
"errors" : "",
"genproclimit" : 8,
"networkhashps" : 39830,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true
}
very strange I just checked the old laptop with the same settings and its at like 40280 ( this was in the mininginfo) better than my desktop? I dont see how that is possible I must have something wrong in my bios. this laptop is like 4 or 5 years old thing is junk. My desktop is maybe year and a half old 4ghz. what do you guys think? debug says 17 hash. I guess I dont know what Im looking at.
Think you're both looking at 'networkhashps' which doesn't really tell you anything about your own personal hashing speed. I take it both of you are on windows using the previously released windows binary? In which case the line in 'getmininginfo' that Pallas is referring to is not present, it was added later.
March 05, 2016, 08:47:28 PM
very strange I just checked the old laptop with the same settings and its at like 40280 ( this was in the mininginfo) better than my desktop? I dont see how that is possible I must have something wrong in my bios. this laptop is like 4 or 5 years old thing is junk. My desktop is maybe year and a half old 4ghz. what do you guys think? debug says 17 hash. I guess I dont know what Im looking at.
March 05, 2016, 07:45:25 PM
Now is good?

{
"blocks" : 17792,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00128231,
"errors" : "",
"genproclimit" : 8,
"networkhashps" : 39830,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true
}
March 05, 2016, 07:36:58 PM
To read the hashrate it's easier to run "getmininginfo" on the console.
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...
mine Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...

{
"blocks" : 17782,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00132322,
"errors" : "",
"genproclimit" : 16,
"networkhashps" : 39292,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true
}
seems to run about the same no mater how many threads 8 or 16 so im run the 16 for now. Im looking for more stuff to turn off in windows now.
Don't you have 8 cores? Hence why setting it to more than that doesn't improve. The total number of threads is also multiplied by the number of gb like in minermemory.
Thanks for taking the time to teach me. I know where to look now to see if its really on and mining I was trying to look the debug window. Im new to POW mine. Yes i have 8 cores to my knowledge.
I got mine like this now

{
"blocks" : 17798,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00123730,
"errors" : "",
"genproclimit" : 8,
"networkhashps" : 39157,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true
}
March 05, 2016, 07:26:37 PM
To read the hashrate it's easier to run "getmininginfo" on the console.
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...
mine Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...

{
"blocks" : 17782,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00132322,
"errors" : "",
"genproclimit" : 16,
"networkhashps" : 39292,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true
}
seems to run about the same no mater how many threads 8 or 16 so im run the 16 for now. Im looking for more stuff to turn off in windows now.
Don't you have 8 cores? Hence why setting it to more than that doesn't improve. The total number of threads is also multiplied by the number of gb like in minermemory.
March 05, 2016, 07:23:20 PM
To read the hashrate it's easier to run "getmininginfo" on the console.
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...

{
"blocks" : 17779,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00153774,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 39853,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false
}
Everything okay os something needs to change ?
If you want to mine, you need to have generate set to true. Use -gen=1 on the command line or edit the conf file.
March 05, 2016, 07:20:55 PM
To read the hashrate it's easier to run "getmininginfo" on the console.
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...
HPS output in getmininginfo was added in after the last windows binaries were distributed
March 05, 2016, 07:17:29 PM
To read the hashrate it's easier to run "getmininginfo" on the console.
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...
mine Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...

{
"blocks" : 17782,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00132322,
"errors" : "",
"genproclimit" : 16,
"networkhashps" : 39292,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true
}
seems to run about the same no mater how many threads 8 or 16 so im run the 16 for now. Im looking for more stuff to turn off in windows now.
March 05, 2016, 07:15:13 PM
Not work for windows server 2008 
"This Application Request the runtime to terminate it an unusual way " HELP !
"This Application Request the runtime to terminate it an unusual way " HELP ! It worked fine on all my windows server 2008 testing.. Where you trying to use more then 2gb of ram?
wallet now I have not had a problem, I install the os into windows server 12.
one more question, is this working?
March 05, 2016, 07:09:02 PM
To read the hashrate it's easier to run "getmininginfo" on the console.
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...
Yours seems to swing a bit too much, maybe some other process eating resources?
Also try running with just 1gb: you loose less hashes when a new block is detected on the network. Until I can publish my patch...

{
"blocks" : 17779,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00153774,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 39853,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false
}
Everything okay os something needs to change ?
Jump to: