SVM Transactions

​

简介

• 当用户需要从 SVM 链（例如 Solana）发起转账或兑换时，Skip Go API 会返回一个 SvmTx 类型，供开发者传递给用户进行签名。
• 本文面向尚不熟悉 SVM 中交易构造概念、但需要使用 SvmTx 帮助用户在 Solana 与其他 SVM 链之间转入或转出的 CosmosSDK 和 EVM 开发者。
• 由于在网络高度拥堵时，将 Solana 交易上链本身较为困难，我们强烈建议使用 /submit 端点，以避免处理复杂的重试逻辑和/或为提升提交可靠性而接入多个 RPC 提供方。Skip Go API 的 /submit 端点已经为你实现了 Solana 交易提交的最佳实践。

​

与 Solana 钱包交互

​

配置 SkipClient 以使用 Solana 钱包

import { useWallet } from "@solana/wallet-adapter-react";
import { PhantomWalletName } from "@solana/wallet-adapter-phantom"
import { SkipClient } from '@skip-go/client';

const { wallets } = useWallet();

const skipClient = new SkipClient({
  getSVMSigner: async (chainID) => {
		const { svm } = trackWallet.get();
		const solanaWallet = wallets.find((w) => w.adapter.name === PhantomWalletName);
    return solanaWallet
  }
});

​

理解 SvmTx 数据结构

• chain_id：该交易应提交到的链 ID。
• tx：这是交易的 base64 编码字节内容，你应当让最终用户对其进行签名。

​

关于 SvmTx.tx 的说明

• 用户的 nonce（在 Solana 中，默认情况下这实际上是一个 recent blockhash）
• 指令（相当于 Solana 中的消息）
• 基础交易费（默认设置为每个签名 500 lamports）
• 优先费（下文会进一步说明我们的设置方式）

​

对 tx 进行签名

​

优先费是如何设置的

• 如果相对于其他访问相同状态的交易来说费用较低，那么该交易很可能不会被打包。
• 如果相对于这些访问相似状态的其他交易来说费用较高，那么它就更有可能被打包。

​

Intro

• When a user needs to transfer or swap from an SVM chain (e.g. Solana), the Skip Go API will return an SvmTx type for the developer to pass to the user for signing
• This doc is intended for CosmosSDK and EVM developers who aren’t already familiar with the concepts of transaction construction in the SVM and need to use SvmTx to help their users move from/to Solana and other SVM chains.
• Due to the difficult nature of including Solana transactions on chain during times of high network congestion, we HIGHLY recommend using the /submit endpoint to avoid dealing with complex retry logic and/or multiple RPC providers for submission reliability. Skip Go API’s /submit endpoint implements best practices for Solana transactions submission for you!

​

Interact with Solana Wallets

​

Set up the SkipClient to use a Solana wallet

import { useWallet } from "@solana/wallet-adapter-react";
import { PhantomWalletName } from "@solana/wallet-adapter-phantom"
import { SkipClient } from '@skip-go/client';

const { wallets } = useWallet();

const skipClient = new SkipClient({
  getSVMSigner: async (chainID) => {
		const { svm } = trackWallet.get();
		const solanaWallet = wallets.find((w) => w.adapter.name === PhantomWalletName);
    return solanaWallet
  }
});

​

Understand SvmTx Data Structure

• chain_id: The ID of the chain that this transaction should be submitted to
• tx: This is the base64 encoded bytes of the transaction you should have the end user sign.

​

Info on SvmTx.tx

• User’s nonce (In Solana, this is actually a recent blockhash by default)
• Instructions (Solana’s equivalent to messages)
• Base transaction fees (Set to the default of 500 lamports per signature)
• Priority fees (More info on how we set these below)

​

Signing tx

​

How Priority Fees are Set

• If the fee is low relative to other transactions that access the same state, the transaction is unlikely to get included.
• If its high relative to these other transactions accessing similar state, its likely to be included