Quote from: Varvarin on September 14, 2017, 07:54:14 AM

Quote from: redmeat on September 13, 2017, 09:57:56 PM

Quote from: willdono on September 13, 2017, 05:16:36 PM

Quote from: soundposition on September 12, 2017, 11:54:46 PM

Quote from: HashUnlimited on September 12, 2017, 09:42:29 AM

I'm still hanging around on vacation (or held hostage by a well overpriced hotel like I would call it) but at least I was able to have a good look into the wallet / node code. The upgrade needs to be done in 2 steps, first one to sneak in BIP65 and BIP66 as they are still following Bitcoin's isSuperMajority rule and it wouldn't be worth the effort to change those to BIP9 as well IMO. The required hard forks can take place there as well. Second, we could simply upgrade to the latest version whatever this will be but I guess Litecoin 0.14 codebase is the way to go.

I also agree that the new specifications need to be fixed and frozen before actually getting some code out in the wild. There for feel free to discuss them and get us on thinking, coding and testing ;-)

Hi Mike. After discussing everything with our devs, we have decided not to do any hard forking. The only option for a long term project is to create an ETH token, most likely using the ERC223 token standard. Right now we are working on a killer web design, and our devs are now looking directly at the project.

TSP

Will there be a swap from FUNK coins into said ERC 23 token?

I bought alot of funk because I thought you guys will revive it, I hope there is a swap in place.

That swap has been in the works since ETH came out ... oooh two years ago now Cheesy

I vote to fork into current LTC Core while ETH boys do their ETH thing ... just think of the news twice

... ya know ... the whole point of crypto is open sauce .. which should mean if you can do it, you should do it .. or something like that. Trouble is that sheeple love a good shepherd

Basically the code can be updated without the proposed hard forks as well... It's a matter of a few hours coding and testing. In any case I would vote for the soft forks at least (BIP65, BIB66, CSV, SegWit).

edit: with properly added fixed nodes those bootstrapping issues would disappear, no more .conf file.