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

Feature Proposal: Treasury Account #44

Open
ebrightfield opened this issue May 22, 2023 · 0 comments
Open

Feature Proposal: Treasury Account #44

ebrightfield opened this issue May 22, 2023 · 0 comments

Comments

@ebrightfield
Copy link

Problem:
Currently, it is difficult to use multisig signers as funders of lamports, and it requires downstream implementations to use modify lamports directly instead of using a Transfer system instruction. This potentially prevents the use of a Squad as an authority, creator, and/or funder of various account types in the ecosystem. Sometimes there are workarounds, e.g. if there is a separate "funder" field where a system-program owned account can be specified, but this is not always the case and furthermore requires the use of nonce accounts due to time constraints assocaited with recent blockhashes.

Solution:
Each Squad could have a System-program owned PDA derived from the Squad's public key. The Squads MPL program could then sign using that PDA on proposals that involve the use of that address as a signer, thus allowing for direct use of the system program instructions to create accounts and transfer lamports. This greatly expands the possible use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant