search

Daohub-io / cap9

Capability-based security protocol for smart contracts
Apache License 2.0
22 stars 10 forks source link

Decide how capabilities should be replaced/deleted #132

Open JakeOShannessy opened 5 years ago

JakeOShannessy commented 5 years ago

This issue is based on a comment in #129.

When registering a procedure which previously existed there is a potential for the newly registered procedure to inherit the capabilities of the previously deleted procedure. Currently the alpha PR just sets the clists to zero length before registering a new procedure. However, we might want to consider this when deleting procedures. When deleting a procedure we have three options for how we treat the old procedures:

  1. Do nothing. Let registration handle it.
  2. Set all the c-list lengths to zero.
  3. Clear everything.
JakeOShannessy commented 5 years ago

Clarification: by "do nothing" I mean currently option 1 is there in the code by default.

Latrasis commented 5 years ago

Let's do 3. However not in #129, but as a seperate PR.