The OKT Chain (OKTC) features a robust and flexible accounts system designed to support both Cosmos SDK and Ethereum-compatible workflows. Built with interoperability in mind, OKTC enables seamless interactions across multiple blockchain ecosystems while maintaining security and usability. This guide dives into the architecture of OKTC accounts, explores the different address formats, explains public key types, and outlines practical usage scenarios.
Whether you're a developer integrating with OKTC or a user managing assets across platforms, understanding how addresses and keys work is essential for secure and efficient operations.
Core Components of OKTC Accounts
OKTC implements a custom Account type based on Ethereum’s ECDSA secp256k1 elliptic curve cryptography. This design choice ensures compatibility with Ethereum’s Web3 tooling while aligning with Cosmos SDK standards. The system supports hierarchical deterministic (HD) wallets following BIP44 specifications, with a root derivation path of:
m/44'/60'/0'/0This path conforms to EIP84, enabling users to generate consistent key pairs from a single mnemonic phrase—ideal for cross-platform wallet recovery and management.
👉 Discover how to manage multi-format blockchain addresses securely and efficiently.
Types of Addresses and Public Keys
OKTC supports three primary account types, each serving a distinct role within the network. These include user accounts, validator operators, and consensus nodes—each with unique address prefixes and cryptographic curves.
1. User Accounts
Used by individuals to send transactions, participate in governance, and hold assets.
- Address Prefix (Bech32):
ex - Public Key Prefix:
expub - Curve:
eth_secp256k1 - Address Length: 20 bytes
- Public Key Length: 33 bytes (compressed)
Example:
Address: ex1hcngft7gfkhn8z8fnlajzh7agyt0az0v6ztmme
PubKey: expub17weu6qepqgantzvj79rywafrxmye524tpa8kp6akjct3nw7wel623lsnfwynqyfe75k2. Validator Operator Accounts
Identify the operators responsible for running validator nodes. These are used for staking, delegation, and governance voting.
- Address Prefix:
exvaloper - Public Key Prefix:
exvaloperpub - Curve:
eth_secp256k1
3. Consensus Node Keys
Used by validator nodes during the consensus process (e.g., signing blocks).
- Address Prefix:
exvalcons - Public Key Prefix:
exvalconspub - Curve:
ed25519 - Public Key Length: 32 bytes
These distinctions ensure clear separation between identity, operational control, and network-level participation.
Dual Address Format Support
One of OKTC’s standout features is its support for two address formats—Bech32 and hexadecimal (Hex)—to bridge Cosmos and Ethereum ecosystems.
Bech32 Format
Default format used in Cosmos SDK tools like CLI and REST APIs.
- Example:
ex1hcngft7gfkhn8z8fnlajzh7agyt0az0v6ztmme
Hex Format (EIP55-compliant)
Compatible with Ethereum wallets such as MetaMask.
- Example:
0xBE2684Afc84daf3388E99FFB215FdD4116FE89EC
Both formats derive from the same mnemonic seed, meaning they represent the same underlying account. Consequently, the balance and token holdings (e.g., OKT) are identical across both formats.
🔍 Tip: When importing your mnemonic into MetaMask, the wallet recovers the Hex (0x) address. Meanwhile, OKTC’s CLI (exchaincli) displays the Bech32 (ex) version by default.
👉 Learn how to convert between Bech32 and Hex addresses with ease.
Relationship Between ex and 0x Addresses
Despite their different appearances, ex and 0x addresses are two representations of the same cryptographic identity:
| Feature | ex Address | 0x Address |
|---|---|---|
| Format Standard | BIP173 (Bech32) | Ethereum Hex (EIP55) |
| Primary Use Case | OKTC Web & Mobile Apps, CLI | MetaMask, Web3 dApps |
| Derivation Source | Same mnemonic seed | Same mnemonic seed |
| Asset Balance | Fully synchronized | Fully synchronized |
This dual-format approach allows users to interact with both native OKTC applications and Ethereum-based decentralized apps without needing separate wallets or keys.
Practical Usage Guidelines
- ✅ Use
exaddresses directly on OKTC’s DEX web interface, mobile app, or viaexchainclifor transfers, deposits, staking, and voting. - ✅ Use
0xaddresses in MetaMask for sending OKTC tokens. - ❌ Do not attempt cross-format transfers (e.g., sending from an
exaddress to a0xaddress). While they belong to the same user, the network treats them as distinct endpoints. Always send funds using matching format addresses.
Converting Between Address Formats
Since both address types originate from the same private key, conversion between Bech32 (ex) and Hex (0x) is possible using cryptographic utilities.
Developers can leverage official SDKs for format transformation:
Java SDK:
exchain-java-sdk- Methods:
convertAddressFromHexToBech32,convertAddressFromBech32ToHex
- Methods:
JavaScript SDK:
exchain-javascript-sdk- Functions: Available in
/src/crypto/index.js
- Functions: Available in
These tools enable seamless integration into dApps, wallet services, or backend systems requiring multi-format address handling.
Frequently Asked Questions (FAQ)
Q: Are ex and 0x addresses linked to the same wallet?
A: Yes. Both addresses are derived from the same mnemonic phrase and share the same private key. Your OKT balance is unified across both formats.
Q: Can I transfer OKT from an ex address to a 0x address?
A: No. Although they belong to the same user, direct transfers between different format addresses are not supported. Always use the same format for sender and recipient.
Q: Which address should I use for MetaMask?
A: Use the 0x prefixed Hex address. MetaMask recognizes this format natively and will display your OKTC balance when connected to the correct network.
Q: How do I find my Hex address if I only have my Bech32 address?
A: You can use the JSON-RPC method oktc_accounts or SDK conversion functions to derive the Hex equivalent.
Q: Is there any difference in security between the two formats?
A: No. Security depends on private key protection, not address format. Both formats are equally secure when used correctly.
Q: Why does OKTC support two address formats?
A: To ensure compatibility with both Cosmos SDK tools (Bech32) and Ethereum’s vast Web3 ecosystem (Hex), providing flexibility for developers and users alike.
Understanding OKTC’s account model empowers you to navigate its ecosystem confidently—whether you're building decentralized applications or managing digital assets. With native support for dual address formats and strong cryptographic foundations, OKTC delivers a hybrid experience that bridges two major blockchain worlds.
👉 Access advanced tools for managing OKTC accounts across formats.