Too many separate memberships
Every community means another payment to manage. Cost adds up, value gets hard to compare, and most people just stop joining.
Community subscription payments on Stellar. One subscription unlocks partner benefits, Soroban splits the revenue, and the traction is verifiable on-chain.
Every community means another payment to manage. Cost adds up, value gets hard to compare, and most people just stop joining.
Packaging benefits and splitting partner revenue runs on spreadsheets and trust. Manual reconciliation, every single month.
Screenshots and self-reported numbers don't convince partners, ecosystems, or judges. There's no shared proof of activity.
Connect a Stellar wallet and pay one subscription. It opens benefits across whitelisted partner communities.
Every payment splits between project owner, community manager, and platform by contract logic. Zero manual accounting.
Subscribers, volume, and payout events read straight from the chain. Anyone can check the numbers are real.
Stellar Wallets Kit, multi-wallet
10 XLM on testnet, one signature
70 / 20 / 10, set in the contract
Entitlement recorded on-chain
Live reads via Horizon
Connect a supported wallet, pay one subscription on testnet, and the entitlement record updates in the app after confirmation.
Partner resources listed with metadata and subscriber discounts. Tokenization-compatible by design, marketplace comes later.
Fixed-percentage split runs on every successful payment. Payout state is auditable and config changes are access-controlled.
Subscriber count, payment volume, and payout events from testnet data. Judges can match every number to real activity.
Recurring consumer payments need instant settlement at negligible fees. That's Stellar's home turf.
Subscription records, entitlement checks, and the revenue split live in one Rust contract, not in a backend spreadsheet.
The traction dashboard reads the chain directly. Metrics are checkable by anyone, not self-reported.
One guided connect-and-pay flow. A first-time user never sees raw keys or manual transaction building.
One recurring payment instead of a stack of separate memberships.
Automated payouts from every subscription, no reconciliation work.
Partner-led growth with on-chain proof of engagement.
Platform share of subscription revenue plus a share of partner transactions. Payments and payout automation first; marketplace expansion is a later phase.
Successful active subscriptions completed on-chain. It proves the full loop: wallet connect, payment, split, entitlement.
Subscription + split in Soroban, 4/4 unit tests passing. Verified subscribe transaction: 10 XLM in, split 7 / 2 / 1 out on-chain.
Full flow deployed: multi-wallet connect, testnet subscription, entitlement state, and live on-chain stats.
Contract tests and build on every push, a clickable product prototype, and a mobile-responsive pass.
| Weight | Criterion | What we show |
|---|---|---|
| 25% | Technical + Stellar depth | Live wallet connect, testnet payment, Soroban split, Horizon-fed dashboard |
| 25% | Real-world fit | Fragmented community access and partner monetization, solved with recurring payments |
| 20% | Innovation | One subscription, many communities, automatic split, verifiable traction |
| 10% | Viability + GTM | We operate chapter zero ourselves; every future community chapter is a customer |
| 5% | UX | One guided wallet-and-pay flow, built for non-crypto-native users |
| 5% | Team | Four builders, each running a real community, with an SCF referral path to continue |
Design and PM operator. Brand, product flows, design system.
dApp and contracts. Owns the team repo and build pipeline.
Engineering with PM background. Wrote the Komunify PRD.
Business and partnerships. Partner community pipeline.
Wallet connect, testnet subscription, Soroban split to three parties, entitlement activation, and a dashboard that proves it all happened on-chain.