-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Move EIP-173 to final with minor (normal) changes (#5210)
* Move to final + minor changes to bring EIP up to standard * Remove example & requires header
- Loading branch information
Showing
1 changed file
with
4 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,19 +1,15 @@ | ||
| --- | ||
| eip: 173 | ||
| title: Contract Ownership Standard | ||
| author: Nick Mudge <[email protected]>, Dan Finlay <[email protected]> | ||
| description: A standard interface for ownership of contracts | ||
| author: Nick Mudge (@mudgen), Dan Finlay <[email protected]> | ||
| discussions-to: https://github.com/ethereum/EIPs/issues/173 | ||
| type: Standards Track | ||
| category: ERC | ||
| status: Last Call | ||
| last-call-deadline: 2020-09-06 | ||
| status: Final | ||
| created: 2018-06-07 | ||
| --- | ||
|
|
||
| ## Simple Summary | ||
|
|
||
| A standard interface for ownership of contracts. | ||
|
|
||
| ## Abstract | ||
|
|
||
| This specification defines standard functions for owning or controlling a contract. | ||
|
|
@@ -86,7 +82,7 @@ Here are other schemes that were considered: | |
|
|
||
| This standard does not exclude the above ownership schemes or other schemes from also being implemented in the same contract. For example a contract could implement this standard and also implement the other schemes so that ownership could be managed and transferred in multiple ways. This standard does provide a simple ownership scheme that is backwards compatible, is light-weight and simple to implement, and can be widely adopted and depended on. | ||
|
|
||
| This standard can be extended by other standards to add additional ownership functionality. For example [EIP-2767](./eip-2767.md) uses and extends this standard by adding decentralized contract ownership governance. | ||
| This standard can be (and has been) extended by other standards to add additional ownership functionality. | ||
|
|
||
| ## Security Considerations | ||
|
|
||
|
|
@@ -96,13 +92,6 @@ If the address returned by `owner()` is an externally owned account then its pri | |
|
|
||
| Many existing contracts already implement this standard. | ||
|
|
||
| ## Implementations | ||
|
|
||
| * [OpenZeppelin's implementation of Ownable](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/access/Ownable.sol) | ||
| * [0xcert ownable](https://github.com/0xcert/ethereum-erc721/blob/master/src/contracts/ownership/ownable.sol) | ||
| * [FriendlyUser Ownable](https://github.com/FriendlyUser/solidity-smart-contracts//blob/v0.2.0/contracts/other/CredVert/Ownable.sol) | ||
|
|
||
|
|
||
| ## Copyright | ||
|
|
||
| Copyright and related rights waived via [CC0](../LICENSE.md). | ||