You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new proposal/draft for the contract interface for owning and transferring ownership of contracts was recently written and merged with the ethereum eip project. The draft is here: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-173.md
What is Open Zepplin's response/feedback about this?
Also, can Open Zepplin help get the word out about contract ownership becoming standardized? Get the word out about this EIP draft so it can get the feedback it needs for standardization.
The text was updated successfully, but these errors were encountered:
@frangio thank you for your comment. I noticed that the "@notice" for the transferOwnership() function was wrong so I fixed that and will be in the next pull request.
The notice for the transferOwnership() function now says, "Set the address of the new owner of the contract". The notice for the owner() function says, "Get the address of the owner " Are more semantics needed? If so can you give a better idea of the semantics that should be included?
I added this note: "The OwnershipTransferred event does not have to be emitted when a contract is created."
Implementations of functions owner() and transferOwnership() are unspecified because they can be implemented how people want to implement them. But the standard does link to Open Zepplin's implementation of the standard as an example.
A new proposal/draft for the contract interface for owning and transferring ownership of contracts was recently written and merged with the ethereum eip project. The draft is here: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-173.md
What is Open Zepplin's response/feedback about this?
Also, can Open Zepplin help get the word out about contract ownership becoming standardized? Get the word out about this EIP draft so it can get the feedback it needs for standardization.
The text was updated successfully, but these errors were encountered: