Skip to main content
This guide will teach you how to build instructions and transactions that invoke Anchor programs in Kotlin.

​
Add dependencies

Add the following dependencies to your project:
  • web3-solana library provides the abstraction classes like Transaction and AccountMeta to simplify building Solana transactions.
  • rpc-core library provides a SolanaRpcClient class with convenient RPC methods.
  • kborsh library for Borsh serialization of instruction data.
{
`dependencies {
    implementation("com.solanamobile:web3-solana:${versions.KOTLIN_WEB3_SOLANA_VERSION}")
    implementation("com.solanamobile:rpc-core:${versions.KOTLIN_RPC_CORE_VERSION}")
    implementation('io.github.funkatronics:kborsh:${versions.KOTLIN_KBORSH_VERSION}')
}`
}

​
Example: Counter Program

As an example, we’ll build a transaction using this devnet on-chain Counter Program that was created with Anchor. Specifically, let’s invoke the Increment instruction.

​
Instruction Format

Taking a look at the source code, observe that the Increment instruction format expects: Program ID
  • The Counter Program is deployed on devnet with the Program Id: ADraQ2ENAbVoVZhvH5SPxWPsF2hH5YmFcgx61TafHuwu.
Account Addresses
  • The Counter account PDA as a non-signer. "counter" is the only seed used to derive the PDA.
Instruction Data Now, let’s create each of these required inputs.

​
1. Find the Counter account PDA

To derive the Counter PDA, we’ll use the ProgramDerivedAddres interface in the web3-solana module which provides a find method. Call ProgramDerivedAddres.find and pass "counter" as a seed and the Counter program ID: 
import com.solana.publickey.SolanaPublicKey
import com.solana.publickey.ProgramDerivedAddress

val programId = SolanaPublicKey.from("ADraQ2ENAbVoVZhvH5SPxWPsF2hH5YmFcgx61TafHuwu")

// Counter account has a single seed 'counter'
val seeds = listOf("counter".encodeToByteArray())

// Calculate the PDA
val result = ProgramDerivedAddress.find(seeds, programId)

// Unwrap the result
val counterAccountPDA = result.getOrNull()

​
2. Serialize the instruction data

The next step is to build and serialize the instruction data. Using the kotlinx serialization library, define the expected increment arguments as a @Serializable class. 
import kotlinx.serialization.Serializable

@Serializable
class Args_increment(val amount: UInt)
Now, use the AnchorInstructionSerializer to serialize the instruction arguments and lastly use the kBorsh library to Borsh encode the data. 
val encodedInstructionData = Borsh.encodeToByteArray(
    AnchorInstructionSerializer("increment"),
    Args_increment(amount)
)
INFOAnchor instruction data uses a unique Anchor discriminator to determine which instruction is called.The AnchorInstructionSerializer will handle this discriminator during serialization, as long as you pass the correct instruction name (e.g increment) into the constructor.

​
3. Construct the instruction

Putting all the inputs together, you can build the full TransactionInstruction. 
import com.solana.publickey.SolanaPublicKey
import com.solana.transaction.*

val incrementInstruction = TransactionInstruction(
    SolanaPublicKey.from("ADraQ2ENAbVoVZhvH5SPxWPsF2hH5YmFcgx61TafHuwu"),
    listOf(AccountMeta(counterAccountPDA!!, false, true)),
    encodedInstructionData
)

​
4. Create the transaction

Then build a transaction message and construct the Transaction packed with the increment instruction. 
import com.solana.transaction.*
import com.solana.rpc.SolanaRpcClient
import com.solana.networking.KtorNetworkDriver

// Fetch latest blockhash from RPC
val rpcClient = SolanaRpcClient("https://api.devnet.solana.com", KtorNetworkDriver())
val blockhashResponse = rpcClient.getLatestBlockhash()

// Build transaction message
val incrementAmount = 5
val incrementCounterMessage =
    Message.Builder()
        .addInstruction(
            incrementInstruction
        )
        .setRecentBlockhash(blockhashResponse.result!!.blockhash)
        .build()

// Construct the Transaction object from the message
val unsignedIncrementTx = Transaction(incrementCounterMessage)

​
5. Sign the transaction

At this point, you have successfully created an unsigned Solana transaction for incrementing the counter account. Before submitting to the network, the transaction must be signed by the fee payer.

​
Signing with Mobile Wallet Adapter

If you want users to sign the transaction using their mobile wallet app (e.g Phantom, Solflare) you can use Mobile Wallet Adapter to request signing. Read the Using Mobile Wallet Adapter guide to learn how to prompt users to sign these transactions and submit them to the Solana network.

​
Signing with a keypair

If you have direct access to a keypair, you can serialize the Transaction message, sign the bytes, and construct the signed transaction. 
import com.solana.transaction.*
import com.solana.rpc.SolanaRpcClient
import com.solana.networking.KtorNetworkDriver

// Fetch latest blockhash from RPC
val rpcClient = SolanaRpcClient("https://api.devnet.solana.com", KtorNetworkDriver())
val blockhashResponse = rpcClient.getLatestBlockhash()

// Build transaction message
val incrementAmount = 5
val incrementCounterMessage =
    Message.Builder()
        .addInstruction(
            incrementInstruction
        )
        .setRecentBlockhash(blockhashResponse.result!!.blockhash)
        .build()

// Sign the transaction with some keypair signer
val signature = ed25519Signer.signBytes(incrementCounterMessage.serialize())

// Signed transaction ready to be submitted to the network
val signedTransaction = Transaction(listOf(signature), incrementCounterMessage)

​
6. Sending the transaction

After the transaction is signed, it can be submitted to an RPC using the SolanaRpcClient class. 
import com.solana.rpc.SolanaRpcClient
import com.solana.networking.KtorNetworkDriver

val rpcClient = SolanaRpcClient("https://api.devnet.solana.com", KtorNetworkDriver())

val response = rpcClient.sendTransaction(signedTransaction)

if (response.result) {
    println("Transaction signature: ${response.result}")
} else if (response.error) {
    println("Failed to send transaction: ${response.error.message}")
}
Last modified on February 13, 2026