[ANN] New Crypto Currency FRANKO [v0.16][Resurrection]

[Barasha]

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....

altexplorer.net/chain/Franko
I see it for the first time

[defaced]

I also believe you made a bad chain the official fork.
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.

[defaced]

Btw run my little test without the new checkpoints.

Last build and new build agree that my checkpointed chain is valid, if it didnt, reaching consensus would have been alot trickier. Again I am very sorry for the orphaned blocks but it was for the good of everyone involved. We all have to make sacrifices occasionally for the things we believe in.

[Sharkzz1]

damn what happened to frk today? 27000satoshis at the moment, dont know if i might go back up again

[Barasha]

How to determine the count number of transactions for a specific period of time or block? I want to know the number of transactions by month.

UPD. Thank debug.log found

[defaced]

How to determine the count number of transactions for a specific period of time or block? I want to know the number of transactions by month.

UPD. Thank debug.log found

Yea its in the debug.log

[defaced]

damn what happened to frk today? 27000satoshis at the moment, dont know if i might go back up again

Not much interest in fair coins by the pump and dumping day traders. Miners dont dump, the people with a large amount dont buy stuff with them. Everyone is hoarding hoping it will become the next btc -,-.

I think this is because the only people in btc who got rich were the ones who hoarded while they told everyone else to spend it.

[defaced]

Ok so, The Cryptolina convention is coming up in August 15th and 16th, to set up a table it cost $1500. We need to raise a little capital and get a table at that convention.

Some stuff that would be nice to have at the table with us would be.

-- Tshirts
-- Usb drives with a copy of the software and blockchain
-- lanyards
-- brochures
-- flyers

FRK prices have taken a dip, we need to be more proactive about spreading the word. If you cant donate time you can donate coin.


BTC - 1EagKBq75KhNVScHnGPCQPnsYR78bGvFsU
FRK - FUDw4aPDeV2T26kVzg5eqZST6dg74tXRUC

[Barasha]

Where can I download or as a self-extract from the database the following information:

Date    |    Block    |    Transactions    |    Transactions_balance    |   Difficulty

as table for all time?

[defaced]

Where can I download or as a self-extract from the database the following information:

Date    |    Block    |    Transactions    |    Transactions_balance    |   Difficulty

as table for all time?

look up "abe explorer"

[crackfoo]

Hey ya'll, I've added FRK to my new Multipool. Would love to have some miners stop by and mine! FRK is often the most profitable!

xpool - BTC Multipool

 

http://www.xpool.ca

PROP reward system

BTC Payouts

Scrypt & SHA256 Algo's

DDoS Protected

High Performance Backend

Simple setup and usage

0% Fees while in BETA

To mine:

http://www.xpool.ca/get_started

Cheers and Happy Hashing!

[crackfoo]

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

[crackfoo]

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....

[defaced]

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/

[defaced]

look another explorer on the right chain!

https://coinplorer.com/FRK :O

[defaced]

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

The answer is no.

[crackfoo]

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?

[defaced]

yup

[defaced]

done

[crackfoo]

done

thanks! Was a shame to throw away 120 frk