How to use Core wallet for Avalanche Teleporter? (Cross-Subnet)

Core Wallet Integration with Avalanche Teleporter

1. Core Wallet natively supports Avalanche’s three primary chains — X-Chain, P-Chain, and C-Chain — but does not directly expose Teleporter UI controls for cross-subnet message initiation within its standard interface.

2. Users must first confirm wallet connectivity to both source and destination subnets via manual RPC configuration or subnet discovery through the Core Wallet’s “Add Network” flow.

3. The wallet displays balances and transaction history per chain only after successful chain registration and block header synchronization.

4. When interacting with Teleporter-enabled contracts, Core Wallet treats them as standard EVM-compatible smart contract calls on the C-Chain — no special signing logic is triggered automatically.

5. Transaction receipts containing Teleporter ICM (Interchain Messaging) events appear in the activity feed, though event parsing remains limited to raw log data without semantic decoding.

Setting Up Subnet Access in Core Wallet

1. Open Core Wallet and navigate to Settings → Networks → Add Network.

2. Enter subnet-specific RPC endpoint, chain ID, currency symbol, and block explorer URL — all obtainable from subnet registry pages hosted on avascan.io or official subnet documentation.

3. Save the network; Core Wallet validates connectivity by querying genesis block hash and verifying finality status.

4. Once added, the subnet appears in the network selector dropdown alongside native Avalanche chains.

5. Importing a subnet address requires manually entering the correct chain ID and ensuring the wallet’s internal provider matches the subnet’s consensus parameters.

Staking and Yield Mechanics Across Subnets

1. Core Wallet enables AVAX staking exclusively on the P-Chain — no direct delegation interface exists for subnet validator participation.

2. Yield-bearing positions on custom subnets require external dApp interaction; Core Wallet serves only as the signing layer for approval and delegation transactions.

3. Staking rewards earned on subnets are reflected in Core Wallet only after being bridged back to the C-Chain or P-Chain via Teleporter-triggered asset transfers.

4. Users can monitor pending cross-subnet reward claims by inspecting Teleporter inbox contracts using the wallet’s built-in contract read functionality.

5. No automatic claim scheduling or batch execution is supported — each claim must be initiated individually through signed transaction submission.

Transaction Signing and Message Composition

1. Core Wallet signs Teleporter messages using the same ECDSA secp256k1 key derivation path applied to all EVM-compatible chains.

2. Raw ICM payloads — including destination chain ID, fee payment address, and encoded call data — are constructed off-wallet by dApps before being passed to Core for signature.

3. Signature validation occurs locally before broadcast; the wallet verifies that the sender address owns the private key associated with the selected account.

4. Gas estimation for Teleporter transactions follows standard EIP-1559 rules on the source chain, but actual relay fees are deducted separately by the ICM Relayer post-delivery.

5. Failed message deliveries due to insufficient relayer balance or misconfigured messenger contracts result in on-chain revert errors visible in the wallet’s transaction detail view.

Frequently Asked Questions

Q: Does Core Wallet support automatic Teleporter message tracking across subnets?A: No. Core Wallet displays only the originating transaction hash and does not poll destination subnets for message confirmation or delivery status.

Q: Can I use Core Wallet to manage keys for subnet validators?A: Core Wallet stores keys used for signing but does not generate or store validator-specific BLS keys required for subnet validation on the P-Chain.

Q: Is there a way to verify Teleporter message content before signing in Core Wallet?A: Core Wallet shows only the destination contract address and value field; full calldata inspection requires external tools or browser-based contract explorers.

Q: Does Core Wallet support Teleporter message cancellation?A: Teleporter messages cannot be canceled once submitted to the source chain; Core Wallet provides no interface to withdraw or invalidate pending ICMs.