Closed dckc closed 5 months ago
Today, an MN2 dev asked about it, and I mentioned that there's a section to discuss this in the docs, but it's nearly empty. :-/
:bulb: I just realized: I told the core eval story in yesterday's office hours, in response to a question from Jorge. Idea: excerpt the relevant ~5min video segment and link it from the section.
p.s. meanwhile, the MN2 dev was satisfied with a pointer to how it works in dapp-offer-up.
agoric run
andwriteCoreProposal
: explain or avoid?In dapp-offer-up, there's a huge amount of stuff behind the
strart:contract
package script.The code currently follows the approach in:
agoric run
supports bundling proposal modules withwriteCoreProposal
That approach is motivated by having core-eval stuff that fits both in the on-chain governance context and in a separate bootstrap / chain-software-upgrade context. That constraint is not essential to dapp development.
So we have:
startOfferUpContract
with stuff likeconsume: { board, chainStorage, ... }
getManifestForOfferUp
,restoreRef
agoric run
DeployScriptFunction
writeCoreProposal
ProposalBuilder
BootstrapManifest
install
,restoreRef
Maybe rather than explaining all this stuff, we should relax the 2-context constraint so we can do a simpler core-eval script?