Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EIP-173: Contract Ownership Standard #52

Open
drllau opened this issue Oct 30, 2021 · 2 comments
Open

EIP-173: Contract Ownership Standard #52

drllau opened this issue Oct 30, 2021 · 2 comments

Comments

@drllau
Copy link
Member

drllau commented Oct 30, 2021

This EIP is about to enter acceptance stage.

The LexOwnable.sol contract will need to be updated in line.

event TransferOwner(address indexed from, address indexed to) event OwnershipTransferred(address indexed previousOwner, address indexed newOwner);

LexOwnable can be called from either side, previous or new
transferOwner(address to, bool direct)
A workaround may be to combine with ERC1363 to force a recipient call

additional query function
function owner() view external returns(address);

Note: OpenZepplin has express renounce function whereas LexOwnable cannot be set to zero.

@drllau
Copy link
Member Author

drllau commented Oct 30, 2021

As a purely optional feature, instead of using 0x00, we can nominate a number of signals about the contract

  • 0xCede - open to anyone for adverse possession
  • 0xDead - first come first served
  • 0xBade - wait a bit, someone will come along and grab it
  • 0xBeef - contestible, at least 2 different owners want it, halted
  • 0xCa1f - smaller beef, in arbitration so contract paused
  • 0xBlab - a special autonomous contract which emits if anyone gases it
  • 0xC0de - special shareable code which is totally public
  • 0xCo1d - not quite dead, some gas still remains
  • 0xDaff - really stupid
  • 0xDeed - unilateral contract
  • 0xFade - in process of being dismantled (multi-party) after being dead
  • 0xL0de - still got lotsa gas inside (maybe)
  • 0x5a1e - open for offers to take on obligations
  • 0x5ea1 - signed parts still operational
  • 0x5eed - anonymous ready for ustruct picking
  • 0x7a1e - bigger 0xBlab - used for LexDAO licensing?
  • 0xFee5 - negative gas?

@cimplylimited
Copy link
Member

I've finally started taking a look into some solidity directly which is loosely making some sense. If you see this @drllau, let me know what you meant with the use of these contract signals. I need a little help understanding these labels and how they would fit into a user flow.

p.s. I realize this is old stuff, but took a look at ERC 173 and 1363 so it feels like a good thought experiment given we are talking about refreshing a token mint project for membership.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants