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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: