While validating a frame message via the local debugger's hub endpoint (e.g., http://localhost:3010/hub/v1/validateMessage), the response returns the cast hash in base64 format.
This inconsistency between the local and production endpoints (base64 vs. hexadecimal) causes issues in using cast hash. Could you please clarify if this difference is intentional.
Hello,
While validating a frame message via the local debugger's hub endpoint (e.g., http://localhost:3010/hub/v1/validateMessage), the response returns the cast hash in base64 format.
Response:
However, when using the production hub endpoint (e.g., https://hub-api.neynar.com/v1/validateMessage), the response returns the cast hash as a hexadecimal string.
Response:
This inconsistency between the local and production endpoints (base64 vs. hexadecimal) causes issues in using cast hash. Could you please clarify if this difference is intentional.
Thank you!