FAQ
Last updated
Was this helpful?
Last updated
Was this helpful?
A: We don't support Windows officially, the community has a fork for Windows, you can find it .
A: We don't support it officially, the community has a fork for Dart / Flutter, you can find it
A: Not now, but you can try to wrap it using or , one example is .
A: Take a look at Adding Library Dependency section in , we have detailed instructions for installing the package.
A: Nope.
A: No, Here are some reasons:
WIF (Wallet Import Format) is just a private key encoded in Base58-check format, you can decode it using Base58 class.
It's cumbersome to support different prefix byte for all networks (mainly Bitcoin and forks)
Hex string encoding is a more widely used format.
A: Yes, There is a generic AnyAddress class to represent an address for any blockchain you can use AnyAddress.isValid() to validate if an address is valid.
HDWallet from private key?A: HDWallet class is short for Hierarchical Deterministic Wallet, which is a way to deterministically generate a tree of keys from a single seed (aka bip39 recovery phrase). If you only have a private key, you can use PrivateKey class directly, no way to create HDWallet.
A: Wallet Core doesn't provide this feature yet, it also differs from chain to chain, you should check out the blockchain's official RPC or API to see how to query the balance.
A: Wallet Core doesn't provide this feature yet, it also differs from chain to chain, you should check out the blockchain's official RPC or API to see how to send a signed transaction.
A: Usually this error means the node can't find the unspent transaction (UTXO) you are trying to spend, you can check if the transaction hash is correct, Bitcoin implementation in Wallet Core expects the transaction id is network byte order (big endian), you can try to reverse the bytes of the transaction hash.
A: Wallet Core doesn't support any testnet in general:
no testnet network entry in registry.json
no method to generate testnet address for Bitcoin etc.
extra maintenance effort and we always require mainnet transaction signing test.
But for some networks like Ethereum, the testnet just has a different chain id, you can specify chain id when you signing a transaction.
A: Yes
A: Polkadot supports multiple elliptic curve and signature schemes:
The vanilla ed25519 implementation using Schnorr signatures.
The Schnorrkel/Ristretto sr25519 variant using Schnorr signatures.
ECDSA signatures on secp256k1
It's might be incompatible with other wallets because Wallet Core currently only supports ed25519.
You can read , , for more information.
A: You can find some on , the comprehensive and up-to-date examples are in tests folder:
C++ tests:
Swift tests:
Kotlin tests:
TypeScript tests:
For instance, you can use and to query the balance (and token balance) of an Ethereum or EVM compatible address.
For instance, you can use to send a signed raw transaction to Ethereum or EVM compatible chain.
A: AnyAddress generates SegWit address by default for Bitcoin, Wallet Core offers another class BitcoinAddress for legacy address, you can see all the methods .
For more information, please refer to .