Creating Hook data for Solana
0. Order creation
Make sure that you're creating order with receiver = exe59FS5cojZkPJVDFDV8RnXCC7wd6yoBjsUtqH7Zai
(hex: 0x09b966be097f46dcf58ebaae2365f56b74cd218a2b8c62468ffa4c53d484b053)
This is the program that deserializes calldata, converts it into Solana TransactionInstructions and executes them via CPI.
1. Intro
Solana calldata is a serialized TransactionInstruction
list with additional metadata (see next sections). It can be serialized using a wasm module built by deBridge.
After order fulfillment funds are transferred to the AUTHORITY_PLACEHOLDER (in case take token is native sol). When take token is SPL token funds are being transferred to the WALLET_PLACEHOLDER.
During calldata execution (via UI or automatic executor) executor (entity that sends transaction with ExecuteExternalCall instruction) transfers *rewards* amount of native Sol to AUTHORITY_PLACEHOLDER and receives *expenses* amount of take token from WALLET_PLACEHOLDER.
Each calldata instruction is signed by AUTHORITY_PLACEHOLDER during execution, no additional signatures could be passed to the CPI.
2. Expenses
Determine how much lamports your instruction spends on the destination network (most often, for account creation). Record this value as expenses. Each instruction is technically worth 5000 lamports (since we can't determine how many resources it will spend in advance, the implication is that it can be executed in a separate transaction). Therefore, 5000 + expenses is the estimate of how much lamports will cost the execution.
2.1. Rewards
Reward is an amount that covers taker expenses (expenses field) and makes execution of calldata profitable for executor => makes calldata to be executed automatically. Reward for each instruction is deducted from the wallet placeholder amount. Rewards can't be native sol. Rewards are set by the DLN API.
3. Pubkey substituion
Determine which accounts in the instruction are input-dependent and cannot be passed directly from the user for security reasons.
For example, if there is a PDA in the destination network that depends on some unique transfer identifier, then we need to form `PubkeySubstitutions`
3.1 Expenses
As well as pubkey substitutions, placeholders could be used to substitute extcall accounts, but placeholders can't be used to calculate ATA during extcall execution. At the moment we have the following placeholders:
ExtcallMetaPlacehoder:
7cu34CRu47UZKLRHjt9kFPhuoYyHCzAafGiGWz83GNFs
will be replaced by ExtcallMeta. ExtcallMeta contains such info as order take token, take token amount, execution state, orderId.
If both placeholder and substitution are used for the same account, only substitution will be performed.
4. DataSubstitution
If you need a transfer amount as part of your transfer and it cannot be calculated in advance, then you must use DataSubstitution
. One substitution is now available (SubmissionAuthWalletAmount
) which works as follows. Takes the account_index
account of the current instruction, interprets it as a token account, takes its balance, chooses its encoding (big endian, little endian), uses substration
and inserts it into the current instruction by offset
before calling it.
5. Calldata serialization
Instructions should be serialized one by one, final calldata is a concatenation of separately serialized instructions.
Solana's TransactionInstruction
s could be serialized into calldata format using @debridge-finance/debridge-external-call
npm package:
Copy
Last updated
Was this helpful?