Well i'm to the point now where I feel like i'm the only one doing ALL the work and its been that way for about a year now. Everyone wants to say community this and community that but no one else is really contributing but EVERYONE wants to benefit.
You want the wallet to stop freezing? Help me locate and notify any pool that is on the wrong chain. Because the longer chain that is being mined by someone who still hasnt updated will never be the right chain. Ever and they are just wasting their electricity. If they refuse to stop mining it then it has to be considered an attack on the network and delt with accordingly. As in blocking all the nodes who havnt updated yet. The newest client is the right chain. The longer chain is the wrong chain. Its the wrong change because its invalid with the new client. So, again, tell a friend to update. Thats really the only thing that can be done.
On the other hand, a new wallet design is being worked on. Follow me on twitter.com/frankocurrecy im pretty active there.
Topic: [ANN] New Crypto Currency FRANKO [w/ OPENSOURCE FRK ATM!][NEW WEBSITE Design] - page 48. (Read 233954 times)
June 18, 2014, 03:34:51 PM
June 18, 2014, 03:17:33 PM
Dogeberet has a point. Defaced's reply "You wont be missed because you arnt even known, you have never once contributed in any way shape or form with this community. Good bye lol." doesn't do right to the concern he is bringing to the table. Even if he has no Frankos at all or no interest at all in the Franko network at all, his point is to be taken seriously. I share his concern and I am glad he is bringing it up.
In my case I noticed that my client wouldn't update anymore after about two hours the problem occurred. I let it go for a couple of hours also because of the limited amount of nodes available. The Franko forum and this thread showed no indication of a problem at all and I assumed that problem was my own. I was surprised to notice that - after starting it up - my second client (wallet) started synchronizing, up till the same block as my stalled client. Though still no sign on the forum.
I think communication is a key issue here. A lack of activity on the forum also contributed. I have often doubted if there was more than one block chain. An active list of trusted nodes would be welcome in this perspective. More active connections make a stronger network.
If we want to make the Franko a success we should first of all embrace criticism and stop harassing criticasters.
In my case I noticed that my client wouldn't update anymore after about two hours the problem occurred. I let it go for a couple of hours also because of the limited amount of nodes available. The Franko forum and this thread showed no indication of a problem at all and I assumed that problem was my own. I was surprised to notice that - after starting it up - my second client (wallet) started synchronizing, up till the same block as my stalled client. Though still no sign on the forum.
I think communication is a key issue here. A lack of activity on the forum also contributed. I have often doubted if there was more than one block chain. An active list of trusted nodes would be welcome in this perspective. More active connections make a stronger network.
If we want to make the Franko a success we should first of all embrace criticism and stop harassing criticasters.
June 18, 2014, 01:19:48 PM
If you are a pool op and your pool is on the right chain check in.
www.xpool.ca
$ frankod getmininginfo
{
"blocks" : 802038,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.00628013,
"errors" : "",
"networkhashps" : 150802018,
"pooledtx" : 6,
"testnet" : false
}
ty sir
June 18, 2014, 12:47:09 PM
If you are a pool op and your pool is on the right chain check in.
www.xpool.ca
$ frankod getmininginfo
{
"blocks" : 802038,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.00628013,
"errors" : "",
"networkhashps" : 150802018,
"pooledtx" : 6,
"testnet" : false
}
June 18, 2014, 12:46:00 PM
If you are a pool op and your pool is on the right chain check in.
June 17, 2014, 10:42:53 PM
I also believe you made a bad chain the official fork.
Our pool is back online with this , uh, "official" blockchain.
lost alot
Our pool is back online with this , uh, "official" blockchain.
lost alot
Same here, several pools have switched over but one can still compare https://altexplorer.net/chain/Franko and https://coinplorer.com/FRK to see that the bad fork that was made official still has 2x lower diff. What a low move....
The reason I chose the shorter chain was because all of the main nodes including cryptsy and coins-e and the two main block explorers were stuck at block 785863 and reporting that specific block as being invalid. Whoever made the invalid block probably did so on an old wallet before the kgw timewarp fix. Some of the pools accepted it while most of the wallets didnt. By the time I released the fix to get cryptsy syncing again the chain autocorrected and orphaned the longer chain anyways. Why did it do that? Because only a few of the clients were actually accepting it.
So what was the right answer? Allow an invalid block by putting in an "ignore block 785864 it may be invalid but who cares" or orphan a days worth of work to make sure the block chain syncs fine and does so by staying true to the parameters we all agree on.
Altexplorer.net was on the wrong chain, it may be longer, there were a couple pools on the longer chain but it was still an invalid chain, if you dont believe me, set up 2 nodes on a private network with the other chain.. have the one node already have the wrong chain but start the second node from scratch and you will see it doesnt sync past 785863 then check the log and you will see why.
FRK was stuck for 37 hours before anyone noticed, cryptsy needed a fix asap or risk being delisted. So again, what would you have done? I'm sorry some people lost work, I dont have any money to compensate, wish I did but the only option we have is to move forward. We need to do whatever it takes to stay moving forward even if it means to step back a couple steps and correct a problem.
Well, I have been a FRK coin supporter up to now, but if this technically is possible, in my opinion - it deserves to be delisted and go the way of the dodo bird.
How can this sort of thing be expected to get wide acceptance and be treated like a currency when it can go on for 37 hours before anyone notices - and pools can run for days longer with no errors wasting days and days of work.
There have to be innovations to make these blockchains healing and self-correcting or the whole alt coin experiment is just going to be a failure. But we also have to accept failures and move on - which is what we should do with lots of the first round of alt coins, and I am done with this one.
If you've been a FRK supporter for awhile, why haven't hasn't anyone heard of you? I was a salaried operations manager and treasurer for the FRK Collective, yet this is the very first time your name has been mentioned.
STFU troll.
June 17, 2014, 10:27:06 PM
I also believe you made a bad chain the official fork.
Our pool is back online with this , uh, "official" blockchain.
lost alot
Our pool is back online with this , uh, "official" blockchain.
lost alot
Same here, several pools have switched over but one can still compare https://altexplorer.net/chain/Franko and https://coinplorer.com/FRK to see that the bad fork that was made official still has 2x lower diff. What a low move....
The reason I chose the shorter chain was because all of the main nodes including cryptsy and coins-e and the two main block explorers were stuck at block 785863 and reporting that specific block as being invalid. Whoever made the invalid block probably did so on an old wallet before the kgw timewarp fix. Some of the pools accepted it while most of the wallets didnt. By the time I released the fix to get cryptsy syncing again the chain autocorrected and orphaned the longer chain anyways. Why did it do that? Because only a few of the clients were actually accepting it.
So what was the right answer? Allow an invalid block by putting in an "ignore block 785864 it may be invalid but who cares" or orphan a days worth of work to make sure the block chain syncs fine and does so by staying true to the parameters we all agree on.
Altexplorer.net was on the wrong chain, it may be longer, there were a couple pools on the longer chain but it was still an invalid chain, if you dont believe me, set up 2 nodes on a private network with the other chain.. have the one node already have the wrong chain but start the second node from scratch and you will see it doesnt sync past 785863 then check the log and you will see why.
FRK was stuck for 37 hours before anyone noticed, cryptsy needed a fix asap or risk being delisted. So again, what would you have done? I'm sorry some people lost work, I dont have any money to compensate, wish I did but the only option we have is to move forward. We need to do whatever it takes to stay moving forward even if it means to step back a couple steps and correct a problem.
Well, I have been a FRK coin supporter up to now, but if this technically is possible, in my opinion - it deserves to be delisted and go the way of the dodo bird.
How can this sort of thing be expected to get wide acceptance and be treated like a currency when it can go on for 37 hours before anyone notices - and pools can run for days longer with no errors wasting days and days of work.
There have to be innovations to make these blockchains healing and self-correcting or the whole alt coin experiment is just going to be a failure. But we also have to accept failures and move on - which is what we should do with lots of the first round of alt coins, and I am done with this one.
Thing about it is the network IS self healing its just that a multipool using an old client didnt have the timewarp fix and created an invalid block that everyone on the new client refused. Before I even implemented my fix the network already orphaned the longer chain and started the healing process of banning the bad nodes because the legitimate pools mining on the new client started finding blocks that werent being considered stale. Thats the beauty of the bitcoin protocol. Its amazingly elastic.
June 17, 2014, 10:02:44 PM
I also believe you made a bad chain the official fork.
Our pool is back online with this , uh, "official" blockchain.
lost alot
Our pool is back online with this , uh, "official" blockchain.
lost alot
Same here, several pools have switched over but one can still compare https://altexplorer.net/chain/Franko and https://coinplorer.com/FRK to see that the bad fork that was made official still has 2x lower diff. What a low move....
The reason I chose the shorter chain was because all of the main nodes including cryptsy and coins-e and the two main block explorers were stuck at block 785863 and reporting that specific block as being invalid. Whoever made the invalid block probably did so on an old wallet before the kgw timewarp fix. Some of the pools accepted it while most of the wallets didnt. By the time I released the fix to get cryptsy syncing again the chain autocorrected and orphaned the longer chain anyways. Why did it do that? Because only a few of the clients were actually accepting it.
So what was the right answer? Allow an invalid block by putting in an "ignore block 785864 it may be invalid but who cares" or orphan a days worth of work to make sure the block chain syncs fine and does so by staying true to the parameters we all agree on.
Altexplorer.net was on the wrong chain, it may be longer, there were a couple pools on the longer chain but it was still an invalid chain, if you dont believe me, set up 2 nodes on a private network with the other chain.. have the one node already have the wrong chain but start the second node from scratch and you will see it doesnt sync past 785863 then check the log and you will see why.
FRK was stuck for 37 hours before anyone noticed, cryptsy needed a fix asap or risk being delisted. So again, what would you have done? I'm sorry some people lost work, I dont have any money to compensate, wish I did but the only option we have is to move forward. We need to do whatever it takes to stay moving forward even if it means to step back a couple steps and correct a problem.
Well, I have been a FRK coin supporter up to now, but if this technically is possible, in my opinion - it deserves to be delisted and go the way of the dodo bird.
How can this sort of thing be expected to get wide acceptance and be treated like a currency when it can go on for 37 hours before anyone notices - and pools can run for days longer with no errors wasting days and days of work.
There have to be innovations to make these blockchains healing and self-correcting or the whole alt coin experiment is just going to be a failure. But we also have to accept failures and move on - which is what we should do with lots of the first round of alt coins, and I am done with this one.
June 17, 2014, 03:59:36 PM
good thing it was only $14, but yea that sucks im sorry
anyone else notice that their frankod uses a lot of CPU???
During sync?
yes that is expected, but after the sync it stayed like that for ~an hour before I shut it down and started it back up. Seems back to acceptable usage now.
Yea it will do that sometimes.
June 17, 2014, 01:19:16 PM
good thing it was only $14, but yea that sucks im sorry
anyone else notice that their frankod uses a lot of CPU???
During sync?
yes that is expected, but after the sync it stayed like that for ~an hour before I shut it down and started it back up. Seems back to acceptable usage now.
June 17, 2014, 12:54:34 PM
good thing it was only $14, but yea that sucks im sorry
anyone else notice that their frankod uses a lot of CPU???
During sync?
June 17, 2014, 11:11:14 AM
good thing it was only $14, but yea that sucks im sorry
anyone else notice that their frankod uses a lot of CPU???
June 17, 2014, 08:57:50 AM
good thing it was only $14, but yea that sucks im sorry
June 17, 2014, 08:48:18 AM
June 17, 2014, 08:26:40 AM
done 
June 17, 2014, 08:19:19 AM
yup
June 17, 2014, 07:53:24 AM
The reason I chose the shorter chain was because all of the main nodes including cryptsy and coins-e and the two main block explorers were stuck at block 785863 and reporting that specific block as being invalid. Whoever made the invalid block probably did so on an old wallet before the kgw timewarp fix. Some of the pools accepted it while most of the wallets didnt. By the time I released the fix to get cryptsy syncing again the chain autocorrected and orphaned the longer chain anyways. Why did it do that? Because only a few of the clients were actually accepting it.
So what was the right answer? Allow an invalid block by putting in an "ignore block 785864 it may be invalid but who cares" or orphan a days worth of work to make sure the block chain syncs fine and does so by staying true to the parameters we all agree on.
Altexplorer.net was on the wrong chain, it may be longer, there were a couple pools on the longer chain but it was still an invalid chain, if you dont believe me, set up 2 nodes on a private network with the other chain.. have the one node already have the wrong chain but start the second node from scratch and you will see it doesnt sync past 785863 then check the log and you will see why.
FRK was stuck for 37 hours before anyone noticed, cryptsy needed a fix asap or risk being delisted. So again, what would you have done? I'm sorry some people lost work, I dont have any money to compensate, wish I did but the only option we have is to move forward. We need to do whatever it takes to stay moving forward even if it means to step back a couple steps and correct a problem.
Apparently Cryptsy is on the long chain now... and my coins are toast....
lol nope. Why is everyone using altexporer.net?
the official is http://frk.cryptocoinexplorer.com/
Can you distinguish that in the OP?
June 17, 2014, 07:23:24 AM
so.... I'm not sure which chain we should be on... can someone confirm....
should we be on block 803917+
https://altexplorer.net/chain/Franko
should we be on block 803917+
https://altexplorer.net/chain/Franko
The answer is no.
June 17, 2014, 07:22:12 AM
June 17, 2014, 07:20:35 AM
The reason I chose the shorter chain was because all of the main nodes including cryptsy and coins-e and the two main block explorers were stuck at block 785863 and reporting that specific block as being invalid. Whoever made the invalid block probably did so on an old wallet before the kgw timewarp fix. Some of the pools accepted it while most of the wallets didnt. By the time I released the fix to get cryptsy syncing again the chain autocorrected and orphaned the longer chain anyways. Why did it do that? Because only a few of the clients were actually accepting it.
So what was the right answer? Allow an invalid block by putting in an "ignore block 785864 it may be invalid but who cares" or orphan a days worth of work to make sure the block chain syncs fine and does so by staying true to the parameters we all agree on.
Altexplorer.net was on the wrong chain, it may be longer, there were a couple pools on the longer chain but it was still an invalid chain, if you dont believe me, set up 2 nodes on a private network with the other chain.. have the one node already have the wrong chain but start the second node from scratch and you will see it doesnt sync past 785863 then check the log and you will see why.
FRK was stuck for 37 hours before anyone noticed, cryptsy needed a fix asap or risk being delisted. So again, what would you have done? I'm sorry some people lost work, I dont have any money to compensate, wish I did but the only option we have is to move forward. We need to do whatever it takes to stay moving forward even if it means to step back a couple steps and correct a problem.
Apparently Cryptsy is on the long chain now... and my coins are toast....
lol nope. Why is everyone using altexporer.net?
the official is http://frk.cryptocoinexplorer.com/
Jump to: