• Breaking News

    Wednesday, March 3, 2021

    Home Unlabelled Ethereum Welcome to the Future

    Ethereum Welcome to the Future

    March 03, 2021

    Ethereum Welcome to the Future

    Welcome to the Future

    Posted: 03 Mar 2021 05:41 PM PST

    Kings of Leon Will Be the First Band to Release an Album as an NFT

    Posted: 03 Mar 2021 02:12 PM PST

    Expectations for backwards-incompatible changes / removal of features that may come soon

    Posted: 03 Mar 2021 12:07 PM PST

    The time between now and the merge, and possibly a little bit after the merge, is going to be a time of significant change for the Ethereum protocol. These changes are needed for many reasons: proof of stake and scalability, others to enable stateless validation, and others to simplify the protocol and make it easier to maintain it in the long term, all setting the stage for a more sustainable long-term Ethereum protocol. However, some of these changes are backwards-incompatible, in that they may break existing applications or render them uneconomical.

    In all cases, these incompatibilities affect only a small portion of use cases, and there are alternative ways to get the same functionality, but nevertheless it's important to talk about these proposals early, so that developers have as much of a heads up as possible, and so that we have as much time as possible to refine the proposals to minimize disruption.

    After the merge and the other important changes that are already in the roadmap today are complete, I continue to think that it would be valuable for the Ethereum protocol to "ossify", changing much less going forward so as to maximize developers' feeling of stability and ability to rely on protocol features. However, such an ossification is best done after we take into account our learnings from the past 6 years and make this one last push to make some major improvements to Ethereum.

    This is my attempt at a partial listing of some changes that may happen.

    See also: this doc, though the actual changes proposed there only cover the EVM, and this post is broader.

    History storage changes

    • After the Ethereum application state is moved over to the beacon chain as part of the merge, we may want to discard the ethereum PoW chain, and no longer support any transaction or history queries going back into the PoW chain. This greatly simplifies clients, as they can simply forget all the pre-merge protocol rules and thus have a smaller and leaner codebase going forward, but it does mean that dapps that rely on looking back into history need to find some other way to do so.
    • Even outside of the context of the merge, we likely want to move toward a model where "the network" is only expected to be responsible for the most recent 1 year of history (including txs/blocks/receipts). This prevents clients from incurring ever-growing storage burdens, but it does once again mean that dapps that require old history will need an alternative way to get it.

    Statelessness / state expiry

    See my other post on this topic.

    State expiry is definitely likely to be the one change in this list that requires the most significant changes for contracts; contracts that do not change probably will not break (as the most recent state expiry schemes ensure that if you can find a witness, you can continue using existing contracts as is for as long as you want), but developers will likely need to build new versions of contracts to remain gas-efficient.

    EVM changes

    • EIP 2929 (going into the upcoming Berlin hard fork), changing how SLOAD and calls/account accesses are priced. The first time an account or storage slot is accessed is now about 3x more expensive, but subsequent accesses are around 5-10x cheaper. On average, this only increases gas costs paid by users by ~0.3%, but it significantly improves the chain's DoS resistance and bounds on witness size.
    • Gas repricing for code witness size: when we add code Merklization, to finish the job of bounding witness size we will need to charge some cost per chunk of code accessed in a transaction (eg. 400 gas per 32 byte chunk accessed). In general, this would somewhat increase the gas cost of "simpler" transactions (eg. an ERC20 approval accessed about 16 chunks so about 6.4k gas would be added) but it would only negligibly affect more complex transactions that loop over the same code many times. Gas limits can be adjusted upwards so that on average scalability remains the same as it was before, but even still, some applications may need to be rewritten to remain economical.
    • Removal or neutering of SELFDESTRUCT: see this whole document for the rationale.
    • Removal of refunds (proposed for the London hard fork), or limiting how refunds work, with the main goals of reducing block gas usage variance and freeing up blockchain space and storage being used by gastoken contracts.
    • Removal of the 2300 gas stipend: a simplification to the protocol, removing a hard-coded value and hence making future gas cost changes more feasible
    • Replacing some precompiles with EVM code implementations: this could be done mainly to simplify the protocol and the client code complexity, but it would inevitably come with gas cost changes.

    Miscellaneous

    • Ethereum is switching from RLP + hexary Patricia trees to SSZ and possibly Verkle trees. This means that contracts that verify Merkle proofs into history will stop working at some point and will need to be rewritten. To allow developers to make Merkle proofs going forward, one possible route is to make an explicit "history/state proof verification precompile", so that whenever the state structure changes the precompile can change too, but of course this has not yet been implemented.
    • Block hashes will no longer be a good source of randomness after the merge.
    • The DIFFICULTY opcode will be useless after the merge (duh)
    • In the long run, quantum computers will break ECDSA and BLS, and so everything that uses ECDSA or BLS will have to switch, and even ethereum 2.0 itself will have to move from BLS to a post-quantum aggregable signature scheme. Fortunately, there has been a lot of work done recently by Starkware and others on making such schemes more efficient, so we are very confident that we will survive the transition; but contract developers should necessarily be aware that this will happen.

    There are likely items that I have missed, but this covers at least some of the important things that are worth watching out for. I highly encourage application developers and others to participate in this process and do so early, so that the protocol changes that end up happening can be done in a way that is as minimally disruptive as possible.

    submitted by /u/vbuterin
    [link] [comments]

    Geth v1.10.0 out! Snapshots, snap sync, pruning and more!

    Posted: 03 Mar 2021 09:22 AM PST

    No, no I can not.

    Posted: 03 Mar 2021 06:54 PM PST

    MyCrypto has implemented support for xDai chain!

    Posted: 03 Mar 2021 02:40 PM PST

    Where can I learn of upcoming Ethereum feature launches such as dates?

    Posted: 03 Mar 2021 03:38 PM PST

    Interesting Ethereum Use Case? GoFundMe 2.0

    Posted: 03 Mar 2021 04:16 PM PST

    As I have been stewing all day about how I can externally fund some my PhD costs starting in September aside from work in the Summer I came to two ideas: I start an OnlyFans and hope that there is a niche market of creepy guys that are into average looking 6.5 to 7.5 (on a good day) / 10 guys doing weird shit, or I start a GoFundMe and pray that enough people give a shit about economics and invasive species that they'll pitch in to help me achieve that personal goal.

    But then I looked at my cryptos today like I always fucking do and I thought to myself: Wouldn't it be great if there was a GoFundMe for cryptos? And then I thought that it could potentially be an easy use case for a dapp on Ethereum. It would be sooo easy for the GoFundMe donators to see that when enough money gets put in the pool that the smart contract could execute and do what it needs to do in the objective of the GoFundMe.

    So if I said for example that I wanted to try and pay off part of my tuition, the smart contract would build up enough crypto equivalents from the donations and then execute on an exchange or something to convert to stablecoins and send to the target wallet address (the university). This way if I donate to the GoFundMe I know for damn sure it's going to where it should be going instead of ending up in some guys back pocket or lost to fucking UniSwap on a bad trade.

    submitted by /u/FondleMyFirn
    [link] [comments]

    The Associated Press is auctioning off a one-off Ethereum NFT artwork to commemorate calling the Presidential Election on Ethereum. In the future, every historic event will be called on Ethereum and archived with NFTs.

    Posted: 03 Mar 2021 12:32 PM PST

    Binance Smart Chain's Musical Beats, Alleged Ethereum Copycat, Shuts Down Days After Launch

    Posted: 03 Mar 2021 06:49 PM PST

    Enjin to Tackle Soaring Gas Fees, Scaling With New Blockchain Products

    Posted: 03 Mar 2021 07:54 AM PST

    Most privacy-oriented Eth wallet with HW wallet support?

    Posted: 03 Mar 2021 11:46 AM PST

    Curious if there is a wallet for eth that works with hardware wallets and minimizes the risk of being spied on by connecting servers (balances, IPs, etc), similarly to what is possible with some bitcoin wallets (wasabi, electrum, sparrow).

    Asking for a friend.

    submitted by /u/alcinolegumes
    [link] [comments]

    Yield Guild Games (YGG) Raises $1.3M To Invest In Gaming NFTs

    Posted: 03 Mar 2021 05:56 PM PST

    EthHub Weekly #155: EIP-1559 community call, Tether settlement, Optimistic Ethereum launches in March, dYdX layer 2 enters alpha, MEV explorer released and Vitalik’s proposal to remove gas token minting

    Posted: 03 Mar 2021 10:12 AM PST

    I NEED HELP!! SOMEONE GOOD IN THE WORLD?

    Posted: 03 Mar 2021 07:55 PM PST

    is jaxx.io safe

    Posted: 03 Mar 2021 07:47 PM PST

    im new to ethereum

    submitted by /u/SteelingEye
    [link] [comments]

    Noob question about Staking ETH on Coinbase

    Posted: 03 Mar 2021 12:11 PM PST

    When you stake ETH for the 2.0 network that's upcoming, I understand it becomes unavailable / locked.

    My question is around it's value. To keep it simple, I'll just use 1 ETH in my scenario.

    If i was to stake 1 ETH right now, I would earn 7.5% back on that staked ETH. My question, is if ETH were to go 10x it's current price, does my staked ETH also increase in value 10x, or is it locked at the price i staked it at?

    submitted by /u/Kardde21
    [link] [comments]

    How long would this take?

    Posted: 03 Mar 2021 07:18 PM PST

    ��‍�� Workshop Recap: Cheap contract deployment through Clones (minimal proxies); Led by Hadrien Croubois - Smart Contract Engineer at OpenZeppelin. Watch the video recording; Try the code from the workshop.

    Posted: 03 Mar 2021 01:19 PM PST

    Staking rewards for your own node vs 3rd party

    Posted: 03 Mar 2021 06:55 PM PST

    I was wondering how much more staking rewards you receive by doing it yourself vs a 3rd party.

    Right now I am staking with Kraken and calculated that I am getting 7.7% yearly. I know they take about 15% which would mean I would be making 9% if I did it on my own. Does this seem like an accurate number? I am having a hard time finding some numbers on this

    submitted by /u/G_MoneyZ
    [link] [comments]

    Deploy Ethereum Proof of Authority Consortium template on Azure... ? Will MSFT follow suit of Amazon?

    Posted: 03 Mar 2021 06:40 PM PST

    Connect Users To Layer 2 Networks With The MetaMask Custom Networks API

    Posted: 03 Mar 2021 06:39 PM PST
    Read more
    at

    No comments:

    Post a Comment