how to grant chainStorage access to a contract?

[dckc]

As noted in #5687 (comment) , we discussed this in Dec 14 office hours. Someone who watched that recording asked how to write their own version of startPSM.js in order to give the their contract access to a storageNode.

chainStorage-proposal.js (along with bakeSale-permit.json ) is a quick sketch. It's un-tested.

cc @Tyrosine22 @turadg

[carlos-kryha]

Looks like it works on local testnet, I've put together a document with the steps here for anyone interested.

Thanks for the example!

[dckc]

agoricNames beyond reserved names

As we discussed, testing showed that not only does this idiom result in a static error, it doesn't actually work at runtime for names that aren't in a hard-coded "reserved" list:

    instance: {
      // @ts-expect-error bakeSaleKit isn't declared in vats/src/core/types.js
      produce: { [contractInfo.instanceName]: produceInstance },

To register arbitrary names...

  // Add agoricNamesAdmin to the consume
  const {
    consume: { agoricNamesAdmin, board, chainStorage, zoe },
    // @ts-expect-error bakeSaleKit isn't declared in vats/src/core/types.js
    produce: { bakeSaleKit },
    instance: {
      // @ts-expect-error bakeSaleKit isn't declared in vats/src/core/types.js
      produce: { [contractInfo.instanceName]: produceInstance },
    },
  } = powers;

And the "Share instance widely" code becomes...

  // Share instance widely via E(agoricNames).lookup('instance', 'bakeSaleAgent')
  const instanceAdmin = E(agoricNamesAdmin).lookupAdmin('instance');
  await E(instanceAdmin).update('bakeSaleAgent', facets.instance);

You asked about constraints/conventions in this area... whether sharing the publicFacet directly would work...

the AgoricContractInvitationSpec type documentation doesn't say so, but the smartWallet makeInvitationsHelper calls E(zoe).getPublicFacet(instance) between the instancePath and the callPipe. So if the instancePath led directly to a public facet, the call to E(zoe).getPublicFacet) would fail.

So for use with the smart wallet, it has to be an instance that goes into agoricNames.

[dckc]

it doesn't actually work at runtime for names that aren't in a hard-coded "reserved" list

I'm fixing this, btw...

agoric-sdk/packages/vats/test/test-name-hub-published.js

Line 71 in b399893

test('promise space reserves non-well-known names', async t => {

ref

• Bootstrap ocaps are stored durably in vat-bootstrap #4548
• 4548 boot no precious state #7579

p.s. landed in mainnet1B:

agoric-sdk/packages/vats/test/test-name-hub-published.js

Line 51 in ba3b776

test('promise space reserves non-well-known names', async t => {

• fix: remove well-known-name limitation on reserved brands etc. #7604

[0xpatrickdev]

What does extending the bakeSale example to chainTimerService look like?

I added "chainTimerService": "timer" to permit.json and set noTerms to harden({ timer: chainTimerService }), but SwingSet doesn't seem to like this (Error#1: value for instanceRecord is not durable).

Looking at the Inter econ-behaviors as a reference, it seems we need to resolve chainTimerService with deeplyFulfilledObject, an imported module. Is the pattern here to deploy a second intermediary bundle, startBakeSale.js, to handle this setup and reference it in bakeSale-proposal.js?

[dckc]

The chainTimerService you're getting is a promise (all properties of powers are promises). Try resolving it (using await or the like) before using it in the terms of startInstance.

[0xpatrickdev]

:homer_doh: that works - thank you!