Changing the hashing algorithm
-
Love to jump into this topic, I think crypto culture really shows our strengths and weaknesses.
Here’s my 2 cents after getting caught up.
1.) This new switch needs to be announced well ahead of time. 2 Weeks min. If the FTC community needs to help with the transition, thats what we do. I’ll set my GPU’s to do whatever is needed to support the transition.
2.) This opportunity must be synergized. The release of the miner, new wallet, and some PR, all need to be geared towards all GPU miners that hit not too long ago. Making a great GUI for the miner, simple settings on the front end, advanced use on the back end. I think this could double the market cap in a week!
I agree that switching and switching Algo would kill a coin. But, I also think of it this way, GPU owners are the customer, and feathercoin is the supplier. What do our customers want and how can we leverage that to bring more widespread FTC adoption.
-
Hi , ghostlander. I think we have no choice. PoS development. Let’s go.
-
I have been working for months to prove Advanced Averaging, the more I look at this, changing the hashing algorythm is fraught with difficulties and no one has any proof it would work.
Lets get the Anti-multipool fix OUT NOW. That’s what Lizhi and I needs. The multipools are taking the piss and this is discusion is a total irrelevant diversion.
-
Wrapper, this conversation can happen. We have our values and they just need to be set in stone. This is my task. Changing algo is not not going to happen for some time yet.
PoS is something that we should have had in the beginning not now. People have bought into Feathercoin on its current inflation model and putting PoS will break it, unless you want to do 0% PoS which long term would simply be avoided. When you generate a PoS block you loose your coins for 520 blocks while it is confirmed. To do this for nothing would just be avoided.
-
I have been working for months to prove Advanced Averaging, the more I look at this, changing the hashing algorythm is fraught with difficulties and no one has any proof it would work.
Lets get the Anti-multipool fix OUT NOW. That’s what Lizhi and I needs. The multipools are taking the piss and this is discusion is a total irrelevant diversion.
Let’s not mix two problems here.
We have the current problem of multipools messing with hashrates and difficulty to their advantage.
This can be mitigated by implementing advanced averaging and we should implement that as fast as possible.The other problem is, that the upcoming ASICS will lead to a centralization of hashing power to those miners able to afford the high invest for the ASICS.
The second problem is discussed here and for me it is independent to the first one.
So let’s discuss changing the hashing algorithm while implementing advanced averaging.
That way it’s not a diversion, but part of the evolution of feathercoin.
-
In keeping with the theme what about featherscrypt :D
-
sorry I should of read the whole thread someone has said that lol :D
-
Hi , ghostlander. I think we have no choice. PoS development. Let’s go.
Can you do any coding? There is a lot of work ahead, so any help is appreciated.
PoS is something that we should have had in the beginning not now. People have bought into Feathercoin on its current inflation model and putting PoS will break it, unless you want to do 0% PoS which long term would simply be avoided. When you generate a PoS block you loose your coins for 520 blocks while it is confirmed. To do this for nothing would just be avoided.
520 blocks is the PPC way. They merge coin stake and coins generating a stake into a single transaction of two outputs split nearly evenly. It can be made into two separate transactions. Coin stake takes 120 confirmations like FTC coin base and the rest is a regular transaction.
-
What are our values ? Services for everyone .At least not let them starve to death. I think it should be spread around the world. It should not stay in the museum . It requires vitality.So development and growth is the only way.
What is the spirit of the contract ? It is to ensure that the interests of the holders of each.Ensure that everyone can have a future.This is the meaning of existence contract terms.
Every day is a new beginning.Also the end of each day.We need to be responsible for the future, not the past. In the beginning,This is a mistake that we did not choose POS.Now we can not make a second mistake. If the POS in the interests of the holders of each FTC, why do not we do it? Maybe some details of our thinking again, but the main direction can not be wrong.
New algorithm and New difficulty rules is the same goal. Prevent ASICS, will be able to prevent the huge hashing attack. I agree with the new featherscrypt too in PoW.
-
Can you do any coding? There is a lot of work ahead, so any help is appreciated.
Yes. I can. I am willing to pay the greatest efforts.
-
MaxCoin have adopted SHA-3 algorithm . https://github.com/Max-Coin/MaxCoin
Addresses within MaxCoin are almost identical to those in Bitcoin. A MaxCoin address is a base58-encoded hash of a public key and a network identifier, or version. The address also contains a checksum in the final 4 bytes. The encoding can be outlined as follows:
version = 110
hash = RIPEMD160(SHA256(public key))
versioned_hash = concatenate(version, hash)
checksum = substr(SHA3(versioned_hash), -4)
address = BASE58(concatenate(versioned_hash, checksum))This is essentially the same as with Bitcoin except using a single round of Keccak instead of a double round of SHA256 when calculating the checksum.
SHA-3 algorithm code: sph_keccak.h
https://github.com/Max-Coin/maxcoin/blob/master/src/sph_keccak.h
-
Scrypt-Jane uses Keccak and it is the first solution we are going to look at, but we will was look at Blake2 instead of Keccak as it performs faster :P I am looking forward to getting past the coding for the hard fork and working on the new hashing algo. We absolutely need this move as many other Scrypt coins if the want to survive. There is a great darkness coming.
-
Cheers, BLAKE2b . Now it seems that this is a good choice ::)
-
FeatherScrypt (obviously links it to the currency that it evolved from)
You could hint at feathercoin origins, without actually branding it.
Ideas like
Rachis (In biology it’s the central vain or shaft from a feather or leaf)
Or perhaps one of the many feathered creatures of legends.
-
the benefit of using one of the more popular algorithms is that cudaminer already supports them such as Blake2, Scyrpt-Jane amongst others.
-a, --algo=ALGO specify the algorithm to use (default is scrypt)
scrypt scrypt Salsa20/8(1024, 1, 1), PBKDF2(SHA2)
scrypt:N scrypt Salsa20/8(N, 1, 1), PBKDF2(SHA2)
scrypt-jane scrypt Chacha20/8(N, 1, 1), PBKDF2(Keccak)
scrypt-jane:Coin Coin must be one of the supported coins.
scrypt-jane:Nfactor scrypt-chacha20/8(2*2^Nfactor, 1, 1)
scrypt-jane:StartTime,Nfmin,Nfmax like above nFactor derived from Unix time.
sha256d SHA-256d (don’t use this! No GPU acceleration)
keccak Keccak256 as used in MaxCoin
-
BLAKE2b is a better choice than Keccak.
-
BLAKE2b is a better choice than Keccak.
You are right ::)
-
Changing the FTC hashing algorithm, We only have two months time. They come . :-[
-
This is off topic but as the decision is made perhaps the powers that be can consider the following…
tidbit.co.in developed technology that allowed web pages to generate 20 khash per client (great way to “monetize without ads”). Perhaps feathercoin.com could set up a page that a user could put in their public key. Then after logging into the site, (perhaps making use of iframes) the user could continue on browsing the internet.
The object of this would be a no mind way to generate coins but also have a more consistent network. Perhaps this technology could be worked into wallets as well so that just having a wallet would generate FTC…
20KH/s is a performance of a 3GHz AMD quad core running CPUminer on all cores. Why a slower JavaScript miner if one can run a real one? It also smells like a malware.
-
Changing the FTC hashing algorithm, We only have two months time. They come . :-[
We’ll have a solution sooner.
