|
CaptChadd
|
 |
July 12, 2013, 12:51:54 AM |
|
How do we get on the right chain?
|
|
|
|
|
|
Eli0t
|
|
July 12, 2013, 12:57:57 AM
Last edit: July 12, 2013, 01:21:57 AM by Eli0t |
|
not sure what the best method is
primecoin-qt -rescan
or deleting blk00000.dat from the profile directory
EDIT just realised block updates had stopped for me, restarted the client and it caught up
|
LTC: LKpJf3uk7KsHU73kxq8iFJrP1AAKN7Yni7 DGC: DKXGvEbj3Rwgrm2QQbRyNPDDZDYoq4Y44d XPM: AWV5AKfLFyoBaMjg9C77rGUBhuFxz5DGGL
|
|
|
|
tadakaluri
|
|
July 12, 2013, 01:24:43 AM |
|
There is no Block from last 24 hours......... What happened?
a: you got disconnected b: your on the wrong chain c: you chain updates stopped for some reason I am online..... How to solve these other issues? |
|
|
|
|
|
|
hiddenvalleyranch
Member
 Offline
Activity: 103
Merit: 10
|
|
July 12, 2013, 01:50:06 AM |
|
Anyone have an i5 haswell optimized windows binary? I'll shoot you some XPM.
|
|
|
|
|
|
RustyShackleford1950
|
|
July 12, 2013, 01:53:39 AM |
|
Thanks, what's the main differences between the two above? |
On keyboard, the big d, rusty shackleford
|
|
|
|
|
|
Zalfrin
|
|
July 12, 2013, 01:56:10 AM |
|
Thanks, what's the main differences between the two above? Just the processor architecture that the compiler optimized the code for. 11 might be faster but won't run on as many processors. 12 should be more widely supported, it's a more generic instruction set. |
|
|
|
|
mrmanager
Newbie
Offline
Activity: 50
Merit: 0
|
|
July 12, 2013, 02:00:40 AM |
|
Just the processor architecture that the compiler optimized the code for. 11 might be faster but won't run on as many processors. 12 should be more widely supported, it's a more generic instruction set.
Your initial release is solid, and I've mined a few blocks with it. I haven't noticed any blockchain issues on any of my machines. I have a Sandy Bridge CPU working phenomenally with your i5 optimized build. The rest are using your first build. I don't know if I'm unlucky, but I've rebooted all of the machines that haven't found a block in a few hours. |
|
|
|
|
|
Zalfrin
|
|
July 12, 2013, 02:05:41 AM |
|
Just the processor architecture that the compiler optimized the code for. 11 might be faster but won't run on as many processors. 12 should be more widely supported, it's a more generic instruction set.
Your initial release is solid, and I've mined a few blocks with it. I haven't noticed any blockchain issues on any of my machines. Even so, I'd recommend switching over to one of these new versions. Primespersec look to be about the same, and there's definitely something to be said for being on the official codebase versus the code I hacked together based on some optimization suggestions. That was actually done before Sunny released his sieve code update, which made the most difference by far anyways. |
|
|
|
|
mrmanager
Newbie
Offline
Activity: 50
Merit: 0
|
|
July 12, 2013, 02:09:48 AM |
|
Just the processor architecture that the compiler optimized the code for. 11 might be faster but won't run on as many processors. 12 should be more widely supported, it's a more generic instruction set.
Your initial release is solid, and I've mined a few blocks with it. I haven't noticed any blockchain issues on any of my machines. Even so, I'd recommend switching over to one of these new versions. Primespersec look to be about the same, and there's definitely something to be said for being on the official codebase versus the code I hacked together based on some optimization suggestions. That was actually done before Sunny released his sieve code update, which made the most difference by far anyways. I should have been more specific. I'm using a build with the updates from Sunny. That update translated into 4x the speed. |
|
|
|
|
|
96redformula
|
|
July 12, 2013, 02:41:15 AM |
|
I am starting to get orphan city using the a compiled build from github....Something must have happened, maybe optimized miners out now or GPUs being used. It seems a bit fishy.
|
|
|
|
|
|
willphase
|
|
July 12, 2013, 02:45:22 AM |
|
just a warning, when I tried compiling on VS2012 with optimizations, I found that my serialization code was off kilt, and run into all sorts of issues...
if you're playing with the reference client, it might be worth just trying to optimize prime.c (via CFLAGS override in Makefile) since that's where all the logic for calculations are - and you won't risk messing with any of the other important network code.
Will
|
|
|
|
|
96redformula
|
|
July 12, 2013, 02:55:30 AM |
|
That was incredibly strange, 17754 was taking a long long time it seemed. All of a sudden the block solve rate just slowed tremendously from a glance at the block count. It went from one every 10 seconds to 20-30 seconds plus.
|
|
|
|
|
craslovell
Legendary
Offline
Activity: 1470
Merit: 1021
|
|
July 12, 2013, 03:04:44 AM |
|
How long does it usually take for a transaction to appear in your wallet?
I sent 2 separate transactions over 2 hours ago and still nothing  any idea? Did you add .01 tx fee in your wallet settings? |
|
|
|
|
craslovell
Legendary
Offline
Activity: 1470
Merit: 1021
|
|
July 12, 2013, 03:05:33 AM |
|
Nobody noticed Vircurex just added XPM? They went down shortly after that, but now they are fine and dandy again  Looks like coins-e was abandoned because of this  |
|
|
|
|
craslovell
Legendary
Offline
Activity: 1470
Merit: 1021
|
|
July 12, 2013, 03:06:39 AM |
|
How do we get on the right chain?
Looks like some of the custom builds were causing these issues. |
|
|
|
|
|
Zalfrin
|
|
July 12, 2013, 03:08:00 AM |
|
just a warning, when I tried compiling on VS2012 with optimizations, I found that my serialization code was off kilt, and run into all sorts of issues...
if you're playing with the reference client, it might be worth just trying to optimize prime.c (via CFLAGS override in Makefile) since that's where all the logic for calculations are - and you won't risk messing with any of the other important network code.
Will
Probably a good idea, testing with -O3 only on prime. |
|
|
|
|
8bitPunk
Member
Offline
Activity: 70
Merit: 10
|
|
July 12, 2013, 03:10:26 AM |
|
That was incredibly strange, 17754 was taking a long long time it seemed. All of a sudden the block solve rate just slowed tremendously from a glance at the block count. It went from one every 10 seconds to 20-30 seconds plus.
Perhaps an outage/DOS at DigitalOcean has taken the VPS miners out of action? ... This was speculated last time the block spacing jumped from ~10 seconds to ~20 seconds... Edit: and the blockrate is back under 10 seconds... |
BTC 18bPunkuginRBm1Xz9mcgj8mWJnHDAW5Th | Ł LTCgXEdyBdoQ9WdF6JHi7Pa2EWtzbDjG76 | Ψ ATEBiTLkLpAYeW5hQknUfSvnb7Abbgegku
|
|
|
anonppcoin
Newbie
Offline
Activity: 48
Merit: 0
|
|
July 12, 2013, 03:15:36 AM
Last edit: July 12, 2013, 03:37:30 AM by anonppcoin |
|
just a warning, when I tried compiling on VS2012 with optimizations, I found that my serialization code was off kilt, and run into all sorts of issues...
if you're playing with the reference client, it might be worth just trying to optimize prime.c (via CFLAGS override in Makefile) since that's where all the logic for calculations are - and you won't risk messing with any of the other important network code.
Will
How on earth are you compiling this on VS2012? Do you have any project files you could share? |
|
|
|
|
|
