Thread · 2 May 2026
Build in public: an honest ledger of shipped and not-yet-shipped
Eight days before a hackathon submission deadline, the progress post drew its own line: wallet connection, shareable payment links and the on-chain transfer flow were live on the deployed build, while the dashboard, fuller devnet testing and the demo recording were still on the list — stated in the same breath.
This is a progress post for SolaPay NG — self-custodial payment links on Solana for Nigerian freelancers — written mid-build against a dated submission deadline. What makes it worth reading is not the feature list but the structure: a live column and a still-building column, kept deliberately separate, published while the deadline pressure was on.
On the live side: the deployed app was reachable, the Phantom and Solflare wallet adapters were connected, a payment link could be created and shared, and the transfer flow was running on-chain on the deployed devnet build, with settlement going directly to the freelancer’s own wallet. The framing problem it targets is concrete: a Nigerian freelancer losing a double-digit slice of each payout to intermediary fees before the money ever arrives.
On the still-building side, named just as plainly: the real-time transaction dashboard, fuller devnet testing before calling it complete, a recorded demo. None of it dressed up as shipped. The discipline that makes the post work is that “shipped” is defined narrowly — connected wallets plus a signed transfer over the deployed build — and everything else stays labelled.
The broader lesson is about how progress gets communicated. A build post earns credibility from what it refuses to claim: fixing a real scope in public, admitting the unfinished list, and keeping the deadline visible does more for trust than a polished feature blitz. That rule does not weaken a project memo — it is what separates it from marketing.
Adapted from a build-in-public thread published 2 May 2026.