[BLIP] BOUNTY Proposal : Baseline Calendar

[vaibhavgeek]

Grant Application for BLIP Bounty Hunt

Grant applications are completed by individuals or teams to propose allocation of Baseline grant funds to a specific project.
This template is tailored to the 6-week duration of the BLIP Bounty Hunt.

The grant application has been approved if a majority (6 or more) of the Technical Steering Committee members upvote this application (thumbs up), and a community manager updates the label to 'approved'.

If approved, add your project to the 'Approved Grants' list here to signify commitment to the work.

---

Applicant Background

Name of person or team submitting the grant request, (optionally) with background and experience.

Vaibhav Maheshwari

I have been a solidity developer and bounty hunter for multiple projects namely- Ricochet Exchange, Zesty Marketplace, Vite.js, Zilliqa, Matchbox DAO. I graduated from NIT Surat in 2020 with degree in applied mathematics. I love to work on difficult problems that help me grow and allow me to work on exciting technology.

---

Associated BLIP

Give name of associated BLIP with a hyperlink.

Baseline Calender

Details on Grant Work

(Describe your proposed work in greater detail)

The idea is to have a smart contract which will store a mapping that have addresses against available time / default available time of the address. This would then be matched with other address's availability and most recent time slot would be alloted to both the parties.
There would also be a beautiful UI which would allow users to set availability times and match it with other addresses given that they have allowed them to do so.

Tech Stack

• ReactJS (frontend)
• ExpressJS (backend)
• Blockchain (Gananche)
• Zero Knowledge Proof verifier (Circom + SnarkJS)
• (optional) Kafka Pub / Sub to verify proof whenever seeker sends and confirm it (not necessary, only to make it real time, can be done via APIs)

Lets' say there are two people, appointment Seeker (sk) [the person who is seeking an appointment] and interview lister [the person who is listing the interview that is sharing their calendly links in more traditional sense]

Here is how it would work,

• lister lists the available time slots
• lister shares the link publicly
• seeker signs in on the link available
• seeker selects multiple times that he / she is available
• seeker uses appointment time, and address to generate proof
• seeker sends proof to lister
• lister verfies the proof with two outcomes - appointment scheduled or appointment denied.

---

Deliverables / Schedule / Milestones

Provide information on the final deliverables, proposed schedule, and milestones followed to complete the work.

Milestone 1 (30%)
Create backend APIs for the person to login, view and set availabilities, set appointments in node, express js using sqlite as database.

Milestone 2 (30%)
Create the circuit (circom) and use SNARK.JS to create a way to verify.

Milestone 3 (30%)
Create a frontend which would be pleasing and appealing to the end user. Mainly 4 pages would be present in the entire application,

• Home Page with community links
• App Page with connect wallets
• Set time availability default
• Set appointment with someone

Milestone 4 (10%)
Testing of the contracts, documentation of the project.

---

Budget and Justification

Provide proposed amount that should be paid (in USD) for the grant work, with detailed justification.
Feel free to use suggested amount provided in the BLIP, or adjust according to the scope of your proposed project.

6000$
The proposed work would require serious developer hours and would need time and effort to justify the 6000$.

---

Community Grant Agreement

I understand and agree to the BLIP Bounty Hunt Terms & Conditions and the 'Process for Approved Grants' outlined here
(Items #7 and #8 under the 'Process for Approved Grants' list do not apply for the Bounty Hunt work given the shortened duration, instead bi-weekly updates are required as a comment under this grant request.

• I agree
• I do not agree

Questions?

Email the team at baseline-team@oasis-open.org or message in the BLIP Bounty Hunt Discord

[GoldenBit0]

TSC Members - please review this issue, comment with questions, and thumbs up or thumbs down to vote
@stefschmidt @Sjaaaakster @humbitious @Therecanbeonlyone1969 @samratkishor @kthomas @caleteeter @skarred14 @rfisch @mehranshakeri @fosgate29

[fosgate29]

I would change the order of milestones. I believe Frontend should be done at the end. If smart contract and circuit code are delivered and by any chance the frontend get delayed, community could get some benefit having the smart contract and circuit as examples. And also inputs/outputs for the frontend could change depending on the circuit/smart contract requirements.

[vaibhavgeek]

@fosgate29 That makes sense, I have updated my proposal to reflect the same

[GoldenBit0]

BLIP-12 is the work tracker.

[vaibhavgeek]

Update: Milestone one is complete. The idea is to use metamask login with sqlite (can be configured to any database) and API for setting up appointments.

Next milestone is to work on the circuit and verifier smart contract.

[Ybittan]

https://github.com/vaibhavgeek/baseline-calender

[Ybittan]

@vaibhavgeek Could you please provide some additional details on what work was completed within that repo to achieve the proposed milestone #1? I'm not seeing a contract.

I would also suggest checking out your own branch within the baseline repo, and working in a folder within the examples folder that follows our naming convention. This will make future migration easier, and will put the work you're contributing to the standard directly within it.

[vaibhavgeek]

Thanks for your prompt response and review, @Ybittan.
I realised that this is a web2 heavy application and the smart contract is just used to verify the circom circuit (from my understanding of what baseline protocol is). Let me know if I am mistaken in understanding. This is why milestone one is just setting up web2 base and creating backend APIs in it.

Regarding forking and working in examples branch, I will make a point of doing that from now on.

[Ybittan]

@vaibhavgeek The proposed milestone 1 is: Milestone 1 (30%)
Create smart contract which would have time availability in encrypted format and matching can happen for two different addresses.

Is this still your current first milestone? Or would you like to make updates and have the grant proposal re-evaluated?

[vaibhavgeek]

@Ybittan The truth is I am figuring the project as I work on it, so milestone definition and description isn't very clear. I will create the circom proof and smart contract function verification and submit it for review (milestone 1 and milestone 2) along with completed nodejs backend soon and then the milestone 3 in next part. This way, it would fit with current milestone definitions.

I hope that works.

[GoldenBit0]

Work is complete.

ethereum-oasis-op/baseline-blips#24
#92