Dev has moved on..
BH= 640302
BH= 640302
Thanks
www.megahash.co.uk
So is no one taking this over and moving it forward ?
Topic: The Cypherfunks[FUNK]: a coin for a global band! Talking v2. Join! 80+ songs - page 37. (Read 148726 times)
December 26, 2016, 09:17:20 AM
Thanks
www.megahash.co.uk
So is no one taking this over and moving it forward ?
December 24, 2016, 11:11:48 AM
About 20% of the coins which I withdrew from Cryptopia, were burned, but that's sucess after I've had them in my wallet!!!
December 24, 2016, 10:39:41 AM
Dev has moved on..
BH= 640302
BH= 640302
December 24, 2016, 10:32:46 AM
Currently looking for a new dev.
Where is Dev gone ?
I dont mind helping out.
What blk are we all on now, if my pool matches yours height I will switch it back on
December 24, 2016, 10:20:51 AM
100+ MH/s is what the attacker had towards the end. I'm not sure what it was during the height of the attack.
December 24, 2016, 10:13:48 AM
I think the attacker was a mining pool that is now gone. They didn't have that high a hashpower only about 100 MH/s.
100 MH/s,No enough to attack,In normal ,Funk have about 200-600MH/S, If attack 20 days,The attacker hash rate must over 4000-12000MH/S, December 24, 2016, 09:54:39 AM
I think the attacker was a mining pool that is now gone. They didn't have that high a hashpower only about 100 MH/s.
December 24, 2016, 09:41:08 AM
It seems things are working ok now and the attack is over, but we will have to keep an eye out for future attacks and consider options to make it harder to attack the Cypherfunks FUNK mining. Pandacoin had a similar problem in it's past, we were able to add mining hash power when we noticed attempted attacks but ultimately switching to a pure Proof of Stake algorithm for mining is what we decided on.
I will continue to mine with what I have for scrypt mining hardware and can rent some extra power if we notice an attack is being attempted again. Please consider helping us test voting using FUNK http://cryptodepot.org/funk-vote-page/
We have also been working on having a Electrum server and wallet clients for the Cypherfunks FUNK but had some trouble, possibly due to the attack.
I will continue to mine with what I have for scrypt mining hardware and can rent some extra power if we notice an attack is being attempted again. Please consider helping us test voting using FUNK http://cryptodepot.org/funk-vote-page/
We have also been working on having a Electrum server and wallet clients for the Cypherfunks FUNK but had some trouble, possibly due to the attack.
1 ,Add mining hash power,It is unuseful.The attacker have very high hash rate
2,Proof of Stake algorithm,In normal ,Pos coin low value
I think,Keep pow ,Add check point ,Such as feathercoin,Exchange increase deposite confirm number,It will easy to resolve the problem.,
Cryptopia maybe lost more coin ,Over 20 days transactions changed by attacker
December 21, 2016, 12:34:51 PM
It seems things are working ok now and the attack is over, but we will have to keep an eye out for future attacks and consider options to make it harder to attack the Cypherfunks FUNK mining. Pandacoin had a similar problem in it's past, we were able to add mining hash power when we noticed attempted attacks but ultimately switching to a pure Proof of Stake algorithm for mining is what we decided on.
I will continue to mine with what I have for scrypt mining hardware and can rent some extra power if we notice an attack is being attempted again. Please consider helping us test voting using FUNK http://cryptodepot.org/funk-vote-page/
We have also been working on having a Electrum server and wallet clients for the Cypherfunks FUNK but had some trouble, possibly due to the attack.
I will continue to mine with what I have for scrypt mining hardware and can rent some extra power if we notice an attack is being attempted again. Please consider helping us test voting using FUNK http://cryptodepot.org/funk-vote-page/
We have also been working on having a Electrum server and wallet clients for the Cypherfunks FUNK but had some trouble, possibly due to the attack.
December 20, 2016, 07:57:09 PM
Currently looking for a new dev.
December 20, 2016, 07:46:30 PM
Where dev?
December 20, 2016, 04:56:31 PM
Stop mining FUNK on Hashnova there is 150+ Mh/s there:
IMPORTANT: Everything has an end.
Hashnova is closing, due to lack of time to continue develop and administer this project!
Timeplan as following:
Stratum will close 2016-12-22
Pool will be open for withdraw all coins until 2017-02-28, after that date, pool will completly close, we will lower the threshold for minimun payment to get all users able to withdraw all balances
BALANCES NOT WITHDRAWED UNTIL 2016-02-28, WILL BE SEEN AS A DONATION
IMPORTANT: Everything has an end.
Hashnova is closing, due to lack of time to continue develop and administer this project!
Timeplan as following:
Stratum will close 2016-12-22
Pool will be open for withdraw all coins until 2017-02-28, after that date, pool will completly close, we will lower the threshold for minimun payment to get all users able to withdraw all balances
BALANCES NOT WITHDRAWED UNTIL 2016-02-28, WILL BE SEEN AS A DONATION
December 20, 2016, 04:21:45 PM
Message from NovaExchange:
Cypherfunks has been target for an 51% attack the latest days, we have our eyes on that coin, and when attack is stopped and chain seems normal for some days, FUNK will be enabled again, it's too big risk that users got their deposits / withdrawals orphaned under this attack.
Regards
Novaexchange Support Team
I have started up my node and after adding the original nodes I was able to sync the original chain and it seems to be working now.
Add these nodes to a .conf file:
addnode=149.202.102.73:33666
addnode=149.210.168.71:33666
addnode=167.160.36.126:33666
addnode=192.169.6.147:33666
addnode=2.222.221.132:33666
addnode=212.116.78.90:33666
addnode=54.84.124.41:33666
addnode=72.241.235.204:33666
addnode=91.121.67.93:33666
addnode=94.233.103.92:33666
addnode=95.94.112.172:33666
addnode=97.89.166.196:33666
addnode=98.115.147.74:33666
Also running a node helps (add above the nodes in the .conf file):
listen=1
server=1
daemon=1
rpcuser=username
rpcpassword=pass
rpcport=33666
rpcallowip=127.0.0.1
change the rpcuser and rpcpassword fields
to something only you know
Cypherfunks has been target for an 51% attack the latest days, we have our eyes on that coin, and when attack is stopped and chain seems normal for some days, FUNK will be enabled again, it's too big risk that users got their deposits / withdrawals orphaned under this attack.
Regards
Novaexchange Support Team
I have started up my node and after adding the original nodes I was able to sync the original chain and it seems to be working now.
Add these nodes to a .conf file:
addnode=149.202.102.73:33666
addnode=149.210.168.71:33666
addnode=167.160.36.126:33666
addnode=192.169.6.147:33666
addnode=2.222.221.132:33666
addnode=212.116.78.90:33666
addnode=54.84.124.41:33666
addnode=72.241.235.204:33666
addnode=91.121.67.93:33666
addnode=94.233.103.92:33666
addnode=95.94.112.172:33666
addnode=97.89.166.196:33666
addnode=98.115.147.74:33666
Also running a node helps (add above the nodes in the .conf file):
listen=1
server=1
daemon=1
rpcuser=username
rpcpassword=pass
rpcport=33666
rpcallowip=127.0.0.1
change the rpcuser and rpcpassword fields
to something only you know
December 20, 2016, 10:36:16 AM
Message on cryptopia.co.nz
FUNK / LTC market is paused
Network has forked
FUNK / LTC market is paused
Network has forked
Here are the opinions that we can work on.
1. Keep current algorithm, increase security, adding more nodes and checkpoints.
2. Use POW+POS or POS
3. Merged mining
4. Update algorithm, like Scrypt-N, X15, etc.
5. Multi-algorithm ,like DGB ,MYR
December 20, 2016, 05:05:24 AM
Message on cryptopia.co.nz
FUNK / LTC market is paused
Network has forked
FUNK / LTC market is paused
Network has forked
December 20, 2016, 04:04:15 AM
What can we (community/holders) help with?
Fork and updata wallet is necessary, 
December 20, 2016, 03:21:24 AM
What can we (community/holders) help with?
December 19, 2016, 10:31:05 PM
Well this dosn't look good 40 orphaned in a row now, and my balance has just gone to zero with me not doing anything 
Yes there seems to be some serious blockchain restructuring trouble / Attack
I lost all mining proceeds for DEC but the bigger problem is if the mining can't be trusted It seems someone found a way to always build the longest chain by including old transactions in a new longer chain even after they were confirmed but not exactly sure what is going on yet.
Have been working on a vote page using FUNK to vote and just noticed previous votes that were confirmed have become invalid then the same vote would reappear with a new datetime and hash.
http://cryptodepot.org/funk-vote-page/
51% attack ,we need resolve immediately
December 19, 2016, 09:12:58 PM
Well this dosn't look good 40 orphaned in a row now, and my balance has just gone to zero with me not doing anything
Yes there seems to be some serious blockchain restructuring trouble / Attack
I lost all mining proceeds for DEC but the bigger problem is if the mining can't be trusted It seems someone found a way to always build the longest chain by including old transactions in a new longer chain even after they were confirmed but not exactly sure what is going on yet.
Have been working on a vote page using FUNK to vote and just noticed previous votes that were confirmed have become invalid then the same vote would reappear with a new datetime and hash.
http://cryptodepot.org/funk-vote-page/
December 19, 2016, 11:58:05 AM
Well this dosn't look good 40 orphaned in a row now, and my balance has just gone to zero with me not doing anything
Jump to: