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

[Youghoor]

CoffeeCoin's former "dev"

Our former dev released another coin called "Finercoin". Take from that what you will, but most of all, trade with care...

How could you know for certain that is him?

yes , any proof regarding this so that we can also know about it?

[coffeecoin]

CoffeeCoin's former "dev"

Our former dev released another coin called "Finercoin". Take from that what you will, but most of all, trade with care...

How could you know for certain that is him?

yes , any proof regarding this so that we can also know about it?

While he was still directly in charge of CoffeeCoin, we sent emails back and forth to each other about recommendations, potential fixes, and grammar/spelling for new announcements. He continued to email me (from a different email, since he turned over his coffeecoin one to me) concerning the new coin he was working on, and asked for help on his grammar and spelling for the ANN he was working on (Finercoin). I helped him out a little bit, but haven't replied back since the actual ANN was posted. He asked if I could be the community lead for that coin too, but I gave him a piece of my mind about abandoning CFC with a crippled client, and not wanting to be involved with another coin in a similar predicament. I even urged him not to release another coin until he was 100% positive it would work without issues, this time. I've still got the email chains, but honestly I'd rather completely cut ties with the guy and his projects. We've got our new client, and should focus on the road ahead, and the direction we plan to take it.

[coffeecoin]

may want to upload the wallet to another site, downloading is VERY SLOW!!!

I apologize for that, I'll look into it later; today's been a hectic day for me

[coffeecoin]

Possible solution for stuck POS

Our wallets are increasing in weight, so that is a sign that everything is indeed working as intended. The delay in the first POS block is suspected to be caused by the lack of overall weight, and its just a matter of time before POS kicks in. As far as we know, there is no definite way to set the initial weight necessary to trigger the first POS block, so it's more of a waiting game, than anything else. On the test client, the "master wallet" had to accumulate a weight of ~250mil before the first POS block; our current "master wallet" is sitting at around ~114.6mil, so we're about halfway there.

To continue pumping out transactions until POS starts (which may be another week or so, as estimated by myself and OCdev) we're going to enable POW indefinitely... At least until the first POS block hits the network, then it will be disabled again. A POW re-enabled release will be coming shortly.

If you all didn't know, coffeecoinguild.com has its own members-only trollbox. If you ever need to speak to me directly, sometimes you can find me there, username Profitus.Zero. Feel free to drop in to say 'hello'. It still needs to be tested, and feedback is appreciated.

So did PoS kick in already or no? I still have all my coins at Bittrex.

Version 2.0.1 has re-enabled POW to help process transactions until we're positive POS can carry the network 100%.

[marti]

Possible solution for stuck POS

Our wallets are increasing in weight, so that is a sign that everything is indeed working as intended. The delay in the first POS block is suspected to be caused by the lack of overall weight, and its just a matter of time before POS kicks in. As far as we know, there is no definite way to set the initial weight necessary to trigger the first POS block, so it's more of a waiting game, than anything else. On the test client, the "master wallet" had to accumulate a weight of ~250mil before the first POS block; our current "master wallet" is sitting at around ~114.6mil, so we're about halfway there.

To continue pumping out transactions until POS starts (which may be another week or so, as estimated by myself and OCdev) we're going to enable POW indefinitely... At least until the first POS block hits the network, then it will be disabled again. A POW re-enabled release will be coming shortly.

If you all didn't know, coffeecoinguild.com has its own members-only trollbox. If you ever need to speak to me directly, sometimes you can find me there, username Profitus.Zero. Feel free to drop in to say 'hello'. It still needs to be tested, and feedback is appreciated.

So did PoS kick in already or no? I still have all my coins at Bittrex.

according to my wallet, not yet

but the minting weight is increasing constantly, so i hope it will kick in soon

[xlcus]

Yup, just waiting for PoS working correctly.

BTW, I voted several times today on Mintapl, but it moved slowly 

[wu21456]

Yup, just waiting for PoS working correctly.

BTW, I voted several times today on Mintapl, but it moved slowly 

+1
Hope the PoS can come asap...

[murkster]

