You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
agoric run and core proposals currently create different bundles from the same source because the former enables elideComments and the latter doesn't.
When updating proposal builders, we'd like to be able to generate proposals using the same bundles that are published during a software upgrade containing a core proposal (e.g. DCFoundation/cosmos-proposal-builder#59).
Currently that requires patching agoric-sdk to revert both 2abea2d and 2d410c7
Description of the Design
A command line option to agoric run or another dynamic way to disable elide comments.
An alternative is to align the core proposal builder to use elideComments
Security Considerations
None
Scaling Considerations
This will create larger bundles (which may not be able to be published through cosmos tx), but the goal is to be able to re-use large bundles that were already published during core proposals
Test Plan
Integration test (likely a3p-integration) that verifies a cli built bundle is the same as one published by core proposal.
Upgrade Considerations
Changes chain software but doesn't strictly affect running chain code.
The text was updated successfully, but these errors were encountered:
What is the Problem Being Solved?
agoric run
and core proposals currently create different bundles from the same source because the former enableselideComments
and the latter doesn't.When updating proposal builders, we'd like to be able to generate proposals using the same bundles that are published during a software upgrade containing a core proposal (e.g. DCFoundation/cosmos-proposal-builder#59).
Currently that requires patching agoric-sdk to revert both 2abea2d and 2d410c7
Description of the Design
A command line option to
agoric run
or another dynamic way to disable elide comments.An alternative is to align the core proposal builder to use
elideComments
Security Considerations
None
Scaling Considerations
This will create larger bundles (which may not be able to be published through cosmos tx), but the goal is to be able to re-use large bundles that were already published during core proposals
Test Plan
Integration test (likely a3p-integration) that verifies a cli built bundle is the same as one published by core proposal.
Upgrade Considerations
Changes chain software but doesn't strictly affect running chain code.
The text was updated successfully, but these errors were encountered: