Common Parameter Definitions

·

When integrating with Web3 wallet APIs, understanding core parameters is essential for seamless development and accurate data handling. This guide breaks down the most frequently encountered parameters in wallet API services, clarifying their definitions, functions, and practical applications. Whether you're building decentralized applications, managing multi-chain assets, or tracking transaction histories, these concepts form the foundation of efficient API usage.

What Is an accountId?

The accountId is a unique identifier assigned by the wallet API to each user account. It serves as a central reference point that enables developers to link multiple blockchain addresses across different networks under a single logical identity.

👉 Discover how unified account management simplifies Web3 development

This means that whether a user holds Ethereum on Layer 1, funds on Arbitrum, or tokens on Polygon, all these addresses can be associated with one accountId. As a result, you can perform aggregated queries for:

By abstracting away the complexity of managing disparate addresses, the accountId streamlines user experience and backend operations. It’s especially valuable in wallet-as-a-service (WaaS) architectures where scalability and data coherence are critical.

For developers, this parameter eliminates the need to manually track relationships between addresses. Instead, you can query all relevant data using a single ID—reducing code complexity and improving response times.

Understanding chainIndex: The Universal Chain Identifier

In a fragmented multi-chain environment, identifying networks consistently is crucial. The chainIndex is the wallet API’s standardized way of representing blockchain networks—ensuring clarity and interoperability across services.

Unlike traditional methods that rely solely on EIP-155 chain IDs (used in EVM-compatible chains), the chainIndex extends support to non-EVM blockchains like Bitcoin and Solana, which lack universal identification standards.

How Is chainIndex Determined?

This approach guarantees that every supported network has a distinct, unambiguous identifier within the API framework.

Supported Networks and Examples

Below are some common blockchains and their corresponding chainIndex values:

These identifiers allow developers to programmatically interact with specific chains when initiating transactions, checking balances, or monitoring events.

For a complete list of supported networks and their chainIndex mappings, refer to the official documentation.

👉 Access real-time chain support and integration tools

This level of standardization reduces errors caused by mismatched network IDs—a common pain point when working across heterogeneous blockchain environments.

The Role of orderId in Transaction Tracking

Every transaction processed through the wallet API is assigned a unique orderId. This internal identifier plays a vital role in ensuring end-to-end visibility throughout the transaction lifecycle—even before the transaction is confirmed on-chain.

Why Use orderId?

Unlike blockchain transaction hashes (which only exist after broadcasting), the orderId is generated at the moment the transaction is submitted to the API system. This allows your application to:

Because the orderId exists independently of blockchain confirmation, it enables robust error handling and state management in dApps.

Practical Use Cases

Imagine a user initiates a token swap across chains. Even if network congestion delays execution, your backend can use the orderId to:

This makes the orderId indispensable for building reliable financial services, custodial solutions, or high-frequency trading platforms on Web3 infrastructure.

Frequently Asked Questions (FAQ)

What is the difference between accountId and blockchain addresses?

An accountId is an abstract identifier used by the API to group multiple blockchain addresses (e.g., Ethereum, Bitcoin) under one user profile. In contrast, blockchain addresses are public keys specific to individual networks. The accountId enables unified data access without exposing sensitive address relationships.

Can I use chainIndex instead of EIP-155 chainId?

Yes—for EVM chains, chainIndex and eip155chainId are often identical. However, for non-EVM chains like Bitcoin or Solana, only chainIndex applies. Always use chainIndex when interacting with the wallet API to ensure cross-chain compatibility.

How long does an orderId remain valid?

An orderId persists indefinitely within the system. You can query it at any time to retrieve historical transaction details, even years after execution. This supports long-term auditing, reconciliation, and compliance needs.

Is accountId user-specific or application-specific?

The accountId is typically scoped to your application instance. That means each user in your app receives a unique accountId, but the same user across different applications will have different identifiers. This maintains privacy and isolation between service providers.

Do I need to store orderId locally?

While not mandatory, storing orderId in your database enhances traceability. It allows you to correlate on-chain events with internal operations, improve debugging, and deliver better customer support.

Can two transactions have the same orderId?

No—each orderId is globally unique within the wallet API system. Duplicate IDs are prevented through cryptographic hashing and distributed locking mechanisms during generation.

Core Keywords Summary

This article integrates the following core keywords naturally for SEO optimization:

These terms reflect high-intent search queries from developers and technical teams building on decentralized infrastructure.

👉 Start building with powerful Web3 APIs today

By mastering these fundamental parameters—accountId, chainIndex, and orderId—you lay the groundwork for scalable, secure, and user-centric Web3 applications. Whether you're aggregating cross-chain data or ensuring transparent transaction flows, these identifiers empower precision and reliability in every interaction.