Coin exchange done, no dramas, many thanks for the site, made things easy..

[coffeecoin]

Network weight is finally increasing, and the master wallet's already staked 3 times. That's a great sign, but it may still not be staking enough to 100% support the network without POW. I've requested that our block explorer continue to report CFC1 transactions for tracking purposes (for ShareX claims/transactions in particular), so we won't know for sure until the block explorer is switched. With that being said, POW will continue for now.

EDIT: Staked 4 times now.

[kelsey]

yes got a stake on the first 100 coins I mined in the new cfc2....looking good.

[FreebieZoner]

Hi guys, good morning. I have some CFCv1 in Coinnext, how can I proceed to make change to CFCv2??

Coinnext is dead in 3 weeks.

[Sy]

My wallet doesnt sync and yes, i've added those from op - can someone please post some nodes?

[coffeecoin]

My wallet doesnt sync and yes, i've added those from op - can someone please post some nodes?

That's very unusual for it not to sync at all. Did you name the conf file exactly "coffeecoin2.0.conf" and have you restarted the client completely since creating it? My thought is that there could have been a minor detail overlooked

[Youghoor]

My wallet doesnt sync and yes, i've added those from op - can someone please post some nodes?

not having any problem in syncing the wallet, which nodes are you using.

[Sy]

Yes i did restart the client, that's not the first wallet i am running ^^

CoffeeCoin2.0 version v2.0.1.0

Code:

ll .CoffeeCoin2.0/
insgesamt 616
drwxrwxr-x  3 sy sy   4096 Jun 30 08:16 ./
drwxr-xr-x 47 sy sy   4096 Jul  1 16:53 ../
-rw-------  1 sy sy    200 Jun 23 10:19 blk0001.dat
-rw-------  1 sy sy  16384 Jun 23 10:19 blkindex.dat
-rw-rw-r--  1 sy sy     92 Jun 30 08:14 coffeecoin2.0.conf
-rw-rw-r--  1 sy sy     92 Jun 23 12:03 CoffeeCoin2.0.conf
drwx------  2 sy sy   4096 Jun 23 10:19 database/
-rw-------  1 sy sy      0 Jun 23 10:19 db.log
-rw-------  1 sy sy 514067 Jun 30 08:16 debug.log
-rw-------  1 sy sy      0 Jun 23 10:19 .lock
-rw-------  1 sy sy   1238 Jun 30 08:16 peers.dat
-rw-------  1 sy sy  65536 Jun 30 08:16 wallet.dat

coffeecoin2.0.conf should be incorrect since the name is always exactly as the folder but i've created both just to be save

Code:

cat .CoffeeCoin2.0/CoffeeCoin2.0.conf 
addnode=54.235.244.167
addnode=54.235.70.55
addnode=121.215.135.193
addnode=162.250.121.202

Code:

tail debug.log
trying connection 121.215.135.193:16789 lastseen=362308,7hrs
connection timeout
trying connection 54.235.244.167:16789 lastseen=83,8hrs
connection timeout
trying connection 162.250.121.202:16789 lastseen=362308,7hrs
connection timeout
trying connection 54.235.70.55:16789 lastseen=148,9hrs
connection timeout

[coffeecoin]

Yes i did restart the client, that's not the first wallet i am running ^^

CoffeeCoin2.0 version v2.0.1.0

Code:

ll .CoffeeCoin2.0/
insgesamt 616
drwxrwxr-x  3 sy sy   4096 Jun 30 08:16 ./
drwxr-xr-x 47 sy sy   4096 Jul  1 16:53 ../
-rw-------  1 sy sy    200 Jun 23 10:19 blk0001.dat
-rw-------  1 sy sy  16384 Jun 23 10:19 blkindex.dat
-rw-rw-r--  1 sy sy     92 Jun 30 08:14 coffeecoin2.0.conf
-rw-rw-r--  1 sy sy     92 Jun 23 12:03 CoffeeCoin2.0.conf
drwx------  2 sy sy   4096 Jun 23 10:19 database/
-rw-------  1 sy sy      0 Jun 23 10:19 db.log
-rw-------  1 sy sy 514067 Jun 30 08:16 debug.log
-rw-------  1 sy sy      0 Jun 23 10:19 .lock
-rw-------  1 sy sy   1238 Jun 30 08:16 peers.dat
-rw-------  1 sy sy  65536 Jun 30 08:16 wallet.dat

