Hi will you have pow here ,when yes what algo and when launch ?

is anybody still working on the new website?

I've became a father today! Little Michael came to our (crypto driven) world. I don't know why but I felt I need to share this with you all guys! Happy XEL and new life!

I know this is big offtop but I thought it's big news for all of us that new crypto-sick child is aware of the world .

News from my own perspective:

I'm working on XEL PR website. I hope I'll deliver it soon. It will be not CMS but all source will be on github/bitbucket. So anyone who want to update content will have free will (pull requests). Full open source.

Just short update from me.

I'm 24h on foot without sleep. I'm going to bed. Good night for all XEL freaks.

So EK,the winner "idea" be used in elastic now?

Whole package arrives as promised on weekend, including a full documentation and in fully operable state.
The roadmap was reorganized a bit, but (from my side) everything went (and goes) as planned.

When does the token get released? And may I know what's the ICO price?

I think
a) that it is sweet to see that my first "idea" was not so bad after all
and
b) that seems hard to beat
and last but not least
c) that I hope to get the one or another improvement suggestion from you, even after the contest ist over and we have seen this method "in action" in the upcoming 0.9.0 testnet  

Hunterminercrafter:
Largest error: 1.89787520814

L'oracle (PM submission from 07:42:50 PM, someone can verify this in my account if wanted):
Largest error: 1.89720766492

My own one (shame on me)
Largest error: 5.31689202348

VeryNewMember:
Largest error: 5.9709180146

Here, all algorithms in zipped form. Change the first line in tester.py to evaluate a specific submission:
http://www.xup.in/dl,17161517/retarget_algorithms.tar.gz/

Does that seem correct so far?
Unbelieveable, how close the two best submissions were.

If everyone agrees with the result, I would need loracle's BTC address to get rid of my hard earned BTC. 

Is it possible again to run a public testnet / testnode ?

Last time I tried the blockchain couldn't downloaded from the seednodes.

Regards

The new testnet only makes sense when there is at least one super node online. Otherwise, you cannot submit any work at all.
But what is the screenshot about?

Status update coming soon ;-) This weekend I have enough time to summarize everything I have done so far (in our road map) and set up everything so you can try out. It has been a pretty "travellish" week with a lot of offline time.

I see it this way - and this is just my personal view: A decentralized project does not need a leader, does not neet a company and does not need a foundation. Futhermore, a well programmed decentralized project doesn't need anyone, who has more to say than others or takes the responsibility for either man power or planning decisions.

That's why I love decentralization and why I hate crypto companies. I would have never gotten involved in any of the other projects, who first think to form a company (for the image of course) and then start working in some old fashion structures.

But go ahead, it's a free world, why not making a foundation. It's just that I don't want to enter ... but who am I to decide anything  

Now, I am getting back to work .. not because a boss tells me to, but because it is pure fun! Yet, I am not saying that getting rewarded is a bad thing! Everyone got to pay his bills.

Hi Community,

I am writing you to give you a short overview of what we have done so far, why we have done it, and what (from our point of view) still has to be done - and when. I have been moving to a new town in the last days, so

First of all, we had a last-minute idea - the idea of introducing so called super nodes. The reasons were:

1. Since earlier everyone had to verify work, we were very limited: we had very strict constraints regarding the complexity and memory requirement of work packages, simply due to the reason that the weakest node still has to be able to verify everything in a reasonable amount of time. Otherwise, netsplits or node shootdowns would be possible with complex long running tasks. With super nodes we are more flexible: we can set strict requirements that a super node's hardware has to meet and so can allow programs that run longer and use more memory.
Supernodes are basically nodes that do the verification and have no incentive to cheat due to a huge deposit. Contrary to other "well hyped solutions" we do not rely on trust at all ... all calculations and decisions that the super nodes perform can be publicly verified by anyone. For example by the so called guard nodes. These are nodes that randomly cross-check a small fraction of jobs. If they detect that a super node lied, its deposit gets forfeited.

