What's with http://coven.ninja ? DEV left or something already?
site looks fine to me
Topic: [ANN] [COV] Coven [33k Coins/3%POS] - page 26. (Read 32565 times)
site looks fine to me
What's with http://coven.ninja ? DEV left or something already?
just woke up and i'm not syncing either 
switched back to the last version so i could at least stake and keep the chain moving.
switched back to the last version so i could at least stake and keep the chain moving. mine is staying sync'd 2 stakes and a couple more deposits since I updated
The new and old clients are probably going to fork. You'll be on the less permissive chain that will probably be orphaned if the dev fixes this the quick, dirty, and easy way.
just woke up and i'm not syncing either switched back to the last version so i could at least stake and keep the chain moving.
switched back to the last version so i could at least stake and keep the chain moving. mine is staying sync'd 2 stakes and a couple more deposits since I updated
The new and old clients are probably going to fork. You'll be on the less permissive chain that will probably be orphaned if the dev fixes this the quick, dirty, and easy way.
just woke up and i'm not syncing either switched back to the last version so i could at least stake and keep the chain moving.
switched back to the last version so i could at least stake and keep the chain moving. Don't panic. This is not a hard fix. The timings just need to be reverted to what they were before the commit. The blocks that have been minted with the new timings will be acceptable to those with old timings, so there probably won't be a bad fork from this. But the dev should get to it sooner rather than later.
My guess is that the consensus chain will end up being from the clients previous to the commit, like you have done.
It's a good idea and I'm going to do that too.
just woke up and i'm not syncing either switched back to the last version so i could at least stake and keep the chain moving.
switched back to the last version so i could at least stake and keep the chain moving. mine is staying sync'd 2 stakes and a couple more deposits since I updated
just woke up and i'm not syncing either switched back to the last version so i could at least stake and keep the chain moving.
switched back to the last version so i could at least stake and keep the chain moving. at this point it's so cheap I wont risk leaving a buy up and not getting any when I could just buy 
Does anyone who is fully synced have a good set of nodes? I can't sync past block 2.
did you download the new wallet today? mines been working great, what would I have to type into the debug console to get you a node/nodes?
I used the newest wallet as of a few minutes ago and started with a clean app data dir.
This is my debug.log. It looks like one of the seed nodes is serving a bad block from early on. Flash mines (I have nothing against those) bubble like this in the earliest blocks, but I've never seen it effect the sync:
Code:
receive version message: version 60014, blocks=1900, us=174.56.90.17:37768, them=45.55.179.113:22454, peer=45.55.179.113:22454
received block 00000000bce418502eb6
SetBestChain: new best=00000000bce418502eb6 height=1 trust=33554944 blocktrust=16777472 date=04/19/15 03:40:48
ProcessBlock: ACCEPTED
received block 0000000077f387e86aca
SetBestChain: new best=0000000077f387e86aca height=2 trust=50332416 blocktrust=16777472 date=04/19/15 03:40:49
ProcessBlock: ACCEPTED
received block 000000002f8def824329
ERROR: AcceptBlock() : incorrect proof-of-work
And here's the problem with the latest commits:
Code:
-static const int64_t nTargetTimespan = 60 * 30; // 30m
-unsigned int nTargetSpacing = 1 * 90; // Coven - 1.5 minute blocks
+static const int64_t nTargetTimespan = 60 * 5; // 30m
+unsigned int nTargetSpacing = 1 * 60; // Coven - 1.5 minute blocks
Changing the target spacing screws up the calculation of the work required.
Anyone who already has a chain fully synced won't see this. People like me who want to re-sync the chain are going to hang.
This needs to be fixed.
at least you were able to find the issue, it'll make it that much easier/faster for the dev to fix it when he see's your post.
I found it a good habit to back up the whole appdatta file before up dates, and usually do it every month or so... my comp is old when it crash sometimes it f#cks up some of my wallets and I use back ups instead of waiting days for some coins to sync
at this point it's so cheap I wont risk leaving a buy up and not getting any when I could just buy
Does anyone who is fully synced have a good set of nodes? I can't sync past block 2.
did you download the new wallet today? mines been working great, what would I have to type into the debug console to get you a node/nodes?
I used the newest wallet as of a few minutes ago and started with a clean app data dir.
This is my debug.log. It looks like one of the seed nodes is serving a bad block from early on. Flash mines (I have nothing against those) bubble like this in the earliest blocks, but I've never seen it effect the sync:
Code:
receive version message: version 60014, blocks=1900, us=174.56.90.17:37768, them=45.55.179.113:22454, peer=45.55.179.113:22454
received block 00000000bce418502eb6
SetBestChain: new best=00000000bce418502eb6 height=1 trust=33554944 blocktrust=16777472 date=04/19/15 03:40:48
ProcessBlock: ACCEPTED
received block 0000000077f387e86aca
SetBestChain: new best=0000000077f387e86aca height=2 trust=50332416 blocktrust=16777472 date=04/19/15 03:40:49
ProcessBlock: ACCEPTED
received block 000000002f8def824329
ERROR: AcceptBlock() : incorrect proof-of-work
And here's the problem with the latest commits:
Code:
-static const int64_t nTargetTimespan = 60 * 30; // 30m
-unsigned int nTargetSpacing = 1 * 90; // Coven - 1.5 minute blocks
+static const int64_t nTargetTimespan = 60 * 5; // 30m
+unsigned int nTargetSpacing = 1 * 60; // Coven - 1.5 minute blocks
Changing the target spacing screws up the calculation of the work required.
Anyone who already has a chain fully synced won't see this. People like me who want to re-sync the chain are going to hang.
This needs to be fixed.
at this point it's so cheap I wont risk leaving a buy up and not getting any when I could just buy
Does anyone who is fully synced have a good set of nodes? I can't sync past block 2.
did you download the new wallet today? mines been working great, what would I have to type into the debug console to get you a node/nodes?
I used the newest wallet as of a few minutes ago and started with a clean app data dir.
This is my debug.log. It looks like one of the seed nodes is serving a bad block from early on. Flash mines (I have nothing against those) bubble like this in the earliest blocks, but I've never seen it effect the sync:
Code:
receive version message: version 60014, blocks=1900, us=174.56.90.17:37768, them=45.55.179.113:22454, peer=45.55.179.113:22454
received block 00000000bce418502eb6
SetBestChain: new best=00000000bce418502eb6 height=1 trust=33554944 blocktrust=16777472 date=04/19/15 03:40:48
ProcessBlock: ACCEPTED
received block 0000000077f387e86aca
SetBestChain: new best=0000000077f387e86aca height=2 trust=50332416 blocktrust=16777472 date=04/19/15 03:40:49
ProcessBlock: ACCEPTED
received block 000000002f8def824329
ERROR: AcceptBlock() : incorrect proof-of-work
at this point it's so cheap I wont risk leaving a buy up and not getting any when I could just buy
Does anyone who is fully synced have a good set of nodes? I can't sync past block 2.
did you download the new wallet today? mines been working great, what would I have to type into the debug console to get you a node/nodes?
at this point it's so cheap I wont risk leaving a buy up and not getting any when I could just buy
Does anyone who is fully synced have a good set of nodes? I can't sync past block 2.
at this point it's so cheap I wont risk leaving a buy up and not getting any when I could just buy
Price won't go up much without buy support. It's almost nothing down to 80k. If you want price to go up show your support in the orderbooks.
is v1.0.0.0-g32a928e the correct wallet?
v1.0.0.0-g32a928e is the latest one, I'm using.
yeah, v1.0.0.0-g32a928e = latest version of wallet; I put in OP to redownload / sync wallet; it's hyperlinked with the download image; perhaps I should of clarified
http://coven.ninja/ website design is amazing. Dev and community willing this coin can surpass Crave.
idem with you
is v1.0.0.0-g32a928e the correct wallet?
v1.0.0.0-g32a928e is the latest one, I'm using.
yeah, v1.0.0.0-g32a928e = latest version of wallet; I put in OP to redownload / sync wallet; it's hyperlinked with the download image; perhaps I should of clarified
http://coven.ninja/ website design is amazing. Dev and community willing this coin can surpass Crave.
is v1.0.0.0-g32a928e the correct wallet?
v1.0.0.0-g32a928e is the latest one, I'm using.
yeah, v1.0.0.0-g32a928e = latest version of wallet; I put in OP to redownload / sync wallet; it's hyperlinked with the download image; perhaps I should of clarified
thanks for confirming starin...
is v1.0.0.0-g32a928e the correct wallet?
v1.0.0.0-g32a928e is the latest one, I'm using.
is v1.0.0.0-g32a928e the correct wallet?
Jump to: