[ANN][CFC2]Coffeecoin | This coin is under the RevivalCoinGroup management

[Matory]

I had time to think, and now came to the conclusion that two things wrong:

- we do not refuse to POW at all until POS will work perfectly and community will find the strength to be updated.

- we must decrease POW block reward! Maybe to 1 (one) CFC2 per block.

Now we are getting closer to exceed a reasonable number CFC2 coins, in three months we grew up on a lot - 38% or 154% annually!  
This kill coffeecoin idea and  devalues coin price.

I propose to release new update :
-decrease reward to 1 CFC2/block
-continue POW
-update POS fix
-fix "311293 problem" to Bittrex could be updated and open a Deposit/Withdrawal.

(After 311293 block not  fork - quite reload blockchain)

this plan suits me. My wallet is 2.0.2 version, may be turn it off after 380000 block, it coming soon, to estimates in next day. I hope coins I sent to Bittrex will be back after update. 

Maybe today will be update. Off wallet if not sync after 380,000
Your CFC2 in Bittrex not lost, but must wait. 

[kelsey]

I am totally agreed too. When new update will become?

-decrease reward to 1 CFC2/block
-continue POW
-update POS fix
-fix "311293 problem" to Bittrex could be updated and open a Deposit/Withdrawal.

+1
kelsey should be also satisfied, as it is a suggestion and a question before you actually do ;-)
so is there anyone against this proposal?

Wait until kelsey will agree  I need 1 or 2 days, then.

Sorry if I don't get back often atm, holiday traveling across (often rural) China (so internet on and off).
No complaint with Matory's new proposal, I'll agree with what the community agrees on.

[testcoin]

-decrease reward to 1 CFC2/block
-continue POW
-update POS fix
-fix "311293 problem" to Bittrex could be updated and open a Deposit/Withdrawal.

+1
kelsey should be also satisfied, as it is a suggestion and a question before you actually do ;-)
so is there anyone against this proposal?

@Matory

No offense but I have to say I vote against lowering POW block rewards significantly to scare away miners, since it will just leave a security flaw to allow hackers exploiting 51% attacks easily. If you do this the network won’t be secure. Better to re-think about how to shift it to a pure POS.

Besides, before you can guarantee the community they won’t possibly lose their Bittrex funds, you better update checkpoints to ensure those funds are safe. Too bad from your checkpoints.cpp file you obviously haven’t done it. You will need to contact Bittrex (and Bleutrade) first to check for their block hashes.

Up to this post we still have no information who is the coder behind. Why don’t you just bring the coder to this thread so we can all know who he is?

[nxtonly]

Nice coin. I still hold it.

[Matory]

Members who have peers in
-188.165.2.147  block 311298
-62.210.113.162 block 311341
please rescan CFC2 blockchain or turn off your wallets.
Thanks!

v2.0.3.0 copmlete.

[madmartyk]

Members who have peers in
-188.165.2.147  block 311298
-62.210.113.162 block 311341
please rescan CFC2 blockchain or turn off your wallets.
Thanks!

Is there a new QT.EXE?

v2.0.3.0 copmlete.

[Matory]

Members who have peers in
-188.165.2.147  block 311298
-62.210.113.162 block 311341
please rescan CFC2 blockchain or turn off your wallets.
Thanks!

v2.0.3.0 copmlete.

Is there a new QT.EXE?

Yes and now in test mode.

[madmartyk]

Cool!!  Can't wait!!

[Matory]

@Matory

No offense but I have to say I vote against lowering POW block rewards significantly to scare away miners, since it will just leave a security flaw to allow hackers exploiting 51% attacks easily. If you do this the network won’t be secure. Better to re-think about how to shift it to a pure POS.

Besides, before you can guarantee the community they won’t possibly lose their Bittrex funds, you better update checkpoints to ensure those funds are safe. Too bad from your checkpoints.cpp file you obviously haven’t done it. You will need to contact Bittrex (and Bleutrade) first to check for their block hashes.

Up to this post we still have no information who is the coder behind. Why don’t you just bring the coder to this thread so we can all know who he is?

v2.0.2 worked good in POS, we are forced to reduce reward block because community did not update in time, only 7 wallets from 22 worked well. We can't abandon the entire POW now, not worry about 51% attack, i create and keep hashrate all time until POS will work perfectly.

