Transaction Types
Paxeer supports Ethereum transaction types 0, 1, 2, and 4, but not blob transactions (type 3), under the Pectra hardfork.
Transaction Types
Paxeer supports most Ethereum transaction types. The one notable exception is blob transactions.
Supported Types
| Type | EIP | Name | Paxeer support |
|---|---|---|---|
| 0 | - | Legacy | Supported - governance-set minimum gas price applies |
| 1 | EIP-2930 | Access list | Supported |
| 2 | EIP-1559 | Fee market | Supported - base fee is not burned |
| 4 | EIP-7702 | Set code | Supported |
Not Supported
| Type | EIP | Name | Notes |
|---|---|---|---|
| 3 | EIP-4844 | Blob | Not supported - Paxeer runs Pectra without blob transactions |
Blob Transactions
Paxeer runs the Pectra hardfork without blob transaction support. Attempting to send a type 3 transaction will be rejected at the RPC level.
If you are porting code from Ethereum that uses blob transactions (e.g. rollup data availability), that path does not apply to Paxeer.
Sending Transactions
Standard library defaults work correctly. viem, wagmi, and ethers all default to type 2 (EIP-1559) transactions on chains that support it, which Paxeer does.
viem
import { createWalletClient, http, parseEther } from 'viem';
import { privateKeyToAccount } from 'viem/accounts';
import { sei } from 'viem/chains';
const account = privateKeyToAccount('0xYourPrivateKey');
const client = createWalletClient({ account, chain: sei, transport: http() });
// Sends a type 2 transaction - correct default for Paxeer
const hash = await client.sendTransaction({
to: '0xRecipient',
value: parseEther('1'),
});ethers
import { ethers } from 'ethers';
const provider = new ethers.JsonRpcProvider('https://evm-rpc.sei-apis.com');
const wallet = new ethers.Wallet('0xYourPrivateKey', provider);
// ethers defaults to EIP-1559 where supported - correct for Paxeer
const tx = await wallet.sendTransaction({
to: '0xRecipient',
value: ethers.parseEther('1'),
});