Skip to content

feat(price-guard): scope NAV signature requirement per asset (#95) - #1146

Closed
jeffrey-graham wants to merge 1 commit into
DevTobis:mainfrom
jeffrey-graham:feat/per-asset-nav-signature-95
Closed

jeffrey-graham wants to merge 1 commit into
DevTobis:mainfrom
jeffrey-graham:feat/per-asset-nav-signature-95

Conversation

@jeffrey-graham

Copy link
Copy Markdown

Closes #95

Summary

  • Scopes DataKey::RequireNavSignature(Address) and ConfigChange::RequireNavSignature(Address, bool) per asset (defaulting to true when unset) so disabling NAV signature verification for a bring-up or synthetic test asset never weakens verification for live collateral assets on the same PriceGuard deployment.
  • Updates configure_signature_requirement(env, admin, asset, required) (with topic (Symbol("configure_signature_requirement"), asset)) and require_nav_signature(env, asset) -> bool.
  • Updates packages/contract-clients, scripts/configure-nav-key.sh, scripts/deploy-mainnet-prices.sh, contracts/README.md, and contracts/price-guard/README.md, and adds a unit test verifying independent per-asset enforcement across two assets.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make the NAV signature requirement per asset instead of global

1 participant