🤫Workflow

Soiler's primary aim is to establish a secure and decentralized cross-rollup framework within the Ethereum ecosystem, concentrating on improving interoperability between the mainnet and rollup solutions. Initially, cross-rollup transactions in Soiler operate on an optimistic principle, presuming all transactions are valid. To handle potential disputes, an Arbitration Mechanism is integrated, empowering users to lodge arbitration cases and contest the outcome of a cross-rollup transaction.

A distinguishing feature of Soiler is its approach to transaction initiation, wherein Senders directly initiate transactions to a Maker's externally owned address (EOA) rather than a contract address, setting Soiler apart from other bridge protocols. Makers can either develop and deploy their own client for automating the service or utilize the open-source client provided by the Soiler team.

Once the Sender triggers the transaction to the Maker on the source network, the Maker assumes responsibility for transferring the assets to the Sender on the destination network. To finalize the transaction, the Maker verifies three critical parameters:

1. Token Standards: Soiler accommodates ETH and ERC-20 tokens. When Makers deposit margin in the Maker Deposit Contract (MDC), they specify the withholding fee (a pre-established fee), the trading fee (a specific percentage of the transaction amount), and the endorsed token. These parameters are stored in the Event Binding Contract (EBC) and consistently synchronized with the Maker Client.

(Note: Soiler adjusts its fees periodically based on the Gwei rate of the destination network to ensure fees remain below the prevailing average. These adjustments are infrequent, and Senders can check the Orbiter website for current fee rates.)

1. Amount Sender Receives: Using the designated token type, the Maker calculates the exact amount the Sender is entitled to receive using the formula in the EBC.

2. Destination Network: Soiler employs an "Identification Code" to distinguish between different Destination Networks. This code is appended to the final four digits of the transfer amount, enabling the Maker to identify the correct Destination Network for executing the transaction. Any alterations made by the Sender to this transaction will result in transaction failure.