Milestones & budget
$128,000 in XLM over 20 weeks, staged across three tranches
Large enough to cover real infrastructure work, below the $150K cap. Ambition without a maximum-by-default request.
Weeks 1–4
Demo MVP & Proof of Intent
Show a reviewer that Lazee Kit works as a real C-address onboarding flow, not a concept deck.
Deliverables
- —Architecture spec and threat model
- —Lazee Account v1 deployed on testnet
- —Sponsor relay MVP for account creation and first action
- —GiftVault MVP with create, claim, expiry, refund path
- —Reference app: create C-address, sponsor, create gift, claim gift
- —Public 3-minute video
- —Testnet transaction hashes and contract IDs
Reviewer verification
Weeks 5–12
Developer Kit & Integration Readiness
Turn the demo into reusable developer infrastructure.
Deliverables
- —TypeScript SDK alpha
- —React UI kit alpha
- —SessionRegistry v1
- —Intent schemas: send, swap, bridge_in, gift_*, recurring, DCA
- —Indexer / events API
- —Account, gift, relay, and session test suite
- —Two reference integrations or partner test apps
- —Integration docs and component guide
Reviewer verification
Weeks 13–20
Production Readiness & Mainnet Pilot
Make Lazee Kit credible for controlled mainnet usage and post-grant maintenance.
Deliverables
- —Production hardening
- —External review or audit-prep package
- —Critical and high issues remediated or documented
- —Observability dashboard
- —RPC failover and sponsor budget controls
- —Mainnet pilot behind caps and allowlists
- —Complete runbooks + maintenance plan
Reviewer verification
Budget breakdown
Mapped to reusable ecosystem infrastructure
The grant is not paying for a single consumer app. It funds open-source primitives other Stellar teams can adopt: contracts, relay patterns, SDK methods, UI components, docs, test cases, and operational runbooks.
Reviewer objections
Answered before they are asked
Is this just another wallet?
No. Lazee Kit is an embeddable onboarding and execution kit for Stellar apps and wallet teams. The funded outputs are contracts, SDKs, UI components, relay patterns, tests, and docs.
Why fund another C-address project?
SCF #41 funded multiple C-address projects, confirming the need. Lazee combines onboarding, sponsorship, gift/claim UX, SDK/UI packaging, receipts, scoped sessions, and runbooks in one app-embedded layer.
Is the sponsor relay centralized?
The relay is operational infrastructure, not an authorization authority. It pays fees, simulates, submits, and tracks receipts. Authorization and session policy remain onchain. Apps can self-host it.
Is the scope too broad?
The architecture is broad but the milestone plan is staged. M1 is narrow: create, sponsor, gift, claim, receipt. M2 packages tooling. M3 hardens and pilots. Bridge/agent flows are extensions.
How do agents avoid overreach?
Agents execute through scoped sessions: allowed assets, contracts, intent types, per-tx and lifetime caps, expiry, receiver allowlists, and revocation. Out-of-scope attempts fail.
What exists after the grant?
Open-source contracts, SDK, React UI kit, reference app, sponsor relay, indexer, docs, tests, diagrams, demo videos, and runbooks — useful even if a hosted deployment stops.