Designing a who-pays-the-fee interface

A developer at Circle shares their thought process designing a fee-handling UI for a USDC blockchain bridge application. The post covers the challenge of clearly communicating who pays transaction fees (sender vs. recipient), explores two interface approaches — a plain form using the HTML `<output>` element with a checkbox, and a madlibs-style UI — and touches on relevant CSS techniques like `field-sizing` and checkbox styling. The broader context includes cross-border payment UX and Circle's CCTP forwarding service.