It's three coders research CFC2 source, two fixed POS and delete some wrong code, MrData build win wallet, I mentioned his past posts.
Version 2.0.3 ready and work in network https://chainz.cryptoid.info/cfc2/#!network but we must to completely switch ALL 1.0.1 wallets! I contacted with fairglu and we try update explorer before other members change wallet version.
Also, i ready to compensate mining time, f.e. to address CZNpa19JzYK9kQ5GCUZs1DzxAG6DLyD5Dg, from my private CFC2 fund if owner of this address change him wallet asap.

[fairglu]

As community seems to be agreeing (?) I'm switching the explorer to the new github and resynchronizing

Explorer will be down until new wallet has successfully synchronized.

However the latest 2.0.3 version does not seem to include checkpoints beyond block 11, so there is no guarantee it will end up on the same chain as bittrex f.i.

[Matory]

As community seems to be agreeing (?) I'm switching the explorer to the new github and resynchronizing

Explorer will be down until new wallet has successfully synchronized

I'm here all time, PM me or send email (more quick) if i can help .

[fairglu]

As community seems to be agreeing (?) I'm switching the explorer to the new github and resynchronizing

Explorer will be down until new wallet has successfully synchronized

I'm here all time, PM me or send email (more quick) if i can help .

If you can contact bittrex for their last block height hash, you can set that one as checkpoint, this will ensure the new client ends up on the same chain and funds are not lost.

(wallet currently at height 67k, it will be many hours until it has resynchronized, beyond the bittrex issue, having a checkpoint and the network using it would likely speed that process, synchronization is held back by clients on the various forks which submit conflicting chains)

[Matory]

As community seems to be agreeing (?) I'm switching the explorer to the new github and resynchronizing

Explorer will be down until new wallet has successfully synchronized

I'm here all time, PM me or send email (more quick) if i can help .

If you can contact bittrex for their last block height hash, you can set that one as checkpoint, this will ensure the new client ends up on the same chain and funds are not lost.

(wallet currently at height 67k, it will be many hours until it has resynchronized, beyond the bittrex issue, having a checkpoint and the network using it would likely speed that process, synchronization is held back by clients on the various forks which submit conflicting chains)

Ok. Earlier Bittrex support answer their height is 311293, and support wait until new wallet can sync independently. That is why we update explorer first.

//I follow your wallet and add it in addnode. I hope all will be well!

[fairglu]

Ok. Earlier Bittrex support answer their height is 311293, and support wait until new wallet can sync independently. That is why we update explorer first.

//I follow your wallet and add it in addnode. I hope all will be well!

You also need their blockhash for that height, there were multiple forks at a similar height.

Explorer wallet is now at 220167.

[Matory]

Hi all!

We are still working to restore, please be patient.

[fairglu]

Explorer wallet on v2.0.3.0 got stuck at 311293, so I guess the wallet issue is not fixed yet 

Also that's a different fork than bittrex, which is stuck at 311322 according to their status page.

[Matory]

Explorer wallet on v2.0.3.0 got stuck at 311293, so I guess the wallet issue is not fixed yet 

Also that's a different fork than bittrex, which is stuck at 311322 according to their status page.

Answer from Bittrex

 "version" : "v2.0.1.0",
    "protocolversion" : 60503,
    "walletversion" : 60000,
    "blocks" : 311293,

[fairglu]

Answer from Bittrex

 "version" : "v2.0.1.0",
    "protocolversion" : 60503,
    "walletversion" : 60000,
    "blocks" : 311293,

You really need to obtain some block hashes, otherwise it's impossible to know which chain they're on exactly.

[Matory]

Answer from Bittrex

 "version" : "v2.0.1.0",
    "protocolversion" : 60503,
    "walletversion" : 60000,
    "blocks" : 311293,

You really need to obtain some block hashes, otherwise it's impossible to know which chain they're on exactly.

It's one chain.

[richiela]

    "version" : "v2.0.3.0",
    "protocolversion" : 60505,
    "walletversion" : 60000,
    "blocks" : 402320,

 coffeecoin getblockhash 402320
000000f4d335e147136a3f895526919234702fcc996439f3417e267b2951c02e

This is using the downloaded blockchain... for now, everything seems to check out.  Wallet is re-open.  Would appreciate if we can get the BX in sync as well.

Thanks,
richie@bittrex