Blink

Our dashboard of our example app powered by Blink API

Inspiration

Trust is expensive. Freelancers and gig workers often have to choose between high-fee centralized platforms or the "honor system." We wanted to build a bridge that offers the ironclad security of a blockchain escrow with the seamless experience of a modern Web2 API.

What it does

Blink API is a "trust-as-a-service" engine. It allows developers to deploy secure, on-chain Solana escrow rooms with a single REST call. It supports Direct Mode for crypto-native users signing with their own wallets and Custodial Mode for everyone else, allowing users to stake funds via Stripe while the API handles the blockchain heavy lifting.

How we built it

We architected a standalone REST API using Next.js and TypeScript, deployed on Railway. The backbone is a custom Anchor program on the Solana Devnet that manages Program Derived Addresses (PDAs) for mỗi escrow. We used Supabase for real-time data tracking and Stripe for the fiat-to-crypto bridge.

Challenges we ran into

The biggest hurdle was "The Bridge", keeping our Web2 database and Stripe webhooks perfectly in sync with the Solana blockchain. We had to build a custom on-chain event listener and polling system to ensure that when a user stakes SOL or pays via Stripe, the room state updates instantly and accurately across all layers.

Accomplishments that we're proud of

We successfully made blockchain invisible. Through our PackedPay demo, a user can fund a secure, decentralized escrow using a standard credit card without ever knowing they are interacting with a Solana PDA. Making the API fully standalone and Railway-ready was the cherry on top.

What we learned

We dove deep into Solana’s PDA architecture and the nuances of transaction serialization. We also learned that developer experience (DX) is just as important as the tech itself, which is why we prioritized a clean terminal workflow and comprehensive documentation.

What's next for Blink

We’re looking to add automated dispute resolution (arbitration) and support for USDC to minimize volatility for long-term jobs. We also want to expand our "Lockbox" logic to support multi-signature requirements for enterprise-grade escrows.