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

Balance Capability target check #296

Closed
janezpodhostnik opened this issue Jul 15, 2022 · 1 comment · Fixed by #450
Closed

Balance Capability target check #296

janezpodhostnik opened this issue Jul 15, 2022 · 1 comment · Fixed by #450
Assignees
Labels
Bug 🪲 Feature Feedback good first issue Good for newcomers Needs Estimation SC-Eng Issues that we want to see surfaced in SC-Eng ZH Board

Comments

@janezpodhostnik
Copy link
Collaborator

janezpodhostnik commented Jul 15, 2022

Issue To Be Solved

The target of the balance capability in Flow core contracts here:

Is not verified that it is in fact targeting the default FLOW vault.

Suggest A Solution

This can be verified, using the getLinkTarget method.

But you are currently not able to due paths not being comparable onflow/cadence#1815.
A workaround would be to compare the "path.toString()" values, but this seems dirty.

@joshuahannan
Copy link
Member

Looks like this was already addressed in FlowStorageFees but still exists in FlowServiceAccount. I'll make a PR to address it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🪲 Feature Feedback good first issue Good for newcomers Needs Estimation SC-Eng Issues that we want to see surfaced in SC-Eng ZH Board
Projects
Archived in project
2 participants