Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Asset responses can omit
l1_decimalswhen the asset originates on Core or EVM. Make that field optional and exposeevm_decimals,canonical_domain, andevm_tokenas typed fields. Keep the new fields optional so existing API responses remain supported, and preserve zero decimals as distinct from missing metadata.Update the OpenAPI schema and regenerate the Asset model and documentation with OpenAPI Generator 7.7.0. Preserve the SDK's existing
model_constructHTTP deserialization behavior. Add response-decoding coverage for legacy L1, L1 with an EVM wrapper, Core-native, EVM-native, and zero-decimal EVM assets.This draft prepares the client for the corresponding API rollout; it does not change transaction signing.