Clarified Tellor query specs and updated legacy request IDs
Oct 29, 2021
- Query parameter rules are now stricter — All query parameters must now be included in query descriptors. Optional query parameters are no longer supported, so existing specs may need to be updated.
- Tellor query documentation was expanded — The README and QueryType guidance were updated with clearer explanations of query types, query descriptors, response formats, and how to add new query definitions.
Improvements
- Standardized repository wording to use **Query ID** instead of the older **Request ID** term.
- Improved setup guidance for adding new IDs so contributors can follow the correct Query ID format.
Breaking Changes
- Query descriptors must now include **all** query parameters; optional parameters are not supported.
- Legacy ETH/USD and BTC/USD request IDs were updated to match the current LegacyRequest mapping.
Documentation
- Expanded the README with clearer guidance on TellorX query types, query descriptors, response formats, and contract values.
- Added more detailed instructions and examples for creating and documenting new query types.
- Clarified that the first query descriptor field should be the word **type**.
- Clarified that `_queryData` is a `bytes` value and `_queryID` is a `bytes32` value in contract calls.
- Updated QueryType requirements and linked directly to the requirements section for easier reference.
- Documented the legacy request response format, including the `ufixed256x6` ABI type and `packed=False` setting.
- Corrected minor typos and wording in the QueryType documentation.