Ethereum (ETH) - POW/POS - Ethash
Ethereum (ETH) Release Wallet and Mist v 0.9.3
Ethereum (ETH) Release Geth v1.7.3 (Weir)
Geth v1.7.3 (Weir) is a maintenance release to address various issues in our previous releases, most importantly along log filtering and replacement transaction propagation. The release also contains a few developer niceties. Please see compatibility section below!
- Roll out v2 of the
leslight client protocol (#14970, #15367, #15391).
- Insta-mining, zero CPU, clique based PoA developer mode
- Add API endpoint to list modified accounts between two blocks (#15512).
- Gas estimation returns error instead of maxgas if transaction cannot be executed (#15477).
- Improve EVM jump destination analysis for worst case scenarios (#14582).
application/jsonfor HTTP RPC requests (#15220, #15496).
- Private network faucet support Facebook, Twitter and Google+ authentication (#15313).
- Support encrypted SSH keys in the Puppeth network manager (#15443).
- Introduce docker images containing all Ethereum tools (#15467).
- Start shipping Ubuntu Artful Aardvark launchpad packages (#15344).
- Fix log filtering when specifying non-8-multiple starting block number (#15489).
- Fix replacement transaction propagation (#15343).
- Reduce disk overhead on keystore startup (#15526, #15527, #15529).
- Fix occasional Rinkeby chain split by additional fork selection logic (#15470).
- Fix missing commit hash in docker image versions (#15458, #15464).
- All HTTP RPC requests from now on need to have the
Content-Type: application/jsonheader set on them. Geth v1.7.3 will refuse to service requests with no content type headers set (or headers with different content types). This is a security measure to counter a browser CORS circumvention technique.
- Geth v1.7.3 ships with
les/2light client support, which might have harder time finding light servers initially until the server providers upgrade to v1.7.3 too.
For a full rundown of changes, please see the v1.7.3 milestone.
As always, binaries and mobile libraries are available on our download page.
- Roll out v2 of the
Ethereum (ETH) Release pyethereum v2.1.3
Bump version: 2.1.2 → 2.1.3
Ethereum (ETH) Release pyethereum v2.1.4
Bump version: 2.1.3 → 2.1.4
Ethereum (ETH) Release pyethereum v2.1.5
Ethereum (ETH) - Security alert — Chromium vulnerability affecting Mist Browser Beta
Due to a Chromium vulnerability affecting all released versions of the Mist Browser Beta v0.9.3 and below, we are issuing this alert warning users not to browse untrusted websites with Mist Browser Beta at this time. Users of “Ethereum Wallet” desktop app are not affected.
Affected configurations: Mist Browser Beta v0.9.3 and below Likelihood: Medium Severity: High
Malicious websites can potentially steal your private keys.
As Ethereum Wallet desktop app does not qualify as a browser — it accesses only the local Wallet Dapp — it is not subject to the same category of issues present in Mist. For now, it is recommended to use Ethereum Wallet to manage funds and interact with smart contracts instead.
Mist Browser’s vision is to be a complete user-facing bridge to the ethereum blockchain and set of technologies that compose the Web3. The browser paves a significant path for the next Web our ecosystem is proudly building.
Security-wise, making a browser (an app that loads untrusted code) that handles private keys is a challenging task. Over the course of the last year, we have had Cure53 conduct an extensive security audit of Mist, and vastly improved the security of both the Mist browser and the underlying platform, Electron. We’ve promptly fixed found security issues.
But that is not enough. Security in the browser space is a never-ending battle. The Mist browser is based on Electron, which is based on Chromium. Each new Chromium release fixes numerous security issues.
A core problem with the current architecture is that any 0-day Chromium vulnerability is several patch-steps away from Mist: first Chromium needs to be patched, then Electron needs to update the Chromium version, and finally, Mist needs to update to the new Electron version.
We’re examining how we could deal with Electron’s not-so-frequent release schedule, to reduce the gap between Chromium versions we use. From preliminary studies, Brave’s Muon (an Electron fork) follows Chromium updates closely and is one potential option. The Brave browser, which also contains a cryptocurrency wallet integration, has a similar threat-model and demands for security as Mist.
An important reminder: Mist is still beta software, and you must treat it as such. The Mist Browser beta is provided on an “as is” and “as available” basis and there are no warranties of any kind, expressed or implied, including, but not limited to, warranties of merchantability or fitness of purpose. Quick security checklist:
- Avoid keeping large quantities of ether or tokens in private keys on an online computer. Instead, use a hardware wallet, an offline device or a contract-based solution (preferably a mix of those).
- Back up your private keys — Cloud services are not the best option to store it.
- Do not visit untrusted websites with Mist.
- Do not use Mist on untrusted networks.
- Keep your day-to-day browser updated.
- Keep track of your Operating System and anti-virus updates.
- Learn how to verify file checksums (link).
Lastly, we would like to thank the security researchers that worked hard on reproducing and making invaluable submissions through the Ethereum Bounty program.
If you need further information, get in touch here: mist[at]ethereum dot org.
[We’ll update this post as the situation evolves].
@evertonfraga Mist Team
Bump version: 0.1.0-beta.6 → 0.1.0-beta.7
Ethereum (ETH) Release pyethereum v2.3.0
Bump version: 2.2.0 → 2.3.0
Ethereum (ETH) Release Python - EVM v0.2.0-alpha.8
Bump version: 0.2.0-alpha.7 → 0.2.0-alpha.8
Ethereum scalability research and development subsidy programs
The Ethereum community, key developers and researchers and others have always recognized scalability as perhaps the single most important key technical challenge that needs to be solved in order for blockchain applications to reach mass adoption. Blockchain scalability is difficult primarily because a typical blockchain design requires every node in the network to process every transaction, which limits the transaction processing capacity of the entire system to the capacity of a single node.
There are two main paths to improving blockchain scalability. The first (“sharding”) involves creating better-designed base-layer blockchain protocols, which still maintain most of the desired decentralization and security properties of a blockchain that we see in the simple designs available today but only require a small percentage of nodes to see and process every transaction, allowing many more transactions to be processed in parallel at the same time. The second involves creating “layer 2” protocols that send most transactions off-chain and only interact with the underlying blockchain in order to enter and exit from the layer-2 system and in the case of attacks on the system.
We view the two strategies as complementary with each other and we believe in supporting a multi-pronged strategy toward Ethereum scalability that engages both strategies and treats them as complementary with each other.
Technical reading materials on Ethereum scalability technologies
- Sharding FAQ: https://github.com/ethereum/wiki/wiki/Sharding-FAQhttps://github.com/ethereum/research/wiki/A-note-on-data-availability-and-erasure-coding
- Sharding preliminary spec: https://github.com/ethereum/sharding/blob/develop/docs/doc.mdhttps://www.youtube.com/watch?v=Yo9o5nDTAAQ&feature=youtu.be&t=7h55m33s
Examples of existing layer-2 systems:
- Plasma: http://plasma.io/http://www.jeffcoleman.ca/state-channels/
- Raiden: https://raiden.network/101.htm...
With the Ethereum blockchain reaching 1 million transactions per day, and both Ethereum and other blockchain projects frequently reaching their full transaction capacity, the need for scaling progress is becoming more and more clear and urgent. To that end, in addition to ongoing and upcoming work that is happening on scalability internally, we are starting two experimental subsidy schemes that we hope will empower more independent teams to collaborate with the Ethereum Research team’s base-layer scalability research and development efforts as well as building independent layer-2 projects that can tie into and improve Ethereum’s scalability.
Independent teams of developers, companies, and university and academic groups are all welcome to apply; we recognize that different types of applicants may require different formats and processes and we are willing to be flexible to accommodate individual teams’ needs.
Sharding client subsidy program
Over the last few months, development on sharding has picked up quickly. A specification for an initial prototype is close to finalized, with a roadmap that allows it to be slowly introduced into Ethereum, first as a “loosely coupled” sidechain anchored into the Ethereum base chain through a “validator manager contract”, later introducing tighter and tighter integration with the Ethereum base chain over time. A reference implementation is being built in python on top of Py-EVM, and a testnet in python is not too far away.
And in this next step, we want you to be involved. We want the Ethereum sharding testnet, and later sharding mainnet, to be a multi-client ecosystem right from the start, with the Ethereum Foundation not supporting any single privileged production implementation. The Ethereum Foundation-funded research team will continue to build an implementation in python and possibly other languages, but this is intended as a reference and proof of concept first and foremost. While we aim to continue to focus heavily on research and specification, we do not want to ultimately “win” the competition for which client gets the most actual users once the network goes live.
Instead, the Ethereum Foundation will be making subsidies available to independent groups in the community that want to help build an implementation and participate in the sharding testnets and mainnet. These payments are NOT intended to be sources of substantial profit to recipient organizations; they are rather intended to cover some of the costs involved, with the understanding that anyone who participates in the scheme will have access to a unique opportunity to participate in Ethereum 2.0 development, with close collaboration with core Ethereum researchers, and be part of the development of one of the first clients that will be available when the sharding mainnet goes live.
This will take the form of a specialized program, which will exist alongside more general grant program that the Foundation will release soon. Subsidy amounts of $50,000 up to $1,000,000 will be available, and possibly more for highly successful projects; the size of the subsidy will take into account the quality of the team, the scope of the proposed implementation, and the progress of the project over time. Participants will interact closely with the core research team, and will have a key role in shaping the final specification that gets developed over the course of implementing the spec and running the test networks.
Layer-2 scalability solution subsidy program
There has been a large number of independent proposals recently for how blockchains such as Ethereum can be scaled up through second-layer protocols. We recognize and appreciate that developers and researchers are excited about researching and implementing technologies in this area, and that many teams want the freedom to conceive and build out their own design that incorporates their own ideas. We want to offer an opportunity for such teams to exercise their creativity and build out their scalable blockchain proposals, all while staying within the Ethereum family.
To that end, we are announcing a subsidy scheme for projects that are building scalability and latency-reducing “layer 2” platforms that live on top of Ethereum, benefitting from the Ethereum blockchain’s security as a base layer and interoperability with the greater Ethereum community and platform.
Like the sharding client scheme, this will take the form of a specialized grant program, and subsidy amounts of $50,000 to $1,000,000 will be available depending on scope, scale and quality. The subsidy may be available even if the project has an independent business model, or funding from potential other sources in the Ethereum community, though we will prioritize funding projects that otherwise lack ability to sustain themselves, and it absolutely must be the case that the work funded is open source from end to end and provides a common good to the Ethereum ecosystem.
Targets for funding include efforts at developing high-quality implementations of existing known layer-2 scaling strategies (eg. state channels, Plasma), as well as researching and developing new ones.
Both of these programs are in a very early stage, and grants will be initially decided at the discretion of Ethereum core leadership. Details, including the terms, conditions and schedules under which payments will be made may change as the result of our initial experience with program participants, and we expect the program to solidify and expand over the course of the year.
Note also that though the payments from these collaboration programs are much higher than those that we have made from our previous grant programs, these payments come with a much higher expectation of focus and quality. We are targeting skilled teams with either direct experience in the Ethereum or blockchain space, or experience in the broader fields of mechanism design, distributed systems or cryptography, as well as software engineering. The programs are also highly targeted at sharding clients and layer-2 scaling solutions; this is NOT a general-purpose grant program. That is still being developed, and details will be released as soon as they are ready.
How to apply
The first step is to send an email to [email protected], with the following information:
- Official name of project, applicant and core developers
- Further information on the team, including previous activity if any in the Ethereum or blockchain space or distributed systems, mechanism design or cryptography
- Proposal and impact on scalability
- Estimated timeline for development milestones and completion, request for grant amount and estimated total overall budget
If we’re sufficiently interested, we’ll proceed from there with requests for further information.
Bump version: 0.1.0-beta.10 → 0.1.0-beta.11
Ethereum (ETH) Release Python - EVM v0.2.0-alpha.9
Bump version: 0.2.0-alpha.8 → 0.2.0-alpha.9