Login to get your referral link.
16,623
Lunam Points
So first a few history. We have already covered a little what to expect from frontier in the Ethereum launch process The blog post and Gav gave us a Complete preview of the state of the development effort. You can also read on some of the current safety work, Including the bug bonus system. The Bug Bounty program has found my favorite bug so far: Jonas Nickdiscovery You can send a negative payment to someone who makes the value of their account to yours!
As Bug Bounty finds Go, an absolute gem. Well played!
GAV has a new blog article describing a little more what the thorny end of the development process looks like: Creation of a precise specification for Ethereum, keeping three different implementations in synchronizationRather than having a canonical implementation which implicitly defines the specification of the protocol and with which other versions then become compatible with the Bug-For-Bug. This is a fairly difficult and in -depth approach to assemble a system, and it is worth reading to obtain a flavor of the way in which engineering work takes place.
To date, you should have a fairly good idea of what the development process and disparate work threads look like that are woven together in the version. So let’s talk about what must really do the border by here.
There is Four specific challenges So that we meet in Frontier.
Two of them, mining and exchange are partnership efforts: people must take our software and execute it, in concert with their own tools in certain cases, to provide services as part of the ecosystem. Remember that we are launching an ecosystem, not just a product: everything is part of this ecology. Each of these aspects of the release process must operate, both in itself and with others so that the ecosystem really obtains an appropriate test.
Furthermore:
Reasonably good progress is underway on all fronts. Rather than giving you an release date, then risking this under pressure to respect this date, something will pass through the shortcomings that another day of work would have succeeded, we will check the articles in the publication process as and when. This will allow you to have an idea of the distance from the launch that we are a given day, without us essentially having to assume how much this will take, will publish our supposition, then hope that we can make reality on the calendar: as we have already said, it is a process not focused on security and not planned. We can make this process that is quite transparent, and provide summary information so that you do not have to look at the benchmarks – but we prefer to get you into the process so that you understand what is going on and how the work goes rather than giving you a global date and making you guess on the real state of work. We believe that this approach is more transparent, better suited to a development process funded by crowdfund, and overall simply more realistic.
If you want to see the current state of play, Jeffrey Wilcke (Customer in advance on GET 
and the Amsterdam hub) has a Go Customer Issue Tracker for Frontier.
This broadcast is the best reference for the border version: at the moment, 10 closed numbers, 26 open. New problems will be raised, and of course, the number of problems is only a very loose proxy for “ship’s time”, but the work done is the best indicator, so look there if you want to predict.
Please note: that does not mean that we are running “Valve time“(Even if the time of the valve produces spectacular products!) We have open development processes, you can see the code during writing, download the latest branches, participate in tests. It is not hidden behind a wall of corporate public relations. But we are running on “the release of innovative software with huge security processes”, and plan the estimate for things that have never been financed to the Convention which cannot help help to ensure that the benefit of the service of the service of the service of the service of the service of the service of the service of the service of the service of the performance of the service service Service for taking it that is just in the medium and long term, rather than being under constant market pressure for the next quarter figures.
We will say this: there will be a notice at least two weeks before everything is put online. You will get a lot of news from blog articles, you will see the number of problems drop, and we will start to say positive things about the comments of the security audit, etc. We will keep you in the loop!
What about the list of features? We have largely examined this in the post of the launch processes, but to repeat Frontier Will …
In short, we do everything possible to make frontier a safe place to test Ethereum with real value, but we also greatly discourage people from using Ether on the frontier network that they do not want to lose.
Frontier is largely intended for people who write and test tools for mining and exchanges, and perhaps some of the most robust DAPP developers. This is not a general version with which we expect ordinary users to interact at all, although you can download a customer and use a little ether simply because you can. The show really starts at Homestead, and we will have more news on the features of Homestead later
No more news as I have and continue to look at the sky!
post url: https://altcoin.observer/arrive-at-the-border-ethereum-foundation-blog/