read-only chainStorage for any Zoe contract

[dckc]

What is the Problem Being Solved?

Currently, chainStorge is privileged; we set it up thru bootstrap and such.

In contemporary systems such as Ethereum, any contract can write to logs.

Description of the Design

perhaps:

• generic power for any Zoe contract

design issues:

• naming? i.e. choosing a storage key?

perhaps address that by making this a feature of the board? i.e. when you put something in the board, you can get a chainStorage node for it?

Security Considerations

IOU

Test Plan

IOU

cc @dtribble

[warner]

In today's cosmic-swingset meeting, we speculated about a future Big JS Hammer action which would:

• create a new vat to manage the rental/distribution of publishing nodes
• give that vat access to the root publishing node, or something close to the root
• publish a facet of that vat to the Board, making a publically-available service from which you can buy/rent publishing nodes (with a counter-based path)

Then future contract deployers should start by:

• go to the board, contact the publishing-node-rental service
• buy/rent a publishing node, learn the path
• include the publishing node in the privateArgs you pass to the new contract instance
• tell the world about the path, so they cal follow the contract's annoucements (prices/etc) without performing transactions

[dckc]

work-around: use BLD voting in local development

Until we have a lower threshold, for local development, devs have all the BLD in the world, so they can grant chainStorage powers to their contracts using swingset.CoreEval governance.

We discussed this in today's office hours.

See also:

• BLDer DAO governance using arbitrary code injection: swingset.CoreEval - Governance - Agoric Community Forum 5 Nov 2022