2. Also, earlier a bug in the implementation (causing an infinite loop for example) could halt the whole network since every node is execution the task. Now, the network is safe from this. Also, the super node software will have emergency stop mechanisms that would prevent bugs to crash anything. Again, this design has several benefits here. It's better if one supernode freezes for 15 seconds before it detects the anomaly than if every node in the network freezes for 15 seconds.

3. Also, and this is a PR benefit, the earlier design effectively executed foreign code on the own hardware. While it's super safe due to Elastic PL's nature (our own programming language that does not allow to program anything dangerous), managers who want to use Elastic in their commercial setting might get scared. Now, nobody but the supernodes has to execute anything.


So where are we?
--------------------

We have the code base done that incorporates the new logic into the core client. The supernode functionality is there (except one little detail still missing - the guard node logic). And we have the miner done which - since super nodes and miners execute the same code - can be used for both.

What is missing with deadline dates
----------------------------------------

The following packages are still missing and are planned (not promised) to be finished as follows (London time):

09.02.2017 - The core package with guard logic is finished and goes into code-review mode
12.02.2017 - The supernode extension was added to the miner so that it can be used to verify work of others
13.-14.02.2017 - I am offline
17.02.2017 - Guard node software is finished. Parallely, everything goes into testnet mode for heavy testing
18.02.2017 - Open discussion round here, about how things are working out and specially about the retargeting algorithm that we currently have (there were ideas how to get rid of it)
18-24.02.2017 - Grace period to fix problems that we found in the test net
26.02.2017 - I will have written all details about the system down (both technically and non technically) for those guys of you, who are responsible for the PR parts (website, video, whatever)
27.02.2017 - Last discussion here in the thread
28.02.2017 - Milestone freeze, first ready-to-use version should be finished by then. I (and all the others that work on the code) am/are just (an) interested code monkey/s who love/s fascinating tech. We will not launch anything, we just give the code to the community, so if the community thinks the system (that we suggested) is good, just launch it yourself by using it! Remember: we are doing it for you guys, and not to run a company or something by ourselves. Just do with it whatever you like.

Disclaimer
----------------------------------------
We do not run anything, we do not take responsibility for anything. We code because we love coding, and if in doubt just suggest the appropriate changes and we can figure things out. Nobody forces anyone to use anything, and nobody promises anything. We code as good as we can, ... to reduce the likelihood of bugs (which always may or may not occur) we would appreciate to get more eyes on the code. Also: if you think you can do it better ... then just do it!

After everything works out, I am sure we can think about new cool features that pop into our heads.

I am setting up some testnet nodes today or tomorrow, so we can test the super node approach. But before we can test them, we need to get the super node software (the verifier or however we want to call it) done - we work with two people on it and it should be finished soon.

That doesn't mean that we cannot launch the next generation of the testnet before though ;-) it's just that we can't test the work distribution / verification mechanism without this software.

@EK, When do you want to deploy project to GitHub ?
I am following on it.

The supernode infrastructure (so basically the core client) is basically done, I try to keep up with the inofficial deadline of tomorrow.
However, like we said earlier, new TODOs may arise and so far, the one TODO that is still open is getting the "supernode verifier" done. Don't worry, it's not a big deal because it will be just integrated into the miner.

Let me quickly check the message you're referring to!

I'm in the middle of the next job switch. I hope that I'll negotiate 3/4 of full time. If that will happen till 1st of february I can take on my responsibility to create XEL website.

BUT

I need materials
I need texts
I need Q&A; I need FAQ
I need content overall

WIKI isn't enough

I can create a nice, secure, relabile website but I need @EK/@coralreefer brains to fill it with content.

@EK, I know you don't answer to PMs but I'll need you in february with your brain and pen.

I think that we also need a forum. If something happen to BCT we are all in deep hole.

I can provide that but I need your brilliant brains to cooperate. Without that website will be nice looking, empty place.

Status Update:
I will be finished with all my open todos by the last day of January. It might happen that, meanwhile, new TODOs pop up though. Yet, at this moment, I would say we would have a finished product by then.

@coralreefer, I will be finished with the grammar by tomorrow (meaning, I will have caught up with the current state of your miner).
i will then try everything and summarize the "status quo". I cannot write more at this moment, I need to keep working 

See you tomorrow!