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.

Sign up for GitHub

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

Jump to bottom

Getter that aggregates the withdrawable amount across all streams #663

Open
PaulRBerg opened this issue Aug 23, 2023 · 4 comments
Open

Getter that aggregates the withdrawable amount across all streams #663

PaulRBerg opened this issue Aug 23, 2023 · 4 comments
Labels
effort: epic Multi-stage task that may require multiple PRs. priority: 3 Nice-to-have. Willing to ship without this. type: feature New feature or request. work: complex Probe-sense-respond. The relationship between cause and effect can only be perceived in retrospect.

Comments

@PaulRBerg
Copy link
Member

PaulRBerg commented Aug 23, 2023 •
edited
Loading

It may be useful for simplifying our Snapshot strategies.

See this.

Implementing #644 would be a prerequisite.
@PaulRBerg PaulRBerg added type: feature New feature or request. effort: high Large or difficult task. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise. priority: 3 Nice-to-have. Willing to ship without this. and removed backlog labels Jan 1, 2024
@razgraf
Copy link
Member

razgraf commented Jan 8, 2024

Shouldn't this feature reside in a periphery?

@PaulRBerg
Copy link
Member Author

It's not the way it was conceptualized in this issue - it has to be in the Core because the goal is to take a user address as an input and a token and obtain the withdrawable amount for that combo.

This feature requires a reverse mapping (á la #644), but we've never gotten to implement that, so .. this issue remains idle for the time being.

@PaulRBerg PaulRBerg added work: complex Probe-sense-respond. The relationship between cause and effect can only be perceived in retrospect. and removed work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise. labels Jan 11, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 182 days with no activity. Leave a comment or remove the "stale" label, otherwise this will be closed in 14 days.

@github-actions github-actions bot added the stale Inactive for a long time. label Jul 14, 2024
@PaulRBerg
Copy link
Member Author

Let's keep open

@github-actions github-actions bot removed the stale Inactive for a long time. label Jul 21, 2024
@PaulRBerg PaulRBerg added effort: epic Multi-stage task that may require multiple PRs. and removed effort: high Large or difficult task. labels Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: epic Multi-stage task that may require multiple PRs. priority: 3 Nice-to-have. Willing to ship without this. type: feature New feature or request. work: complex Probe-sense-respond. The relationship between cause and effect can only be perceived in retrospect.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PaulRBerg @razgraf