Repository navigation
[Feat] Support manual exec with solana 2.0 as destination - #477
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
👋 PabloMansanet, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
CI Test Report✅ 3907/3913 tests passed (996 suites) in 5m 33s SummaryCoverage report |
| export async function bufferExecutionInputsIxs( | ||
| connection: Connection, |
There was a problem hiding this comment.
nit: do we also need ctx here to keep the convention?
| describe('SolanaChain.buildMessageForDest', () => { | ||
| it('should populate SVMExtraArgsV1 with computeUnits from gasLimit', () => { | ||
| const message = { | ||
| receiver: 'So11111111111111111111111111111111111111112', |
There was a problem hiding this comment.
is this receiver value correct?
There was a problem hiding this comment.
It's just a placeholder pubkey, I went with default +1, but I know it reads a bit strangely, can replace with an arbitrary string if it reads better.
|
|
||
| // Accounts of `buffer_execution_inputs` and `close_execution_inputs_buffer`, the last two for | ||
| // their CPI events | ||
| function bufferingAccounts( |
There was a problem hiding this comment.
are this accounts for buffering the message or just additional accounts that we need to send among?
There was a problem hiding this comment.
They are buffering only. The comment may not be super clear, the last two accounts are just needed for the buffering instructions to call emit_cpi!
| caller, | ||
| bufferId, | ||
| }) | ||
| unsigned = await unsignedExecuteV2Tx(ctx, caller, instruction, lookupTables, { |
There was a problem hiding this comment.
the names generateUnsignedExecuteV2 and unsignedExecuteV2Tx are really similar right? What's the difference?
There was a problem hiding this comment.
Hmmm yeah they're quite similar, generate is the exported entrypoint. The other one just wraps the raw unsigned instruction with some extras i.e. heap frame request, LUT, etc.
I can rename to wrapUnsignedExecuteV2Tx maybe for clarity
a9a65df
No description provided.