EduVault supports three primary product paths: creators publish resources, learners discover and access resources, and marketplace services coordinate listings, purchases, and entitlement checks.
- Create or update a profile: the creator connects a wallet, adds profile details, and saves the profile so marketplace listings can be attributed to a recognizable seller.
- Prepare a material: the creator chooses a title, description, category, price, cover image, usage rights, and the source file that learners will receive after purchase.
- Upload content: the app sends files to the upload API, pins content and metadata through Pinata/IPFS, and stores the resulting references with the material record in MongoDB.
- Publish the listing: the creator reviews pricing, visibility, and licensing terms before making the material discoverable in the marketplace.
- Manage ongoing listings: creators should keep metadata current, unpublish outdated resources, and monitor marketplace activity as analytics and payout features mature.
- Future Stellar step: once Soroban purchase flows are enabled, published materials will also be registered with the Stellar contract layer so pricing and entitlement state can be verified independently.
- Browse the marketplace: learners search and filter educational materials by topic, creator, format, and price.
- Review a material: learners open a material detail page to inspect the description, rights, creator information, and purchase requirements.
- Start checkout: the learner connects a supported wallet and confirms the purchase flow.
- Complete payment: the current prototype models marketplace access in the application, while the planned Stellar flow submits a Soroban transaction for XLM or supported Stellar-asset settlement.
- Receive access: after purchase confirmation, the app checks entitlement records before exposing protected download or viewing actions.
- Return later: learners can revisit purchased resources through saved materials, dashboard views, or entitlement-backed access checks as those features are expanded.
- Catalog ingestion: material metadata is validated by API routes and stored in MongoDB with creator, pricing, rights, and content-address references.
- Discovery: public marketplace pages query active listings and display normalized cards, detail pages, and creator attribution.
- Purchase coordination: checkout connects the learner, material, price, accepted asset, and seller account into a single transaction intent.
- Entitlement creation: successful purchases produce an access record. In the Stellar design, Soroban events are indexed into MongoDB collections such as purchases and entitlement caches.
- Protected access: download and view requests should verify the learner's entitlement before returning private file references.
- Operational recovery: indexer dead-letter queues and reprocessing scripts help maintain consistency when blockchain event processing fails or needs replay.
- Frontend owns profile, upload, marketplace, checkout, and dashboard user experiences.
- Backend API routes own validation, session handling, storage writes, upload orchestration, and access checks.
- MongoDB owns durable off-chain records for profiles, materials, purchases, cached entitlements, and operational metadata.
- Pinata/IPFS owns content-addressed file and metadata persistence.
- Stellar/Soroban layer owns the planned payment, entitlement, and event source of truth for purchase verification.