fix: resolve invalid hex prefix in openapi.json example

[erenyegit]

Description

While auditing the API specification, I identified an invalid hex string format in the openapi.json file.

The Issue:
On line 5140, the calldata example was incorrectly prefixed with 0fa0x... instead of the standard 0x.... This is not a valid hex format and would cause "invalid hex string" errors for developers trying to use the example values in automated tools or manual testing.

The Fix:

• Corrected the calldata value in ./api-reference/openapi.json by removing the erroneous 0fa prefix.

Impact

Ensures the OpenAPI specification remains technically accurate and prevents integration errors for developers copying example values.

[cursor]

PR Summary

Low Risk
Documentation/example-only change in the OpenAPI spec with no runtime or behavioral impact.

Overview
Fixes an invalid hex string in api-reference/openapi.json by correcting the calldata example value (removing the erroneous 0fa prefix) so the OpenAPI examples are copy/paste valid.

^{Written by Cursor Bugbot for commit a7cd99f. This will update automatically on new commits. Configure here.}