##OwnedAttributeStore
This is a proposal for the functioning of a core OwnedAttributeStore contract.
The idea being that the core OwnedAttributeStore contract, can be extended with arbiratry logic as convensions/standards evolve. Allowing it to remain constant while the underlying logic and permissions are updatable. In the primary instance, it would be used as follows (as an example):
- A OwnedAttributeStore is created. It has an
owner
(essentiallyactiveKey
) attribute by default. - A
delegatedKeyReset
contract is created, and the OwnedAttributeStore'sowner
attributes' ownership is transfered to the delegated contract. - A
delegatedKeyRevoker
contract is created, and the OwnedAttributeStore'sowner
attributes' revoker propery is set to the delegated contract.
Essentially all attributes have an owner
, writer
, revoker
and value
. All of these being optional.
The only exception is that the OwnedAttributeStore has an owner
attribute (essentially activeKey
), which is checked in the case that an attribute does not specify an owner (the default).
- generic
- extensible
- challenge periods and their application
comments welcome 😄