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
  1. Guides

Source chain notifications

PreviousTestnetNextRefund Logic

Last updated 6 months ago

The protocol allows for initiating notifications regarding the status of a transfer sent to the destination network by sending notifications from the relay to the source network. In this case, the following event is emitted on the client's contract:

event TransferSendingResultNotification(bytes32 indexed _transferHash, uint8 _statusCode)

Event parameters:

  • _transferHash - the hash of the transfer that triggered the notification

  • _statusCode - the status code of the transfer in the destination network

At the moment, the following list of statuses is supported:

  • 0 - the transfer was successfully sent to the destination network

  • 1 - the transfer was not sent due to insufficient commission sent to cover the gas in the destination network.

Each client has the ability to enable or disable these notifications at their discretion, depending on the logic built into the client system.

IMPORTANT!

In the event of disabling notifications, the client can save on network fees (the transfer will become slightly cheaper in terms of gas). However, the will not receive data about the status of the transfer delivery in the destination network. This can impact certain internal logic, such as automatically resending a transfer in case of insufficient fees to cover gas in the destination network.

It's essential to understand this if you plan to disable these notifications.

client's off-chain module