As part of the Orchestration API, canonical chain info will be published to agoricNames for contracts to consume. A core eval is needed to publish this information to agoricNames. We have @agoric/orchestration/src/proposals/init-chain-info.js from https://github.com/Agoric/agoric-sdk/pull/10110, but it's unreleased and has outstanding dependencies.
What is the Problem Being Solved?
As part of the Orchestration API, canonical chain info will be published to
agoricNames
for contracts to consume. A core eval is needed to publish this information toagoricNames
. We have@agoric/orchestration/src/proposals/init-chain-info.js
from https://github.com/Agoric/agoric-sdk/pull/10110, but it's unreleased and has outstanding dependencies.We might want to include this task in the same release as https://github.com/Agoric/agoric-sdk/issues/9967, which covers asset info also used by the
ChainHub
.Description of the Design
Security Considerations
Scaling Considerations
This information is environment-dependent, so an emerynet proposal will need different data than a proposal for another network.
Test Plan
Upgrade Considerations