Using the vat-mint to create mints causes errors when trying to pass a config

[katelynsills]

Using the vat-mint in the SwingSet tests works fine for the basic, fungible mint. However, when you try to pass a config, you are passing a function, and marshal doesn't allow it:

const stockMintP = await E(mint).makeMint(usableStockConfig, 'Tyrell');

gives the error:

doProcess: vat[_bootstrap][0].bootstrap dispatch failed: TypeError: arrays must not contain methods TypeError: arrays must not contain methods
        at isPassByCopyArray (/Users/katelynsills/code/ERTP/node_modules/@agoric/marshal/marshal.js:91:13)

It seems like either we don't want a vat-mint at all, or that vat-mint is not set up correctly. Is vat-mint intended to be a long-lived, trusted party?

[katelynsills]

I think vat-mint just doesn't make sense given that there may be custom mint configurations that need to be passed into the makeMint. It makes more sense for a smart contract developer to import mint.js in whatever vat they want to use.

[Chris-Hibbert]

In the tests, you're probably right that the developer should put the mint where it's conveniently remote from the code being tested.

The vat-mint.js in cosmic-swingset doesn't export a makeMint() function. Its purpose seems to be to hold 'trusted' 'system' mints. I think what we'd expect developer to do is to install a mint in a spawner (née contract host) so the clients can see what code the mint is running.

[warner]

this was issue 70 in the old ERTP repo

[katelynsills]

Closing this issue because it's been answered.