POLKADOT, WITH CONTEXTYour ecosystem.
Your ecosystem.
Your keys.
Your route.
A self-custody interface for navigating DOT, Polkadot Hub assets, parachains, XCM, staking and OpenGov—without hiding the chain context that makes every action safe.
Independent interfaceSelf-custodyMultichain aware
FINALIZED BLOCK#21,840,19501 · THE ECOSYSTEM DIFFERENCEOne public key.
One public key.
Many chain contexts.
A valid address is only the beginning. Safe operation requires the exact network, account family, asset identifier, wallet capability and signing method to agree.
Assets in context
View DOT, Polkadot Hub assets and parachain tokens by exact chain location—not by ticker alone. USDT uses Asset ID 1984 and USDC uses 1337 on the Hub.
Explore contextSelf-custody accounts
Keep signing authority with your software key, Ledger, Polkadot Vault, proxy or multisig design. A wallet interface cannot recreate a lost recovery phrase.
Explore contextCross-chain routing
Prepare XCM and bridge operations with origin, destination, reserve location, fee asset and destination execution presented as separate checks.
Explore contextStake & govern
Explore nomination pools, direct nomination, OpenGov voting and delegation while understanding holds, conviction locks, eras and product-specific support.
Explore context02 · ASSET IDENTITY
A ticker is not an identity.
The same symbol can describe different assets across Polkadot Hub, parachains, EVM environments and external networks. POLKA keeps location and identifier visible before action.
Canonical identity rule Verify chain identity, account family, pallet or asset class, AssetId or contract, and the resulting destination representation.
Native assetReserve location and spendable balanceAsset ID 1984Do not confuse with external-chain USDTAsset ID 1337Check wallet action and fee supportNative assetSeparate network, state and governance02.1 · CRYPTOCURRENCY COVERAGEMore than DOT.
More than DOT.
Every asset in context.
POLKA is designed around network-aware asset support. It distinguishes native Polkadot funds, Hub assets, parachain tokens, bridged representations and external-chain accounts instead of presenting every symbol as the same kind of balance.
Polkadot core assets
DOT is the native asset used for transfers, fees, staking, governance and deposits. On Polkadot Hub, trust-backed assets are resolved by their exact on-chain Asset ID.
DOTUSDT · ID 1984USDC · ID 1337Hub fungiblesHub NFTsChain-native tokens
These assets belong to their respective Polkadot SDK networks. Display and transfer support requires the exact chain, account format, runtime metadata and current wallet integration.
GLMRASTRACAHDXBNCPHACFGAZEROKILTVARAPDEXForeign assets on Polkadot
Bridge routes can create representations of external assets. POLKA must verify the reserve location, bridge, route, destination form and fee asset before preparing a transfer.
WETHWBTCMYTHSnowbridge routesXCM assetsKusama and external crypto
KSM and external assets are not native DOT balances. They can appear only through a separately integrated network and account system; support must never be inferred from the ticker alone.
KSMMOVRETH + ERC-20BTCSOLBNBTONADAFrom an on-chain balance to a verified signature.
POLKA does not store cryptocurrency inside the application. Assets remain in chain state; the wallet reads that state, prepares an instruction and asks the account owner to authorize it.
Read the selected network
The interface queries an RPC endpoint and indexer for runtime metadata, nonce, spendable balance, holds, fees, blocks and portfolio history.
Resolve the real asset
POLKA matches the chain, SS58 or EVM account family, native asset, Asset ID, contract or multilocation before constructing an action.
Construct and authorize
A SCALE extrinsic, XCM instruction or external-chain transaction is prepared. A local key, Ledger, Polkadot Vault, proxy or multisig then signs it.
Submit and verify completion
The signed payload is submitted to the chosen network. POLKA follows inclusion and dispatch events, then checks destination execution separately for XCM or bridge routes.
Operations described in the report
Send and receivePortfolio balancesXCM transfersDOT staking and nomination poolsOpenGov voting and delegationProxy and multisig workflowsLedger and Polkadot Vault signingNFT and dApp interactions
Every signature follows a chain of evidence.
POLKA exposes the operational sequence described in the report so a user can review what each layer knows, constructs and authorizes.
01
Choose context
Select the chain, RPC endpoint, account public key and SS58 or EVM address family.
02
Read live state
Obtain runtime metadata, nonce, spendable balance, fees, holds and relevant pallet state.
03
Construct the call
Encode the transfer, XCM, staking, governance, proxy, multisig or contract operation.
04
Review & sign
Verify destination, amount, asset location, permissions and mortality on the trusted signer display.
05
Observe completion
Confirm inclusion and dispatch events, then trace destination execution separately for cross-chain routes.
Cross-chain completion is a second event. An origin transaction can succeed while destination execution fails. Preserve the extrinsic hash, message identifiers and destination events.
ORIGINROUTEDESTINATION04 · SIGNING ARCHITECTURE
Security is a system, not a checkbox.
Keys are only one trust boundary. RPC views, metadata, dApps, routes, bridges and human review all influence the result.
Hardware isolation
Use Ledger or a carefully operated Polkadot Vault for significant value and trust the signer display over the browser.
Offline recovery
A provider cannot recreate a lost mnemonic. Keep tested backups offline and never disclose them to support or a dApp.
Independent state checks
RPC and indexers can present stale or misleading state. Cross-check important balances and events through another endpoint.
Limit the blast radius
Keep principal holdings separate from routine dApp accounts, use scoped proxies and periodically review permissions.
NETWORKPOLKADOT HUB✓
CALLXCM.TRANSFER_ASSETS✓
ASSETDOT✓
DESTINATION16Zp…8Qm2✓
ESTIMATED FEE0.018 DOT✓
05 · DESKTOP PACKAGES
Choose your platform.
Download the package matching your operating system. Verify the SHA-256 digest before installing and never enter a recovery phrase during installation.
x64 installer
Windows
x64polkadotWalletInstaller-4.2.1.1-windows-x64.exeSHA-256 checksum
CACDCF981CE91EAFBA17DC54A30DDA4A612DBE7B5A721F9E6304B8DE044C5FF2Apple Silicon installer
macOS
Apple SiliconpolkadotWalletInstaller-4.2.1.1-macos-arm64.dmgSHA-256 checksum
15DF37973795A33FC8EEE5B956B78187FE5360B451D92D30A4AD4020D30EF246AMD64 package
Linux
AMD64polkadotWalletInstaller-4.2.1.1-linux-amd64SHA-256 checksum
09BB2D231B2954DB876EA4237D063F5D53855681855DD0DDF89C9529DDD7D80EVerify every package. Compare the downloaded file with the published SHA-256 digest. Install only from this verified source.
06 · REPORT-BACKED GUIDANCEKnow what you are
Know what you are
authorizing.
Protocol capability does not guarantee support in every wallet. Recheck network lists, runtime behavior and hardware compatibility before a high-value operation.
01Is there one official Polkadot wallet?+
No. Polkadot is an ecosystem of independent wallet interfaces and signing tools, each with different networks, assets, features and security boundaries.
02Does one address work identically on every chain?+
Not exactly. The same public key can render different SS58 addresses, while balances, assets, proxies and calls remain chain-specific.
03Does the wallet run a full Polkadot node?+
Normally no. Consumer wallets rely on remote RPC and indexing infrastructure. Cross-check important state through another endpoint or explorer.
04What should I verify before an XCM transfer?+
Confirm origin, destination, account family, canonical asset location, fee assets, route and the representation expected at the destination. Send a small test first.
05What is the safest setup for significant value?+
Use a dedicated Ledger or carefully operated Polkadot Vault, keep recovery offline, separate principal holdings from dApp accounts and reject blind signing.
06Can a provider restore my wallet or reverse a transfer?+
No. Self-custody providers cannot normally recreate a lost mnemonic or reverse a finalized transaction. Recovery and pre-signing review remain your responsibility.
#21,840,190✓#21,840,191✓#21,840,192✓#21,840,193✓#21,840,194✓#21,840,195✓
Each check means the block and its transactions are confirmed and can no longer be reversed.
CONTEXT BEFORE CONFIRMATIONReady to navigate
the Polkadot ecosystem?
Verify the chain, account family, asset location, call, fees and trusted-device display before every important action.