DIDO Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
==== EIP 1167: Minimal Proxy Contract  ====
[[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip| Return to Ethereum ERCs ]]

  : **Note**: The following is an excerpt from the official Ethereum site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.

<table>
<caption>Data sheet for Minimal Proxy Contract</caption>
| Title                      | Minimal Proxy Contract |
| Author                     | Peter Murray, Nate Welch, Joe Messerman |
| Status                     | Final |
| Created                    | 2018-06-22  |
| Description                | [[http://eips.ethereum.org/EIPS/eip-1167]] |
| Specification              | [[http://eips.ethereum.org/EIPS/eip-1167#Specification]] |
| Category                   | ERC |
| Requires                   | [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0211|ERC 211]] |
</table>

=== Simple Summary === 
  : //To simply and cheaply clone contract functionality in an [[dido:public:ra:xapend:xapend.a_glossary:i:immutable|immutable]] way, this standard specifies a minimal bytecode implementation that delegates all calls to a known, fixed address.//

=== Abstract === 
  : //By standardizing on a known minimal bytecode redirect implementation, this standard allows users and third party tools (e.g. Etherscan) to (a) simply discover that a contract will always redirect in a known manner and (b) depend on the behavior of the code at the destination contract as the behavior of the redirecting contract. Specifically, tooling can interrogate the bytecode at a redirecting address to determine the location of the code that will run - and can depend on representations about that code (verified source, third-party audits, etc). This implementation forwards all calls and 100% of the [[dido:public:ra:xapend:xapend.a_glossary:g:gas|gas]] to the implementation contract and then relays the return value back to the caller. In the case where the implementation reverts, the revert is passed back along with the payload data (for revert with message).//

=== Motivation === 
  : //This standard supports use-cases wherein it is desirable to clone exact contract functionality with a minimum of side effects (e.g. memory slot stomping) and with low gas cost deployment of duplicate proxies.//
DIDO Wiki

User Tools

Site Tools

Page Tools
