OISY is a new browser-based, network-custodial and multi-chain wallet powered by Internet Computer's chain fusion technology.
The OISY wallet provides a convenient user experience known from custodial wallets but without their strong trust assumptions. In contrast, OISY provides trust assumptions based on network custody, and comparable to self-custody. Different from self-custody wallets though, OISY requires no browser extensions or additional mobile app, a standard off-the-shelf web browser is sufficient. In conclusion, OISY provides an attractive user experience with a low entry barrier, yet requires no strong trust assumptions.
Building on ICP, OISY achieves a unique set of features:
-
Browser-based: no matter your browser and operating system preferences, OISY allows you to receive, hold, and send native ICP, ICRC-1, ETH, ERC20 (and in the near future BTC).
-
Cross-device: due to the use of Internet Identity, OISY can easily be used across all devices you have linked to your Internet Identity.
-
Network custody: the key controlling your multi-chain assets is not controlled by a single entity nor has it ever existed as such. The key was generated using advanced cryptography that distributed key-shares among dedicated ICP replica nodes and signatures are created using threshold ECDSA.
-
Fully on-chain: not only the keys but the entire wallet application is stored on-chain and served directly to your browser. The entire wallet is secured by a decentralized trust model, which guarantees that neither the front-end, nor the back-end have been tampered with.
-
Interoperable: OISY integrates with the WalletConnect protocol allowing you to use it as a wallet for many established web3 services, such as Uniswap. The OISY team is actively working on integrating OISY with ICP's signer standards allowing OISY to interact with ICP's rich dapp ecosystem.
-
Free to use and develop: OISY is open-source software and licensed under Apache 2.0. Feel free to fork it or propose improvements.
What are the unique ICP technical building blocks enabling the creation of OISY?
-
Chain-key signatures: the world's best threshold ECDSA signature protocol suite (only available on ICP) enables smart contracts to perform cryptographic signatures without a single entity having full access to the private key. Read more about chain-key cryptography or start building based on chain-key signature sample code.
-
Internet Identity (II): based on ICP's threshold BLS signature schemes and WebAuthn, Internet Identity (II) is an authentication and key management system with strong privacy and security guarantees. Using WebAuthn, users can conveniently create secure sessions with their fingerprint or other biometric identifiers. Read more about Internet Identity technology or start integrating II into your canister smart contract.
-
Web applications served from chain: ICP is not only designed to run backends, such as ledgers, on chain, its low storage cost and low latency allow it to serve frontends, such as HTML files and images, from chain, too. Read more about smart contracts serving web applications or directly start building your first decentralized web frontend.
-
(Upcoming) HTTP outcalls: for now, OISY calls centralized Ethereum endpoints, such as Infura or Alchemy, from the frontend. In the future, OISY might be improved to use HTTP outcalls to call these endpoints in a decentralized fashion. Check out the HTTP outcalls sample code to explore how to use Web 2.0 services on ICP.
To file a request to have your dApp listed in the dApps explorer of OISY Wallet, please submit this dApp Submission Request.
Please note that this is a beta version of OISY Wallet which is still undergoing final testing before its official release. The platform, its software and all content found on it are provided on an “as is” and “as available” basis. OISY Wallet does not give any warranties, whether express or implied, as to the suitability or usability of the application, its software or any of its content.
- Install the IC SDK.
Open a new terminal window in the project directory, and run the following command to start the local replica. The replica will not start unless dfx.json exists in the current directory.
dfx start --background
When you're done with development, or you're switching to a different dfx project, running
dfx stop
from the project directory will stop the local replica.
Make sure you switch back to the project root directory.
First, install the frontend dependencies by running
npm ci
To build and deploy the project locally, first create a .env.development file by copying the .env.example file. Once you've correctly set the api keys for all the different services that OISY needs, then run:
npm run deploy
It should output something like the following
...
Deployed canisters.
URLs:
Frontend canister via browser
frontend: http://127.0.0.1:4943/?canisterId=br5f7-7uaaa-aaaaa-qaaca-cai
Backend canister via Candid interface:
backend: http://127.0.0.1:4943/?canisterId=bd3sg-teaaa-aaaaa-qaaba-cai&id=bkyz2-fmaaa-aaaaa-qaaaq-cai
internet_identity: http://127.0.0.1:4943/?canisterId=bd3sg-teaaa-aaaaa-qaaba-cai&id=be2us-64aaa-aaaaa-qaabq-cai
Click on the frontend URL to access the OISY Wallet that is running locally.
See HACKING
The backend is written in Rust and you can find it under the backend folder. It uses the tECDSA API provided by IC. To find out more about tECDSA, you can read the Eurocrypt 2022 paper.
If you want to locally deploy the backend only, you use the following command
./scripts/deploy.backend.sh
The frontend is written entirely in Svelte. You can serve the frontend in development mode like you normally develop a svelte app using the command
npm run dev
Some Iconly icons are used in the project, not included. You must obtain a license separately.
The license for this project is bought and owned by the DFINITY Foundation, please see terms and conditions here.