Transactions

This section covers how KalyChain processes transactions, including different transaction types, the transaction pool, and validation rules.

Overview

Transactions are cryptographically signed instructions from accounts that modify the blockchain state. On KalyChain, transactions can:

• Transfer KMT — Send native currency between accounts.
• Deploy Smart Contracts — Create new contract instances.
• Call Contract Functions — Execute contract methods.
• Interact with DeFi Protocols — Use KUSD, KalySwap, and other ecosystem applications.

Transaction Lifecycle

User Signs Transaction
        ↓
Submit to Node (RPC)
        ↓
Transaction Pool (mempool)
        ↓
Validator Includes in Block
        ↓
Block Validated & Finalized
        ↓
State Updated

Key Concepts

Gas and Fees

Every transaction requires gas to execute:

• Gas Limit — Maximum gas units the transaction can use.
• Gas Price — Fee per gas unit (in wei).
• Transaction Fee — gasUsed × gasPrice

KalyChain's low gas prices make transactions inexpensive compared to Ethereum mainnet.

Nonce

Each account has a nonce — a sequential counter of transactions sent from that account:

• Transactions must use the correct nonce.
• Nonce prevents replay attacks.
• Gaps in nonce sequence block subsequent transactions.

Transaction Types

KalyChain supports multiple transaction formats:

Type	Description
Legacy (FRONTIER)	Original Ethereum transaction format
EIP-2930 (ACCESS_LIST)	Includes access list for gas optimization
EIP-1559	Dynamic fee market with base fee + priority fee

Submitting Transactions

Using eth_sendRawTransaction

KalyChain requires pre-signed transactions:

curl -X POST --data '{
  "jsonrpc":"2.0",
  "method":"eth_sendRawTransaction",
  "params":["0xf86c...signed-transaction-hex"],
  "id":1
}' http://localhost:8545

No Account Management

KalyChain nodes don't store private keys. Use eth_sendRawTransaction with transactions signed by external wallets, not eth_sendTransaction.

Transaction Parameters

Parameter	Description
nonce	Transaction sequence number
to	Recipient address (null for contract deployment)
value	Amount of KMT to send (in wei)
data	Contract call data or deployment bytecode
gas	Gas limit
gasPrice	Gas price (legacy) or maxFeePerGas/maxPriorityFeePerGas (EIP-1559)

In This Section

• Transaction Pool — How pending transactions are managed.
• Transaction Types — Detailed format for each transaction type.
• Transaction Validation — How transactions are validated.

Further Reading

• API Reference — JSON-RPC methods for transaction submission.
• Events and Logs — Smart contract event handling.