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

Make payer optional in ExtendLookupTable instruction #23411

Closed
ckamm opened this issue Mar 1, 2022 · 1 comment · Fixed by #23678
Closed

Make payer optional in ExtendLookupTable instruction #23411

ckamm opened this issue Mar 1, 2022 · 1 comment · Fixed by #23678

Comments

@ckamm
Copy link
Contributor

ckamm commented Mar 1, 2022

Problem

Programs that maintain address lookup tables may want to fund these tables fully upfront to avoid passing in a payer and system_program to the ExtendLookupTable instruction.

This comes up when a program wants to take user lamports only once, during some create-account instruction and wants to later extend an address lookup table without needing access to user lamports again.

It can currently be worked around by manually funding the address lookup table account during creation, and then passing a stub payer to ExtendLookupTable. But a cleaner API would be appreciated.

Proposed Solution

Make accounts 2 ("[SIGNER, WRITE] Account that will fund the table reallocation") and 3 ("System program for CPI.") optional in ExtendLookupTable. Possibly add an option to fully fund the table to CreateLookupTable.

@jstarry

@github-actions
Copy link
Contributor

This issue has been automatically locked since there has not been any activity in past 7 days after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant