Mist DApp Browser
Mist is the browser for decentralized web apps. What Mozilla Firefox or Google Chrome are for the Web 2.0, the Mist Browser will be for the Web 3.0 (which will be decentralized).
Mist is still in heavy development (for instance it's not recommended to visit untrusted DApps until the full security audit is done). You can find the releases ...
In his DEVCON1 Keynote, Vitalik Buterin addressed the roadmap of Ethereum beyond the Frontier release:
expected when the ethereum network, miners and other critical components work without serious hiccups for about 4 weeks.
metropolis, with focus on the mist browser.
serenity, Ethereum 2.0, with 4 primary research directions:
casper, the proof-...
At the time of writing this, there are two types of accounts in Ethereum. First, there are external accounts which are controlled by private keys, like the accounts in a wallet. Then there are contract accounts, which are controlled by the code deployed to the blockchain.
Account Abstraction is an improvement to make these two types of accounts more similar,...
Yes, Byzantium brings some exciting changes that Smart contract developers should be aware of:
REVERT - This new call stops execution of a transaction and reverts
all state, but, unlike throw it returns all unused gas.
In Solidity, the require method now should use REVERT internally meaning, if you require something and it is not met, state will be ...
Let me first explain Mist in simple terms. There are two types of mist for Ethereum, one is a cryptocurrency wallet and the other is a browser.
Mist wallet is basically used to store and send your Ether. If you are choosing to buy, invest or trade in Ethereum, then you'll require a wallet to carry out the transactions. that's where mist wallet is helpful.
At a very high level, you can think of the current version of Ethereum as V2.1 of Ethereum and Metropolis as being another name for version 3. Byzantium is kind of like version 3 alpha (a feature-incomplete version of version 3, except not really in testing phase) -- it is the first half of the rollout of Byzantium. The rest of version 3 is being rolled out ...
You can find the Meta EIP listing the changes included in the hard fork named Metropolis/Byzantium here: https://github.com/ethereum/EIPs/pull/609
Metropolis has been split into two upgrades; Byzantium and Constantinople.
Metropolis/Byzantium is still describe in EIP 609 as above, with a nice ELI5 summary of changes from @avsa here.
Yes, this is correct, per this conversation.
All undefined instructions behave the same way as INVALID. And yes, the behavior of 0xfd changes at Metropolis, but before or after Metropolis, 0xfd always throws. The difference is whether some output is made available for the caller... and, also that the remainder of gas is refunded.
As far as I know, ZoKrates + Byzantium precompiles is the most generic solution currently available. Recently they also added sha256 support in ZoKrates, which extremely improves the applicability.
For tutorial and documentation for ZoKrates see https://zokrates.github.io/introduction.html
For more advanced examples see ZKDai, which basically reassembles ...
Metropolis is not a fork but a milestone in the Ethereum roadmap. Simplified:
Proof of Concept 1-8 (ETH 0.1) were several implementations of the Ethereum protocol in 2014 and 2015.
Olympic (ETH 0.9) was the last proof-of-concept testnet for Ethereum prior to the mainnet launch (2015).
Frontier (ETH 1.0) was the beta phase and the launch of the Ethereum ...