# General Grant Proposal - eSim Wallet

* **Project:** Blockchain powered eSIM

## Project Overview :page_facing_up:

### Overview

This proposal is for a renewal grant for a mobile-based hardware crypto wallet using eSIMs with remote provisioning of accessibility. The initial grant details can be found https://hackmd.io/swQfOzVmR4OuwqER7EeOfQ

### Project Details
In the first grant, the team successfully completed a proof of concept demonstrating that remote provisioning and issuing of private keys over eSIM is feasible. They also explored and refined the process for launching this technology in a production environment, with the goal of onboarding many non-Web3 users to a cryptographically secure environment.

This renewal grant will support major activities such as production release, Devcon engagement, and research and development on Zero-Knowledge (ZK) technology, among others. More details are provided in the roadmap section.

The nature of this proposal involves using flexible deliverables while adhering to the projected roadmap which can be found below. During the grant period, team will be non-profit and not take any commision from the data plan sale in order to accerlate the adoption of this technology.

## Team :busts_in_silhouette:

### Team members
* Arpit Kumar , [e-mail] , [telegram](https://t.me/dungexn)

* Manul Singh Parihar , [e-mail] , [telegram](https://t.me/manulparihar)

* Tanmay Goel , [e-mail] , [telegram](https://t.me/guyphy4)

### Team's experience
Please describe the team's relevant experience. Some links would be useful.

* [Manul Singh Parihar](https://www.linkedin.com/in/manul-singh-parihar-8a9790171/)
Blockchain developer and architect (3.5+ years) with expertise in full-stack dev, smart contracts, & validator infrastructure. Proven ability to deliver impactful solutions:
Designed [LSD protocol](https://docs-ipfs.joinstakehouse.com/lsd/overview/) at Blockswap, attracting significant staking & revolutionizing validator requirements.
Built bridge at Unido-PAC, enabling seamless token utilization between private & public blockchains.
Deployed robust contracts across diverse platforms (Ethereum, Flow, Substrate) at [GVOS.io](https://github.com/gvos/gvosio).
Led architectural discussions & audits, ensuring production-ready solutions at Blockswap.
Proactively educated users via [tutorials](https://docs-ipfs.joinstakehouse.com/lsd/DAOsForLSD/) and documentation and created numerous SDKs ([Stakehouse SDK](https://www.npmjs.com/package/@blockswaplab/stakehouse-sdk), [LSD Wizard SDK](https://www.npmjs.com/package/@blockswaplab/lsd-wizard), [K2 SDK](https://www.npmjs.com/package/@blockswaplab/k2-sdk)).
Collaborative & passionate learner, eager to contribute to a team pushing blockchain boundaries.

* [Tanmay Goel](https://www.linkedin.com/in/tanmay-goel-59a1981b5/)
B.Tech graduate in Electronics and Communication Engineering from the IIIT Guwahati. CPU Verification Engineer at Nvidia, working on performance micro-architecture of cutting-edge data-center CPUs and as an intern I worked on developing a high-precision CUDA-enabled library, I've also done research internships at I.I.T. Jodhpur and I.I.T. Ropar where I worked on DRAM, GDDR memory technologies to create more performant and efficient architectures. These resulted in research publications in peer reviewed journals. My most recent work involves doing research in the space of Post Quantum Cryptography (PQC).
[Conference Paper](https://ieeexplore.ieee.org/abstract/document/9424339) [Journal Paper](https://www.sciencedirect.com/science/article/abs/pii/S0141933122002411?via%3Dihub)

* [Arpit Kumar](https://twitter.com/ARPITKU80579385)
B.Tech graduate with majors in Electronics and Communication from IIIT Guwahti.
Academic Project [Blockchain based Dynamic Spectrum Sharing](https://github.com/ArpitxGit/Blockchain-Based-Dynamic-Spectrum-Sharing), where i started learning about integration of blockcahin technology in telecommunication for potential innovation.
Blockchain Development (2.5+ years) with expertise in smart contract development on EVM compatible chains and decentralised protocols integration in dapps for various use case, worked on 3 projectcs , 2 in production and 1 in testing phase at this moment.
[Applied cryptographic internship](https://github.com/lambdaclass/sparkling_water_bootcamp), got good understanding of cryptographic primitives, modern cryptography and worked on groth16.
Research work on [Blockchain and Telecom Integration](https://dungexn.notion.site/dungexn/GMMS-5f2896191f2b47ca8bc81de8357ed4cf) for a year which i started at [EthIndia Fellowship 3.0](https://devfolio.co/projects/blockchain-powered-esim-942f).

### Team Code Repos
* https://github.com/Blockchain-Powered-eSIM

## Development Roadmap :nut_and_bolt:

The roadmap for the next 10 months will focus on production release, incorporating feedback, and R&D on OpenRSP.

#### July - September (3 months)
1. Implement account abstraction and enable passkey authentication, replacing device wallet smart contracts.
2. Submit the final smart contract for security audit (PSE audit team support requested).
3. Prepare for entity registration, necessary for production release from Airalo and eSIM (advised by EF’s lawyer; it will be an LLC with no profit generation during the grant period).
4. Design and develop Android and iOS apps for users to purchase data plans (with support from Pollen Labs).
5. Conduct closed beta testing for 100-300 users.
6. Submit a Devcon proposal to offer the wallet as an official perk for all attendees.
7. Draft and review OpenRSP*.

#### October - December (3 months)
1. Iterate based on closed beta results.
2. Polish and prepare for Devcon release.
3. Review and design OpenRSP engineering, followed by implementation.
4. Release the app in multiple countries via iOS App Store and Google Play Store.
5. Identify use cases and collaborate with other protocols to enhance the experience.

#### Janurary - March (3 months)
1. Release OpenRSP paper, implementation, and benchmarks.
• Initiate “Modern eUICC” research led by Tanmay, aiming to build a hardware public good for real-time unique secure identifiers to onboard and authenticate end users for third-party mobile apps.
• Initiate “Consensus Designing for eSIM-based Chain” research led by Manul, aiming to create a fraud-proof system by design.
2. Continuously improve the app based on feedback.

### Overview

- Total Estimated Duration: 37 weeks (July 2024 - March 2025)
- Full-time equivalent (FTE): 3 = 3 x Full time
- Total Costs: $

### Milestone 1 - July:
* **Estimated Duration:** 4 weeks
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: July 26th, 2024
* **Focus:** :
* Complete smart contract and get ready for audit
* Website, App design & building (collab with Pollen labs)
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

### Milestone 2 - Aug:
* **Estimated Duration:** 4 weeks
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: Aug 23rd, 2024
* **Focus:** :
* Smart contract improvmenet
* Complete the entity registeration
* Target to release App as internal beta (collab with Pollen labs)
* Submit Devcon proposal as travel perk
* Continue on OpenRSP research
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

### Milestone 3 - Sep:
* **Estimated Duration:** 4 weeks
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: Sep 20th, 2024
* **Focus:** :
* Launch app for closed beta release and testing
* Conduct beta testing
* Prepare for Devcon release
* Continue on OpenRSP research
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

### Milestone 4 - Oct:
* **Estimated Duration:** 4 weeks
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: Oct 18th, 2024
* **Focus:** :
* Iterate and polish app and any user touch points for offical v1 release
* Continue polish smart contract
* Build out user flow for Devcon
* Start OpenRSP implemntation
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

### Milestone 5 - Nov:
* **Estimated Duration:** 4 weeks
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: Nov 15th, 2024
* **Focus:** :
* Participate Devcon and observe mass-scale of user base
* Continue polish solution
* Continue on OpenRSP implementation
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

### Milestone 6 - Dec:
* **Estimated Duration:** 5 weeks (Nov 18th - Dec 20th)
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: Dec 20th, 2024
* **Focus:** :
* Continue on OpenRSP implementation
* Incorporate user feedback from Devcon
* Start explore to onboard partners for adoptions
* Prepare app to release to more countries
* Explore possible partnership direct with telecom corp. for better price to users
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

### Milestone 7 - Jan:
* **Estimated Duration:** 4 weeks (Jan 6th - 31st)
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: Jan 31st, 2025
* **Focus:** :
* Prepare to release research paper on OpenRSP
* Continue OpenRSP development
* Continue explore other partnership for adoptions
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

### Milestone 8 - Feb:
* **Estimated Duration:** 4 weeks
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: Feb 28th, 2025
* **Focus:** :
* Implement OpenRSP to the app
* Continue explore other partnership for adoptions
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

### Milestone 9 - March:
* **Estimated Duration:** 4 weeks (March 3rd - Apr 4th, with one week holiday)
* **FTE:** 3
* **Costs:** $ x ($x / each member)
* **Estimated delivery date**: Apr 4th, 2025
* **Focus:** :
* Implement OpenRSP to the app
* Continue explore other partnership for adoptions
* Other enhancement
* **Deliverable**:
* List of tasks performed and the time allocated to each task.
* List of outputs: PRs, commits, write-ups, and etc

---

# Addtional info

What's OpenRSP?

**Open Source Remote SIM Provisioning (OpenRSP)** systems should inherit the secure and efficient activation of embedded SIMs (eSIMs) in a variety of devices from traditional RSP and utilise modern cryptography for data integrity resulting in trustworthy systems by removing trusted parties involved in the system.

Recent advancements in cryptographic techniques have significantly enhanced both the security and efficiency of these systems.

Exploring the application of state-of-the-art cryptography, including Zero-Knowledge Proofs (ZKP) and garbled circuits, to develop a highly secure, privacy focused and trustworthy RSP framework.

Designing this with the motivation of incorporating ZKP for device and user authentication, ensuring that authentication can be performed without revealing sensitive information to establish a secure handshake for network access. This method leverages the properties of ZKP to maintain privacy while proving possession of valid credentials. Additionally, garbled circuits are employed to secure profile management operations, allowing encrypted data to be processed without exposing it, thus ensuring end-to-end confidentiality.

We address the key management challenge through Identity-Based Cryptography (IBC). By using identities as public keys, IBC simplifies the key distribution process and enhances security. This framework is designed to be open-source, promoting collaboration among various stakeholders in the ecosystem and fostering innovation and interoperability.

We will be providing a detailed analysis of the theory, implementation, challenges and potential benefits of incorporating these advanced cryptographic techniques into eSIM technology.

Our result will demonstrate that the proposed framework not only significantly improves the security and privacy of the RSP process but also lays the foundation for a more trustworthy and collaborative environment in the digital communication domain.