Ethereum (ETH) - POW/POS - Ethash

  • Ethereum (ETH) dev update - Roundup Q2

    Thanks to all the developers and team leads who contributed to the sections on their projects

    In the last month and a half, the Ethereum network went through a rapid growth in usage, to the point that it now processes as many transactions per second as Bitcoin. To accommodate the increased load, which has on a few occasions reached the network’s full capacity for hours at a time, the community independently came together and miners voted to increase the gas limit to 6.7 million. We at the Foundation have been rapidly putting additional resources toward increasing the efficiency of the network, alongside planning longer-term changes that will greatly increase the network’s scalability.


    • The Ethereum research team came together in Singapore and discussed various topics to do with Casper, sharding and Ethereum protocol economics.

    The pyethereum client has seen a substantial revamp, and version 2.0 has been released. See for download; in Ubuntu you can also do “sudo pip install ethereum”. Additionally, we have implemented experimental versions of:

    Metropolis testing

    Metropolis testing is rapidly moving forward. We are actively seeking additional help with finishing testing. See:

    We have started a substantial cross-client benchmarking effort to identify places that are in greatest need of performance improvement. See some preliminary results for opcode benchmaking in geth here:

    Ethereum core developer meetings #15-#19 took place. Notes and audio/video of the meetings can be found here:

    Mist team

    In May-June, the Mist team had a team meetup: for one week the team had face to face meetings, some members for the first time, in which we sat together to share details on projects we were working on and to talk about the current codebase and future roadmap. While we have a long list of features we are working on, we realized that most of the issues reported on github were related to two main issues: slow synchronization and lost account private keys/passwords. We outlined features that we could implement to help prevent user errors and other related issues, including more options for node switching (including Infura support) and better options for account management (including HD wallets and mnemonic seeds – but with a twist).

    • Many of those new issues require some changes on how the signing process is done to make Mist more independent of Geth, which is being worked on as a standalone signer.
    • We have also done some research on refactoring parts of the Mist codebase to make it more modular and easier to maintain.
    • Victor Maia presented some research on how to make apps load quicker and be more reliable and we are currently testing some of these concepts as either pieces of the main codebase and/or an alternative web-based product.
    • Progress has been made on ENS integration: we have added ENS support to our address component, meaning that any of the apps we have built in meteor (wallet and ens registrar app) will accept a name in any field where it would usually expect an ethereum address. We are also working on making a web component for generic input types for ethereum addresses, so any webapp developer can use an input field with support for ENS, checksum and ethereum identicons. With swarm now using the main net registrar, it also means that Mist will accept ENS addresses on the url as soon as the swarm branch is merged..
    • Swarm integration has been tested and is a lot more stable than it has been even a few weeks ago. We predict it will finally be ready to release soon.


    Web3.js is  coming along well. The new whisper API was recently added to the old 0.x.x and the new 1.0.0 version. Whisper v5 is currently only available in geth and needs to be started using –shh.  We are currently adding swarm.js and finishing the JavaScript account management. If everything goes well, an alpha release will happen soon.

    You can already test the new web3.js 1.0 here:


    We have received several bounty submissions for vulnerabilities in EthereumJS, Solidity and Cpp-ethereum. See the leaderboard for the current stats.

    We now have pyethereum on board on the cross-client blackbox consensus testing in Hive, which continuously performs over 10K tests on each client. See As a lightweight alternative to Hive, we’ve also started a project to perform fuzz testing directly on the virtual machines, starting with Geth, Parity and Python. In the same vein, we’ve also set up an automated AFL-based fuzzing of Solidity.

    In preparation for Metropolis, a benchmarking suite for the Geth EVM has been implemented to ensure that the gas prices for new opcodes and precompiles are within reasonable bounds, so as to not constitute DoS-vectors at a later point.

    EVM 1.5

    The “EVM 1.5” proposals are now EIP drafts for “Subroutines and Static Jumps for the EVM #615,” and “SIMD Operations for the EVM #616”.  Discussion and critique are welcome at the conversations.


    The ethereumJS team is still looking for community contributors Intro to Core Development with Ethereumjs-vm” has been released.

    Light Client

    New algorithms have been designed and implemented in order to improve log searching performance in the next version of the LES protocol. Promising R&D work has been done toward achieving quick and trustless initial syncing without hardcoded checkpoints. We have put some efforts into finalizing the topic discovery protocol, which helps clients to find suitable LES servers as it is currently a somewhat weak point in the experimental light client service.


    The main Remix feature in the last month is the alpha release of Remixd:

    Formal Verification

    The progress in the eth-isabelle project was mostly from external contributions. In particular,  the better separation logic tactics, which were externally contributed allow much shorter proofs about Ethereum contracts.

    • Better separation logic tactics (contributed)
    • Coq build fixed, and added in the continuous integration
    • Removing unmaintained files, and `Annotation` structure not needed anymore (PR pending)
    • Running Blockchain Tests (in progress; ecdsa recover implementation in OCaml wanted).


    • The compiler is generating bytecode for all initial examples
    • Syntax perfection following community feedback
    • End-to-end testing of the compiler (in progress)


    The Solidity project has been quite active in the last months, although most of the updates is not yet directly visible on the user side. We saw a lot more engagement by the community and now have volunteers regularly contributing both to the core code as well documentation including translation, mainly into Spanish.


    We added a feature that allows export of the full abstract syntax tree with all type annotations, which makes it much easier to write tools that would otherwise need a custom-made parser. The next feature will be to also re-import this data after potential modifications, which would allow things like mutation testing.

    We extended the inline assembly language with structured elements (for, switch and functions) and deprecated manual jumps. This new inline assembly language will become a new intermediate language (together with type information), which allows Solidity to be more transparent in its compilation, more efficient (we will be able to add much more sophisticated optimizer routines) and more portable (it can already compile to EVM, EVM1.5 and some eWASM). We are currently rewriting the ABI encoder in this intermediate language which will include structs and nested dynamic objects.

    Finally, we are adding an automated compile-time overflow and assertion checkerbugfixes and smaller features.


    The swarm team has onboarded new members and held an in-person Swarm Summit in Berlin in June, 2017. The week-long event brought together Ethereum team members, community contributors andspecial guests representing projects and companies interested in swarm. More than twenty talks and tutorial sessions were recorded. The edited videos will be published soon on the swarm summit website. Our public alpha test saw a great community response allowing us to gather more information on prospective user base needs and what the typical usage patterns might be. The high churn of nodes requires an explicit distinction between nodes that can and cannot commit to being available for a longer period of time to provide sufficient storage and bandwidth resources for the network. To support noncommiting nodes and mobile clients, swarm will offer various light modes of operation.

    We have developed a suite of example applications highlighting the architectural and implementational peculiarities of Swarm-hosted distributed web applications that are quite a departure from the traditional client-server model. In particular, the building blocks of a distributed functional equivalent of dropbox are being developed, such as a web-interface providing a file-system view of swarm-hosted volumes, ENS integration, Mist-integration, FUSE mounting of swarm-volumes and privacy protections.

    We added a new protocol, pss (bzz whispered) allowing internode messaging with deterministic routing based on the relaying kademlia network topology of swarm. The protocol uses whisper envelopes and offers udp-like protocol communication between nodes that are not directly connected.

    Furthermore, we have developed a network testing and simulation framework in which we can model and benchmark a broad range of scenarios emerging from the interaction of a potentially large number of  nodes. This framework includes both scripting and visualization capabilities.

    In cooperation with the Remix team, the implementation of a fully distributed integrated contract development environment is underway.

    The next major release, POC 0.3 is scheduled to come out around Metropolis and will include  obfuscation support for plausible deniability, a rewrite of the swap peer-to-peer accounting for bandwidth incentivisation among other things.


    Vitalik Buterin

  • Ethereum (ETH) Release AYTABTU (Geth v1.6.7)

    Geth v1.6.7 (All Your Transaction Are Belong To Us) is another fine maintenance release:

    • The transaction pool now tracks 'local' transactions based on sender address (#14737).
      • Transactions sent by local addresses are exempt from gas pricing- and overall queue size limits.
    • Docker images are smaller because consensus tests are no longer included (#14734, #14792).
    • Extend RPC formatting error messages with field details to better describe the failure (#14686).
    • Add Whisper v5 CLI flags to Geth and add a Whisper Go client library (#14540).

    Important notice to projects running public nodes (MyEtherWallet, Etherscan, Infura, etc): The sender address of any transaction submitted via RPC will be considered a local address, and all transactions from such addresses will be exempt of the gas price and pool size enforcement. To avoid DOS attacks due to the exemption algorithm, please run with --txpool.nolocals to disable special exemptions for local accounts.

    For other minor changes in this release, see the 1.6.7 milestone.

    Binaries and mobile libraries are available on our Download Page

  • Ethereum (ETH) Release Mist v0.9.0


  • Ethereum core devs meeting update (July 14, 2017)

    All Core Devs Meeting #20

    Ethereum Foundation’s core developers meeting was streamed live on youtube. yesterday , July 14, 2017.


    • Metropolis updates/EIPs.  a. Any “subtleties” or questions we need to work out.  -Split metropolis into 2 forks? Leave out EIP 86/208 in fork #1.  b. Updates to testing.  c. Details and implementations of EIPs.
    1. Updates from client teams. geth — ethereum/go-ethereum#14337 Parity — paritytech/parity#4833 cpp-ethereum — ethereum/cpp-ethereum#4050 yellowpaper — ethereum/yellowpaper#229 pyethapp Other clients
    2. Determining gas prices for new opcodes & pre-compiles d. Review time estimate for testing/release.

    Main outcomes of the meeting (as reported by Souptacular):

    • Splitting Metropolis into 2 hard forks.

    Part A — Aug / Sep 2017

    Part B — Jan / Feb 2018

    • These dates are still entirely guesses and subject to change depending on how testing goes and what EIPs are decided to add to Metro. B.
    • Delaying EIP 86 until Metro HF 2.  The reasoning is that EIP 86 is a significant change to the underlying way accounts are created and recently there has been extensive discussion (summarized here) about the concerns and challenges of safely implementing it. At this point completing the analysis and testing of 86 would delay Metropolis further than necessary, especially considering that the other EIPs that are to be added are nearly all finalized, implemented in clients, and have tests developed for them.
    • In short, no other EIP going into metro is reliant on EIP 86 so to make sure Metropolis as a whole goes smoothly we want to give ourselves plenty of time to evaluate the recently discussed issues surrounding EIP 86’s design.
    • Likely adding miner block reward deduction to Metro HF 1.
    • Block time estimates calculated today (subject to change):

    22 sec. — end of July

    27 sec. — Aug. 26

    35 sec. — Sept. 27

    45 sec. — Nov. 6th

    • EIP649 (difficulty bomb delay) is planned for HF1.
    • Nick/Vitalik working on EIP 96, 98, and addressing concerns with gas scheduling in 198.
    • EIP for miner reward reduction (will be combined with ethereum/EIPs#669 likely)
    • Put ice age changes in 669.
    • Martin H.S will bring new opcode gas data next time.
    • Parity team to supply benchmarks to compare with Martin’s geth ones.

    Why are block times increasing?

    As explained by PoliticalDissidents, “It’s the difficulty bomb. Difficulty was programmed to increase exponentially beyond what is warranted to account for increasing hashrate. This means block time keeps getting longer and longer and doing so at an exponentially increasing rate.

    This was designed as a suicide pill for Etheruem as the plan all along was to fork later in the the future (primarily due to a plan to Implement POS) so the difficulty bomb exists to make it so that the current chain will die regardless of if miners want to keep it alive or not because eventually difficulty will get so high that block time will become so long that it’s no longer a viable currency to use and it dies off.”

    Further details related to this meeting are available at GitHub.

    For more updates, technical blogs and general discussion on Blockchain Technology and Ethereum, please join us at our Website, reddit, Facebook, Medium, steemit and follow us at Twitter. Please feel free to share this post, email us with your suggestions and connect at LinkedIn.

  • EtherWorld’s weekly: July 16, 2017


    Project updates

    New Projects

    • Graphene Operating System (GEOS) — a fully decentralised operating system for blockchain applications.
    • Mattereum — Internet of Agreements infrastructure project.
    • LocalEthereum — Ether’s local private marketplace.
    • Orocrypt — When the Ethereum blockchain meets the precious metals.
    • Decentraland — Moving towards a decentralized future.
    • Ujo- A look under the hood.
    • Weipoint- Address verification
    • Coral- Secure platf0rm for tokensales
    • Doma- Platform for networked home ownership

    Hiring and Bounty

    Developer’s Update

    ICO / Token sale updates

    Upcoming Events

    For more updates, technical blogs and general discussion on Blockchain Technology and Ethereum, please join us at our Website, reddit, Facebook, Medium, Slack and follow us at Twitter. Please feel free to share this post, email us with your suggestions.

    #Ethereum #blockchain #FinTech #cryptocurrency #hackathon #bounty #EEA #ICO

    Originally published at localhost on July 16, 2017.

  • Ethereum (ETH) Security Alert

    Parity Multisig Wallet Hack

    Severity: Critical

    Product affected: Parity Wallet

    Affected implementations: Parity 1.5 or later

    Summary: A vulnerability in Parity Wallet's variant of the standard multi-sig contract has been found.

    Affected users: Any user with assets in a multi-sig wallet created in Parity Wallet prior to 19/07/17 23:14:56 CEST.

    Mitigation steps: Immediately move assets contained in the multi-sig wallet to a secure address.

    UPDATE (20/07/17, 00:26 CEST): Future multi-sig wallets created by versions of Parity are secure (Fix in the code is

  • Ethereum (ETH) Release Wallet and Mist 0.9.0 "It's happening"

    This release adds some anticipated features and also addresses important security improvements.

    IMPORTANT FOR DAPP DEVELOPERS! Read the notes below about changes in Mist's web3 object!

    Mist Browser

    Swarm supportbeta

    It is now possible to navigate through the Swarm decentralized network with the bzz:// protocol. Every request lands on the Swarm node, which will search for the content through the p2p network and display your website/file of choice.

    Basically it means that if you point your ENS domain to a swarm hash, the swarm content can be accessed on Mist via bzz://mydomain.eth. How cool is that? New web, much wow 😎

    Also, in order to upload files and folders on Mist is as easy as File > Upload to Swarm....

    Keep in mind that in order to use ens domains, your chain has to be synced, as it looks up to ENS resolver contracts.

    For more information about the project, head to bzz://theswarm.eth — after updating Mist, of course. Kudos to @zelig and Swarm team.

    Security hardening

    Increased security by leveraging the use of a fully isolated JavaScript context between Mist and the Dapps. See #2087.


    From this version on Mist will not ship its own web3.js instance anymore. We only provide for now web3.currentProvider so you can connect to ethereum. In the future we will provide a special ethereum object with a default provider.

    Also this web3.currentProvider will not allow sync calls anymore, as it is already the case in MetaMask (and it's bad practice in general). So make sure to use the async ones e.g. web3.eth.accounts -> web3.eth.getAccounts(function(){...})

    To instantiate your (self included) web3.js lib you can use:

    if(typeof web3 !== 'undefined')
        var web3 = new Web3(web3.currentProvider);
        web3 = new Web3(new Web3.providers.HttpProvider("http://localhost:8545"));

    Easier test networks

    In addition to Ropsten, you can now switch to the Rinkeby test network from the Develop menu. Rinkeby is also set as the default testnet, as it is much lighter to sync. See #2723.

    And if you want to create your own solo network for testing purposes (or in a workshop where you have a very poor internet connection) you can also do it directly via the Develop menu: it will create a local network just for your computer in which you can test, mine and publish local contracts. It will use the --dev flag on your geth node. From the Mist UI console (developer tools), you can use and control the web3 object. See (command line options)[]. #2723.

    An in-depth view of the Mist 0.9.0 changelog:

    Ethereum Wallet

    ENS support for addresses

    You can write an ENS address on any address field on the Wallet, and the actual address represented by that name will appear when you click outside of the field.

    It will even double check the name and can redirect to preferred names, so if you type "ethereum" it will see that it points to the address of the ethereum foundation tipjar, which calls itself "ethereumfoundation".

    Accounts also do reverse name lookup: if any of your accounts, wallets or contracts have registered a reverse name lookup, then they will be shown the ENS name in your app.

    The meteor package containing this special input type is publicly available at Meteor Package [email protected], so you can use it on your Dapp today.

    ENS support for tokens

    Now it's easier than ever to watch Tokens and see your balances. By clicking on Contracts > Watch Token, the modal will appear and you can type the Token symbol. Instantly all the available details will appear and you just have to confirm.

    This was only possible after @kvhnuke created the big list o' tokens, and @Arachnid created thetoken.eth service 👏

    Refer to the Wallet 0.9.0 changelog for a more in-depth view of the changes.


    Checksum (md5)










  • Ethereum (ETH) - Parity Announcing the Bug Bounty Program

    As recent events have shown us, it's not always enough to have good programmers, open-source software and peer reviews in order to ensure no critical bugs make it through to release. While users of all Free software should always do ones own auditing of software to a level reflecting the amount it is relied upon, there is inevitably some degree of duplication that this regrettably implies across any given software's user base.

    With this in mind, and after getting some promising feedback from our previous blog article, Parity is starting a bug-bounty programme. While Parity has initially seed this, our resources are mostly deployed on writing open-source software, so we appeal to the community to help itself and fund this as much as possible.

    To minimise any potential (technical) security issues the bounty funds will be initially collected into a cold-wallet account managed by Parity. This will be transitioned into a multi-sig once we have finalised who the trustees/"owners" of the multi-sig will be that will judge and administer any payments to be made from the fund.

    For anyone who would like to contribute to the Bug Bounty Programme, please send funds to 0x00f1C77935AC482fC075B55b5990E86ea40851Bb, or if you're using Parity Wallet, the name bugbounty. For additional security, this same address will be tweeted from our official twitter account. Here's a picture of it (the identicon is like a green teddybear on an orange background).


    The programme will initially cover the Parity Ethereum client for the latest released versions of beta and stable branches, together with staging branches during the QA period prior to a release. It will be a narrow-focussed fund covering specifically security issues, rather than more general setup, crashing or consensus issues. Depending on feedback from donors, this may be extended in scope at a later time, to cover areas of consensus and other clients and infrastructure that do not currently have a bug-bounty programme.

    The initial targets of this will be Parity's key management (to ensure secrets cannot be compromised or misused), Parity's auto-update Operations contract and Parity's multi-signature Wallet, the base of which can be found in the contracts repository.

    Next up

    This is a beginning, but certainly not the end. We will be reaching out to a number of well-respected security professionals and teams to create a club of bounty-hunters. This club could then be called upon by Parity and others in the community to do targeted and well-incentivised reviews of new code. More news when we get it.

  • Ethereum (ETH) - Weekly  News Update

    Ethereum News and Links


    • SEC finds TheDAO to be a security, but does not pursue enforcement against
      • Context: It was my impression at the time that helped conjure TheDAO in order to achieve a technological work around of securities laws.  It’s not surprising that the SEC fired back and claimed jurisdiction.  You could argue that a federal regulator showed admirable restraint in a new technological field, all things considered.
      • Report affirms that the Howey test is the right way to look at tokens.  Obviously some are securities, some are not. Duh.
      • Fact finding report was rather weak on one of the Howey prongs (“Derived from the Managerial Efforts of Others”) which may also help explain the lack of enforcement action.
      • Real talk: Bitcoin maximalist and ETC FUD over the last few years has claimed that the DAO fork happened because insiders would take losses on the DAO. That always seemed to be nonsense, as few ETH insiders appeared to hold substantial DAO tokens.  The rumor at the time was that many people felt forking was necessary to avoid long and painful SEC enforcement actions.
      • The report laid an expensive yet ambiguous regulatory burden on exchanges with American customers to avoid security tokens.
      • Catch 22: to not be a security under Howey, a token should have utility value.  But if American consumers can’t buy the tokens because exchanges are afraid to list tokens, then it’s tough for that token to be utilized.
      • This report ensures that the US will continue to far further behind in web3.  Jurisdictional competition is real, and so far regulators have not provided meaningful guidance as to how they will interpret the Howey test for token sales. The investigative report was quite reasonable, yet unfortunately some of the investor bulletin contained strong assumptionspay for Facebook ads for that investor bulletin?]  Mixed messages.
      • Status quo of ambiguity remains: a non-zero number of projects will continue to choose to move abroad and most token sales will bar Americans from participating.
      • Only way to reverse that trend is for SEC/Congress to issue either a safe harbor or clear guidance on utility tokens.
    • Parity bug.  An attacker got about $32m USD in Ether from a bug in the Parity multi-sig wallet used by various projects
      • Bug had just a single code review when it was introduced.
      • Zeppelin explains the hackvideo explainer of the exploit
      • Timeline compiled by Bok KooEdgeless, then came back 13 hours later for SwarmCity and aeternity.  5 hours later, the WhiteHatGroup began safeguarding Ether and tokens worth ~$200m and finished in about 7 hours.
      • How to get your value back from the WHGreturned most of it.  Thank you WHG.
      • But why didn’t the attacker take that $200m? It’s ridiculously easy to find a target list of vulnerably Parity multi-sigs by finding similar contracts, and the attacker had plenty of time. Presumably that attacker is sophisticated enough to realize how ridiculously harder it would be to hard fork than it was for the DAO.  Perhaps the constraint was a byproduct of the DAO fork, but that seems unlikely.
      • Attacker appears to have picked targets based on Parity’s logo.  Edgeless, SwarmCity and aeternity all have logos similar to the infinity sympol. [Can’t find the tweet where I first saw this in order to cite it.]  Parity’s logopost mortem.  Emin Gün Sirer’s.


    Stuff for developers

    • Oyente v0.2web3j v2.3
    • Truffle v3.4.6
      • Truffle breaks 100k downloads
      • Truffle dapp tutorial on implementing a tracking system for a pet shop
    • BlockCypher Ethereum APIEthereum Name Service and Swarm
    • HackThisContract: a site to hack Solidity code
      • Yoichi: Empty this Ropsten contract written in Bamboo
    • Eric Rafaloff’s Solidity Function Profiler



    Project Announcements & White papers

    Project Updates

    Interviews and Talks

    Token Sale Projects

    Token Sales


    Dates of Note

    From Token Sale Calendar:

    Upcoming token sale start dates:

    Ongoing token sales:

    You can find this calendar updated daily-ish at

    [email protected]_van_ness a message with 1) your URL, 2) sale date and 3) a brief description of how you are using Ethereum.  Listings are free.  But please make sure to follow those instructions.

    WARNING: list may include scams.  Do your own research and due diligence before putting value at risk.

    [I aim for a relatively comprehensive list of Ethereum sales, but make no warranty as to even whether they are legit; as such, I thus likewise warrant nothing about whether any will produce a satisfactory return. I have passed the CFA exams investing thesis and token sale appreciation strategies in previous newsletters.]

    I like to share it, share it (Sir Mix-A-Lot style)

    Some time in early August, there will be an announcement that I’ve joined ConsenSys.  Here’s a logo to draw your eye in case you were going to skip over this section:

    I’m very excited about this move and will have significantly more to say in the future.  The newsletters should become more regular again! In the meantime, I wanted to make it clear so that you can judge whether I favor ConsenSys projects.

    My charge from Joe Lubin is pretty similar to what Status has told me: keep telling the truth and covering the space objectively, even if the truth hurts.     

    The link for sharing

    I measure the success of each issue by how much it gets upvoted and shared.  This is the link:

    Follow me on Twitter?  But in case you still want to send Ether (or tokens?):  0x96d4F0E75ae86e4c46cD8e9D4AE2F2309bD6Ec45

  • Ethereum - Parity SECURITY UPDATE 27/7/2017

    A quick update on the status of Parity Ethereum client


    There is now a significant amount in our bug bounty programme (many thanks to all contributors). As mentioned in a previous post, critical security bugs in the latest versions of Parity, both beta and stable branches, are valid targets for bounty-collecting reports. The multi-sig wallet, in particular, should be considered a prime target for review and any significant bug will attract a large proportion of the bounty. Any bugs found should be reported to [email protected]


    Several minor changes have been made to the Parity multi-sig, mainly to enable compilation by later versions of Solidity. We understand the "white hat group" is using this code to return some of the funds they temporarily commandeered. After code reviews by many of our developers, there are no known issues. The bug bounty programme is active and we have so far had no issues reported


    Though we try to be as thorough as a bleeding-edge software project can be, bugs sometimes creep into our codebase and, as recent events show, left unchecked these can have significant impacts in the wild. Older versions of Parity can have known bugs (generally mentioned in the release notes): if you are using Parity for anything of any significant value please do ensure that you are running the latest version to minimise the chances of any problems and establish procedures according to the value as risk.

  • Ethereum (ETH) Release solidity Version 0.4.14

    This release contains several new features and bugfixes and also an important security fix: The ecrecover function can be forced to return invalid data, which can be used to bypass authentication in very special circumstances.


    • C API (jsonCompiler): Export the license method.
    • Code Generator: Optimise the fallback function, by removing a useless jump.
    • Inline Assembly: Show useful error message if trying to access calldata variables.
    • Inline Assembly: Support variable declaration without initial value (defaults to 0).
    • Metadata: Only include files which were used to compile the given contract.
    • Type Checker: Disallow value transfers to contracts without a payable fallback function.
    • Type Checker: Include types in explicit conversion error message.
    • Type Checker: Raise proper error for arrays too large for ABI encoding.
    • Type checker: Warn if using this in a constructor.
    • Type checker: Warn when existing symbols, including builtins, are overwritten.


    • Code Generator: Properly clear return memory area for ecrecover.
    • Type Checker: Fix crash for some assignment to non-lvalue.
    • Type Checker: Fix invalid "specify storage keyword" warning for reference members of structs.
    • Type Checker: Mark modifiers as internal.
    • Type Checker: Re-allow multiple mentions of the same modifier per function.

    We especially thank all our open source community contributors:

    Antonio Tenerio-Fornés, benjaminion, Federico Bond, Harry Wright, hh3755, James Ray, Juaj Bednar, Luke Schoen, Loa Arias, maurelian, Nathan Hernandez, NIC619, Rhett Aultman, Skiral Inc and VoR0220.

    If you want to perform a source build, please only use solidity_0.4.14.tar.gz and not the zip provided by github directly.


  • Ethereum (ETH) New Mining Pool 

    Aurora Ethereum Pool - 0% fee


  • New dutch Ethereum pool

    DutchMining - Ethereum Pool

    0.25% Fee

    You can find pool on these details:

    Stratum port: 8008
    Ethminer port: 8888
    There are no blocks yet as this is a brand-new pool! Just launched :smiley:

    Server location is Amsterdam and is our own server and network.
    Soon we will launch Ξthereum Classic also.

    For now the pool fee is 0.25%. We could start with 0% but we decided to keep it low, but keep it.
    Give us a try and give your honest opinion and maybe suggestions!

    Happy mining, together we can find blocks!

  • Ethereum (ETH) Release Parity 1.7.2

    Parity 1.7.2 is a bug-fix release to improve performance and stability. Among others, it addresses the following:

    • Byzantium fork support for Ropsten and Foundation networks.
    • Added support for the Gnosis and ConsenSys multi-signature wallets.
    • Significantly increased token registry and token balance lookup performance.
    • Fixed issues with the health status indicator in the wallet.
    • Tweaked warp-sync to quickly catch up with chains fallen back more than 10,000 blocks.
    • Fixes to the Chrome extension and macOS installer upgrades.
    OS Arch Download SHA256 Checksum
    Windows Icon by Pixel Perfect from x86_64 InstallParity.exe e23a3aa039dbd6ed0e1d8866006968c68285a187cc974f83639ee8ec4f2f9428
    Apple Icon by Pixel Perfect from x86_64 parity-1.7.2-macos-installer.pkg 1b038979e9af07675cdf78b6c445029f18ff97916eb1f6cd21aaf92463ff66ff
    Linux Icon by Pixel Perfect from x86_64 parity_1.7.2_amd64.deb 4c82d7e8a9d53b0020cbc761c39a8f889672093d47b6016516bedc070149eca7
    Linux Icon by Pixel Perfect from armv7 parity_1.7.2_armhf.deb 1b5d0aea02eeec4f79e4fe68abd31731709993617af1a1072baa2d336da8796f
    Linux Icon by Pixel Perfect from aarch64 parity_1.7.2_arm64.deb 38869df8a96234dfad49899a6208a4140c2331de30b3f2b8f4984cb40c9434e4
    OS Alternative Link
    Apple Icon by Pixel Perfect from Homebrew
    Settings Icon by Pixel Perfect from Docker

    Full list of included changes can be found in


  • Ethereum (ETH) - Release solidity Version 0.4.17

    As we are getting closer to the next breaking release, we want to give everyone a heads up by introducing pragma experimental "v0.5.0" which already enables some of the new safety features of the 0.5.0 release.

    Furthermore, this release finally checks the modifiers view (used to be named constant) and pure on functions. As a rule of thumb, use view if your function does not modify storage and pure if it does not even read any state information - but the compiler will also suggest the tightest restriction itself.

    We also worked further on the new ABI encoder: Functions can now return structs. Switch it on using pragma experimental ABIEncoderV2. It should already work, but still generates more expensive code.

    Finally, many new warnings were introduced and error messages improved.


    • Assembly Parser: Support multiple assignment (x, y := f()).
    • Code Generator: Keep a single copy of encoding functions when using the experimental "ABIEncoderV2".
    • Code Generator: Partial support for passing structs as arguments and return parameters (requires pragma experimental ABIEncoderV2; for now).
    • General: Support pragma experimental "v0.5.0"; to activate upcoming breaking changes.
    • General: Added .selector member on external function types to retrieve their signature.
    • Optimizer: Add new optimization step to remove unused JUMPDESTs.
    • Static Analyzer: Warn when using deprecated builtins sha3 and suicide (replaced by keccak256 and selfdestruct, introduced in 0.4.2 and 0.2.0, respectively).
    • Syntax Checker: Warn if no visibility is specified on contract functions.
    • Type Checker: Display helpful warning for unused function arguments/return parameters.
    • Type Checker: Do not show the same error multiple times for events.
    • Type Checker: Greatly reduce the number of duplicate errors shown for duplicate constructors and functions.
    • Type Checker: Warn on using literals as tight packing parameters in keccak256, sha3, sha256 and ripemd160.
    • Type Checker: Enforce view and pure.
    • Type Checker: Enforce view / constant with error as experimental 0.5.0 feature.
    • Type Checker: Enforce fallback functions to be external as experimental 0.5.0 feature.


    • ABI JSON: Include all overloaded events.
    • Parser: Crash fix related to parseTypeName.
    • Type Checker: Allow constant byte arrays.

    We especially thank all our open source community contributors:

    Ali92hm, Aaron Colaço, Lefteris Karapetsas, Matthieu Caneill, Robert Edström and Suman

    If you want to perform a source build, please only use solidity_0.4.17.tar.gz and not the zip provided by github directly.


  • Ethereum (ETH) Release Wallet and Mist 0.9.1

    This release contains a security fix. Updating Mist is highly recommended. If you want to keep using an older Mist version, you mustn't visit untrusted websites.

    Refer to Electron 1.7.8 release notes for more info.

    Ethereum Wallet users are not affected by the vulnerability.

    Thanks to Yoonho Kim for reporting via the Ethereum bug bounty program.

    Introducing Light Client integration (beta)

    The long-awaited Light Client integration has come, in its own beta version.

    Syncing time decreased by an order of magnitude, compared to running a full node.

    As Geth 1.7.x uses LES protocol v1, you'll notice log retrieval takes more time than usual. The good news is v2 is coming to ease that. We'll keep you posted.

    In order to enable it, head to Develop > Use Light Client menu.

    You can join us for further discussion at the Gitter channel.


  • Ethereum (ETH) Release Ptolemy (Geth v1.7.1)

    This is a maintenance release that fixes regressions in the 1.7.0 release.

    This release enables the Byzantium hard fork transition at block number 4370000 (~17th October) on the mainnet and block number 1035301 (~9th October) on the Rinkeby test network. Please update well before these dates to ensure a smooth transition.

    Noteworthy changes:

    • Log queries handle the null topic correctly. (#15195#15232)
    • p2p: messages are compressed using Snappy. See EIP706#15106)
    • ethclient: The new TransactionSender method can be used to derive the sender address of a transaction at the time of inclusion. (#15127).

    For a full rundown of changes, please see the v1.7.1 milestone.

    As always, binaries and mobile libraries are available on our download page.


  • Ethereum (ETH)  Hotfix release 1.6.3 of Ethereumj

    Fixes an issue in framing configuration. It might cause inability to accept devp2p packets from EthereumJ peers.


  • Ethereum (ETH) Release pyethereum v2.2.0


  • New Ethereum Mining Pool with the latest technology, Only 0.5% fee. You will be surprised

    Hi all,
    We at would like to welcome all miners to our newly launched Ethereum Pool.
    latest technology available to build it, we are confident once you try
    mining with us you will appreciate the difference as have we.
    There are daily payouts and with your help we can build a presence on the network and increase our profits together.
    Only 0.5% Pool Fee
    We carry costs of all transactions
    We offer a referral program.
    There is live chat available for support.

    -epool -ewal

    0xc94ce6d3dff9d7f1b34add10a8364978c9843027 -eworker (rigname) -epsw x
    -mode 1 -ftime 10

    If you have any questions:
    Email - [email protected]
    Skype - live:6916ce8b82bec02e

Log in to reply

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.