OKRW_EAS_TRANSFER_LIMIT_POLICY
Removed upstream. Compose EAS_POLICY with the cap template instead
OKRW_EAS_TRANSFER_LIMIT_POLICY is no longer a policy type 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. A PolicySet that names this id now fails — changeContractPolicies and setGlobalPolicies revert with UnknownPolicyType(string templateId) (a PolicySet with an empty policy value fails first, with CannotEmpty) — and registering it reverts too (on maroo-testnet-1, whose registry still lists it, with DuplicatedPolicyTemplate). 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_TRANSFER_LIMIT_POLICY enforced a per-transaction 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 VOLUME_POLICY (the per-transaction 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 one the chain does not recognize is rejected at submission with
UnknownPolicyType(string templateId). Do not rely on policyTemplate(templateId) to detect this: the maroo-testnet-1 registry still returns a descriptor for this id. The related query methods for this template were removed at the same time.