[C4GT Community]: Scheme Manager for ONEST

[tanishk2907]

Ticket Contents

Description

Organizations like Protean Vidyasarthi, Scholarlify, and Physics Wallah want to run financial support or scholarship scheme trials quickly without needing to invest heavily in understanding and implementing the full protocol stack.
Scheme Manager aims to solve this by creating a lightweight adapter that exposes a minimal set of Low Code APIs to integrate quickly with the ONEST financial support protocol.

Key functionalities:

PushSchemes: Push schemes with defined eligibility.

GetApplications: Fetch applications from the network, auto-validated for eligibility.

UpdateStatus: Update the status of schemes or applications.

With just ~10 lines of code, an organization can start running scheme trials on the ONEST Network, saving time and cost.

📘 Reference links:

Pre-read

Sample Code

Protocol Specs

Expected Timeline: 2–3 weeks

Goals

Goals

• [] Design API contracts for PushSchemes, GetApplications, UpdateStatus

• [] Implement stateless Go-based microservice with REST APIs

• [] Integrate a lightweight in-service database

• [] Dockerize and prepare the adapter for local deployment

• [] Provide sample client integration using 10 lines of code

Setup Guide: Will be linked once MVP is implemented.

Expected Outcome from Contributor

Expected Outcome

A dockerized, stateless Go microservice that serves as an integration adapter for the ONEST financial support protocol. It should:

• Expose 3 key APIs (PushSchemes, GetApplications, UpdateStatus)
• Perform automatic eligibility validation using ONEST protocol rules
• Allow external clients to integrate easily via sample code
• Serve as a foundation for future production-ready adapters

Expected Outcome from Mentor

NA

Acceptance Criteria

✅ APIs respond correctly with valid inputs and gracefully with invalid ones

✅ Auto-validation of applicant eligibility using credentials works

✅ Adapter runs in a Docker container with minimal configuration

✅ Adapter is stateless with persistent store for schemes and applications

✅ Integration sample works with minimal developer effort (~10 LoC)

Implementation Details

Language: Go

Microservice Architecture: Stateless with REST endpoints

Database: Lightweight in-service DB (PostgreSQL preferred)

Deployment: Docker container

Security: Minimal — headerless for now; subject to future enhancements

Protocol Integration: Based on ONEST financial support protocol specs

Design Paradigm: Clean and modular; ease of plug-and-play

Mockups/Wireframes

N/A for this stage — API contract design will be shared during implementation

Product Name

Scheme Manager

Organisation Name

ONEST

Domain

Finance

Tech Skills Needed

Go

Mentorship Status

Mentor Required

Mentor(s)

@tushar-ekstep @aryasoni98

Complexity

High

Contribution Type

Code contribution

Issue Type

Bounty ticket

Monetary Incentive

INR 10k

[rish9511]

Hi @tushar-ekstep @aryasoni98 - Interested in learning more about this task. To get started, will be helpful to get more information about different components involved. Looking forward to connect :)

[rish9511]

I took some time to understand the Beck protocol. Definitely helped in understanding more about the issue
The question I have for now is, let's say the /search API is called , now where does the bpp backend look for the available scholarships ? Does it directly lookup a DB or does it depend on other APIs to get these results ? And if it does depend on a DB, is there such a DB with a list of available scholarships, and if so how can I use that DB for local testing ?

@tanishk2907

[rish9511]

In the sample code, for getting job recommendations, the following package is being used - github.com/ONEST-Network/Whatsapp-Chatbot/bap/backend/pkg/clients", however the Whatsapp-Chatbot project is not part of ONEST-Network Github repo anymore. Going to github.com/ONEST-Network/Whatsapp-Chatbot/ instead gets redirected to https://github.com/ONEST-Network/Job-Manager-Adapter

[amaydixit11]

Hi @tushar-ekstep @aryasoni98
I’ve gone through the issue details and the reference links, and this seems like a solid and well-scoped project. I’m particularly interested in the Go-based microservice part and how it fits into the ONEST protocol. I’d like to contribute to this and take it forward.
Could you please assign me to the issue?

[Aerospace-prog]

@aryasoni98 , @tanishk2907
I have submitted the PR after completing all tasks. Kindly review it.
#5

[Uzaifm127]

I want work on this issue, assign this to me.

[aryasoni98]

Hi @amaydixit11,

Thank you for your interest in the Scheme Manager project. I see you've already gone through the issue details and reference links. That's great!

Since you're particularly interested in the Go-based microservice part, we could potentially collaborate on this implementation. Would you like to:

1. Start with setting up the basic project structure and Go modules?
2. Work on the database schema design?
3. Begin implementing one of the core APIs?

Let me know which aspect you'd like to focus on, and we can coordinate our efforts.

[aryasoni98]

Hi @amaydixit11,

Thank you for your interest in the Scheme Manager project. I see you've already gone through the issue details and reference links. That's great!

Since you're particularly interested in the Go-based microservice part, we could potentially collaborate on this implementation. Would you like to:

1. Start with setting up the basic project structure and Go modules?
2. Work on the database schema design?
3. Begin implementing one of the core APIs?

Let me know which aspect you'd like to focus on, and we can coordinate our efforts.

[aryasoni98]

Hi @Uzaifm127,

Thank you for your interest in working on this issue. Since this is a significant implementation, I'd suggest we:

1. First discuss your experience with Go and microservices
2. Review the implementation plan together
3. Potentially collaborate with other interested contributors

Could you share:

1. Your experience with Go and REST APIs?
2. Any previous work with PostgreSQL or Docker?
3. Which part of the implementation interests you most?

This will help us determine the best way to proceed.

[amaydixit11]

Hi @aryasoni98,

Thanks for the quick response! I'd love to start by setting up the basic project structure and Go modules. That’ll help me get a good grasp of the flow and set a strong foundation for the rest of the implementation.

Once that’s in place, I'll start by designing the database schema, and then move on to implementing the APIs

It would be great if you can assign me this issue, so that it becomes official
Let me know if there’s any existing structure or conventions I should follow before I get started. Looking forward to collaborating!

[amaydixit11]

Hi @aryasoni98
I have raised a PR for the Schema Designs, let me know if they look good to you,
I'll Proceed with the SQL Migration files, and then the PushSchemes API Design