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] Use --fork-block-number configuration setting to fetch allowances and associations #96

Open
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

HIP-980 introduces a timestamp parameter that allows to query allowances and token associations up to a given timestamp.

We should fetch allowances and token associations up to that specified block.number.

Note

This issue is blocked until HIP-980 is implemented in the Mirror Node and deployed to mainnet, testnet and previewnet.

@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 Use blockNumber configuration setting to fetch allowances [Foundry] Use blockNumber configuration setting to fetch allowances Nov 2, 2024
@acuarica acuarica changed the title [Foundry] Use blockNumber configuration setting to fetch allowances [Foundry] Use --fork-block-number configuration setting to fetch allowances Nov 12, 2024
@acuarica acuarica moved this from Backlog to Blocked in Smart Contract Sprint Board Nov 15, 2024
@acuarica acuarica changed the title [Foundry] Use --fork-block-number configuration setting to fetch allowances [Foundry] Use --fork-block-number configuration setting to fetch allowances and associations 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: Blocked
Development

No branches or pull requests

1 participant