I build fintech and Web3 products people trust with their money.

The problem

Bridging assets across chains is one of the riskiest actions a crypto user can take — a single misread transaction state can mean lost funds. The bridge needed an interface that made multi-step, multi-chain transactions legible and hard to get wrong.

Technical decisions

• Modeled the bridge flow as an explicit state machine (select chain → approve → confirm → relay → finalize) so the UI could never show an ambiguous 'in-between' state.
• Persisted in-flight transaction state to local storage keyed by wallet address, so a refresh or dropped connection never orphaned a pending bridge transaction.
• Built wallet-connection and network-switching as isolated, reusable hooks to keep chain-specific logic out of presentational components.

Challenges & trade-offs

• Reconciling inconsistent confirmation times across source and destination chains without leaving the user staring at an ambiguous loading state.
• Handling wallet/network-switch edge cases (user changes network mid-transaction, rejects a signature, etc.) without corrupting the tracked transaction state.

The problem

As SFx Money grew past 8,000 users and ~$11M in volume — with Nigeria driving roughly 60% of flow — the ops team needed one place to review transactions, track user activity, and monitor money moving across fiat, card, mobile-money, and on-chain rails. Spreadsheets and backend logs weren't going to scale.

Technical decisions

• Structured the dashboard around how ops actually works — searchable transaction lists, user lookup, and corridor-level views — instead of dumping raw API data into tables.
• Kept multi-currency amounts formatted consistently across every view, since a misread number in an admin tool has the same cost as one in the consumer app.
• Built filterable transaction views that handle high volume — inbound/outbound, rail type, status — so the team can find a specific payment without scrolling through thousands of rows.
• Used clear loading and empty states so the dashboard stays usable on slow connections, which is common for ops staff working remotely.

Challenges & trade-offs

• Presenting dense fintech data — multi-rail flows, stablecoin settlement, card spend — in a layout that's scannable without hiding what matters.
• Keeping currency formatting and status labels consistent as new payment rails and corridors were added.
• Making sure the dashboard stayed useful during the April–May 2026 platform outage, when transaction volume dropped to near zero and then spiked back on recovery.