-
Notifications
You must be signed in to change notification settings - Fork 43
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
Enable Automatic ATA Creation in ChainWriter #1033
Open
silaslenihan
wants to merge
8
commits into
develop
Choose a base branch
from
ata-creation
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
7da755c
Revert "Added location parsing for IsWritable and IsSignable on Accou…
silaslenihan fcfc039
Added ArgsTransform to ChainWriter (#1015)
silaslenihan 6ac6fe9
Cleaned up example
silaslenihan 46a7404
Updated chain_reader_test error from go.mod bump
silaslenihan d4df43a
Revert "Updated chain_reader_test error from go.mod bump"
silaslenihan cb6a64f
Added transform registry
silaslenihan aa71d84
Updated PDALookup internal field to use codec
silaslenihan 0ad1ce7
Enabled automatic ATA creation in CW
silaslenihan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably makes sense to split this into 2 separate TXs to save space for the main TX. @amit-momin does the TXM guarantee order of execution natively, or do we have to poll for finality on the first TX before sending the second one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just mentioning this here for visibility before I make the change. I think we may need to poll for finality if we split it. We would broadcast the transactions sequentially but don't think there's any guarantees that they are included in that order. Since they interact with the same account, I think Solana's localized gas markets would mean the tx with the higher price out of the 2 would get included first. Since they would be individual tx in the TXM, I don't think we can make the distinction to ensure the ATA tx always stays higher priced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. Regardless I think it makes sense to split them up since tx sizes are so small on Solana. Should probably check with the on-chain team to confirm they agree