You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
The text was updated successfully, but these errors were encountered: