third tab over. control
type
getinfo
Topic: [ANNOUNCE] New alternate cryptocurrency - Geist Geld - page 23. (Read 74190 times)
I'm not sure how to get info like block# and connections other than looking at ggID. So here's a screenshot.
I swear, I always overlook something so obvious. Sorry for the n00b questions.
Orphans should show up in listtransactions, IIRC.
are you sure you have ntp=1, Sekioh ?
are you sure you have ntp=1, Sekioh ?
On the 'real' chain as count states above, got 12 hashes (last at 3:16pmEST, 2 min ago) over the last 8hrs, and 0 balance, 0 account transactions. I'm assuming they're all orphaned and somethings still up.
This line keeps coming up in geistd
ProcessBlock: ORPHAN BLOCK, prev=0000000066bd76b9e7c9
Something wrong here?
ProcessBlock: ORPHAN BLOCK, prev=0000000066bd76b9e7c9
Something wrong here?
Not necessarily. What is your current block per getinfo ?
Did you get my coins ?
Getinfo blocks 1635
I added the ntp=1 flag and now the orphans are gone. Everything back to normal.
I received the coins! 400 confirmations. Thank you very much!
block count would easily shed some light on this:
60k+ = you're on the old GG chain without enablefullretargetperiod
~350 = you're on the old GG chain with enablefullretargetperiod
~240 = you're on the new GG chain without enablefullretargetperiod
~1650 = you're on the new GG chain with enablefullretargetperiod
last one is the "real" chain.
60k+ = you're on the old GG chain without enablefullretargetperiod
~350 = you're on the old GG chain with enablefullretargetperiod
~240 = you're on the new GG chain without enablefullretargetperiod
~1650 = you're on the new GG chain with enablefullretargetperiod
last one is the "real" chain.
So it's agreed if I'm getting 0/0 shares it's something wrong on my end.... I'm just not sure what it is. At this point I wanna get it to work just so it doesn't beat me.
Grrr shoulda went to school for tech.
Grrr shoulda went to school for tech.
I've always felt that there's no reason to have a limit when adjusting downwards. If the current hashing rate is less than the required to adjust exactly by /4 then you'll need 2 long retargets to get back to normal speed, but if it can adjust freely then only 1 is needed. Namecoin is currently on this predicament. The next adjustment will be by /4 to 23,500 but the "instant" difficulty (average of the last 120 blocks) is 7,000 so after this very long adjustment cycle there will be yet another long cycle, if the current hash rate remains constant.
Er!!! the downward side clamp is essential for security.
E.g. say the difficulty is a zillion and I want to mine a fantasy fork in order to trick clients that I've isolated into accepting txn that will never be confirmed on the main network. I wait until near the end of a cycle at current difficulty pushing the timetamps into the future, ... when the adjustment happens on my fork if there is no limit the new difficulty it ends up pretty low and I can then maintain that fork in realtime for as long as I like.
With the limit it would require me mining tens of thousands of blocks at high difficulty to produce a valid chain at a difficulty I could maintain.
This line keeps coming up in geistd
ProcessBlock: ORPHAN BLOCK, prev=0000000066bd76b9e7c9
Something wrong here?
ProcessBlock: ORPHAN BLOCK, prev=0000000066bd76b9e7c9
Something wrong here?
Not necessarily. What is your current block per getinfo ?
Did you get my coins ?
I *think* this might be some people running without enablefullretargetperiod=1, but I'm far from certain on that.
Got a new card, now I'm at ~400 mh/s
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Did you do the NTP thing above ? How many connections ? I've fired up a ghettobox with 250 mhashes some time ago (to test Cosbycoin's complaints of "orphan storm") and it gets an occasional block, though only one so far (GUIminer w poc on Wx64)
Well that would be my problem. The ntp setting wasn't in the config. Thanks.
Oky, sorry for missing it on first go.
P.S.:
This also nicely confirms that we did, indeed, succeed at evicting timetravellers, lol
lol back to the future!
This line keeps coming up in geistd
ProcessBlock: ORPHAN BLOCK, prev=0000000066bd76b9e7c9
Something wrong here?
ProcessBlock: ORPHAN BLOCK, prev=0000000066bd76b9e7c9
Something wrong here?
Got a new card, now I'm at ~400 mh/s
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Did you do the NTP thing above ? How many connections ? I've fired up a ghettobox with 250 mhashes some time ago (to test Cosbycoin's complaints of "orphan storm") and it gets an occasional block, though only one so far (GUIminer w poc on Wx64)
Well that would be my problem. The ntp setting wasn't in the config. Thanks.
Oky, sorry for missing it on first go.
P.S.:
This also nicely confirms that we did, indeed, succeed at evicting timetravellers, lol
The block generation rate appears much more stable. Good work lolcust!
Got a new card, now I'm at ~400 mh/s
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Did you do the NTP thing above ? How many connections ? I've fired up a ghettobox with 250 mhashes some time ago (to test Cosbycoin's complaints of "orphan storm") and it gets an occasional block, though only one so far (GUIminer w poc on Wx64)
Well that would be my problem. The ntp setting wasn't in the config. Thanks.
Oky, sorry for missing it on first go.
P.S.:
This also nicely confirms that we did, indeed, succeed at evicting timetravellers, lol
Got a new card, now I'm at ~400 mh/s
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Did you do the NTP thing above ? How many connections ? I've fired up a ghettobox with 250 mhashes some time ago (to test Cosbycoin's complaints of "orphan storm") and it gets an occasional block, though only one so far (GUIminer w poc on Wx64)
Well that would be my problem. The ntp setting wasn't in the config. Thanks.
NTP Thingy - Done
Number of connections - no idea. A lot of this stuff is over my head. However, I'm good at screenshots, so I'll post this:
http://i.imgur.com/aPfc6.png
Number of connections - no idea. A lot of this stuff is over my head. However, I'm good at screenshots, so I'll post this:
http://i.imgur.com/aPfc6.png
Got a new card, now I'm at ~400 mh/s
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Did you do the NTP thing above ? How many connections ? I've fired up a ghettobox with 250 mhashes some time ago (to test Cosbycoin's complaints of "orphan storm") and it gets an occasional block, though only one so far (GUIminer w poc on Wx64)
Got a new card, now I'm at ~400 mh/s
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
"blocks" : 1494,Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
"difficulty" : 111.50074768,
= about 20min expected average at 400Mh/s
That would explain things. Have the Bitcoin devs fixed the timewarp (sorry for lack of a better description, that's the only word I could think of) issue and what's there to stop someone from doing it right now? Or is there still a bit of muscle required to overcome the existing 10-12TH/s on the network?
1. No.2. You still roughly need 51% to do it, so something like 15Th/s for bitcoin...
Got a new card, now I'm at ~400 mh/s
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Still can't get any work in. Cards will chug away, but even after 10m still at 0/0. Using poclbm, win7x64, 2.1sdk
I still think I may be doing something wrong... but I can't tell. So my best guess is 400 is still too low.
Jump to: