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

Prevent Unauthorized Fund Spending in ChainSignature Contract using FunctionCall key #242

Open
Pessina opened this issue Jun 5, 2024 · 0 comments
Open

Prevent Unauthorized Fund Spending in ChainSignature Contract using FunctionCall key #242

Pessina opened this issue Jun 5, 2024 · 0 comments
Assignees
@Pessina

Comments

@Pessina
Copy link
Collaborator

Pessina commented Jun 5, 2024 •
edited
Loading

Currently, it's possible to call the ChainSignature contract using a FunctionCall key, allowing the dApp that holds the key to spend user funds. To prevent this, we propose adding a deposit fee to the contract call, ensuring only a FullAccess key can execute the contract.
@Pessina Pessina self-assigned this Jun 5, 2024
@Pessina Pessina transferred this issue from near/mpc Jun 5, 2024
@Pessina Pessina changed the title FunctionCall key should not be able to call ChainSignature contract Prevent Unauthorized Fund Spending in ChainSignature Contract using FunctionCall key Jun 5, 2024
@Pessina Pessina removed their assignment Jun 5, 2024
@Pessina Pessina self-assigned this Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Pessina Pessina

Labels
None yet
Projects
Emerging Technologies
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Pessina