Merged
Conversation
Nft support
Add response models
…. now we just skip those.
…. now we just skip those.
…o always have the SigningPubKey field
Multisigning
…. now we just skip those.
…. now we just skip those.
…o always have the SigningPubKey field
Feature: Response Models
Feature: Integration Tests
LimpidCrypto
approved these changes
Feb 26, 2025
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
2 participants
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.
Release v0.5.0
parse_nftoken_idandget_nftoken_idutility functionsMetadatamodelssigning_pub_keyis not set for multisigning but it is required, so it's just an empty string