Address Formats in MPC Wallet Systems

·

In the rapidly evolving world of digital asset custody, understanding address formats is essential for secure and efficient management of blockchain assets. Multi-Party Computation (MPC) wallets, such as those offered by ChainUp Custody, support various address types tailored to different blockchain architectures. This guide breaks down the supported address formats, explains address merging capabilities, and helps you navigate best practices for integration and use—ensuring accuracy, security, and operational efficiency.

Whether you're integrating with APIs or managing wallets through custodial platforms, knowing how UTXO, account-based, and memo-enhanced addresses function will empower your team to avoid common pitfalls like lost funds or failed transactions.

Understanding MPC Wallet Address Types

MPC technology eliminates single points of failure by distributing key shares among multiple parties, enhancing security without sacrificing usability. Within this framework, ChainUp Custody supports three primary address types: UTXO-type, account-type, and memo-type. Each serves distinct blockchains and use cases.

UTXO-Type Addresses

The Unspent Transaction Output (UTXO) model underpins Bitcoin and several of its forks. In MPC systems, UTXO-type addresses follow the Legacy format, recognizable by their “1” prefix (e.g., 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa).

When you create a wallet for a UTXO-based chain—such as Bitcoin, Bitcoin Cash, or Bitcoin SV—the system automatically generates a Legacy address tied to the hash of your public key. These addresses are deterministic and securely derived using cryptographic standards.

👉 Learn how to generate secure UTXO addresses with advanced custody solutions.

A notable feature in UTXO management is change address handling. During transactions, any remaining balance not sent to the recipient returns to a change address. ChainUp Custody allows both manual and API-driven creation of multiple UTXO addresses, with the second generated address typically designated as the change address. This ensures better privacy and fund segregation.

Pro Tip: Always verify change address logic in your transaction flow to prevent misrouting of residual funds.

Account-Type Addresses

Unlike UTXO models, account-based blockchains maintain balances directly at addresses, similar to traditional banking accounts. This model powers Ethereum and most EVM-compatible networks.

When creating a wallet for chains like Ethereum (ETH), BNB Smart Chain (BSC), HECO, or other EVM-based protocols, the MPC system generates an account-type address using the BIP-44 standard. These addresses are consistent across all EVM networks—meaning one wallet can manage assets on multiple chains using the same public address.

For example:

This cross-chain compatibility simplifies user experience but requires careful network selection during transfers to avoid irreversible losses.

The first address created becomes the default active address, used for all manual deposits and withdrawals. However, via API access, you can specify alternative addresses for inbound or outbound transactions—offering flexibility for institutional workflows.

Memo-Type Addresses

Certain blockchains—especially those built on the Tendermint or Cosmos SDK frameworks—require additional identifiers beyond the standard address. This is where memo fields come into play.

A memo is a unique alphanumeric string paired with a deposit address to ensure transaction uniqueness and accurate fund attribution. Without the correct memo, deposits may be lost or misallocated.

While app-based creation of memo-type addresses may not visibly expose the memo field, API-created addresses include the memo as a required parameter. This distinction is crucial for automated systems processing high-volume deposits from users.

Example: On networks like Cosmos or OKTC, sending tokens without the correct memo means the receiving exchange or wallet cannot credit the sender properly.

Ensure your integration validates memo inclusion before broadcasting transactions on memo-dependent chains.

👉 Discover how automated systems handle memos and prevent deposit errors.

Address Consolidation Across Supported Chains

To streamline asset management and reduce operational overhead, ChainUp Custody offers address merging functionality. This allows institutions to use a single address across multiple blockchains within the same family—reducing address sprawl and minimizing user error during deposits.

Supported UTXO Chain Merging

For UTXO-based networks, the following are eligible for address consolidation:

This means one Legacy address can receive funds from all three chains—ideal for custodians managing multi-chain Bitcoin forks. However, caution is advised during withdrawals; each chain must be processed separately due to differing consensus rules.

EVM Chain Merging Support

Even more extensive is the support for EVM-compatible chain merging. A single account-type address can serve as a unified receiving point across numerous Layer 1 and Layer 2 networks:

This cross-EVM interoperability significantly reduces the need to generate and track dozens of separate deposit addresses. It enhances user experience while lowering support costs related to incorrect deposits.

However, it's vital to remember:

Even with merged addresses, you must select the correct network when sending funds. Sending ETH on the BSC network (or vice versa) results in permanent loss unless recovered via bridging tools.

Frequently Asked Questions (FAQ)

Q: Can I use the same address for both Bitcoin and Ethereum?
A: No. Bitcoin uses UTXO-style Legacy addresses starting with "1", while Ethereum uses hexadecimal account addresses starting with "0x". They are incompatible and belong to different cryptographic ecosystems.

Q: What happens if I forget to include a memo?
A: On memo-requiring chains, missing or incorrect memos often result in lost deposits. Always double-check API responses and user input forms to ensure memos are captured and validated.

Q: Is address merging safe? Could funds get mixed up?
A: Merging only applies to receiving addresses. Internally, each chain’s balance is tracked separately. Funds do not mix—the system knows which chain each transaction belongs to based on on-chain data.

Q: Can I change my default (primary) address?
A: Yes, but only via API configuration. The first-created address remains the default unless explicitly changed through administrative settings.

Q: Are there plans to support Bech32 (SegWit) or Taproot addresses?
A: While Legacy format is currently used, future updates may introduce SegWit and native SegWit (bc1) support for improved fee efficiency and scalability.

Q: How do I verify which chains support address merging?
A: Refer to the official documentation or API schema for real-time eligibility checks. Supported chains are grouped under UTXO or EVM families with clear labeling.

Best Practices for Developers and Custodians

  1. Validate Network Before Transfer: Always confirm the blockchain network matches the intended destination.
  2. Enforce Memo Checks Programmatically: Build validation layers that reject transactions missing required memos.
  3. Use APIs for Precision Control: Leverage API capabilities to assign specific addresses for inflows/outflows beyond the default.
  4. Monitor Change Address Usage: Audit change address generation to prevent fund leakage.
  5. Educate End Users: Provide clear UI cues about memos and network selection to reduce support tickets.

👉 Access powerful tools that simplify multi-chain address management and transaction validation.

By mastering these address formats and leveraging consolidation features wisely, organizations can achieve greater scalability, fewer errors, and enhanced security in their digital asset operations.