Ravdesk
Pay on progress, not promises—onchain &verifiable.
About
The problem it solves - Trust and payment risk in freelance work: Clients fear paying for unfinished work; freelancers fear not getting paid after delivery. - Coordination overhead: Managing milestones, approvals, and multi-party sign-offs is error-prone using spreadsheets and chats. - On/off-chain fragmentation: Project state (milestones, roles) lives off-chain, while payments are on-chain, causing mismatches and disputes. - Lack of transparency: Stakeholders can’t easily verify progress, funds status, or who can authorize releases. **What people can use it for** - Milestone-based escrow on Base: Create a contract with clients/freelancers, deposit funds per milestone, and release only when conditions are met. - Multi-party approvals: Involve an admin council or multiple stakeholders to approve releases or resolve disputes. - Per-user contract tracking: Each creator can deploy and manage their contracts, filter and view by creator. - On-chain verification: All payments and releases are transparently recorded on-chain for auditability. - Farcaster Mini App usage: Interact via a Farcaster Mini App UI for quick approvals and status checks without heavy wallets. **How it makes tasks easier/safer** - Escrow guarantees: Funds are locked in RavdeskEscrowSecure until milestones are met—reduces counterparty risk for both sides. - Granular progress control: Milestones (amount + description) break large engagements into safe, reviewable chunks. - Configurable governance: Admin council members can arbitrate or co-sign releases, reducing deadlocks and disputes. - Transparent state: agreement() exposes total, deposited, net amounts, and milestone counts; anyone can read contract status. - Automated bookkeeping: On-chain amounts act as the source of truth; no manual reconciliation needed. **Developer-friendly stack:** - Next.js app with Wagmi and OnchainKit configured for Base. - API routes to read DB and contract state. - ENV-driven config (RPC, API keys, contract address) for quick setup. **Typical scenarios** - Client-funded projects: Client deposits for upcoming milestones; funds release only after approval. - Agency workflows: Multi-freelancer splits with fixed percentages; admins co-approve releases. - Dispute resolution: Admin council can intervene when milestone acceptance is contested. - Lite procurement: Small teams can run reliable on-chain procurement without enterprise tools. Smart Contract Address(es) 0x4aF45c1A10b2F32ec3cEe6663dEC84E1aC1747c9
How it's made
Challenges we ran into Next.js type issues with Web3 and RPC fallbacks resolved via explicit typings, Base chain config, and .env-driven providers. Getting My Coinbase Developer Platform API key because verification doesnt go through for african numbers