NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
The first native Flutter/Dart SDK for the Avalanche network. Pure Dart, no platform channels. Covers C-Chain EVM, Data API (Glacier), P-Chain staking, and X-Chain native assets.
Last release 1 months ago
07 Sep 2026
Ships on a steady schedule
a new release about every 3 weeks
Unknown
no stable releases
Nothing withdrawn
no release was ever pulled
3 months old
6 releases · first in 2026
One column per month.
First on-chain write operation from avalanche_flutter_sdk.
First on-chain write operation from avalanche_flutter_sdk.
TX: 0x43f9d7b50013a5b18b0c1b6eda82875a39f7e7a01d114fa62595ced6f52d1ff2
Amount: 0.001 AVAX | Block: 58,211,707 | ~2s confirmation ✅
final tx = AvaxTransferTransaction(
chainId: 43113,
nonce: nonce,
maxPriorityFeePerGas: options.normal.maxPriorityFeePerGas,
maxFeePerGas: options.normal.maxFeePerGas,
gasLimit: BigInt.from(21000),
to: '0xRECEIVER',
value: BigInt.parse('1000000000000000'),
);
final txHash = await client.sendRawTransaction(tx.sign(privateKey));323/323 passing
v0.2.0-dev: ERC-20 transfers (USDC/USDT) - Phase 2 complete
Phase 2 started: C-Chain read operations available.
Phase 2 started: C-Chain read operations available.
final client = CChainClient(network: NetworkConfig.fuji);
final balance = await client.getBalance('0x71C7...');
final estimator = GasEstimator(client);
final options = await estimator.getPriceOptions();
print(options.normal.maxFeePerGas); // in Wei278/278 passing · 24 new tests
v0.1.2-dev: AvaxTransferTransaction (EIP-1559 signing + broadcast)
Phase 1 complete: the first native Flutter/Dart SDK for Avalanche can now derive wallets and addresses for all three chains.
Phase 1 complete: the first native Flutter/Dart SDK for Avalanche
can now derive wallets and addresses for all three chains.
final mnemonic = Mnemonic.generate(wordlist: WordlistEs.instance);
final wallet = HDWallet.fromMnemonic(mnemonic);
final cAddr = EvmAddress.fromPublicKey(
wallet.derivePublicKeyForCChain());
final xpAddr = XPAddress.fromPublicKey(
wallet.derivePublicKeyForXPChain());254/254 passing · 46 new tests this release
M2: C-Chain JSON-RPC client (EIP-1559 AVAX transfers, ERC-20)
BIP-39 mnemonics EN + ES complete and verified.
BIP-39 mnemonics EN + ES complete and verified.
Ready to publish v0.0.3-dev to pub.dev.
Next: HD key derivation (BIP-44) + address derivation (develop)
Phase 1 in progress: secp256k1 cryptography implemented and verified.
Phase 1 in progress: secp256k1 cryptography implemented and verified.
PrivateKey: secp256k1 private key generation, import, and export
PrivateKey.generate() using FortunaRandom (cryptographically
secure pseudo-random number generator)PrivateKey.fromHex() with strict range validation against the
curve order n (rejects d <= 0 and d >= n)toHex(), toBytes(): 32-byte big-endian exportpublicKey getter: derives Q = d * G per secp256k1toString() returns PrivateKey[REDACTED] - key material is
never exposed via logs, error messages, or debug outputPublicKey: secp256k1 public key derivation, import, and encoding
PublicKey.fromEcPoint(), PublicKey.fromHex() (accepts both
compressed and uncompressed SEC1 encodings)toCompressed(): 33-byte SEC1 encoding - required input for
X-Chain/P-Chain address derivation (sha256 + ripemd160)toUncompressed() / toRawUncompressed(): 65-byte and 64-byte
encodings - required input for C-Chain/EVM address derivation
(keccak256)==, hashCode) based on the underlying
elliptic curve pointpointycastle: ^4.0.0 and meta: ^1.15.0 added as dependenciesn confirmed directly from pointycastle's
ECDomainParameters('secp256k1') at runtime:
fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141d=0 (rejected), d=1 (accepted), d=n-1 (accepted), d=n
(rejected), d=n+1 (rejected)Phase 1 in progress: secp256k1 PrivateKey/PublicKey complete and
tested.
Not ready for production use.
Next: CB58 encoding, then EVM and X/P-Chain address derivation.
SECURITY.md: vulnerability reporting and key handling policy
Initial SDK scaffold - Phase 1 in progress.
SDK Core
Quality Infrastructure
Documentation
After merging and publishing v0.0.1-dev on pub.dev:
Phase 1 (M1): secp256k1 key generation, BIP-39 mnemonics (EN + ES),
HD key derivation (BIP-44), EVM address derivation from public key
Phase 1 in progress: SDK skeleton and project architecture.
AvalancheClient: main entry point for the SDK
NetworkConfig for Mainnet or Fuji TestnetNetworkConfig: official Avalanche RPC endpoint configurations
NetworkConfig.mainnet: Avalanche Mainnet (C-Chain, P-Chain, X-Chain, Glacier API)NetworkConfig.fuji: Avalanche Fuji Testnet (C-Chain, P-Chain, X-Chain, Glacier API)docs.avax.networkNetworkId: enum for Mainnet (1) and Fuji Testnet (5)AvalancheException: base exception class for all SDK errorsanalysis_options.yaml with very_good_analysis linter (zero warnings enforced)scripts/pre_commit.ps1: local quality gate (format + analyze + test).github/workflows/ci.yml: GitHub Actions CI pipeline
develop push).github/pull_request_template.md: PR checklistCONTRIBUTING.md: branch strategy, commit conventions, code and testing standardsSECURITY.md: vulnerability reporting policy and key handling rulesPhase 1 in progress: SDK skeleton, project architecture, and CI infrastructure complete.
Not ready for production use.
Next: secp256k1 key generation, BIP-39 mnemonics (EN + ES), HD key derivation (BIP-44).
Your coding agent can read these notes before it upgrades. Set up the MCP server →