https://github.com/anoushk1234/solana-otp-wallet

A Smart Contract Wallet that can be recovered with an OTP on your mobile number.
https://github.com/anoushk1234/solana-otp-wallet

otp shamir-secret-sharing smart-contract-wallet solana wallet

Last synced: 20 days ago
JSON representation

A Smart Contract Wallet that can be recovered with an OTP on your mobile number.

• Host: GitHub
• URL: https://github.com/anoushk1234/solana-otp-wallet
• Owner: anoushk1234
• License: mit
• Created: 2022-12-07T05:40:58.000Z (about 2 years ago)
• Default Branch: main
• Last Pushed: 2022-12-08T12:07:07.000Z (about 2 years ago)
• Last Synced: 2024-10-26T22:14:42.922Z (2 months ago)
• Topics: otp, shamir-secret-sharing, smart-contract-wallet, solana, wallet
• Language: TypeScript
• Homepage:
• Size: 2.36 MB
• Stars: 5
• Watchers: 4
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Solana-otp-wallet

## Problem

The problem with current hot wallets is that the user has to store a mnemonic somewhere and manage the key. 

This opens the possibility of losing private keys and hence users' funds with it. We introduce a simple wallet recovery mechanism 

using OTPs integrated into our smart contract wallet. 

The wallet is now not only recoverable but also seamless due to the use of user friendly OTP system.

## Implementation

The main challenge that we faced was to rely on a trusted and centralized OTP verifying service which opens up the possibility of censorship. Ideally we'd want this OTP verification to be done on the smart contract itself making it trustless.

Some possible solutions that could be used to address this issue:

   - Use of zk-proofs like Bulletproofs (a special optimized case of range-proofs) to prove that the OTP lies in a certain numeric range but without revealing it.

   - Using Shamir Secret sharing to split the OTP off-chain into 2 or more shares that can be recombined on chain to be verified. These shares would of course be homomorphically encrypted and verified using zk proofs.

    

We chose the second option for our v1.

# How it Works



Right now we haven't added encryption but it can be added



# TODO

- [ ] Add session key encryption

# Credits: 

  - [@harsh4786](https://github.com/harsh4786) for contributing with the cryptography

  - [@abishekk92](https://github.com/abishekk92) for giving us the Idea