More efficient clone contract features could soon arrive at Ethereum Blockchain


EIP 1167 entered the "last call" status yesterday and is open for comments for the next two weeks before it is finalized. This proposed improvement Ethereum allows any number of cloned contracts to redirect calls and gas tariffs cheaper and with fewer side effects than is currently possible.

Thursday EIP 1167: Minimal Proxy Contract created by Peter Murray, Nate Welch and Joe Messerman, entered the last call. The proposed improvement Ethereum is open for comment for the next two weeks, after which, assuming that all goes well, the code will be considered finalized. If rejected by the community, the EIP will revert to the draft state.

The proposed standard applies to the functionality of cloned contracts and aims to reduce gas prices in cloned contracts. Specifically, EIP 1167 allows any number of cloned contracts to redirect calls to a known address (known as the master contract) and to trust that the master contract behaves the same way as redirect contracts. The reliability of the code depends on its immutability: once distributed on a main contract, the code can not be changed and the main contract is irreplaceable. If the main contract self-destructs, all cloned contracts will cease to function.

The dependency of the cloned contracts on the main contract and the immutability of the main contract can promote user confidence, but it is also a central weakness. You might remember the fiasco multisig Parity . Although this was not a case of cloned contracts, it illustrates the inherent vulnerability to dependence on a central contract. All of Parity's multisig wallets linked to a library contract, but there was a vulnerability that led to the self-destruction of the contract. All 587 wallets linked to the library, which together contained a total of 513.774.16 Ether, were frozen.

Social coder and writer for Giveth Bowen Sanders explained to ETHNew s that, through this EIP, cloned contracts are not replicas of the entire main contract, but are "minimum proxies" (from here the name EIP) which allows a programmer to reduce a voluminous contract to its essential parts. The minimum proxies therefore rely on the main contract for full functionality. Sanders explained:

"[As it is,] thousands and thousands of contracts are regularly cloned, occupying useless space and inflating the blockchain data segment. This data space could be used for things other than multiple clones of the same contract. contracts that must be cloned for use and security, as with the ConsenSys or Gnosis multi-signing portfolios, but many cases of these clones could reuse the original contract with a proxy contract that routes calls in and out of the This would save enormous amounts of space. "

The other important function of this standard is that it specifies the creation of a contract that will allow third parties, such as Etherscan, to query the bytecode of the redirection (cloned ) contracts and determine the location of the main contract.

At the technical level, EIP 1167 would standardize "on a" minimum known bytecode redirect "implementation. If finalized, this guideline will affect all developers who attempt to build a system of cloned minimal proxy contracts that redirect calls to the original master contract.

Alison is an occasional publisher and writer for ETHNews. He has a master's degree in English from the University of Wyoming. He lives in Reno with his husband and the growing family of animals. Among his favorite things there is the binge to listen to the podcasts, have the laughs through the memes of the dogs and spend as much time as possible outside.

ETHNews is engaged in its editorial policy

Do you like what you read? Follow us on Twitter @ETHNews_ to receive the latest news on the EIP 1167 ecosystem, Ethereum or other Ethereum.

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *