Post Data to ImFact network

The ImFACT SDK allows you to submit transactions to the ImFACT Network.

In the ImFACT Network, a transaction is referred to as an operation. Operations are used to perform all state-changing actions on the network, such as creating accounts or deploying contract accounts (CA).

For details on how to create operations using the SDK, please refer to the section on operation construction.

This section focuses only on submitting a signed operation to the network.Once an operation has been created and signed, it can be submitted to the network using the SDK.

Under the hood, the submission is handled through the ImFACT digest API. However, developers do not need to interact with the digest API directly. The SDK provides a dedicated method that internally performs the HTTP POST request and processes the response.

Operation submission is asynchronous. A successful HTTP response indicates that the operation has been accepted for processing, but it does not guarantee that the operation has been finalized in a block.

In the ImFACT Network, transaction fees are charged only if the operation is successfully processed and recorded in a block. If the operation fails before finalization, no fee is deducted.

Since the ImFACT Network is based on PBFT consensus, once an operation is finalized in a block, its result is deterministic and cannot be reverted.

To simplify finality verification, the SDK provides a wait method that submits the signed operation and continuously polls the network until it is confirmed in a block. This allows developers to reliably determine whether the transaction has ultimately succeeded.