coffeecoin2.0.conf should be incorrect since the name is always exactly as the folder but i've created both just to be save

Code:

cat .CoffeeCoin2.0/CoffeeCoin2.0.conf 
addnode=54.235.244.167
addnode=54.235.70.55
addnode=121.215.135.193
addnode=162.250.121.202

Code:

tail debug.log
trying connection 121.215.135.193:16789 lastseen=362308,7hrs
connection timeout
trying connection 54.235.244.167:16789 lastseen=83,8hrs
connection timeout
trying connection 162.250.121.202:16789 lastseen=362308,7hrs
connection timeout
trying connection 54.235.70.55:16789 lastseen=148,9hrs
connection timeout

As far as the conf file being the same name as the folder, I don't have a single wallet with that characteristic. I create a custom folder on a my data harddrive for the blockchain and conf, (since my main OS harddrive is a relatively small SSD) then launch the shortcut with the argument -datadir=<directory>. The default name of the conf file is embedded in the code, although I can't remember where off the top of my head.

Here's a getpeerinfo dump from the master wallet. Hope it helps!


[
{
"addr" : "188.165.3.223:16789",
"services" : "00000001",
"lastsend" : 1404314212,
"lastrecv" : 1404314212,
"conntime" : 1404314174,
"version" : 60503,
"subver" : "/CoffeeCoin2.0:1.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 41338,
"banscore" : 0
},
{
"addr" : "74.105.241.83:16789",
"services" : "00000001",
"lastsend" : 1404314176,
"lastrecv" : 1404314211,
"conntime" : 1404314175,
"version" : 60503,
"subver" : "/CoffeeCoin2.0:1.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 41338,
"banscore" : 0
},
{
"addr" : "178.201.97.60:16789",
"services" : "00000001",
"lastsend" : 1404314211,
"lastrecv" : 1404314211,
"conntime" : 1404314175,
"version" : 60503,
"subver" : "/CoffeeCoin2.0:1.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 41338,
"banscore" : 0
},
{
"addr" : "128.72.141.165:16789",
"services" : "00000001",
"lastsend" : 1404314212,
"lastrecv" : 1404314211,
"conntime" : 1404314187,
"version" : 60503,
"subver" : "/CoffeeCoin2.0:1.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 41339,
"banscore" : 0
},
{
"addr" : "188.0.75.112:16789",
"services" : "00000001",
"lastsend" : 1404314189,
"lastrecv" : 1404314211,
"conntime" : 1404314187,
"version" : 60503,
"subver" : "/CoffeeCoin2.0:1.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 41339,
"banscore" : 0
}
]

[Sy]

It's working now, one of the new nodes connected and it's really .CoffeeCoin2.0/CoffeeCoin2.0.conf on linux - might want to update your first post since it won't work the other way around

Code:

addnode=188.0.75.112
addnode=128.72.141.165
addnode=178.201.97.60
addnode=74.105.241.83
addnode=188.165.3.223

[skeet]

Got all my SAT's exchanged to SAT2 fast and simple through the "manual" website.....Thanks DEV, GREAT WORK !!!!

Good for you but this is not Saturncoin ANN thread. 

[coffeecoin]

It's working now, one of the new nodes connected and it's really .CoffeeCoin2.0/CoffeeCoin2.0.conf on linux - might want to update your first post since it won't work the other way around

Code:

addnode=188.0.75.112
addnode=128.72.141.165
addnode=178.201.97.60
addnode=74.105.241.83
addnode=188.165.3.223

Aha, you learn something new everyday I'm glad you got it working, and I updated the OP.

[quasimodo]

Why my wallet does not stake?

Your Weight is 2803845

Network weight is 75106

Expected time to earn reward is 0 second.