how to limit excess authority when registering a storage node

[0xpatrickdev]

What is the Problem Being Solved?

In a permit for a core-eval, a contract can request access to chainStorage like this:

{
  "consume": {
    "chainStorage": true
  }
}

This grants excess authority and the ability to overwrite other storage nodes.

first observed as a potential SDK improvement in https://github.com/Agoric/agoric-sdk/issues/8194#issuecomment-1710725136 - @raphdev

Description of the Design

A similar approach to this suggestion, where chainStorage is limited to particular path(s):

{
  "consume": {
    "chainStorage": {
      "myNode": true
    }
  }
}

Security Considerations

The goal of this ticket is to limit excess authority granted around chainStorage during the core-eval process.

Scaling Considerations

Test Plan

Upgrade Considerations

[raphdev]

Worth noting this was first observed as a potential SDK improvement in https://github.com/Agoric/agoric-sdk/issues/8194#issuecomment-1710725136

[dckc]

We have a prototype in https://github.com/Agoric/dapp-offer-up/commit/0c894f6b7126ccfa575c11117e82e87c93a67186

I don't think that one (https://github.com/Agoric/dapp-offer-up/pull/61 ) has landed, but the one in dapp-agoric-basics has:

• https://github.com/Agoric/dapp-agoric-basics/pull/16

cc @Jovonni