Merkle gives transaction senders complete control over the transaction lifecycle. Release happens when:

  • A transaction does not receive a bid.

  • A bid is made, but does not get included in the next block.

In order to not hold back transactions, Merkle will release the transaction.

There are two types of release:

  • public: released to the public mempool. This makes the transaction visible to everyone and vulnerable to sandwich attacks and generalized front running.

  • private: send to trusted popular builders via a private transaction. The transaction stays private until it is mined. Transaction is protected from sandwiches and generalized front running.

Last updated