In modular blockchain architectures, users often find it challenging to grasp how transactions move between the execution and settlement layers—making the question of “how a transaction is completed” central to understanding the system.
This issue typically spans three areas: the transaction submission path, processing logic at the execution layer, and the settlement confirmation mechanism. These elements together form the SOON network’s end-to-end workflow.
How Users Access the SOON Rollup Ecosystem
Users generally enter the SOON network by connecting to the execution layer via supported wallets or application interfaces.
Practically, users connect a SOON-compatible wallet or dApp and bridge assets to the corresponding Rollup network, enabling interactions with the execution layer. This bridging process relies on the underlying chain and cross-chain protocols.
From a system perspective, the user entry point integrates the wallet, front-end application, and cross-chain bridge—working together to provide the user interface for interacting with the execution layer. User actions do not interact directly with the base chain; instead, they are routed to the execution layer first.
This approach abstracts complex base-layer operations into simple user interactions, letting users execute transactions in a high-performance environment while maintaining a connection to the base chain.
How Transactions Are Submitted and Broadcast in the SOON Network
Transactions on the SOON network are submitted and broadcast to execution nodes using standardized data formats.
Operationally, once a user initiates a transaction, the data is packaged as a request and sent to the execution node network, where nodes handle initial verification—checking signatures and account balances. The transaction is then propagated among nodes to synchronize execution.
Structurally, the transaction propagation process involves the client, the node network, and the mempool. Before execution, transactions are temporarily stored and ordered to optimize processing.
This mechanism ensures that transactions reach multiple nodes, enhancing network reliability and execution consistency.
How the SOON Execution Layer Handles Transactions and State Updates
The execution layer processes transaction logic and updates the system state—serving as the core of the workflow.
Functionally, when transactions reach the execution layer, the SVM environment runs the relevant smart contract logic, calculates results, and updates account states. This includes asset transfers, contract calls, and data modifications.
The execution layer consists of execution nodes, state storage, and a compute engine—leveraging parallel processing to boost throughput. Execution results are output as state changes and await settlement.
This design centralizes compute-intensive tasks within a high-performance environment, reducing base-chain load and increasing efficiency.
How the SOON Settlement Layer Achieves Finality
The settlement layer is responsible for finalizing execution results and ensuring network security.
Mechanistically, state updates from the execution layer are packaged and submitted to the base chain, which uses consensus to verify and record them in blocks—delivering final confirmation.
Typically, the settlement layer is provided by a main chain like Ethereum, which offers a tamper-proof security foundation and ensures transaction finality.
This separation of execution and security allows the system to achieve high performance while relying on proven chain security.
How Cross-Chain Communication Works in the SOON InterSOON System
SOON’s InterSOON framework facilitates cross-chain communication, enabling data and asset transfers between blockchains.
InterSOON uses a messaging protocol to encode state changes from one chain, verify and execute them on the target chain—synchronizing data across networks.
Structurally, InterSOON includes a messaging layer, verification mechanisms, and execution interfaces, creating a unified communication path between different execution layers and main chains.
This design empowers SOON to connect with multiple ecosystems, expanding both its use cases and liquidity.
Structural Breakdown of the SOON Transaction Execution Workflow
A complete transaction on SOON can be broken down into these key steps:
Step 1: User initiates a transaction
The user submits a transaction request via a wallet or app, specifying the operation.
Step 2: Transaction enters the network
The transaction is sent to execution nodes, propagated, and verified across the network.
Step 3: Execution layer processing
The SVM execution environment processes the transaction logic, performing calculations and updating state.
Step 4: Results submitted to the settlement layer
Execution results are packaged and sent to the base chain for verification.
Step 5: Final confirmation
The base chain achieves consensus and permanently records the transaction status.
This model separates execution from settlement, assigning computation and security to distinct layers.
Each step is managed by a dedicated module—client, execution layer, or settlement layer—ensuring a clear division of responsibilities.
This architecture transforms user actions into verifiable on-chain states while optimizing both efficiency and reliability.
Summary
SOON’s modular architecture splits the transaction process into submission, execution, and settlement, allowing the execution and security layers to work in tandem—delivering both high throughput and robust security.
FAQ
Are SOON transactions executed directly on the main chain?
No. Transactions are first processed by the execution layer; only the final results are submitted to the main chain for confirmation.
What’s the difference between the execution layer and the settlement layer?
The execution layer handles computation and state updates; the settlement layer is responsible for security and permanent record-keeping.
Why is cross-chain communication necessary?
It enables data and asset interoperability between different blockchains, supporting a broader ecosystem.
How does SOON increase transaction speed?
By leveraging the SVM execution environment and parallel processing to maximize throughput.
What happens if a transaction fails?
The execution layer rolls back any state changes, maintaining system data integrity.
