$150,000 · SCF Build Award

Milestones & Budget

Four tranches over five months — 10% on acceptance, 20% at MVP, 30% at testnet complete, 40% at mainnet and UX readiness. $150,000 XLM equivalent total.

Tranche Structure

Each tranche has specific, verifiable acceptance criteria defined upfront. No deliverable is ambiguous or subjective. The first tranche explicitly requires the public repository to be live at submission — this is a hard precondition, not a post-approval task.

Tranche Milestone Flow
Each tranche unlocks on SCF acceptance of the previous tranche's deliverables. T4 requires mainnet deployment, three live integrations, and a mainnet demo video.

Development Timeline

5-Month Development Gantt Chart
Parallel workstreams within each tranche. Engineering and documentation run concurrently. No tranche depends on a single critical path.

Budget Breakdown

Budget Allocation — $150,000
72% engineering. 17% product and ecosystem. 11% infrastructure and community bounties. No marketing spend. No token giveaways.
CategoryAmountNotes
Engineering — Alex Astrum$54,0005mo · SDK + CLI + AP2 validator + DX
Engineering — Drew Raines$54,0005mo · Soroban contracts + x402 + reference agents
Product & Ecosystem — Max Shama$25,000Coordination · community · docs oversight · partnerships
Infrastructure$8,000Horizon nodes · facilitator hosting · CI/CD · Docusaurus
Community bounties$9,000External integrations in T4 · office hours
TOTAL$150,000100% development costs — no marketing, no token giveaways

Engineering Hours Breakdown

~800 Engineering Hours — Allocation by Engineer
400 hours per engineer over 5 months. Senior Web3/TypeScript/Rust rate ~$135/hr. The Soroban contract work is the highest-complexity single deliverable at ~150 hours.

Honest Budget Assessment

Two things stand out on scrutiny and are worth addressing directly rather than hoping reviewers miss them:

No formal audit line itemNotable gap

The Soroban contracts handle real user funds on mainnet. The budget covers only an internal threat model review plus a community audit request submitted separately. A formal audit by a recognized Soroban security firm would cost $15-30k and is not in scope. This is a conscious tradeoff — not an oversight.

Response:Mitigated by: conservative spending limit defaults, OpenZeppelin audited building blocks, bug bounty at launch, and community audit request. The contract logic is intentionally minimal to reduce attack surface.
T4 back-loading — 40% in the final monthExecution risk

$60,000 drops in month 5, which requires mainnet deployment, security review, three external integrations, a community builder guide, and a mainnet demo video — all in 30 days. If anything slips in T1-T3, T4 gets squeezed hard.

Response:T4 deliverables are designed to run in parallel: mainnet deployment and security review happen simultaneously, community integrations are funded by bounties (not direct engineering time), and the builder guide is documentation work that can be done alongside deployment.
800 hours is tight for the scopeTimeline pressure

5 months, 2 engineers, 800 total hours for: a Rust Soroban contract, a 5-package TypeScript SDK, a CLI, a full docs site, testnet + mainnet deployment, and 3 external integrations. Doable — but there is no slack for unexpected complexity.

Response:The team has pre-validated all integration surfaces before submission. No discovery phase is budgeted because discovery is already done. The adapter-first architecture reduces the blast radius of AP2 changes. Scope is locked — no stretch goals in any tranche.