OKRW_EAS_PERIODIC_VOLUME_LIMIT_POLICY
Removed upstream. Compose EAS_POLICY with the cap template instead
OKRW_EAS_PERIODIC_VOLUME_LIMIT_POLICY no longer exists on chain. It was one of the monolithic policy templates that bundled an attestation condition with a cap; upstream removed them so that the same rule is expressed by composing the pieces. Registering or referencing this template id now fails — changeContractPolicies reverts with PolicyNotRegistered(string templateId). This page is kept so that integrations still carrying the id find out what happened and what to write instead.
What it used to be
OKRW_EAS_PERIODIC_VOLUME_LIMIT_POLICY enforced a reset-period cumulative OKRW cap that applied only to un-attested senders. Attested senders were admitted regardless of amount, subject to whatever other policies applied.What to write instead
Compose
EAS_POLICY (the attestation condition) and PERIODIC_VOLUME_POLICY (the reset-period cumulative cap) under a LOGICAL_POLICY root. Each piece is registered and documented on its own, the combination is explicit in the PolicyConfig, and you can change one side without touching the other — which is why upstream moved this way. See pcl-composite-policies for the composition rules and short-circuit behaviour.If you still reference the id
Nothing silently degrades: the template id is a string and an unregistered one is rejected at submission with
PolicyNotRegistered(string templateId). Check with policyTemplate(templateId) before submitting. The related query methods for this template were removed at the same time.