search

⛓️Blockchain Identifiers

The OffBlocks API is chain-agnostic, meaning that our services can theoretically be integrated with a variety of different blockchains that support smart-contract functionality. This includes, but is not limited to, EVM-compatible L1 and L2 chains, Solana, and Tron.

To effectively set up entities such as users and accounts, perform compliance monitoring, and manage the transaction lifecycle, we employ universal identifiers for blockchain entities. We have chosen a CAIP-compatible (Chain Agnostic Improvement Proposalarrow-up-right) naming convention for Chainarrow-up-right, Accountarrow-up-right and Assetarrow-up-right identifiers, our internal Transaction identifier is also using Accountarrow-up-right-like structure for consistency.

hashtag
Chain Identifier

We use a blockchain namespace identifier suggested by CAIP-2arrow-up-right. Here are some examples of what it would look like for supported chains:

// zkSync Era Mainnet
eip155:324

// zkSync Sepolia Testnet
eip155:300

hashtag
Account Identifier

We use a blockchain account identifier suggested by CAIP-10arrow-up-right. Here are some examples of what it would look like for supported chains:

// zkSync Era Mainnet
eip155:324:0x22227A31dd842196A246d8f3b775998560eAa61d

// zkSync Sepolia Testnet
eip155:300:0x22227A31dd842196A246d8f3b775998560eAa61d

hashtag
Transaction Identifier

We use a blockchain transaction identifier that is similar to the account identifier, as suggested by CAIP-10arrow-up-right, where the transaction hash replaces the account address. Here are some examples of what it would look like for supported chains:

hashtag
Asset Identifier

We use a blockchain asset identifier suggested by CAIP-19arrow-up-right. Here are some examples of what it would look like for supported chains:

PreviousIdempotencyNextBlockchain Updates

Last updated