Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Foundry] Fetch HIP-719 remote state for fungible tokens #98

Open
Tracked by #94
se7enarianelabs opened this issue Oct 31, 2024 · 0 comments
Open
Tracked by #94

[Foundry] Fetch HIP-719 remote state for fungible tokens #98

se7enarianelabs opened this issue Oct 31, 2024 · 0 comments
Labels
feature Enhancing an existing feature driven by business requirements. Typically backwards compatible.

Comments

@se7enarianelabs
Copy link

se7enarianelabs commented Oct 31, 2024

As a follow up of #82, fetch remote state related to associate, dissociate and isAssociated methods for Foundry contract.

The remote state should come from accounts/{accountId}/tokens?token.id={tokenId}1 endpoint.

Note

Currently, the Mirror Node only allows the user to fetch associations without specifying a "block number"/timestamp. See #96 for more details.

Footnotes

  1. https://testnet.mirrornode.hedera.com/api/v1/docs/#/accounts/getTokensByAccountId

@se7enarianelabs se7enarianelabs added the feature Enhancing an existing feature driven by business requirements. Typically backwards compatible. label Oct 31, 2024
@se7enarianelabs se7enarianelabs changed the title Implement HIP-719 for fungible tokens [Foundry] Implement HIP-719 for fungible tokens Nov 2, 2024
@acuarica acuarica changed the title [Foundry] Implement HIP-719 for fungible tokens [Foundry] Implement HIP-719 state for fungible tokens Nov 15, 2024
@acuarica acuarica changed the title [Foundry] Implement HIP-719 state for fungible tokens [Foundry] Fetch HIP-719 remote state for fungible tokens Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Enhancing an existing feature driven by business requirements. Typically backwards compatible.
Projects
Status: Backlog
Development

No branches or pull requests

1 participant