Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arism Wallet - A hybrid-custodial wallet and distributed key management protocol. #163

Open
SnowyField1906 opened this issue Apr 18, 2024 · 0 comments
Assignees
Labels
Q3'24 Q3'24 Cohort

Comments

@SnowyField1906
Copy link

SnowyField1906 commented Apr 18, 2024

Grant Proposal

  • Project name: Arism Wallet
  • Team name: Arism Lab
  • Website: https://docs.arism.org
  • Category: Privacy-as-a-Service
  • Open-source: YES

About Project

Project overview

Arism Wallet is a hybrid-custodial wallet and distributed key management protocol. This decentralized wallet application uses advanced cryptographic algorithms to ensure the security and integrity of user's private keys.

Key features include:

  • Friendliness: One-click login via third-party platforms. No need to remember seed phases or private keys.
  • Loss Prevention: Easy recovery with Multi-Factor Authentication (MFA). No longer worry about losing access to accounts by mistakes.
  • Security: Protected by a distributed network of nodes. Keep your accounts safe from any attack attempts.
  • Feature Variety 1: Account Abstraction and Decentralized Identifier support. Manage and represent multiple accounts/assets by a single identity.

Target audience

Node providers

We launch a Fungible Token called Arism Token (ARM) which is used for staking, rewarding and fining in operating Arism Nodes. There are two types of nodes in the Arism Network:

  • Validation Network (Mainnet): The main network that executes algorithms to verify third-party accounts and conduct "Network Key" for users.
  • Relay Network (Subnet): The relay network that provides promoted Relay Nodes when there is a dead, malicious or expired Validation Node in Mainnet.

Node providers can stake their ARM tokens to become a Node Provider and earn rewards by taking part in verifying user's accounts. When a node provider registers a node, they will be required to stake a certain amount of ARM tokens to join the Subnet. The more ARM tokens staked, the higher the chance of being promoted to the Mainnet.

Users

Users can create an identity by using their third-party platform accounts (e.g. Google) and link them to their Arism Wallet. There are 3 factors to verify a user's identity:

  • Network Factor: Responsible by the Arism Network.
  • Device Factor: Responsible by the user's devices (e.g. phone, computer, etc.).
  • Recovery Factor: Responsible by the user's recovery information (e.g. password, fingerprint, etc.).

Users can sign in to the Arism Wallet by providing 2/3 factors. A user can also create multiple keys associated with their identity which is responsible by Arism Metadata.

Developers

Developers can integrate the Arism SDK into their applications to allow users to sign transactions by their Arism Wallet. The Arism Application allows users to choose which key to sign the transaction with.

We also provide special APIs to allow developers to interact with the Arism Network.

Problem statement

Our motivation for building the Arism Wallet comes from the following problems:

  • Most current wallets are saved entirely on local storage (non-custody) or entirely on service providers (custody). Arism Wallet is a hybrid-custody wallet that take advantages of both custodial and non-custodial models.
  • There are also some hybrid-custodial wallets but they still rely heavily on a single party whereas Arism Protocol lets the user's wallet to be held by a community instead, but its safety is still protected from any attack and hack attempts through cryptographic algorithms and MFA mechanism.
  • Storing and signing transactions right on the web application will eliminate the gap between mobile and desktop, something that wallet extensions suffer from.

Our vision is to create a wallet with complete and native support on Secret Network, then consider to expand towards Cosmos ecosystem and other chains.

Inspiration

Web3Auth is a forerunner of the Arism Wallet which as a total raised of 15.5 million USD over 4 funding rounds. To date, it's supporting thousands of Web3 projects with more than 12 million monthly users.

Key Features Web3Auth Arism Wallet
Node providers 9 fixed node providers from reputable parties: Binance, Ethereum, Name Service, Etherscan, Matic/Polygon, Zilliqa, Tendermint, Ontology, SKALE and Torus. 5 node providers on Mainnet and unlimited node providers on Subnet which are totally anonymous.
Stake No staking mechanism. Earn rewards by staking ARM tokens.
SDK integration Available with 4 plans: Base, Growth, Scale and Enterprise. Fees are charged around 399 USD per month. Free to integrate.
Assets management support No support for assets. Support fully assets and chain's services.
Token launch No token launched. ARM token.
Protocol vulnerability Unavailable if Torus Network is down or user lose access to connected OAuth account. Network Factor can be replaced by others (Device Factor and Recovery Factor).
Support EVM-based only. Any chain.
Smart contract Centrally controlled by Torus admin (contract owner). Decisions are casted by node providers through voting schemes as a DAO.

Reason for interest

The Arism Contract enables a transparent and secure way to manage anonymous node providers powered by voting schemes.

Therefore, high transaction speed and low gas fees are the prerequisites that we aim for.

Besides, we are also looking for a friendly chain that well-supports assets (e.g. Fungible Token, Non-Fungible Token, etc.). It will not only highlight the Arism Wallet's features but also provide a good basis for the Arism Protocol to grow.

Technology stack

