• Anatomy of a 30-line PR That Could Save 50ms Per Checkout
  • The original code path
  • The fix
  • Why I’m writing this up

§Anatomy of a 30-line PR That Could Save 50ms Per Checkout

I shipped two PRs today on a Solana stablecoin payment gateway (Cypher-CP0/fluxpay):

• Backend (#2): include sol_price_usd in GET /payments/:id, not just POST /create.
• Widget (#5): read it from the payment object instead of doing a separate GET /api/price/sol.

Total diff: ~30 lines across 3 files. Why is this worth a writeup?

§The original code path

// CheckoutModal.tsx
useEffect(() => {
  fetch(`${apiUrl}/api/price/sol`, { headers: { 'x-api-key': apiKey } })
    .then(r => r.json())
    .then(d => { if (d.sol_usd) setSolPrice(d.sol_usd) })
}, [])

Two issues here that are subtle until you stare at it:

1. Extra HTTP roundtrip on every modal open. The widget already polls GET /payments/:id every 3 seconds to check status. That response is sitting right there. Hitting /api/price/sol separately is a free latency tax.

2. Oracle drift. The price the widget shows can disagree with the price the backend used at payment creation time. With a 30-second cache that’s usually fine, but during volatile market moments (which is exactly when SOL/USDC payment apps need to be tight) the widget could quote 153.20 while the backend recorded 153.45 for the same payment. Customers see different numbers in different parts of your stack. Not great.

§The fix

Make the backend include sol_price_usd in the GET response too. The widget reads payment.sol_price_usd first, falls back to the separate fetch only for older backends. Backward compatible. Optional field. ~15 lines per repo.

§Why I’m writing this up

A common dev mistake when contributing to OSS is “make a big splashy PR.” But the PRs that get merged in 24 hours are small, surgical, and align exactly with the issue body. This one literally quotes the issue’s “Expected behavior” wording. No scope creep.

If you want to learn to ship merge-able OSS PRs fast, the rule is: read the issue twice, change as little as possible, and explain why in the PR description.

Open code: https://github.com/Cypher-CP0/fluxpay/pull/2 + https://github.com/Cypher-CP0/fluxpay-widget/pull/5

Zaps welcome if useful.