Dev Update: Faster Transaction Feedback on opBNB

When you complete an on-chain action, the most useful thing the app can tell you is whether it worked.

With the latest MPC update for opBNB, supported transactions can now show success as soon as successful inclusion is observed on-chain, while final settlement checks continue in the background. This gives users earlier confirmation without removing the finality checks that the system still relies on for settlement and accounting.

Why We Changed It

Previously, there could be a noticeable gap between a transaction being included on-chain and MPC showing the result. A transaction could already be included in a block while the app continued showing a pending state because the system was still waiting for finality. In one production example, inclusion took approximately two seconds, while the application could continue waiting for more than 20 seconds before displaying success.

From the user's perspective, an action that had already reached the chain could still look unfinished. The update addresses that gap by separating the point where MPC can tell the user that an action was successfully included from the later process used to finalize settlement.

From Pending to Feedback

The previous flow looked like this:

Transaction submitted → Included on-chain → Finality → Success shown

The updated flow moves the user-facing success state earlier:

Transaction submitted → Included on-chain → Success shown → Final settlement continues

Once successful inclusion is observed, MPC can update the interface and give the user feedback sooner, while the remaining settlement process continues in the background. This means less time spent staring at a pending transaction when the action has already reached the chain.

What Users Can Expect

The update improves transaction feedback across several familiar MPC flows, including check-ins, quest rewards, My Mine, and voting, with support for applicable sponsored and wallet-sent transactions.

For supported transactions, users can see success earlier after successful on-chain inclusion, making the state of an action easier to understand without requiring the user to wait for every later settlement step.

My Mine also receives an important visibility improvement, as recent on-chain Crew balance changes can appear before final settlement is complete.

Faster Feedback, Final Checks Intact

Earlier feedback does not remove the finality stage. Final settlement, accounting writes, and relay lane release continue to wait for finality where those checks are required. MPC therefore separates the user experience from the longer settlement process while preserving the checks behind the finalized state. This distinction matters because an earlier success message represents successful inclusion observed on-chain, not a replacement for finalized settlement.

What Happens if the Outcome Changes?

Blockchain transactions can still require reconciliation before finality. When the on-chain outcome changes before finality, MPC can correct the transaction's Activity status and reconcile it with the finalized result. This allows the interface to provide earlier feedback while retaining the ability to reflect the final state accurately.

A Better My Mine Experience

For My Mine, earlier transaction feedback also means earlier visibility into recent Crew balance changes. Users can see relevant on-chain balance updates before final settlement is complete, while spendable allowances continue to depend on finalized accounting checks. In other words, seeing a balance update earlier does not automatically mean that every displayed unit is immediately available to spend.

Built for a More Responsive Experience

The goal of this update is straightforward: reduce unnecessary waiting between an on-chain action and the feedback users see in MPC. The underlying opBNB network is not becoming faster because of this change, and the update does not change opBNB's finality process. Instead, MPC is responding to successful inclusion sooner and allowing the settlement process to continue without keeping the user-facing state pending for the same reason. The result is a more responsive transaction experience while keeping final settlement where it belongs in the system.

Measuring the Update

The engineering targets for the implementation are a relay-submit p50 below three seconds and UI success within approximately one second of inclusion.

These are internal validation targets rather than guaranteed production performance. The approximately two-second inclusion and 20-second-plus waiting period referenced above also describe prior observed behavior and should not be interpreted as universal transaction timings.

---

Disclaimer. My Mine is a simulation for experiencing MPC. It is not an investment, security, or financial product.