We focus on developing cryptographic algorithms on the Arism Node and Arism Application side. The front-end parts are built with Next.js and the back-end parts are built with Nest.js. We also use Redis for caching and MongoDB/IPFS for storing metadata.

About Us

Team members

Name Role GitHub Contact
Nhi Tran Team Leader, Business Development Executor, Smart Contract Engineer @TranNhi27 beahayden27@gmail.com
Kiet Tran DevOps Engineer, Backend Developer, Smart Contract Engineer @Kiet1618 kiettran1618@gmail.com
Thuan Nguyen Frontend Developer, Backend Developer, Smart Contract Engineer @SnowyField1906 snowyfield1906@gmail.com

Repositories

Repository Description Link
Arism Node The peer-to-peer network that powers the Arism Network arism-node
Arism Contract The smart contract that powers the transparency of the Arism Nodes arism-contract
Arism Application The Interface for the Arism Protocol arism-application
Arism SDK The Software Development Kit for the Arism Protocol arism-sdk
Arism Metadata The service that stores metadata for the Arism Protocol arism-metadata
Arism Docs The documentation and whitepaper for the Arism Protocol arism-docs

Development Roadmap

Overview

  • Costs per FTE: 35 USD per hour
  • Working hours per FTE: 40 hours per week
  • Number of Milestones: 6
Milestone Description Estimated Duration Manpower Hours Costs Percentage
1 Implement core algorithms 1 month 3 people 320 hours 11,200 USD 16.67%
2 Draft interface 1 month 2 weeks 3 people 480 hours 16,800 USD 25%
3 Deepen interface 1 month 3 people 320 hours 11,200 USD 16.67%
4 Overall optimization and audit 1 month 3 people + Audit Team 320 hours 11,200 USD2 16.67%
5 Documentation and whitepaper 2 weeks 3 people 160 hours 5,600 USD 8.33%
6 Test phase and air drop 1 month 3 people 320 hours 11,200 USD 16.67%
Total 6 months 3 people + Audit Team 1,920 hours 67,200 USD 100%

Current status

Milestone Percentage Notes
1 10% We have implemented 1/5 of the core algorithms. Not integrated with the Arism Network yet.
2 10% We have drafted the interface for the Arism Application for demo purposes. Not integrate with the chain yet.
3 0% We have not started deepening the interface yet.
4 0% We have not started overall optimization and audit yet.
5 20% We have built a documentation site and written a brief technical insights.
6 0% We have not started test phase and air drop yet.

Milestone 1 — Implement core algorithms

ID Scope Specification Risk
1 Contract Implement management, staking, rewarding and voting Low
2 Node Integrate smart contract and implement DSS, ISS Medium
3 Application Implement base UI and SSS Low
4 Metadata Implement base metadata storage Low

Milestone 2 - Draft interface

ID Scope Specification Risk
1 Contract Implement token distribution and complete the DAO Low
2 Node Implement RSS, PSS and VSS Medium
3 Application Integrate Node, Metadata and blockchain Low
4 SDK Implement base SDK Medium
5 Metadata Complete metadata storage Low

Milestone 3 - Deepen interface

ID Scope Specification Risk
1 Node Complete algorithms Medium
2 SDK Complete SDK Medium
3 Application Complete UI, integrate blockchain and services Low

Milestone 4 - Overall optimization and audit

ID Scope Specification Risk
1 Node Audit algorithms Medium
2 Contract Audit smart contract Medium
3 SDK Optimize SDK Medium
4 Application Optimize blockchain and services Low
5 Metadata Optimize metadata storage Low

Milestone 5 - Documentation and whitepaper

ID Scope Specification Risk
1 Docs Write technical insights Low
2 Docs Write whitepaper Low
3 Docs Write guides Low
4 Docs Complete documentation site Medium

Milestone 6 - Test phase and air drop

ID Scope Specification Risk
1 Node Deploy test nodes Low
2 Contract Deploy test contract Low
3 Application Deploy application Low
4 Metadata Deploy metadata Low
5 Protocol Launch air drop (ARM tokens or NFTs) Low

Future Plans

  • Integrate Decentralized Identifier (DID) and Verifiable Credential (VC) into the protocol.
  • Integrate Account Abstraction (AA) into the protocol.
  • Integrate Swap, Lending, Staking, Aggregator, etc. into the protocol.
  • Integrate Multisig into the protocol.
  • Develop a mobile application for iOS and Android which manages and takes part in authenticating user's accounts.
  • Implement Authorization Credential for SDK and in-app environment for Application to support executing custom scripts (any script like gathering user's tokens, doing airdrop tasks, etc.).

Additional Information

Contact us via email: snowyfield1906@gmail.com for more information.

Footnotes

  1. Features are planned to be implemented in the next phase.

  2. Extra costs might be charged for the audit team.

@azaidelson azaidelson self-assigned this Apr 30, 2024
@azaidelson azaidelson added the Q3'24 Q3'24 Cohort label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Q3'24 Q3'24 Cohort
Projects
None yet
Development

No branches or pull requests

2 participants