Reinforced Transactions

OMNIA acts as an intermediary between the user and the blockchain. This "reinforced transaction broadcast" is a key differentiator for OMNIA users. It ensures that even if a transaction has a low gas and dropped by nodes or is not seen as an MEV opportunity and does not receive a bid, it will still be broadcasted to the private or public mempool and have a chance to be included in a block. This prevents the user from experiencing a "transaction not found" error, which can occur if a transaction is only sent to the private mempool and does not receive a bid.
As an RPC, it is our job to complete the transaction.
OMNIA's approach to addressing the needs of DeFi traders is twofold. If a transaction is not directly included in the mempool or blockchain or is being dropped, OMNIA ensures the transaction still gets processed through its “reinforced transaction” features and broadcasts the transaction to the private/public mempool and private venues until this gets included in the blockchain. This dual approach ensures that traders are covered for transaction completeness.
OMNIA is integrated with dozens of OFAs (auction houses). If the auction house successfully monetizes the transaction, it sends a bundle to the block builder and the user receives a cashback in their wallet. If the auction house does not monetize the transaction, OMNIA broadcasts the transaction to the public/private mempool as a fallback (depending on user's choice).
OMNIA makes sure you don't experience the "transaction not found" error when making RPC calls. We ensure our node is fully synced and not being overloaded with requests, plus we're making sure it's being included.
This is one of OMNIA's guarantees and differentiators: we provide a reinforced transaction broadcast.
Other reasons "transaction not found" error typically arises when you're trying to retrieve information about a transaction that isn't recognized by the network.
  1. 1.
    Transaction hasn't been mined yet. When a transaction is submitted to the network, it doesn't get included in the blockchain immediately. It first enters the transaction pool (also known as mempool) where it waits to be picked up. If you query the transaction too quickly after it's been sent, it might not have been mined yet, and therefore might not exist in the blockchain.
  2. 2.
    Transaction dropped from the transaction pool. If the network becomes congested, the transaction pool might become full, and transactions with lower gas prices could get dropped. If your transaction gets dropped, it won't be retrievable until it's re-broadcasted to the network.
  3. 3.
    Invalid transaction hash. If you're looking up a transaction by its hash, ensure that the hash is correct. An invalid or mistyped hash will also return a "transaction not found" error.