fix createLUTProposal tx size #1777
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@hauchu1998 is attempting to deploy a commit to the blockworks-foundation Team on Vercel. A member of the Team first needs to authorize it. |
hauchu1998
commented
Aug 16, 2023
asktree
reviewed
Aug 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While extending lookup table, the max address to add at once]e is ~20 addresses.
reference from here.
Since sending cNFT can easily exceed that amount due to the proof and other instruction accounts, splitting
extendInstructioninto multiple transactions is necessary. Moreover, maybecreateLookupTableandextendLookupTableshould also separate into different transactions or the tx size will be larger than the restriction?