Skip to content

feat: multi-slot initialization, feature parity in metadata, safe contract-info labels, and the off-chain policy layer with orphan module coverage - #545

Open
laraba9987-cmyk wants to merge 1 commit into
ApexChainx:mainfrom
laraba9987-cmyk:laraba/prs-425-424-423-422
Open

feat: multi-slot initialization, feature parity in metadata, safe contract-info labels, and the off-chain policy layer with orphan module coverage#545
laraba9987-cmyk wants to merge 1 commit into
ApexChainx:mainfrom
laraba9987-cmyk:laraba/prs-425-424-423-422

Conversation

@laraba9987-cmyk

@laraba9987-cmyk laraba9987-cmyk commented Aug 30, 2026

Copy link
Copy Markdown

Resolves #425,
Resolves #424,
Resolves #423,
Resolves #422.

#425 — multi-slot initialization

initialize accepts "multi", so either slot of a multisig pair can deploy the contract. get_public_api documents admin/operator/multi as the valid moment labels (test test_get_public_api_initialize_auth_is_multi).

#424 — feature parity in get_contract_metadata

The metadata now advertises exactly the feature set the runtime implements (calc, audit, pause, stats, history, failcode, safe_call, ver_nego, corr_id, freeze), with a regression test asserting the advertised slice matches the compiled-in feature list.

#423 — safe contract-info labels

contract_info derives its advertised contract-version/label from the relayed info without depending on an off-chain-labels runtime, fixing mislabeled metadata on platforms that lack that runtime.

#422 — off-chain policy layer + orphan module coverage

Adds the off-chain policy decision layer (policy, deployment_policy, payload_optimizer as a compatibility facade) and enables the previously orphaned test modules: event_state, event_ordering, outage_id, payload_versioning, pruning_perf, threshold_config, topic_stability, auth_matrix, and the new orphan_lint module.

Verification: cargo check clean (0 warnings); full test suite 686 passed / 0 failed / 5 ignored (was 599 without the orphan modules).

…tract-info labels, and the off-chain policy layer with orphan module coverage

- ApexChainx#425: initialize accepts "multi" so either slot of a multisig pair can deploy, and get_public_api documents admin/operator/multi as the valid moment labels
- ApexChainx#424: get_contract_metadata advertises the same feature set (calc, audit, pause, stats, history, failcode, safe_call, ver_nego, corr_id, freeze) the runtime code actually implements
- ApexChainx#423: contract_info derives feature labels in a way that no longer depends on off-chain-labels runtime support
- ApexChainx#422: add the off-chain policy decision layer (policy, deployment_policy, payload_optimizer) and enable the orphan test modules: event_state, event_ordering, outage_id, payload_versioning, pruning_perf, threshold_config, topic_stability, auth_matrix, orphan_lint

Closes ApexChainx#425, ApexChainx#424, ApexChainx#423, ApexChainx#422
@drips-wave

drips-wave Bot commented Aug 30, 2026

Copy link
Copy Markdown

@laraba9987-cmyk Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment