Topic: The Cypherfunks[FUNK]: a coin for a global band! Talking v2. Join! 80+ songs - page 32. (Read 148746 times)
August 31, 2017, 02:12:21 PM
Hash is the easy part... 3 GH/s SCRYPT hanging around waiting, another 5 on the way. So all the infrastructure including servers is there.
August 30, 2017, 09:56:22 PM
Hi guys,
I was checking around a little after Varvarin was pointing his finger here... probably I could be of some help.
Basically the codebase is 2014 which is not a big issue to get it pulled up to date in 2 steps. But what I do see are some critical hard coded issues which could be hard forked out:
- KGW: That thing is actually creating nothing but problems. It is k
That would be fantastic
:)illing performance and opening the door for hoppers.
- re-target time: adding some more issues to the problem above. Miners can just collect coins until the next re-target, jump out and wait for the diff to go back down
Thing is, even if those 2 issues can be forked out, one major problem can't: The KGW part needs to stay and validate blocks during IBD. Due to the extensive calculations and well known C++ performance, blockchain downloads would remain incredibly slow...
There are some more minor issues which are creating additional work when it's ported to new standards, but that should be OK.
I've done one or two migrations from this codebase to latest standards (up to LTC 0.14.2), having mining infrastructure available and always willing to support if friends of my friends are in need ;-)
Greetz
Mike
I was checking around a little after Varvarin was pointing his finger here... probably I could be of some help.
Basically the codebase is 2014 which is not a big issue to get it pulled up to date in 2 steps. But what I do see are some critical hard coded issues which could be hard forked out:
- KGW: That thing is actually creating nothing but problems. It is k
That would be fantastic
:)illing performance and opening the door for hoppers.- re-target time: adding some more issues to the problem above. Miners can just collect coins until the next re-target, jump out and wait for the diff to go back down
Thing is, even if those 2 issues can be forked out, one major problem can't: The KGW part needs to stay and validate blocks during IBD. Due to the extensive calculations and well known C++ performance, blockchain downloads would remain incredibly slow...
There are some more minor issues which are creating additional work when it's ported to new standards, but that should be OK.
I've done one or two migrations from this codebase to latest standards (up to LTC 0.14.2), having mining infrastructure available and always willing to support if friends of my friends are in need ;-)
Greetz
Mike
That would be fantastic
August 25, 2017, 03:02:12 AM
Hi guys,
I was checking around a little after Varvarin was pointing his finger here... probably I could be of some help.
Basically the codebase is 2014 which is not a big issue to get it pulled up to date in 2 steps. But what I do see are some critical hard coded issues which could be hard forked out:
- KGW: That thing is actually creating nothing but problems. It is killing performance and opening the door for hoppers.
- re-target time: adding some more issues to the problem above. Miners can just collect coins until the next re-target, jump out and wait for the diff to go back down
Thing is, even if those 2 issues can be forked out, one major problem can't: The KGW part needs to stay and validate blocks during IBD. Due to the extensive calculations and well known C++ performance, blockchain downloads would remain incredibly slow...
There are some more minor issues which are creating additional work when it's ported to new standards, but that should be OK.
I've done one or two migrations from this codebase to latest standards (up to LTC 0.14.2), having mining infrastructure available and always willing to support if friends of my friends are in need ;-)
Greetz
Mike
I was checking around a little after Varvarin was pointing his finger here... probably I could be of some help.
Basically the codebase is 2014 which is not a big issue to get it pulled up to date in 2 steps. But what I do see are some critical hard coded issues which could be hard forked out:
- KGW: That thing is actually creating nothing but problems. It is killing performance and opening the door for hoppers.
- re-target time: adding some more issues to the problem above. Miners can just collect coins until the next re-target, jump out and wait for the diff to go back down
Thing is, even if those 2 issues can be forked out, one major problem can't: The KGW part needs to stay and validate blocks during IBD. Due to the extensive calculations and well known C++ performance, blockchain downloads would remain incredibly slow...
There are some more minor issues which are creating additional work when it's ported to new standards, but that should be OK.
I've done one or two migrations from this codebase to latest standards (up to LTC 0.14.2), having mining infrastructure available and always willing to support if friends of my friends are in need ;-)
Greetz
Mike
Hi Mike,
That codebase is as old as moldy crackers now! What you are suggesting is definitely needed. If we could solve some of those serious issues, it would help the whole project incredibly. I can only humbly ask on behalf of the community here for your help. I'm willing to offer any assistance I can provide.
Many thanks for your input.
https://www.youtube.com/watch?v=LsBJ62jSCl0
I want in! Nele & Alex are great and we go back
plus I need a job now. Mike is the finest wallet dev around and legendary miner, just check out the spiffy new EMC2 Core wallet and hash rate
The FUNK Phenomenon Time
August 23, 2017, 12:15:58 AM
Problems with wallet synchronization.
It seems like two weeks from today,
It seems like two weeks from today,
Try adding this nodes to your wallet hopefully it will help you with the syncing problem
addnode=149.202.102.73:33666
addnode=149.210.168.71:33666
addnode=192.169.6.147:33666
addnode=23.94.55.149:33666
addnode=82.200.205.30:33666
addnode=109.105.40.15:33666
addnode=104.200.67.31:33666
addnode=78.248.188.112:33666
August 22, 2017, 11:48:58 PM
Problems with wallet synchronization.
It seems like two weeks from today,
It seems like two weeks from today,
you might need to restart the wallet now and again to prompt syncing
August 22, 2017, 11:43:49 PM
Problems with wallet synchronization.
It seems like two weeks from today,
It seems like two weeks from today,
August 22, 2017, 11:36:23 PM
Quote from: noizer71
Can you give me for free, just 100 funk? Thanks before.
pls re-read my post and check your wallet
August 21, 2017, 06:36:30 AM
hey noizer71 i sent you a few, welcome
FUNK markets
https://www.cryptopia.co.nz/Exchange/?market=FUNK_LTC
https://www.cryptopia.co.nz/Exchange/?market=FUNK_DOGE
https://novaexchange.com/market/DOGE_FUNK/
https://novaexchange.com/market/ESP2_FUNK/
https://novaexchange.com/market/ETH_FUNK/
https://novaexchange.com/market/MOON_FUNK/
https://novaexchange.com/market/LTC_FUNK/
August 20, 2017, 12:07:10 PM
I've asked Nele and Alex to take a look at this thread, the proposed changes, and to discuss it. I'll let you know as soon as I hear from them.
August 20, 2017, 12:01:34 PM
It's probably a good idea. It's a lot of changes so I really have to discuss it with some others, but I will let you know for sure. I'm very excited about this project, and I want to thank you very sincerely for your help.
August 20, 2017, 11:18:47 AM
Fantastic! Let me discuss it with Nele and Alex and we'll go from there.
Alright, let me know if SegWit is OK, that would make life easier if it is.
August 20, 2017, 11:17:17 AM
Fantastic! Let me discuss it with Nele and Alex and we'll go from there.
August 20, 2017, 11:14:09 AM
I'm a little offline for the next 3 days, then on the plane home. Maybe I can start merging it on the flight. Will do some testing first, then let me know the desired HF block and consider it done shortly.
August 20, 2017, 11:03:27 AM
We want to list the coin on Liqui, but before we do that we really need to update the client first.
August 20, 2017, 10:55:15 AM
Hi guys,
I was checking around a little after Varvarin was pointing his finger here... probably I could be of some help.
Basically the codebase is 2014 which is not a big issue to get it pulled up to date in 2 steps. But what I do see are some critical hard coded issues which could be hard forked out:
- KGW: That thing is actually creating nothing but problems. It is killing performance and opening the door for hoppers.
- re-target time: adding some more issues to the problem above. Miners can just collect coins until the next re-target, jump out and wait for the diff to go back down
Thing is, even if those 2 issues can be forked out, one major problem can't: The KGW part needs to stay and validate blocks during IBD. Due to the extensive calculations and well known C++ performance, blockchain downloads would remain incredibly slow...
There are some more minor issues which are creating additional work when it's ported to new standards, but that should be OK.
I've done one or two migrations from this codebase to latest standards (up to LTC 0.14.2), having mining infrastructure available and always willing to support if friends of my friends are in need ;-)
Greetz
Mike
I was checking around a little after Varvarin was pointing his finger here... probably I could be of some help.
Basically the codebase is 2014 which is not a big issue to get it pulled up to date in 2 steps. But what I do see are some critical hard coded issues which could be hard forked out:
- KGW: That thing is actually creating nothing but problems. It is killing performance and opening the door for hoppers.
- re-target time: adding some more issues to the problem above. Miners can just collect coins until the next re-target, jump out and wait for the diff to go back down
Thing is, even if those 2 issues can be forked out, one major problem can't: The KGW part needs to stay and validate blocks during IBD. Due to the extensive calculations and well known C++ performance, blockchain downloads would remain incredibly slow...
There are some more minor issues which are creating additional work when it's ported to new standards, but that should be OK.
I've done one or two migrations from this codebase to latest standards (up to LTC 0.14.2), having mining infrastructure available and always willing to support if friends of my friends are in need ;-)
Greetz
Mike
Hi Mike,
That codebase is as old as moldy crackers now! What you are suggesting is definitely needed. If we could solve some of those serious issues, it would help the whole project incredibly. I can only humbly ask on behalf of the community here for your help. I'm willing to offer any assistance I can provide.
Many thanks for your input.
August 20, 2017, 10:18:26 AM
Hi guys,
I was checking around a little after Varvarin was pointing his finger here... probably I could be of some help.
Basically the codebase is 2014 which is not a big issue to get it pulled up to date in 2 steps. But what I do see are some critical hard coded issues which could be hard forked out:
- KGW: That thing is actually creating nothing but problems. It is killing performance and opening the door for hoppers.
- re-target time: adding some more issues to the problem above. Miners can just collect coins until the next re-target, jump out and wait for the diff to go back down
Thing is, even if those 2 issues can be forked out, one major problem can't: The KGW part needs to stay and validate blocks during IBD. Due to the extensive calculations and well known C++ performance, blockchain downloads would remain incredibly slow...
There are some more minor issues which are creating additional work when it's ported to new standards, but that should be OK.
I've done one or two migrations from this codebase to latest standards (up to LTC 0.14.2), having mining infrastructure available and always willing to support if friends of my friends are in need ;-)
Greetz
Mike
I was checking around a little after Varvarin was pointing his finger here... probably I could be of some help.
Basically the codebase is 2014 which is not a big issue to get it pulled up to date in 2 steps. But what I do see are some critical hard coded issues which could be hard forked out:
- KGW: That thing is actually creating nothing but problems. It is killing performance and opening the door for hoppers.
- re-target time: adding some more issues to the problem above. Miners can just collect coins until the next re-target, jump out and wait for the diff to go back down
Thing is, even if those 2 issues can be forked out, one major problem can't: The KGW part needs to stay and validate blocks during IBD. Due to the extensive calculations and well known C++ performance, blockchain downloads would remain incredibly slow...
There are some more minor issues which are creating additional work when it's ported to new standards, but that should be OK.
I've done one or two migrations from this codebase to latest standards (up to LTC 0.14.2), having mining infrastructure available and always willing to support if friends of my friends are in need ;-)
Greetz
Mike
August 20, 2017, 08:40:44 AM
I guess I should try to be more clear. Simon is definitely still way too busy with ETH to focus on the Cypherfunks. He's simply given me permission to redesign the website with updated information. Nele, myself, and some other guys from GameCredits are dedicated to building a platform for Cypherfunks. That's what is happening behind the scenes presently.
Long live the FUNK!!
Long live the FUNK!!
August 19, 2017, 11:43:46 AM
Here is a quick update. I've received permission from Simon (original dev) to update the website, and a platform around the Cypherfunks will be developed. I'll post more details soon!
All hail The Simon
I guess ETH was too much fun until now, we welcome you.
August 19, 2017, 08:29:09 AM
Here is a quick update. I've received permission from Simon (original dev) to update the website, and a platform around the Cypherfunks will be developed. I'll post more details soon!
August 19, 2017, 01:53:57 AM
Look like thing are going to start happening
I was wondering how long until FUNK is back at sub 6 litoshi ... *waves to Nele*
Jump to: