#System Design

4 posts · All tags

  1. The Reconciliation Alert Fired Twice: Missed and Double-Counted Interest When Bitfinex Positions Switch Sides

    I check user earnings with a ratio of interest actually paid to booked accrual; it fired twice, once undercounting and once double-counting, both because Bitfinex splits one position across credits and loans.

    Engineering ·
    2026.10.10

  2. The Admin Side of a One-Person SaaS: Trade-offs in Permissions, Broadcasts, and Notification Channels

    Once my lending platform had users and billing, I built an admin console and multi-channel notifications; this covers permissions, kill switches, broadcast transaction boundaries, Telegram binding, and recipient rules for targeted broadcasts.

    Engineering ·
    2026.10.10

  3. From Performance Fees to a Flat Annual Fee: Design Decisions Behind Subscription Billing and Promotions

    EZLO switched from performance fees to subscriptions. Plan limits shipped before billing, promo bonuses freeze onto the invoice, the 30-day notice only gates passive charges, and suspension never touches users' own lending toggles.

    Engineering ·
    2026.10.10

  4. From a FastAPI Script to a Spring Boot SaaS: Rebuilding My Bitfinex Auto-Lending Platform

    How an auto-lending side project went from a "good enough to run" single-person script to a multi-module platform with idempotency, reconciliation, circuit breaking, and full monitoring.

    Engineering ·
    2026.05.20