Asterizm
  • What is Asterizm
    • Overview
    • Architecture
    • Benefits
    • Supported chains
      • Non-EVM chains integration plan
    • Frequently asked questions
    • White paper
    • GitHub
  • Infrastructure
    • Overview
    • Asterizm Connector
      • Client smart contract abstraction
      • Initializer smart contract
      • Translator smart contract
    • Client off-chain module
    • Asterizm Relayer
    • Asterizm Interfaces
      • IAsterizmConfigEnv
      • IConfig
      • IAsterizmEnv
      • IClientReceiverContract
      • IInitializerReceiver
      • IInitializerSender
      • IMultiChainToken
      • INonce
      • ITranslator
  • Guides
    • Transaction flow
    • Getting started
      • 1. Deploy your smart contracts
        • AsterizmDemo contract
        • Client contracts implementation logic
        • Solana integration logic
      • 2. Implement off-chain module
        • Simple implementation (shell script)
        • Default implementation (manual)
      • 3. Important! One final pre-flight check
    • External relays
      • Relay deployment and configuration
      • List of external relays
        • Chainlink
          • Mainnet
          • Testnet
    • Source chain notifications
    • Refund Logic
    • Error messages
      • EVM
        • Source chain
        • Destination chain
      • TVM and TON
      • Solana
    • Fee management
    • Code examples
    • Multi-Owner (Sender) System
  • Advanced
    • Best practices
    • Asset transfer
    • Debugging
  • Technical reference
    • Mainnet
    • Testnet
    • Smart contract audits
    • SDK
Powered by GitBook
On this page
  • Is Asterizm a centralazied solution?
  • How do you verify the cross-chain transaction validity?
  • Is it mandatory to run a server to use Asterizm?
  • What happens if the client's server or relayer server is hacked?
  • What happens if one of the networks supported by Asterizm fails / crashes?
  1. What is Asterizm

Frequently asked questions

The most important questions about how Asterizm works

PreviousNon-EVM chains integration planNextOverview

Last updated 6 months ago

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: and . Learn more about .

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 , 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 in the source network, a hash is calculated from the transmitted data, and a unique ID for that transaction is generated. Subsequently, the retrieves the payload, hash, and xID for transmission to the destination network, while 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 via the , 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 . Additionally, there is a verification of the xID to prevent duplicates and spam transactions.

in detail and Asterizm logic in the

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 or 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 or 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 , we recommend utilizing the built-in for storing the on the .

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.

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

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.

Refer to the and to ensure that all security measures are met before deploying your project

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

Best practices
Takeoff checklist
working blockchains
Asterizm Relayers
Client off-chain module
client smart contract
client's smart contract
Client server
relayer servers
client contract
Client server
relayer servers
Explore cross-chain transaction flow
white paper
relayer
client servers
client's
relayer servers
Client server
Client server
how this works
Fireblocks module
owner account's private key