Operation Encoding: Split Operation and Parameters #15
Description
Priority: Medium
Description
The within operation returns operation: "within:50000" and resolvers are told to use prefix matching. This is a footgun:
- Easy to implement incorrectly
- Makes schema evolution brittle
- Requires string parsing in smart contracts
Fix Direction
Consider splitting fields in the attested payload:
operation = "within"
params = { radius_cm: 50000 }
Or add radiusCm as a separate numeric field.
- Document the rationale for current encoding
- If changing, create migration guide
- Update resolver examples to handle edge cases robustly
Related
- Issue Documentation improvements for Location-Gated NFT guide and compute API #7 (closed) touched on this with the
_startsWith()helper