Frequently asked questions

The most important questions about how Asterizm works

Is Asterizm a centralazied solution?

No, Asterizm is not a centralized solution because cross-chain transaction validation is performed on-chain based on information provided by two independent entities: Asterizm Relayers and Client off-chain module. Learn more about how this works.

How do you verify the cross-chain transaction validity?

The cross-chain transaction validation process is divided into multiple steps and is based on a unique transaction identifier (xID) generated in the source network within the client smart contract, and a hash function on the client contract in the source and destination network.

  1. During the initialization of a cross-chain transaction on the client's smart contract in the source network, a hash is calculated from the transmitted data, and a unique ID for that transaction is generated. Subsequently, the Client server retrieves the payload, hash, and xID for transmission to the destination network, while relayer servers receive only the hash and xID from the client contract for subsequent transmission to the destination network.

  2. In the destination network, before executing the payload received from the client contract via the Client server, validation and integrity checks of the transaction are performed. This is achieved by calculating a hash from the received payload and comparing it with the hash obtained from relayer servers. Additionally, there is a verification of the xID to prevent duplicates and spam transactions.

Explore cross-chain transaction flow in detail and Asterizm logic in the white paper

Is it mandatory to run a server to use Asterizm?

Yes. This is the only way you can be 100% sure that the transmitted data stays private.

What happens if the client's server or relayer server is hacked?

Asterizm Protocol is designed to mitigate the risk of hacking relayer servers and the client's server responsible for transmitting the payload.

Even if all relayer or client servers are compromised, the business logic of cross-chain transactions performed through Asterizm cannot be compromised because the final check of transaction integrity and validity is performed on smart contracts. It is essential for at least one server to function correctly.

In the worst-case scenario, if the client's or relayer servers have been compromised, the most significant impact could be a temporary reduction in uptime or the suspension of business logic for cross-chain operations, along with a potential loss of gas tokens used to cover fees on behalf of the owner's account. To enhance the security of the Client server, we recommend utilizing the built-in Firebocks module for storing the owner account's private key on the Client server.

It is important to note that the client is responsible for the business logic of implementing cross-chain transactions in the project. Asterizm offers a reliable and secure solution for confidential cross-chain transactions but is not responsible for the client's business logic.

Refer to the Best practices and Takeoff checklist to ensure that all security measures are met before deploying your project

What happens if one of the networks supported by Asterizm fails / crashes?

The Asterizm approach allows cross-chain transactions between working blockchains regardless of the performance of other connected networks.

Once disconnected networks resume operation, all incoming and outgoing cross-chain transactions will be delivered in accordance with the queuing and block time rules of those networks.

Last updated