# Introduction

Learn about OISY Wallet and how to integrate with it.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fkim0mcVXYUeGMIDwVqnG%2Fapp-preview.jpg?alt=media&amp;token=e612d38e-b326-4969-8553-a72b96db5e59" alt=""><figcaption></figcaption></figure>

**OISY Wallet** was incubated at DFINITY Foundation to simplify DeFi navigation. Initially built for ICP, it quickly evolved to unify primitives across all DeFi chains.

Today, OISY is the world’s first fully on-chain digital asset wallet, consolidating chains, identities, and primitives into a single immutable DeFi terminal.

Powered by [ICP’s Chain Fusion technology](https://internetcomputer.org/chainfusion), OISY delivers security, transparency, and scalability by default.

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th><th data-type="content-ref"></th><th data-hidden data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Getting started</strong> </td><td><a href="/introduction/why-oisy-wallet">Why OISY Wallet</a></td><td><a href="/introduction/internet-identity">Internet Identity</a></td><td><a href="/using-oisy-wallet/how-tos/logging-into-oisy">Logging Into OISY</a></td><td><a href="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FndTQ3gs3AKMUqDWVQyeU%2FGetting%20started.jpg?alt=media&amp;token=6b6c1108-7504-462b-b568-6cab87f45c95">Getting started.jpg</a></td></tr><tr><td><strong>Using OISY Wallet</strong></td><td><a href="/using-oisy-wallet/how-tos/sending-tokens">Sending Tokens</a></td><td><a href="/using-oisy-wallet/how-tos/connecting-to-dapps">Connecting to dApps</a></td><td><a href="/using-oisy-wallet/how-tos/receiving-tokens">Receiving Tokens</a></td><td><a href="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FbvwYLNgfRcURQbhiSZBH%2FUsing%20OISY%20Wallet.jpg?alt=media&amp;token=8c2e18b8-c2cd-4f7c-a212-ca0a1cd6c5c7">Using OISY Wallet.jpg</a></td></tr><tr><td><strong>Security</strong> </td><td><a href="/security/asset-control-recovery-and-governance-in-oisy-wallet">Asset Control, Recovery, and Governance in OISY Wallet</a></td><td></td><td><a href="/security/best-practices">Best Practices</a></td><td><a href="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FFXxXdt5LpFExopDBEU7J%2FSecurity.jpg?alt=media&amp;token=98a1642d-343a-47c0-826c-5bf3c2634b25">Security.jpg</a></td></tr><tr><td><strong>For Developers</strong></td><td><a href="/for-developers/icp-building-blocks">ICP Building Blocks</a></td><td></td><td><a href="/for-developers/icp-building-blocks/build-and-run-yourself">Build and Run Yourself</a></td><td><a href="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FCjXy6s0ajKkWvv7HJKcx%2FInfrastructure.jpg?alt=media&amp;token=3850b6b3-5e95-4829-80e4-f3bb7372eedd">Infrastructure.jpg</a></td></tr><tr><td><strong>Integrate With OISY Walle</strong>t</td><td><a href="/for-developers/how-to-connect-with-oisy">How to &quot;Connect with OISY&quot;</a></td><td></td><td><a href="broken://pages/SzjdsLxdVECYBwlsCZ6D">Broken link</a></td><td><a href="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FACbX5AK2SMI1P2Uu5E3E%2FIntegrate%20With%20OISY%20Walle.jpg?alt=media&amp;token=b4d16208-feb5-4831-ba54-2c9638c698de">Integrate With OISY Walle.jpg</a></td></tr><tr><td><strong>Media Kit</strong> </td><td><a href="/media/media-kit">Media Kit</a></td><td></td><td><a href="/media/logos-and-assets">Logos &amp; Assets</a></td><td><a href="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FZRJsedHmVNptT6omGHWN%2FMedia%20Kit.jpg?alt=media&amp;token=64e606c0-1a78-4b2c-b513-5d7c88d84b18">Media Kit.jpg</a></td></tr></tbody></table>


# Why OISY Wallet

OISY Wallet is a fully on-chain solution that requires no downloads or installations. Explore the wallet’s features in detail below:

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FyESD50zBkUQ3ydWZasWt%2FBreakout%20slide.jpg?alt=media&amp;token=1ba1c195-f78c-45c4-a1c2-6b9f5d2ca197" alt=""><figcaption></figcaption></figure>

## Digital Asset Management

OISY empowers you to manage all your digital assets—including Bitcoin, Ethereum, ICP, Solana and more—within a single, unified wallet. Say goodbye to the hassle of juggling multiple wallets for different cryptocurrencies. With OISY, you can enjoy a seamless, efficient experience that bridges the gap across various platforms.

## Network Custody

OISY Wallet introduces network custody, a groundbreaking approach that leverages the Internet Computer’s advanced cryptography to eliminate the need for directly handling private keys. This innovative method offers a secure and user-friendly alternative to traditional practices, embodying the principles of the “Onchain is the New Online” movement. By operating on a distributed network, OISY enhances security and resilience against cyber threats.

Your multi-chain assets are safeguarded by a key that is neither controlled by a single entity nor has ever existed as a singular unit. Instead, this key is generated through advanced cryptography that distributes key-shares across dedicated ICP replica nodes, with signatures created using threshold ECDSA.

## Fully On-Chain

OISY’s security extends beyond keys—the entire wallet application is fully stored on-chain and served directly to your browser via the Internet Computer. This architecture ensures the wallet adheres to a decentralized trust model, making it inherently tamper-proof and highly secure.

Regardless of your preferred browser or operating system, OISY enables you to seamlessly receive, hold, and send native ICP, ICRC-1, ETH, ERC-20, SOL, BTC, and many more tokens.

## Limitless Access

Through Internet Identity, OISY allows you to access your wallet across all devices linked to your decentralized identity. Whether you’re using a smartphone, tablet, or desktop, you can enjoy a consistent and secure experience.

## Multichain Compatibility

OISY integrates the [WalletConnect](https://walletconnect.com/) protocol, enabling you to interact with a wide range of established Web3 services, such as Uniswap. Additionally, the OISY team is actively working to integrate [ICP signer standards](https://github.com/dfinity/wg-identity-authentication/blob/main/topics/signer_standards_overview.md), paving the way for seamless interaction with ICP’s [dApp ecosystem](https://internetcomputer.org/ecosystem).


# Internet Identity

OISY Wallet uses Internet Identity for authentication.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FMcTvAxojMYYZ8rMCdJOz%2FInternet%20Identity%20page.jpg?alt=media&amp;token=7ca743bf-e3bb-4511-a8df-f0457fc456d3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**OISY recently switched from version 1.0 of Internet Identity to version 2.0.**\
Please check [OISY Wallet switches to Internet Identity 2.0](/using-oisy-wallet/support/oisy-wallet-switches-to-internet-identity-2.0) for detailed information about this switch.
{% endhint %}

[Internet Identity](https://id.ai/) provides a secure, privacy-focused, and user-friendly authentication solution for the Internet Computer ecosystem. It allows users to securely and anonymously access decentralized applications (dapps) on the platform. Here are the key features of Internet Identity:

1. **Passwordless** Authentication: Instead of traditional usernames and passwords, Internet Identity uses passkeys, which are cryptographic public/private key pairs. Users can authenticate using biometric methods like fingerprint sensors (TouchID) or facial recognition (FaceID), or hardware security modules like YubiKeys or Ledger wallets.
2. **Privacy-Enhancing**: Internet Identity creates a unique pseudonym for each dapp a user authenticates with, preventing tracking across different applications and enhancing user privacy.
3. **Decentralized and Secure**: It operates entirely on the Internet Computer blockchain, allowing users to verify the code it runs. This decentralized approach enhances security and transparency.
4. **User-Friendly:** Users can create "identity anchors" and assign multiple devices to them, making it convenient to access dapps across different devices without managing complex cryptographic keys directly.
5. **No Personal Information Required:** Unlike traditional authentication methods, Internet Identity does not collect or store any personal identifying information from users.&#x20;
6. **WebAuthn Integration:** Internet Identity is built on the WebAuthn API, which is supported by modern web browsers and operating systems, ensuring broad compatibility.

More information:&#x20;

1. [Internet Identity Help & Support page](https://identitysupport.dfinity.org/) ↗
   1. [Internet Identity explained](https://identitysupport.dfinity.org/hc/articles/27213167791124-Internet-Computer-Internet-Identity) ↗
   2. [What's new in Internet Identity 2.0](https://identitysupport.dfinity.org/hc/articles/39593373981588-Internet-Identity-2-0) ↗
2. [Internet Identity homepage](https://id.ai/) ↗
3. [Manage your Internet Identity ](https://id.ai/manage)↗
4. [Manage your legacy Internet Identity (Internet Identity 1.0)](https://identity.internetcomputer.org/) ↗


# OISY protects you!

This page describes means that OISY implements to keep your funds protected.

{% hint style="success" icon="user-shield" %}
Just like with email or social media, not everyone on the internet acts in good faith. Some try to trick others into making mistakes they can profit from. While the nature of crypto makes it fundamentally secure, it doesn't make its users immune — there are still ways bad actors try to take advantage.

**OISY keeps you protected** by offering a set of features that either flag potential dangers before you act, or prevent harmful mistakes from happening in the first place.
{% endhint %}

## Features that keep you protected

### Filter for small transactions

{% hint style="info" icon="user-shield" %}
**OISY filters out transactions with very small values.**

Blockchain users sometimes receive very small amounts of tokens from unknown sources. Those are typically spam transactions and are coming from a sender address that looks very similar to a legit address you have interacted with very recently.\
These transactions are an attempt to trick you into accidentally picking or copying a wrong address instead of a legit one when you do a new send transaction later.

<sub>Note that this filter is</sub> <sub></sub><sub>**enabled by default**</sub><sub>, and</sub> <sub></sub><sub>**you can turn it off**</sub> <sub></sub><sub>any time you want.</sub>
{% endhint %}

When opening the Activity page or the transaction list of an individual token, you see an info element that indicates that transactions with a small values are hidden. You can close the notification, and it will not be shown again, unless you turn the filter off and back on again.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FvaWRPTLDD1qItFGkX9Pl%2Fimage.png?alt=media&amp;token=72716c77-72bc-42ac-8edb-e408255c5bfd" alt="" width="563"><figcaption></figcaption></figure>

When the filter is enabled, all transactions with a very small value will be hidden. Note that the value is calculated based on a token's current price.

Go to the Settings page to turn the filter off or back on again.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FaamafRJQHqqthf2mQ988%2Fimage.png?alt=media&amp;token=6cd950ae-cfc4-42df-a700-221f6eb0cc39" alt="" width="375"><figcaption></figcaption></figure>

### Privacy mode

OISY allows you to quickly blur all token balances and values on your overview or token screens. You can find more information on how to use it [here](/using-oisy-wallet/how-tos/enabling-privacy-mode), or just hit the key **`P`** to enable/disable it :wink:.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FvsI1h3mchdMJ75OlgvJU%2Fimage.png?alt=media&amp;token=c1a24c8a-e130-4489-aaee-cf4512de717f" alt="" width="375"><figcaption></figcaption></figure>

### Contacts

{% hint style="success" icon="shield-check" %}
OISY allows you to maintain a list of contacts and save multiple crypto addresses for each of them.\
**Using contacts significantly reduces the risk of using a wrong address when doing crypto transactions.**
{% endhint %}

When you **send** a token, you can select an existing contact instead of entering the address manually, avoiding errors during the copy process or accidentally copying a wrong address.

Also when you **receive** tokens, the transaction details screen will 'resolve' the contact, and show you to contact name as sender, so you can be sure it's the correct sender.

You can access your Contacts list from the user menu

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F0a27cEMDfsXm4Tyn2MEl%2Fimage.png?alt=media&amp;token=904b5a27-f844-4355-b07b-55113030c019" alt="" width="258"><figcaption></figcaption></figure>

### First time use warning

When you make a new transfer, and we detect that you have never used the destination address before, OISY shows you a warning. So if you have sent tokens to the intended address before, it seems that the used address is not correct.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FBHKSGDWpdo7PPYitc2el%2Fimage.png?alt=media&amp;token=9079fae3-8a3a-49ac-80be-44ab5bd3e2f8" alt="" width="375"><figcaption></figcaption></figure>

### Recently used addresses

When initiating a new send, the "address entry" step also shows a list of used addresses for recent send transactions. For each address, it shows you the contact name if it's stored with a contact, the tokens and amounts you recently sent to that address, and the date of the last transaction.

This allows you to verify an entered address is correct, or even lets you directly select one of these addresses.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FgZJc8OgzEMtyMZm2F3kT%2Fimage.png?alt=media&amp;token=da045653-ae7c-4745-ac28-cf789a5094f8" alt="" width="375"><figcaption></figcaption></figure>

### Not loading data from unknown sources

{% hint style="success" icon="user-shield" %}
OISY does not load data or images from unverified sources.
{% endhint %}

This means it does not even load icons for tokens you imported manually. This might sound strict, but loading an icon from an external source informs the provider of this source about you accessing the image, including your 'address' on the internet. This would allow a bad actor to track your schedule, or even worse, try to attack your computer directly.

For NFTs, where the linked media file often it the main 'value', you can explicitely approve to load this data from it source.

And under no circumstances, OISY is loading embedded executable code, like it's done for some NFTs, into your wallet.

### Only showing the tokens you really want to see

OISY only shows fungible tokens you want to work with. If you get sent spam tokens, OISY does not load them automatically.

There is the exception for NFTs, which are imported automatically if you receive one. But you have the means to mark them as spam, and they will get removed from your active list.

### Securely connect OISY to other applications

OISY supports the so called "Signer Standard", the recommended way to connect wallets to applications on the ICP blockchain.

{% hint style="success" icon="user-shield" %}
OISY only allows dApps to connect in a mode, where **each transaction that affects your assets has to be confirmed by you** via a confirmation dialog that is shown inside OISY.

This means you can safely connect to a dApp without risking your assets.
{% endhint %}

This means that every transaction that the application tries to initiate and that would transfer out funds from your wallet will pop up OISY showing a confirmation window, and it's not possible for the application to execute this transfer without your consent.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FyNUOt6woM0WEBTK8mdD0%2Fimage.png?alt=media&amp;token=c4adb0f1-76a6-48ae-b71e-9cd1ac5cdfd0" alt="" width="315"><figcaption></figcaption></figure>

## Best practices when using a crypto wallet

### Always verify the recipient address of a transaction!

{% hint style="danger" icon="fire" %}
**ALWAYS verify the transaction before you send, especially the recipient address. ALWAYS!**
{% endhint %}

The OISY team went through great length to provide a concise **Review page** before you can execute a send transaction. Take a few seconds to have a last look at

* the **token**
* the **network**
* the **amount**
* the **value** in your selected currency
* and the destination **address**

{% hint style="success" icon="user-shield" %}
We recommend to save often used addresses in a **Contact**. This way the review page of a new send transaction will 'resolve' the address and display the contact name as an additional confirmation that you have entered the right address.
{% endhint %}

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FDqzaIOf60i6szz6kILwM%2Fimage.png?alt=media&amp;token=8e939707-fe21-4718-a98b-829a6a9fee3c" alt="" width="375"><figcaption></figcaption></figure>


# What's New

This page describes each OISY release and their included new features, improvements, or fixes.

## v2.5.6

Release date: September 10, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.5.6>

{% hint style="success" icon="circle-plus" %}
**New Features**

* **BTC** can now be **swapped** from/to all our supported chains via NEAR Intents.
* **EVM** send transactions now allow to speficy the **priority fee** (slow, standard, fast).
  * Also for send requests through **WalletConnect!**
* **Chain Fusion** is now integrated as **swap provider**. You can now convert BTC to ckBTC directly via the normal swap flow.
* **OISY Trade** is also added as **swap provider**. For each active order book on it, OISY now also calculates a swap offer, and executes it as fill-or-kill (FOK) limit order on OISY Trade.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* **WalletConnect** requests on the **Solana** network now get simulated and show the balance changes and all contained instructions.
* **WalletConnect** requests on **EVM** networks now also contain more information about their content.
* **Solana** transactions on the **transaction history** are now shown aggregated per affected token, with an **improved summary text** if the transaction can be identified as send or swap.
* **Solana transaction details** now show more information about the transaction, including all balance changes and all contained operations.
* **Velora**, **NEAR Intents**, **Chain Fusion**, and **OISY Trade** swaps now also show in the list of **active transactions** until they are completed.
* We improved the **send flow for EVM tokens** and don't refresh the fee on the review step anymore, but the fee amount to be used will expire after one minute.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed a bug where the AI Assistant didn't include the deposited amount on OISY Trade when asking for the total balance.
  {% endhint %}

{% hint style="info" icon="book" %}
**Content**

* Added support for **ckBAT** (and its native BAT token twins), including chain fusion from/to Ethereum.
  {% endhint %}

## v2.5.5

Release date: September 1, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.5.5>

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed a bug that caused loading the BTC balance to fail when the ckBTC minter was not available.
  {% endhint %}

## v2.5.4

Release date: August 18, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.5.4>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Bitcoin is now also supported through WalletConnect.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* We optimized the memory consumption and fixed also a few issues that caused large memory spikes.
* Improved how the warning about unavailable index canisters of icrc tokens are displayed.
* Improved the display of erx-20 transactions.
* Improved how gas costs of erc-20 transactions are displayed.
* Clean up the assets page to make it lighter and more reasable.
  {% endhint %}

## v2.5.3

Release date: July 30, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.5.3>

{% hint style="warning" icon="heart" %}
**Improvements**

* Consistently renamed NFT to Collectible.
* Placed the grouping option for collectibles more prominently below the page hero.
* Placed the feature to check for new collectibles more prominently into the hero.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed a bug that could cause the Manage tokens modal to fail rendering available tokens.
  {% endhint %}

## v2.5.2

Release date: July 23, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.5.2>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Added **ICP** and **ckBTC**, **ckUSDC**, and **ckUSDT** to the options to supply/borrow from **Liquidium**.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* The **Universal Scanner** now also identifies **WalletConnect deep links** (that include the OISY domain) and initiates the connect flow directly.
* Added support to **sign messages** on the **Solana** network through **WalletConnect**, allowing OISY to connect to all Solana dapps that require message signing to sign in.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* The supply modal for BTC on Liquidium now correctly shows the confirmed BTC amount only.
  {% endhint %}

{% hint style="info" icon="book" %}
**Content**

* Added USD1 (World Liberty Financial USD) on Ethreum, BNB, and Solana.
  {% endhint %}

## v2.5.1

Release date: July 10, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.5.1>

{% hint style="warning" icon="heart" %}
**Improvements**

* We translated our deposit and withdraw forms on OISY Trade into all supported languages.
* We removed the consent checkbox for deposits ton OISY Trade.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* The token picker for the "sell" side of a limit order now correctly shows the deposited and free amount instead of the amount in the wallet.
  {% endhint %}

## v2.5.0

Release date: July 9, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.5.0>

{% hint style="success" icon="circle-plus" %}
**New Features**

* **OISY Earn welcomes Liquidium:** Borrow and lend Bitcoin, Ethereum, ICP and USDT directly from your OISY Wallet. True DeFi lending without centralized bridges.
* **OISY Notes:** Store your private notes with the same level of confidence as your digital assets. Encrypted and only readable by you (thanks to vetKeys). Share notes with links that expire after a single view.
* **OISY Trade limit orders:** Buy and sell your digital assets at prices you decide. Set your target price and let the order fill itself when it the price target hits. Live for ICP and ckUSDT, with more pairs coming.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* We **overhauled the navigation bar** both on desktop and on mobile devices, to now show more options direct from the menu. The mobile nav bar now uses popup submenus to offer multiple options for a category.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fix a bug that could cause a "Gas fee not defined" error after the app went into the backgroup on mobile devices.
  {% endhint %}

## v2.1.2

Release date: June 30, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.1.2>

{% hint style="warning" icon="heart" %}
**Improvements**

* Allow multiple open WalletConnect connections, and allow to close them individually.
* Improved the NFT image loading process to use the collection contract directly as fallback for the metadata, if we don't get them otherwise.
* Improved the activity list to now show swap transaction that are contained in a single transaction to show the send and the receive parts in the 'expected' chronological order.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

*
* Fixed a bug that caused some native coin swaps (ETH, BNB, POL) to fail when routing through the Velora API.
  {% endhint %}

## v2.1.1

Release date: June 17, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.1.1>

{% hint style="warning" icon="heart" %}
**Improvements**

* Language and Currency settings were moved from the user menu to the settings page.
* 1Sec conversions will now execute in the background after the transaction is successfully submitted. A new list of active and finished transactions helps the user to keep track of them.
* Sending an NFT now shows the available NFTs in the same order the user has specified in the main NFT list.
* Allow to filter NFTs and tokens also by their token standard
  {% endhint %}

## v2.1.0

Release date: June 1, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.1.0>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Support for **NFT** collections from the **ICRC-7** standard.
* A new **export feature** allows users to export their token balance or transaction list into a CSV text file:   [Exporting Tokens and Transactions](/using-oisy-wallet/how-tos/exporting-tokens-and-transactions)
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* The main token list can now also be filtered by the address of the token contract.
* BTC transaction details now also show the provided fee amount.
* OISY Scan now also allows to initiate a send transaction when scanning an ICP principal, a bitcoin address or a solana address. (EVM to come next)
* When a swap fails with a generic error coming from the provider side, OISY now shows an information element on the swap review page.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed a bug where the OISY scanner went into inactive mode on mobiles after scanning an unsupported QR code.
* Fixed an issue where Velora swaps showed no active state for the first few seconds of the swap.
* Fixed a bug where some error toasts were shown behind the blur layer when a modal is open.
  {% endhint %}

## v2.0.9

Release date: May 22, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.9>

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Upgrading to oisy-wallet-signer v6 to resolve sdk incompatibility issues.
  {% endhint %}

## v2.0.8

Release date: May 13, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.8>

{% hint style="success" icon="circle-plus" %}
**New Features**

* We added a **Transaction filter** that allows users to filter the list of all transactions by token, transaction type, or contact.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* Improved the UTXO selection algorithm when sending Bitcoin. We now select UTXOs to minimize the transaction costs, while also trying to lock as little BTC as possible.
* We also improved the Bitcoin sending process by allowing multiple simultaneous sends, by verifying the confirmation status of all UTXOs before composing a next transaction.
* <i class="fa-shield-check" style="color:green;">:shield-check:</i> **OISY protects you!** We now show a confirmation box if we can't get both token prices for a swap and can't display the value difference between the paid and the received amount.
* We improved the Swap form to recalculate the possible receive tokens after the user selected the token to pay.
  {% endhint %}

{% hint style="info" icon="book" %}
**Content**

* Added the new NNS Governance app to the App Explorer.
  {% endhint %}

## v2.0.7

Release date: May 8, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.7>

{% hint style="info" icon="book" %}
**Content**

* Support for **USDC.e** token (USD Coin Bridged) on Arbitrum and Polygon
  {% endhint %}

## v2.0.6

Release date: May 4, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.6>

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed an issue where swaps from IC tokens was not properly filtering the allowed target networks.
  {% endhint %}

## v2.0.5

Release date: May 4, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.5>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Integration with [**1sec.to**](https://1sec.to) to offer in-wallet bridging from Internet Computer to Ethereum, Base or Arbitrum for ICP, USDC, USDT, cbBTC, CHAT, GLDT, and BOB.
  {% endhint %}

## v2.0.4

Release date: April 28, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.4>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Users can now **sign up or in** very quickly with their **Google**, **Apple**, or **Microsoft** accounts.
* Newly designed **landing page.**
* A new **filter for small transactions** now hides spam transactions from the user's Activity list.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* Improved the sorting of networks. Except for the first 3 fixed networks Bitcoin, Ethereum and ICP, the additional ones are sorted alphabetically consistently throughout the application
* Improved the default sorting for tokens. All native coins (ETH, BNB, POL, SOL) now appear first in the list, before all the 'regular' tokens.
  {% endhint %}

## v2.0.3

Release date: April 17, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.3>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Added an improved QR Code **scanner** to OISY, which allows to pay with OISY Pay, establish WalletConnect connections, or scan network addresses during a send transaction.
* Clicking the **WalletConnect connection indicator** does not disconnect the connection directly, but opens a modal that shows a list of open connections, and allows to user disconnect a specific one.
* **NFT** and **NFT Collection pages** now have a **close button** that allow a quick return to the page the user came from.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* **ICP transactions** that contain the account of a counterparty instead of a principal can still find the matching contact if it has only stored the principal.&#x20;
* The **WalletConnect connection indicator** is now only shown when a connection is active.
* **Inactive tokens** get automatically **activated** after a user **swapped** into them.
* The **warning** about ICRC tokens that don't have an index canister is now **only shown once per token**. Once the user confirmed this, it's not shown again.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed an issue where **swappable Solana tokens** did not show the **Swap button** in their token view.
  {% endhint %}

## v2.0.2

Release date: April 10, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.2>

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed a bug where the application name in the web manifest was not resolved during the build and remained `{{OISY_NAME}}` , which was then used as app name when installed as PWA on Android.
  {% endhint %}

## v2.0.1

Release date: April 10, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.1>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Enable to download OISY as **PWA** on mobile phones and desktops.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* Temporarily removed the Harvest Autopilot vault for Ethereum USDC.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed the calculation of the "swappable" vs. "convertable" assets in the Earn section.
  {% endhint %}

{% hint style="info" icon="book" %}
**Content**

* Added "Where in the World is Motoko Tokyo" to the app explorer.
  {% endhint %}

## v2.0.0

Release date: April 9, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v2.0.0>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Added a new **Earn** section, which allows to see a list of all available earn opportunities in OISY.
* Integrated **Harvest Autopilot** **Vaults** as new earn opportunity, and allow users to stake or unstake from them.
* Integration with the **NEAR Intents** protocol, allowing to swap tokens across multiple networks.
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* Move the help menu into the user menu to get more space available on the header row.
* Keep the text based token filter when switching between Tokens, NFTs and Earning.
* Use ICPSwap as fallback price source if we don't get a price for an icrc token.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed a bug that caused some icrc tokens to fail loading the latest balance.
  {% endhint %}

## v1.9.15

Release date: April 1, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v1.9.15>

{% hint style="success" icon="circle-plus" %}
**New Features**

* Swap offers that have a value difference larger than -5% now show a confirmation info box on the review page, and the user must check it before the swap can be executed.
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed a bug where a user could get automatically logged-out when using OISY in multiple browser tabs simultaneously.
  {% endhint %}

## v1.9.14

Release date: March 30, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v1.9.14>

{% hint style="warning" icon="heart" %}
**Improvements**

* Enable ckUSDC minting and burning
  {% endhint %}

## v1.9.13

Release date: March 27, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v1.9.13>

{% hint style="warning" icon="heart" %}
**Improvements**

* Improved the hero image for VEUR
* Removed KongSwap as swap provider and from the app explorer
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed some lists where the scrollbars were not properly displayed anymore
* Fixed an issue where token performance indicators were not correctly shown on Android phones
  {% endhint %}

## v1.9.12

Release date: March 26, 2026\
Change log: <https://github.com/dfinity/oisy-wallet/releases/tag/v1.9.12>

{% hint style="success" icon="circle-plus" %}
**New Features**

* OISY PAY now also support additional ICRC tokens, like ckBTC, VCHF and VEUR
* Users can filter fungible tokens by their asset type: Crypto, Stablecoin, Stock, or Commodity
  {% endhint %}

{% hint style="warning" icon="heart" %}
**Improvements**

* Temporarily disable converting ckUSDC from/to USDC and show an info banner
* Allow scrolling in lists when a toast is shown
* Improved the scanner to successfully scan borderless QR codes in dark mode
  {% endhint %}

{% hint style="danger" icon="screwdriver-wrench" %}
**Fixes**

* Fixed a but where a transaction execution modal could not be closed after a successful execution
  {% endhint %}


# How To's

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FsDiyXX9q4H95MZtXhMzR%2FHow%20to.jpg?alt=media&amp;token=b8023441-a5f1-4c5e-9f25-2f014833d8b7" alt=""><figcaption></figcaption></figure>

Jump to any How To you need. If you need a new How To, just hop into [our discord](https://discord.com/invite/ejBT7dQneK.) and request it.

### Onboarding

{% content-ref url="/pages/FbhivGasHFMN4ljN6QnK" %}
[Creating a Wallet](/using-oisy-wallet/how-tos/creating-a-wallet)
{% endcontent-ref %}

{% content-ref url="/pages/E5kCCrpieLTPIYnXVow4" %}
[Logging Into OISY](/using-oisy-wallet/how-tos/logging-into-oisy)
{% endcontent-ref %}

{% content-ref url="/pages/d12EiHzqGhT2ohaaLlfQ" %}
[Create an Internet Identity](/using-oisy-wallet/how-tos/create-an-internet-identity)
{% endcontent-ref %}

{% content-ref url="/pages/UWqhw43msXpucUrg0LBI" %}
[Find Your Internet Identity number](/using-oisy-wallet/how-tos/find-your-internet-identity-number)
{% endcontent-ref %}

### Using OISY Wallet

{% content-ref url="/pages/OKEYznsoxP4ptQTcNKHz" %}
[Sending Tokens](/using-oisy-wallet/how-tos/sending-tokens)
{% endcontent-ref %}

{% content-ref url="/pages/JNnI7lLmmgp5TQDzhyU9" %}
[Receiving Tokens](/using-oisy-wallet/how-tos/receiving-tokens)
{% endcontent-ref %}

{% content-ref url="/pages/LYC81N5Z2BjX4O8ADiJo" %}
[Managing & Adding Tokens](/using-oisy-wallet/how-tos/managing-and-adding-tokens)
{% endcontent-ref %}

{% content-ref url="/pages/HnmPebGJORVrlsmoxwPU" %}
[Swapping Tokens](/using-oisy-wallet/how-tos/swapping-tokens)
{% endcontent-ref %}

{% content-ref url="/pages/cbOvGxorNrxb9wu0BjQW" %}
[Connecting to dApps](/using-oisy-wallet/how-tos/connecting-to-dapps)
{% endcontent-ref %}

#### Hints

{% content-ref url="/pages/67acaPYLnF80VYhRAlKF" %}
[Saving OISY Web App to Your Device](/using-oisy-wallet/how-tos/saving-oisy-web-app-to-your-device)
{% endcontent-ref %}

### Help & Community

{% content-ref url="/pages/PRwHExOT1FnJBDt4XTjU" %}
[Join the Tester Program](/using-oisy-wallet/how-tos/join-the-tester-program)
{% endcontent-ref %}

{% content-ref url="/pages/v4KtJcrXMLD7P8rNqlbw" %}
[Raise a Support Ticket](/using-oisy-wallet/how-tos/raise-a-support-ticket)
{% endcontent-ref %}

{% content-ref url="/pages/93pEK8EiwYq7PWXI74x7" %}
[Submit Feedback](/using-oisy-wallet/how-tos/submit-feedback)
{% endcontent-ref %}


# Creating a Wallet

{% hint style="info" %}
OISY uses [Internet Identity](/introduction/internet-identity) to identify and authenticate users. This means that OISY does not store any login related information itself, and the entire sign-up and login process is handled by Internet Identity. Conceptually this is similar like logging in to a website using your LinkedIn or Google account, with the distinction that Internet Identity does not track what application is used by a user, and individual applications can not identify a user on a different application, because the same Identity will 'look' different for each application.

If you already have an Identity (e.g. by signing up to another dapp on the Internet Computer via Internet Identity, e.g. caffeine.ai, you can use the same Identity to also log in to OISY, and you will have your wallet ready.

And If you have to create a new Identity first, you can then use this Identity to log in to all applications on the Internet Computer that support Internet Identity.
{% endhint %}

OISY Wallet is a fully on-chain, browser-based, multi-chain crypto wallet designed for seamless access to decentralized finance. Unlike traditional wallets that require browser extensions or downloads, OISY operates directly from your web browser, allowing for secure, passkey-enabled sign-ins with no reliance on third-party servers.

To create an OISY Wallet:

1. Navigate to [OISY.com](https://oisy.com).
2. Click “Open or Create” to begin the setup process.
3. On the Choose Identity screen, select “More Options".
4. Enter your Internet Identity or select “Create New” if you do not yet have one.
5. Follow the Internet Identity setup process:

* Click “Create Passkey” and choose whether to create your passkey on your current device or another device.
* Complete the CAPTCHA verification.
* Your Internet Identity number will be displayed—this is your unique identifier for accessing OISY Wallet. Save it in a secure location.

6. Once verified, your OISY Wallet will be generated and you will be redirected to the main wallet interface.

OISY Wallet is fully on-chain and powered by threshold ECDSA cryptography, ensuring secure key management across dedicated ICP nodes.


# Create a Wallet

This page describes how to create a new OISY wallet.

{% hint style="danger" %}
**This content is outdated not correct anymore.**
{% endhint %}

OISY Wallet is a fully on-chain, browser-based, multi-chain crypto wallet designed for seamless access to decentralized finance. Unlike traditional wallets that require browser extensions or downloads, OISY operates directly from your web browser, allowing for secure, passkey-enabled sign-ins with no reliance on third-party servers.

To create an OISY Wallet:

1. Navigate to [OISY.com](https://oisy.com).
2. Click “Open or Create” to begin the setup process.
3. On the Choose Identity screen, select “More Options".
4. Enter your Internet Identity or select “Create New” if you do not yet have one.
5. Follow the Internet Identity setup process:

* Click “Create Passkey” and choose whether to create your passkey on your current device or another device.
* Complete the CAPTCHA verification.
* Your Internet Identity number will be displayed—this is your unique identifier for accessing OISY Wallet. Save it in a secure location.

6. Once verified, your OISY Wallet will be generated and you will be redirected to the main wallet interface.

OISY Wallet is fully on-chain and powered by threshold ECDSA cryptography, ensuring secure key management across dedicated ICP nodes.


# Create an Internet Identity

Setting up your [Internet Identity](/introduction/internet-identity) is quick and secure. Follow these steps to get started:

1. Go to [OISY.com](https://OISY.com).
2. Press “Open or Create”
3. Choose the method you want to use to log in.\
   You can either use an existing account on Google, Apple, or Microsoft to authenticate yourself, or you can choose to continue with a passkey.

## Create an Identity using a Passkey

{% hint style="info" %}
Also see [Create an Internet Identity 2.0 using a Passkey](https://identitysupport.dfinity.org/hc/en-us/articles/39743852326420-How-do-I-create-an-Internet-Identity-2-0-using-a-Passkey)
{% endhint %}

4. Select “Create new identity”
5. Choose your passkey security method (e.g., Face ID, fingerprint, or security key)
6. Complete the passkey setup flow
7. You’ll be redirected to OISY Wallet, where your wallet will load automatically

## Create an Identity using a social login provider

{% hint style="info" %}
Also see [Create an Internet Identity 2.0 using my Google account](https://identitysupport.dfinity.org/hc/en-us/articles/39744877389844-How-do-I-create-an-Internet-Identity-2-0-using-my-Google-account)
{% endhint %}

4. Select your preferred provider and log in with that provider
5. Confirm the new Identity
6. You’ll be redirected to OISY Wallet, where your wallet will load automatically

## Read more

{% hint style="info" %}

## **Read more**

* **OISY Documentation**
  * [Internet Identity](/introduction/internet-identity)
  * [OISY Wallet switches to Internet Identity 2.0](/using-oisy-wallet/support/oisy-wallet-switches-to-internet-identity-2.0)
* **Internet Identity Help Center**
  * [Internet Identity Help Center](https://identitysupport.dfinity.org/hc)
  * [Internet Identity 2.0 : Basics](https://identitysupport.dfinity.org/hc/articles/39593373981588-Internet-Identity-2-0)
  * [Internet Identity 2.0 : Upgrade FAQ](https://identitysupport.dfinity.org/hc/articles/40276570234132-Internet-Identity-Upgrade-FAQ)
    {% endhint %}

📌 Once completed, you’ll have seamless access to OISY and other ICP services.


# Find Your Internet Identity number

This page describes how you can find an Internet Identity number that you previously used to sign in to OISY on the same device and browser.

If you forgot your Internet Identity number, you can find it using any of the following methods:

* Review the list of identity numbers you’ve previously used at Legacy URLs, ensuring you use the same device and browser:
  * [https://identity.internetcomputer.org](https://identity.internetcomputer.org/).
  * [https://identity.ic0.app](https://identity.ic0.app/)
  * **Important:** This will not work once Legacy Identity has been sunsetted, currently slated for January 26th, 2026.
* Look at the number at the beginning of a recovery phrase you may have saved earlier.

💡 *Tip: If your Internet Identity still doesn’t show up in the new modal, re-check that you’re using the correct device and browser used during registration.*

If you encounter any issues, reach out via our [support ticket system](/using-oisy-wallet/how-tos/raise-a-support-ticket)—we’re happy to help.<br>


# Logging Into OISY

{% hint style="info" %}
**OISY recently switched from version 1.0 of Internet Identity to version 2.0.**

Please check [OISY Wallet switches to Internet Identity 2.0](/using-oisy-wallet/support/oisy-wallet-switches-to-internet-identity-2.0) for detailed information about this switch, and check the additional links in the [#read-more](#read-more "mention") box at the bottom of the page.
{% endhint %}

Since OISY Wallet is browser-based, you can log in seamlessly without requiring a password. Instead, it leverages Internet Identity authentication, allowing you to use biometrics (FaceID, TouchID) or a security key.

To log in

1. Go to [OISY.com](https://oisy.com).

2. Click “**Open or Create**”

   <div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FloEORYgFSnMSxLv4pZiK%2Fimage.png?alt=media&amp;token=f08dabb8-dde8-447b-ab7d-58b35be4eab7" alt="" width="276"><figcaption></figcaption></figure></div>

3. On the **Choose method** screen, select if you want to continue with a passkey or with a social login provider.

   <div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fbzl7u0IZHLFW80eBo13w%2Fimage.png?alt=media&amp;token=9b16bfed-9711-4790-a612-8ce267d6b00b" alt="" width="188"><figcaption></figcaption></figure></div>

4. On the "**Sign in**" screen, ensure you see the correct Identity on top right, and click "**Continue**"

   <div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F0LT7R4Z3vw6ERQuTa6Hu%2Fimage.png?alt=media&amp;token=32cb9093-6cf6-480d-81a3-110966b865fe" alt="" width="188"><figcaption></figcaption></figure></div>

   1. You can change the Identity you want to use via the selector on top right.<br>

5. Click "Continue" and complete the sign-in verification using your preferred method (FaceID, TouchID, or security key).

{% hint style="info" %}

## **Read more**

* **OISY Documentation**
  * [Internet Identity](/introduction/internet-identity)
  * [OISY Wallet switches to Internet Identity 2.0](/using-oisy-wallet/support/oisy-wallet-switches-to-internet-identity-2.0)
* **Internet Identity Help Center**
  * [Internet Identity Help Center](https://identitysupport.dfinity.org/hc)
  * [Internet Identity 2.0 : Basics](https://identitysupport.dfinity.org/hc/articles/39593373981588-Internet-Identity-2-0)
  * [Internet Identity 2.0 : Upgrade FAQ](https://identitysupport.dfinity.org/hc/articles/40276570234132-Internet-Identity-Upgrade-FAQ)
    {% endhint %}

OISY Wallet offers cross-device access without the need for extensions, ensuring a frictionless experience across desktop and mobile browsers.


# Locking and Logging Out

While using OISY, some data like your token list or your public addresses are stored in the browser cache. Note that this cache is only accessible to the current user account on the used computer.

{% hint style="warning" %}
Note that the cached data **does not contain any private keys that someone could use to access your funds**. OISY's chain-key technology allows it to operate without having any private keys on the device you are using it on.
{% endhint %}

Once you are finished using OISY, you can end your session in two ways:

1. **Logging out**
2. **Locking**

The User Menu in the top right corner of OISY offers those 2 options:

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FTR2pdqorrJ3gFXoRc47F%2Fimage.png?alt=media&amp;token=85ec5bfa-a4d9-4206-88f4-3f7c03c3bb03" alt="" width="375"><figcaption></figcaption></figure></div>

## Logging out

Logging out **ends your valid session** and **clears your locally cached data**. This is the safest way and recommended when you use shared devices.

## Locking

Locking your OISY Wallet will also **end you valid session**, but will **keep the cached data**, so when you unlock your account, you can continue right where you left much faster.

After you locked your wallet, you will land on a lock page, which allows you to unlock (log back in), or fully log out, which then also clears all cached data.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fpexd7eN1UrH8kPqGXBX3%2Fimage.png?alt=media&amp;token=dd3ab8d2-4bda-4267-986c-7b12a3293eb7" alt=""><figcaption></figcaption></figure>


# Sending Tokens

OISY Wallet supports seamless token transfers with zero reliance on centralized intermediaries.

To send tokens:

1. Open your wallet and select the token you wish to send.
2. Click the “Send” button.
3. Enter the recipient’s wallet address or scan their QR code.
4. Specify the amount you wish to send (or select “Max” to transfer all available tokens).
5. Review the transaction details, including network fees.
6. Confirm and submit the transaction.<br>

Transactions are executed using threshold ECDSA cryptographic signatures, ensuring decentralized, verifiable security.


# Receiving Tokens

To receive tokens into your OISY Wallet:

1. Open your wallet and select the token you wish to receive.
2. Click the “Receive” button.
3. &#x20;Your wallet address will be displayed—copy the address or scan the provided QR code.
4. Share this address with the sender to receive tokens.<br>

OISY Wallet’s on-chain architecture ensures full transparency in all transactions.


# Swapping Tokens

## Overview

OISY Wallet features a built-in decentralized swap function, allowing users to exchange assets directly within the wallet.

To swap tokens:

1. Click the “Swap” button below your available balance.
2. Select the tokens you wish to swap in the “You Pay” and “You Receive” dropdown menus.
3. Enter the amount for the swap.
   1. The "You receive" field now also shows the expected amount of tokens and their value in your currency.
   2. Additionally, it also shows the difference in value between the amount sent and the amount expected to receive. Often this value is slightly lower, because a swap involves some transactions to be executed, and some fee for the provider of the liquid assets required.
4. Adjust or confirm the Max Slippage Rate (if applicable).
5. Change the suggested swap provider if desired.\
   \****Note**: OISY always suggests the provider with the highest receive amount.*
6. Click “Review Swap” to verify transaction details.
7. If all values are correct, click “Swap Now” to execute the swap transaction.

Swaps are executed through on-chain liquidity pools, ensuring full decentralization and provable fairness.<br>

***

## Convert assets from/to the ICP Network

The Internet Computer network ICP allows to bridge the most widely used tokens in or out of its network. Once on the ICP network, transactions are much faster and cheaper.

{% hint style="success" icon="brain" %}
**Learn more here:** <https://docs.internetcomputer.org/defi/chain-key-tokens/overview>
{% endhint %}

Supported are currently BTC, and these tokens on the Ethereum network: ETH, USDC, USDT, EURC, XAUT, UNI, PEPE, LINK and a few more.

{% hint style="info" %}
The token on the ICP network can be identified by a **`ck`** (for "chain-key") in front of its symbol.

![](https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FjeDFo986HXMTsYyYpU7c%2Fimage.png?alt=media\&token=b2d1f654-9543-42be-be4e-ecee0019d4d1)
{% endhint %}

#### Convert into the ICP Network

1. Select the token you want to convert, and open its token view
2. Click the convert button in the hero of the page\
   ![](https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F12wEKLQTSDy3D1zLk0Xt%2Fimage.png?alt=media\&token=bf340933-017b-4e14-a9cf-4facf4e9f9f6)<br>
3. Specify the amount to be converted, review the transaction and execute it.\
   ![](https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FkDyluzPDcHSO0czkIQnA%2Fimage.png?alt=media\&token=3e3547e3-1c97-4760-98fd-d5ced75f8b9c)<br>
4. The conversion will now start and you will receive the token on the ICP network.

{% hint style="warning" %}
**Note**: Based on the source network (Bitcoin, Ethereum), the conversion can take several minutes (Ethereum) and up to 20 minutes (Bitcoin) to be completed. This is due to the time it takes to have a transaction confirmed on those networks.
{% endhint %}

#### Convert out of the ICP Network

Converting out of the ICP network works the same way like converting in.

1. Select the ck token and open its token view
2. Click the convert button
3. Specify the amount, review, and execute.

## Manually withdraw Funds from ICPSwap

{% hint style="info" %}
When using ICPSwap as swap provider, there is a very small chance that in case the swap fails, the funds can not get automatically withdrawn by OISY and must be withdrawn manually via their web app.\
Note that usually when a swap fails, OISY automatically withdraws the funds sent for the swap back into your wallet.

The section below describes how a user can manually withdraw them anytime later.
{% endhint %}

{% hint style="success" %}
Note that these funds are always under your control and can always be accessed on ICPSwap anytime later by connecting OISY.
{% endhint %}

### Swap failed and the fund could not be withdrawn

When the swap failed and the funds could not get withdrawn, the swap review modal will show this message:

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FLOhsYaalcAbUir8Dp5L1%2Fimage.png?alt=media&amp;token=d71a8137-bf2c-4519-a428-8dae1bece7ec" alt=""><figcaption></figcaption></figure>

### Go to the ICPSwap website

Clicking the link to ICPSwap brings you to their website. Or you can access the website directly: <https://app.icpswap.com/swap>

**Note: It's important that the same swap "Pair" (e.g ICP and PANDA) is selected on their website.** Otherwise the blocked tokens are not visible. Using the provided link at the end of the message in OISY selects this pair automatically.

Their website should now look something like this

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FIkMLLItG0K6iZRIZVBWU%2Fimage.png?alt=media&amp;token=e5a47956-4bfd-4128-a2f9-48ec49fa2e3f" alt=""><figcaption></figcaption></figure>

### Connect OISY

Now you have to [connect your OISY wallet](/using-oisy-wallet/how-tos/connecting-to-dapps) to the website, in order to have access to your funds that are still 'parked' on ICPSwap.

Click the "Connect wallet" on top right and select OISY Wallet in the wallet selection.

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FEbc3us1AhvgKtaGDkszz%2Fimage.png?alt=media&amp;token=6632fe2a-8b62-4ff3-b6a1-a3c5fc1c8729" alt="" width="375"><figcaption></figcaption></figure></div>

A confirmation popup will show (ensure that you allow popups from the ICPSwap website) where you have to confirm that the website is allowed see your wallet's address:

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FcPLNQ9xtHaaTuJqYwuqw%2Fimage.png?alt=media&amp;token=03e25d54-21f8-4de0-96e6-e4690a8e2aea" alt="" width="264"><figcaption></figcaption></figure></div>

After the confirmation, the site will show as connected (see top right), and you can see the amount you sent for the swap on the main form together with a "Withdraw" option:

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fy5BryrwMQTcWcbzHelw6%2Fimage.png?alt=media&amp;token=ce28b438-8c43-42ce-b20c-e4efc026bf00" alt=""><figcaption></figcaption></figure>

### Withdraw the assets

Clicking the "Withdraw" will show a confirmation dialog.

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FGAmszo91Mm0CNPN8cxQg%2Fimage.png?alt=media&amp;token=d5514c6e-45a2-48e4-b989-d914ddc20858" alt="" width="264"><figcaption></figcaption></figure></div>

Approving it will then send those tokens back to your wallet and show a confirmation in ICPSwap

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FKzpRUhO8D5gEjFnT6gaE%2Fimage.png?alt=media&amp;token=b3228016-9346-4762-9d43-7e3e5abb6af6" alt=""><figcaption></figcaption></figure>


# Universal Scanner

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fl7Ti1szeit7rXHUJKyXo%2Fimage.png?alt=media&amp;token=e4e0fbef-e278-44dd-b03a-16f16e44a5d6" alt=""><figcaption></figcaption></figure>

The scanner in OISY lets you scan various types of QR codes, and it will then initiate the correct action for the type of QR code.\
Alternatively, it also allows you to paste a code manually and then also initiate the intended action.

{% hint style="info" icon="fire" %}
The new scanner replaces the individual ones used for OISY PAY, WalletConnect, send transactions, or contact address scanning.

You now have one scanner that does it all: **ONE TO RULE THEM ALL**
{% endhint %}

To star the scanner, just press the new scanner button in the menu bar: <img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FPZlTR1wGBeTJiqbb3Pv9%2Fscan.png?alt=media&amp;token=7f3c65c4-e0df-4b0a-97ab-ab5f14ca7862" alt="" data-size="line">

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F2HQhC5OSmKhCzhiijZap%2Fimage.png?alt=media&amp;token=896d7b7a-00bb-49d3-b8f7-9101b6cdf85b" alt=""><figcaption></figcaption></figure>

## WalletConnect

This works 100% as before: Open the scanner and scan or paste the connect code.

## OISY Pay

Same here. Simply open the scanner and scan the QR code at the register.\
Read more about [OISY Pay](/using-oisy-wallet/oisy-pay)

## Send Flow

The send flow also works as before. The field where you can enter the destination address shows the scanner symbol, which then allows to open the scanner to directly scan the destination address.

## Contacts Addresses

Open a contact, click the plus to add a new address, and press the scanner icon to scan the address instead of typing it in manually.


# Saving OISY Web App to Your Device

## Adding OISY to your Phone

### iOS (Safari)

1\. Open Safari on your iPhone or iPad.

2\. Navigate to [OISY.com](https://OISY.com).

3\. Tap the Share icon (square with an upward arrow) at the bottom center of the screen.

4\. Scroll down and select ‘Add to Home Screen’.

5\. A prompt will appear to name the app (default: OISY Wallet). You can keep or customize it.

6\. Tap ‘Add’—the OISY Wallet icon will now appear on your home screen.

***

### iOS (Firefox)

1\. Open Firefox on your iPhone or iPad.

2\. Navigate to [OISY.com](https://OISY.com).

3\. Tap the three lines in the bottom right corner.

4\. Select ‘Share’ from the menu.

5\. Tap ‘Add to Home Screen’.

6\. Confirm or modify the default app name (OISY Wallet).

7\. Tap ‘Add’—the OISY Wallet shortcut will now be available on your home screen.

***

### Android (Chrome)

1\. Open Chrome on your Android device.

2\. Navigate to [OISY.com](https://OISY.com).

3\. Tap the three-dot menu in the top right corner of the screen.

4\. Select ‘Add to Home screen’.

5\. A prompt will appear to confirm installation—tap ‘Install’.

6\. The OISY Wallet icon will now appear on your home screen.

***

### Android (Brave)

1\. Open Chrome on your Android device.

2\. Navigate to [OISY.com](https://OISY.com).

3\. Tap the three-dot menu in the bottom right corner of the screen.

4\. Select ‘Add to Home screen’.

5\. A prompt will appear to confirm installation—tap ‘Install’.

6\. The OISY Wallet icon will now appear on your home screen.

***

### Android (Firefox)

1\. Open Firefox on your Android device.

2\. Navigate to [OISY.com](https://OISY.com).

3\. Tap the three-dot menu in the bottom right corner.

4\. Select ‘Install’.

5\. When prompted with ‘Add to Home Screen’, tap ‘Add’.

6\. The OISY Wallet shortcut will now appear on your home screen.

***

## Adding OISY to your Desktop

### Apple (Safari)

1. Open ‘Safari’ browser
2. Navigate to [OISY.com](https://OISY.com)
3. Press the Share button in the top right corner of the window
4. Select ‘Add to Dock’
5. Adjust the Icon, Name, and URL as you wish
6. Press ‘Add’
7. You can now go to  your dock and move the ‘app’ where you’d prefer

***

### Having issues with Web App?

As we continue to optimise OISY for the mobile environment sometimes you'll run into issues which are fixed by simply removing and re-adding OISY. If you needed, here's some context beyond the instructions above.&#x20;

#### How to fix it

{% columns %}
{% column %}

1. **Remove OISY from your Home Screen**
   1. Tap and hold the OISY icon
      * Choose **Remove App → Delete App**
2. **Reinstall OISY in browser mode**
   1. **Open Safari**
   2. Go to <https://oisy.com>
   3. When prompted to *“Open as Web App”*, **deselect** this option
   4. Continue using OISY directly in Safari, or add it again to your Home Screen **without enabling “Web App” mode**
      {% endcolumn %}

{% column %}
![](https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FsPGJThb3M3LaKGRvpepZ%2FIMG_3089.jpg?alt=media\&token=2eb84d4e-34ce-4c5e-9dd7-ff84621579e3)
{% endcolumn %}
{% endcolumns %}

**Why this matters**

Running OISY as a normal browser app ensures it can:

* Connect and sign transactions with other ICP dapps
* Maintain session consistency across the ICP ecosystem
* Stay up to date with wallet and network features


# Connecting to dApps

### Via WalletConnect (Select Wallet)

1\. Navigate to the dApp’s website (e.g., [AltitudeFi ](https://app.altitude.fi/)).

2\. Click ‘Connect Wallet’.

3\. Choose WalletConnect.

4\. Search for and select OISY Wallet.

5\. Approve the connection when prompted.\
\
✅ Your OISY Wallet is now linked—ready to interact with DeFi protocols.

### Via WalletConnect (QR Code/Enter Link)

1\. Navigate to the dApp’s website

2\. Click ‘Connect Wallet’.

3\. Choose WalletConnect.

4\. The site will populate a QR Code within the popup window.

5\. Go to OISY Wallet on [mobile](/using-oisy-wallet/how-tos/saving-oisy-web-app-to-your-device) (ensure you are [logged in](/using-oisy-wallet/how-tos/logging-into-oisy))

6\.  In the top right corner of the wallet press the wallet connect icon

7\.  Press 'Scan QR Code' or enter 'wallet connect link'

8\.  Approve the connection when prompted

✅ Your OISY Wallet is now linked—ready to trade, stake, and interact with DeFi protocols.

***

### Via Internet Computer (ICP)

1\. Open the dApp (e.g., [Kongswap](https://kongswap.io)).

2\. Click ‘Connect Wallet’ and select OISY Wallet.

3\. In the pop-up, click ‘Open or Create’.

4\. Choose your Internet Identity in the second pop-up.

5\. Complete the Internet Identity sign-in flow.

6\. A ‘Review Permissions’ page will appear—check details and approve.

7\.  A second permissions page will request transaction approval—approve to enable token transfers.\
\
✅ Your wallet is now connected—trade, stake, and use dApps directly from OISY.


# Using OISY Chatbot

### Enabling the Chatbot

1. Open the OISY Wallet interface
2. Go to Settings
3. Scroll to the Beta Features section
4. Select OISY AI Assistant
5. Toggle it to ON

You should now see a small blue circle in the bottom-right corner of the screen with two white eyes.

***

### Using AI Assistant

1. Click the blue circle to open the assistant
2. A chat window labeled OISY AI Assistant will appear
3. Use the buttons at the top of the chat to access available tools:
   * Show Contacts
   * Send Assets
4. Type into the bottom input bar to ask questions or interact with the assistant

Note: Available tools are limited at this stage. We’ll be expanding functionality weekly<br>

{% hint style="info" %}
For more information about the chatbot please visit the [chatbot section](/using-oisy-wallet/ai-assistant) of the docs
{% endhint %}


# Filter & Manage Network

### Filter Networks

Want to focus on one chain at a time? You can quickly filter your wallet view to only show tokens from a specific network.

Here’s how to do it:

1. Head to the top right corner of your wallet interface.
2. Click the dropdown labeled *All Networks*.
3. Choose the network you’d like to view (e.g., Ethereum, ICP, Solana).
4. Your wallet will automatically update to display only tokens from the selected chain.

{% hint style="info" %}
Note: You can only view one network at a time.
{% endhint %}

5. To reset your view and see everything again, just reopen the dropdown and select *All Networks*.

That’s it. One view, one chain, less noise.

***

### Manage Networks

Prefer a cleaner view? You can also hide networks you don’t use and keep them hidden:

Here’s how to do it:

1. Go to the left-hand menu and click on Settings.
2. Navigate to the Networks section.
3. Click Edit — a modal will appear with a list of networks and toggle switches.
4. Toggle off the networks you don’t want to see (or toggle on ones you do).
5. Press Save to update your settings.

Your wallet will now only show the networks you’ve chosen. Fewer distractions, smoother experience.


# Enabling Privacy Mode

OISY Wallet includes a Privacy Mode designed to hide all token balances and transaction amounts on-screen, there for when you need to keep your holdings discreet.

You can toggle this setting at any time using a simple keyboard shortcut.

**To enable or disable Privacy Mode:**

1. While on the desktop wallet interface, press the P key on your keyboard.
2. All balances and numerical values will be instantly hidden from view.
3. A confirmation message will appear at the bottom center of your screen, indicating that Privacy Mode is ON.
4. To turn Privacy Mode off, press the 'P' key again.
5. Another message will confirm that Privacy Mode is OFF, and your balances will reappear.


# Buying Tokens

\
\
1\.  Open OISY Wallet at [OISY.com](https://OISY.com).

2\.  Click ‘BUY’ on the main dashboard.

3\.  A new modal will appear with two dropdown menus labeled:

* &#x20;‘You Spend’ – Select the token you want to use for the purchase.
* ‘You Get’ – Choose the token you want to buy.

4\.  Enter the amount in either ‘You Spend’ or ‘You Get’, depending on whether you are specifying the amount you want to spend or the amount you want to receive.

5\.  In the ‘Buy via’ section, choose your preferred onramp provider from the dropdown menu.

6\.  (Optional) If you want to set up a recurring purchase, toggle ‘Repeat Payment’ on or off.

7\.  Under ‘Pay Using’, select your payment method (e.g., credit/debit card, bank transfer, or other available options).

8\.  Click ‘Continue’—you will be redirected to your selected third-party onramp provider.

9\.  Follow the provider’s instructions to complete the transaction (this may include KYC verification, entering payment details, and confirming the purchase).

10\.  Once the payment is confirmed, return to OISY Wallet—your purchased tokens should now appear in your wallet.<br>

📌 *Note: Processing times may vary depending on the onramp provider, payment method, and network congestion. Some providers may require additional verification before completing the transaction.*


# Managing Collectibles in Your Wallet

{% hint style="info" %}
Before sending an ICP Collectible to your OISY wallet, open Manage Collections and check that the collection is enabled. \
\
Scroll to the bottom of this page for more info on this.
{% endhint %}

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FAYWS5ehn0HDYyiIz8VOt%2Fnft.jpg?alt=media&amp;token=b3b4c0b8-06f6-41e0-982c-fb34f9f3a531" alt=""><figcaption></figcaption></figure>

#### Viewing collectibles in Your Wallet

OISY Wallet allows you to view and manage collectibles directly within the browser interface. To find your collectibles:<br>

1. Navigate to the main wallet interface.
2. Click on ‘Collectibles’ to switch views.
3. Your visible collectibles will appear here. Hidden collectibles will not appear unless manually enabled (see below).

💡 *OISY Wallet hides* collectibles *media by default to prevent issuers from tracking your views. You stay in control of when, how, and whether* collectible *content is shown.*

***

#### Making a Hidden Collectible Visible

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FTxGisfJ2g9hE4DXtxoB4%2Fnft-Making%20a%20Hidden%20NFT%20Visible.jpg?alt=media&amp;token=b3f513c0-4b03-41b7-bc71-cd4d7f4b329c" alt=""><figcaption></figcaption></figure>

To view a hidden collectible and decide how it’s displayed in your wallet:

1. Navigate to the Collectibles page and locate the hidden collectible entry.
2. Click ‘Review’ to inspect the collectible and choose your preference.
3. If you’d like to permanently see the collectible's image or animation, click ‘Enable Media.’
4. If you want to keep it listed without loading the content, select ‘Keep Media Disabled.’
5. If the collectible appears to be unsolicited or spam, press ‘Spam’ to hide it from your wallet.

<br>

🔒 *Media is only loaded if you explicitly choose to enable it. This protects your privacy from NFT issuers that use image requests to track views.*

***

#### &#x20;Marking a Collectible as Not Spam

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FYMwXwa4K43UGFDIBSFgE%2Fnft-Marking%20an%20NFT%20as%20Not%20Spam.jpg?alt=media&amp;token=5932f39c-530e-498a-8c9e-592a0ac35db7" alt=""><figcaption></figcaption></figure>

If a legitimate collectible was mistakenly flagged as spam:

1. Navigate to the Hidden section and click ‘Review.’
2. Press ‘Not Spam’ to remove the spam classification.
3. To make the collectible fully visible, click ‘Enable Media’ if desired.<br>

⚠️ *Spam-marked* collectibles *remain hidden from your wallet view unless manually restored.*

***

#### Viewing Hidden or Spam-Flagged Collectibles

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FK5ofAReDo6GcWk5BYALK%2Fnft-Viewing%20Hidden%20or%20Spam-Flagged%20NFTs.jpg?alt=media&amp;token=a09edb4f-2aa0-4b03-9d33-9f33e8efb48b" alt=""><figcaption></figcaption></figure>

To access collectibles that are hidden or previously marked as spam:

1. Click ‘Manage Collections’ at the bottom of your wallet interface.
2. Scroll to the collectibles section where you can toggle collections on or off.
3. Toggle the desired collection to make them appear in your wallet interface.
4. If the collectible appears but media is still hidden, you’ll need to go through the ‘Review’ flow and select ‘Enable Media’.

<br>

📌 *Toggling visibility does not automatically load the media—you stay in control of exposure at every step.*

***

#### Importing a Collectible That Isn’t Showing

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FRJ9lcDZ1ZENjSYdwBOzM%2Fnft%20-%20Importing%20an%20NFT%20That%20Isn%E2%80%99t%20Showing.jpg?alt=media&amp;token=ea873283-779d-4629-b9ed-45f869f53b1a" alt=""><figcaption></figcaption></figure>

If you don’t see a specific collectible in your wallet:

1. Open the ‘Manage collections’ menu.
2. Click ’+ Import Collection.’
3. Select the correct token chain and address.
4. If the collectible is live and properly indexed, it will appear for import.
5. Once added, go to the collectible and click ‘Enable Media’ to make it visible in your wallet.

🔍 *Be sure to double-check the contract address and chain for accuracy before importing.*

***

#### Importing an ICP Collectible&#x20;

OISY supports ICP collectibles that follow the EXT standard, including collections from platforms such as Entrepot, Tonic, and DGDG.

To ensure your NFTs display correctly, there are a couple of important steps to follow.<br>

**Before Sending an ICP Collectible**

Before sending an ICP collectible to your OISY wallet, open Manage Collections and check that the collection is enabled.

This helps prevent collectibles from appearing hidden or unrecognised after transfer.

If you don’t see your collection listed, let us know in Discord and we can add support for it.

\
**After Sending an ICP NFT**

Once your collectible has been sent to your wallet:

* Go to the Collectibles page
* Click the Reload button

OISY will rescan your wallet and enable the NFT so it appears correctly in your collection.<br>

{% hint style="info" %}
Please note that you should NEVER interact with a spam collectible by sending it or burning it anywhere.  It is best to mark it as spam and ignore it as interacting with it even by viewing the image can present a risk
{% endhint %}


# Finding Tokens in Your Wallet

If a token does not automatically appear in your wallet, follow these steps to manage your assets:

1. Click the “Manage Tokens” button at the bottom of your wallet interface.
2. Select the tokens you wish to display.
3. The selected tokens will now be visible in your wallet.

\
OISY Wallet automatically detects major assets, but users have full control over token visibility.


# Finding & Using dApps

### On Desktop

1\. Open OISY Wallet.

2\. Click ‘Explore’ in the left menu.

3\. Use filters (All, dApps, DeFi, etc.) to find the dApp you need.

4\. Click ‘Go to \[dApp name]’—this opens the dApp in a new tab.

***

### On Mobile

1\. Open OISY Wallet.

2\. Tap the account icon (top right).

3\. Select ‘Explore’ from the dropdown menu.

4\. Use filters to browse dApps.

5\. The dApp opens in a new window. Click ‘Done’ to return to OISY.


# Exporting Tokens and Transactions

{% hint style="info" icon="sigma" %}
**TL;DR**

OISY allows you to export your token or transaction lists into a text file in CSV format.
{% endhint %}

## Export tokens or transactions

{% hint style="danger" icon="triangle-exclamation" %}
Please have a look at the [chapter on rounding](#a-word-on-rounding) before you process the exported data via a spreadsheet tool.
{% endhint %}

You can initiate your export on the "Settings" page:

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F0GqKh9b2EnUjKpXwmh4m%2Fimage.png?alt=media&amp;token=78d21777-234a-4ebd-931c-2cbfcb36c493" alt=""><figcaption></figcaption></figure>

The **Basic** exports contain a smaller set of exported columns and focus mainly on the information needed to get a good overview and don't expose blockchain specific details.

**Extended** exports also add blockchain specific information to the exports, such as contract addresses, token precision, or token standard. Those are intended for advanced crypto users.

Please verify that all token balances and prices have completely loaded before you start an export, or you might miss some some tokens or transactions in the export.

{% hint style="info" %}
You can access the Google Sheets template we made for the following screenshots and make a copy for your own use.\
<https://docs.google.com/spreadsheets/d/1RWnR_Y0qqMQmHuWjSko7oWEfzuhcXGqIcmusEt3omv0/edit?usp=sharing>
{% endhint %}

### Token Exports

**Basic**

* Exports a minimal set of columns
* The **Balance** is exported regular number, e.g. 12.4789654
* The **Value** is exported in your currently selected currency

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F1MZsPNMBh2rj2ElWVAg2%2Fimage.png?alt=media&amp;token=14dda2aa-378b-4cc5-8d47-68cf65292294" alt=""><figcaption></figcaption></figure>

**Extended**

* Also exports the token standard and the address of the token
* The **Balance** is exported as full integer, together with the number of digits precision
* **Price** and  **Value** are both exported in USD and in your currently selected currency

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FWRlB37mMFp7EV8fg8Zkl%2Fimage.png?alt=media&amp;token=2b9f2c81-86ec-4688-8146-3f3849ed671f" alt=""><figcaption></figcaption></figure>

### Transaction Exports

**Basic**

* Exports the core data for a transaction
* The **Timestamp** is in your local timezone
* The **Amount** is exported regular number, e.g. 12.4789654
* The **Counterparty** shows either the sender address (for a receive) or the destination address.\
  It's resolved into the contact name (and address alias in parenthesis) if found.
* The **Fee** is shown separately.
* To help summarizing, 3 additional helper columns show the amount either as **Credit** (for incoming) or as **Debit**. The third column, **Fee Token Debit**, shows the fee amount paid with the network native coin on EVM networks (mostly ETH).
* It also shows the **Transaction ID**.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FbolEfVmVnxK0f5mvJAOz%2Fimage.png?alt=media&amp;token=0957c8cc-e905-4a37-83d2-c89ed5d081cc" alt=""><figcaption></figcaption></figure>

**Extended**

* Shows some additional columns compared with the Basic version
* **Timestamp** is in UTC (Zulu time, GMT, ...)
* Also shows **From** and **To** addresses for all transactions
* And also contains an **Explorer Link** to an app showing this specific transaction

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FZV8W2tGoErpatj85VXsd%2Fimage.png?alt=media&amp;token=6d5dffd3-04a9-4bf7-b9f0-153dcd2a0013" alt=""><figcaption></figcaption></figure>

## A word on rounding

{% hint style="success" %}
Crypto tokens often use a precision of 18 or even up to 24 digits after the decimal separator, which can lead to numbers that need a larger amount of digits to represent.\
Spreadsheet tools usually only allow up to 15 significant digits per numeric value, which can lead to a loss of precision when importing them, or that a value is then imported as text instead of a numeric value.

**Note that OISY exports the full precision into the CSV text files. Rounding can happen when importing them into spreadsheet tools.**
{% endhint %}

### Problems

**Problem 1 - Precision**

* Tokens use up to 24 places after the decimal point to store a balance. For example you can have `1234.123456789012345678901234 NEAR`, a number that needs 28 digits to represent.
* Spreadsheet tools can only store at max 15 significant digits (leading and trailing zeros don't count) per numeric value, for example:
  * `1234567890123450000000000` (stored as `123456789012345e10)`
  * `1234.12345678901`
  * `0.123456789012345`&#x20;
  * `0.00000123456789012345` (stored as `1.23456789012345e-6)`

**Problem 2 - Automatic conversion with precision loss**

When you import a text file into a spreadsheet tool, a value that represents a numeric value can automatically be converted into a number and then cut to the maximum precision, so

* The value in the CSV fils is `0.1234567890123456789`
* The resulting value in the spreadsheet will be `0.123456789012345`

Note that spreadsheet tool allow to import without automatically converting a cell into a numeric value. In this case the value would be imported as a text:

* `"0.1234567890123456789"`&#x20;

But this cell then can not be used in mathematical functions.

{% hint style="danger" icon="fire" %}
This means that it's not always possible to import all balances and amounts as numbers into a spreadsheet while keeping the full precision.\
But having 15 significant digits mean that if some digits are cut off, they contribute less than 0.0000000000001% of its value, so the rounding is not all too bad.
{% endhint %}

{% hint style="success" %}

1. OISY exports all token amounts with full precision into the CSV export files.
2. The **Basic** exports export them as regular numbers, containing a decimal point.
   * `5.1234` USDC will be exported as `5.1234`
3. The **Extended** exports write the amounts as Integer value without decimal points, and also exports a column indicating the number of digits precision of the token.
   * `5.1234` USDC will be exported as `5123400` and a column indicating that USDC has `6` digits precision

The Basic exports allow to easily import the numbers anywhere without further processing, but you might lose those digits after 15.\
While the Extended exports allow safer imports, as large integer value are usually not automatically rounded by spreadsheet tools, and remain a text value.
{% endhint %}


# Migrating Wallets

If you’re moving your assets from another wallet to OISY Wallet, follow these steps carefully to ensure a smooth migration.<br>

### Step 1: Retrieve Your OISY Wallet Address

1\. Open OISY Wallet at [OISY.com](https://OISY.com).

2\. Click ‘Receive’ on the main dashboard.

3\. Select the blockchain network corresponding to the tokens you’re transferring.

4\. Copy the wallet address displayed or scan the QR code.

📌 *Make sure the selected network matches the tokens you’re migrating—sending assets to an incorrect network can result in loss.*

### Step 2: Send Assets from Your Existing Wallet

1\. Open the wallet you are migrating from (e.g., Metamask, Phantom, NFID, or another crypto wallet).

2\. Navigate to the ‘Send’ or ‘Transfer’ function.

3\. Paste the OISY Wallet address you copied earlier in the recipient field.

4\. Select the correct token and network for the transfer.

5\. Enter the amount you want to send.

6\. Double-check that all details are correct, then confirm and submit the transaction.

📌 *Depending on the network, you may need to pay a gas fee to process the transfer. Fees vary by blockchain.*

### Step 3: Verify Assets in OISY Wallet

1\. After sending, return to OISY Wallet.

2\. Go to ‘Assets’ and check if the transferred tokens appear.

3\. If the tokens do not show up immediately:

* Wait a few minutes—some networks take longer to process transactions.
* Click ‘Manage Tokens’ and search for the token.
* &#x20;If the token is missing, follow the steps in ‘[Managing & Adding Tokens](/using-oisy-wallet/how-tos/managing-and-adding-tokens)’ to manually import it.

📌 *Blockchain congestion or network delays may impact how quickly your assets appear in OISY Wallet. If you experience delays, check the transaction status on a blockchain explorer (e.g., Etherscan, Solscan, or ICScan).*

### Important Notes on Migration

* You may need to transfer tokens individually—some wallets do not support bulk transfers.
* Certain wallets charge withdrawal fees, so check the cost before initiating a migration.
* If you encounter issues, refer to ‘[Managing & Adding Tokens](/using-oisy-wallet/how-tos/managing-and-adding-tokens)’ or reach out to OISY Support for assistance.

✅ Once the transaction is complete, your assets will be available in OISY Wallet, and you can begin using them across supported dApps and DeFi protocols.


# Generate Referral Link

Want to share the OISY Wallet love and earn a little extra along the way? With the [Sprinkles](/rewards/oisy-sprinkles) reward program, you can generate a personal referral link and start getting rewarded when friends sign up.<br>

Here’s how to get your referral link:

1. Open OISY Wallet
2. In the top right corner, click your profile dropdown
3. Select *Refer Your Friends*

A modal will pop up with your personal referral QR code and link.

4. Copy the link or save the QR code to share it with others
5. Once someone creates a wallet using your link, the status message (“You haven’t referred anyone yet”) will update to reflect your referrals.

That’s it. Start sharing and watch your referral count grow.


# Send a Token Using a dApp

This page describes how OISY users can send a token from their OISY Wallet using Uniswap. This can be helpful in an instance with OISY where sending a token fails.

## Preface

If sending a token directly from OISY fails—due to a temporary bug, a third-party dependency, or a token-specific issue—you can still move your funds by connecting OISY to a supported DeFi dApp. Many apps, including Uniswap, allow users to send tokens directly through their interface.

This flow provides a reliable fallback. The example below uses Uniswap, but the same steps apply to other dApps that support WalletConnect.

## Send a token using Uniswap

In general, sending a token from your wallet via an web application requires the following steps

1. **Open** OISY and the application
2. **Connect** OISY to the application
3. **Initiate the send** in the application by selecting the token, the amount and the destination.
4. **Confirm** **the send in OISY**. This step is important can can often be overlooked, resulting in thinking the send failed.

{% hint style="info" %}
**Note**: This process works for tokens from all networks, but Uniswap only supports Ethereum / EVM based Networks (Ethereum, Base, BNB). For tokens from other networks, you can use a different Defi website and follow the same process:

* For ICP / ICRC tokens, we recommend using **KongSwap**.
* For Solana, **Jupiter** or **Raydium** are feasible options.
  {% endhint %}

### 1. Open OISY and Uniswap

To initially connect and then confirm the send, you manually need to switch to OISY. So it's recommended to have both OISY and Uniswap open in 2 individual browser tabs.\
The Uniswap URL is: <https://app.uniswap.org/>

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FxZ3wTfIMxU4xOG0c9s1E%2F00%20Uniswap___Trade_crypto_and_NFTs_safely_on_the_top_DeFi_platform.png?alt=media&amp;token=f0e8b7ad-d775-4361-a1a1-437e88d8354a" alt="" width="563"><figcaption></figcaption></figure>

### 2. Connect OISY to Uniswap

OISY supports a standard method called [**WalletConnect** ](/using-oisy-wallet/how-tos/connecting-to-dapps)to connect to DeFi applications.\
This part shows you step by step how to connect OISY to Uniswap via WalletConnect.

**Important:** Do not log in to Uniswap 'directly'. Only connect your OISY wallet through the flow described below.

**Step 1** - Click "Connect" on top right of the Uniswap homepage

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F5gaFaoI7AToZk521v885%2Fimage.png?alt=media&amp;token=aabc7c9a-9f18-4993-a612-f4c5518ee006" alt="" width="563"><figcaption></figcaption></figure>

**Step 2** - Click "Other Wallets" and then "WalletConnect"

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FDq5bBRPYoexK19iD1WQw%2Fimage.png?alt=media&amp;token=d1b917de-5cf9-421e-9006-14c400d53aee" alt="" width="563"><figcaption></figcaption></figure>

**Step 3** - Click "Copy link" on the appearing **WalletConnect** modal window\
If you don't see this QR code modal, press a blue QR code button on the appearing modal.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FaG8B5RpaAx5VCi56oPBl%2Fimage.png?alt=media&amp;token=68411fd3-9e78-4b9c-aa15-3ca8943a7fb6" alt="" width="563"><figcaption></figcaption></figure>

**Step 4** - Paste the code in OISY

* Switch to the OISY tab
* click the WalletConnect Button on the upper right part
* Paste the copied link into the field
* and click Connect

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FxVAAoPU0nhsNAiEjDx4P%2Fimage.png?alt=media&amp;token=4ad0998d-a396-49ba-97f7-656c010930ca" alt="" width="563"><figcaption></figcaption></figure>

**Step 5** - And Confirm

All actions that WalletConnect wants to do with your OISY wallet must be confirmed by you. This keeps all your assets safe, and allows you to review all transactions before they take place.

{% hint style="danger" %}
**Ensure that the displayed name & URL of the Proposer are the same as the one your are connected to.**
{% endhint %}

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FQ6bfNAKlw4rhwKePrtZV%2Fimage.png?alt=media&amp;token=abf42626-75f1-4e2d-b6d1-2217f6636e71" alt="" width="563"><figcaption></figcaption></figure>

Now you should see that the WalletConnect button in OISY changed into a "Disconnect" button, allowing you to close the connection anytime you want.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F6TeNeva017lQb0kXNQ8Q%2Fimage.png?alt=media&amp;token=63f2c5c0-257f-4180-a5a7-e5cacafc0bb4" alt="" width="563"><figcaption></figcaption></figure>

You can now switch back to Uniswap. There you should also see your OISY principal on top right instead of the Connect button.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FhPx3nQytfs6iFFxPsRiG%2Fimage.png?alt=media&amp;token=9d1d26f1-72a5-4064-981d-0c381bcee4af" alt="" width="563"><figcaption></figcaption></figure>

### 3. Initiate the Send

**Step 1** - Click on "Send"

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FeSNhoe3Xcybwmxyly4Jg%2Fimage.png?alt=media&amp;token=afbbeaeb-518a-4cb7-9ef1-06f19a4cf0a1" alt="" width="563"><figcaption></figcaption></figure>

**Step 2** - Click on the Token to select the token you want to send.

{% hint style="info" %}
**Ensure to select the right Network first** (dropdown in the upper right area of the modal). This allows you to see all tokens from that network that are in yourWallet. Then you can select the token you want to send.
{% endhint %}

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fp1H7kz8CSwc08CMmku4c%2Fimage.png?alt=media&amp;token=bde96271-51f0-4e12-a4c7-e13fb9913739" alt="" width="563"><figcaption></figcaption></figure>

**Step 3** - Enter amount, destination, and hit send.

{% hint style="info" %}
Hint: Like in OISY, you can switch between entering the USD value or the token amount directly by clicking the icon with the 2 arrows below the number field.
{% endhint %}

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FjPGanBicE9iV5LfpXiXH%2Fimage.png?alt=media&amp;token=e2c1cb93-7e8e-4ff7-8da3-7022e5231584" alt="" width="563"><figcaption></figcaption></figure>

**Step 4** - Confirm the transaction in Uniswap

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FRLwc3zrF1SrsCuscZcT9%2Fimage.png?alt=media&amp;token=6c6aea9c-c233-42eb-835a-1f95674bead4" alt=""><figcaption></figcaption></figure>

### 4. Confirm the Send in OISY

{% hint style="warning" %}
**This step is very important, and the send will not go through without it.**
{% endhint %}

OISY does not allow an application to access your assets unchecked, so have to give consent to each individual transaction that attempts to withdraw assets from your wallet.

To do so, switch to the OISY tab where you should see a confirmation modal open, with the details of the transaction you just initiated.

Approve this modal, and the transaction will be executed.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F89IVfsnUOTpbRk2IQNcS%2Fimage.png?alt=media&amp;token=5cfd7c5f-8140-4949-bc69-493f4a02446e" alt="" width="563"><figcaption></figcaption></figure>

Uniswap then shows you a notification that the transaction has been executed (takes a few seconds)

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FtKsXoj3wKohCh2vhTXS8%2Fimage.png?alt=media&amp;token=5d849da7-29b8-47f8-8170-e6727694120a" alt="" width="563"><figcaption></figcaption></figure>

And you can then see the transaction appear in OISY (also after a few seconds)

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FBZge5sTwHrs55sSHkVon%2Fimage.png?alt=media&amp;token=58a4d86c-e6f9-46cd-b55a-ecb1095c6f55" alt="" width="563"><figcaption></figcaption></figure>


# Managing & Adding Tokens

OISY Wallet supports a wide range of assets across multiple blockchains. If you don’t see a token in your asset list, follow these steps to manage and add tokens manually.

### Step 1: Viewing Your Assets

1\. Open OISY Wallet at [OISY.com](https://OISY.com).

2\. Click ‘Assets’ on the left-hand sidebar.

3\. Standard assets should appear in the center of the screen.

📌 *If your token is not visible, follow the steps below to manually add it.*

### Step 2: Searching for a Token

1\. Scroll down and select ‘Manage List’.

2\. Use the Search bar to look up the token by name or symbol.

3\. If the token appears in the results, select it, and it will now display in your wallet.

📌 *If the token is still missing, you may need to manually import it.*

### Step 3: Manually Adding a Token

If your token is not detected automatically, follow these steps to import it:

1\. Click ‘+ Don’t see your token? Import’.

2\. Select the correct blockchain network from the dropdown menu:

* &#x20;Ethereum → Enter the ERC-20 contract address.
* &#x20;Solana → Enter the SPL token address.
* Internet Computer → Enter the Ledger Canister ID.

📌 *The Index Canister ID is not required, but without it, you won’t see the token’s transaction history.*[*\**](https://x.com/oisy/status/1859603949545828787)

3\. Review the token details carefully:

* Name
* Network
* Symbol
* Contract Address

4. &#x20;If everything is correct, click ‘Add the Token’
5. Your newly added token will now be visible in your wallet under the Assets tab.

### Step 4: Troubleshooting Missing Tokens

If your token still doesn’t appear after importing:

* Double-check that the contract address is correct (you can verify it on Etherscan, Solscan, or ICScan).
* Ensure you selected the correct network—tokens on different chains require separate contract addresses.
* If necessary, refresh your wallet or log out and back in to update the asset list.

📌 *If you continue to have issues, please raise a* [*support ticket*](/using-oisy-wallet/support)*.*


# Raise a Support Ticket

### Raise a Support Ticket (In-App)

1\. Open OISY Wallet.

2\. Click your profile (top right).

3\. Select ‘Support’.

4\. Follow the steps to email <support@oisy.com> or use Discord.<br>

***

### Raise a Ticket (Discord)

1\. Join [OISY Discord](https://discord.com/invite/ejBT7dQneK).

2\. Verify your account.

3\. Navigate to ‘#📮・get-support’.

4\. Click ‘Create Ticket’.

5\. A private thread will open—post your issue.


# Submit Feedback

Give Feedback

1\. Join [OISY Discord](https://discord.com/invite/ejBT7dQneK).

2\. Go to ‘#💡・feedback’.

3\. Share your thoughts.

4\. A ✅ means your feedback has been logged.


# Join the Tester Program

1\. Join [OISY Discord](https://discord.com/invite/ejBT7dQneK)

2\. Verify your account.

3\. When a test is announced, react with 🧪.

4\. Get the ‘\[α] Testers’ role.

5\. Access private tester channels with instructions.


# FAQ

### Who controls the private key for the native assets?

The private keys are controlled by the Network Nervous System (NNS), a decentralized autonomous organization (DAO) on the Internet Computer. These keys are secured using threshold cryptography, meaning they are collectively managed by the network and inaccessible to any individual or entity, including Oisy.

[Learn more: NNS Overview](https://internetcomputer.org/nns)

***

### What chains is OISY Wallet currently compatible with?

Bitcoin, Ethereum, Solana, ICP, Binance Smart Chain, Base, Polygon, Arbitrum and many more to come

***

### Can OISY access the private keys of the native assets?

No, Oisy cannot access the private keys.  The private keys are held as [decentralized threshold keys on the internet computer](https://internetcomputer.org/docs/current/references/t-sigs-how-it-works).  Transactions can be signed only by  a user authorized by the NNS-controlled Internet Identity via the NNS-controlled Chain Fusion Signer [canister](https://dashboard.internetcomputer.org/canister/grghe-syaaa-aaaar-qabyq-cai).

Read more: [What is the Chain Fusion Signer](https://github.com/dfinity/chain-fusion-signer?tab=readme-ov-file#what-is-the-chain-fusion-signer)&#x20;

***

### How are transactions signed for these native assets?

Transactions are signed by a canister smart contract on the Internet Computer, called the Chain Fusion Signer. This ensures secure and decentralized transaction handling without exposing the private keys.

[Read more: How Transactions Work](https://internetcomputer.org/docs/current/references/bitcoin-how-it-works)

***

### Is the address created specifically for me as an end-user?

Yes, the address is created specifically for you during the setup of your Oisy wallet. The Chain Fusion Signer canister generates this unique address tied to your account.

[Reference: Canister Key Management](https://internetcomputer.org/docs/current/references/t-sigs-how-it-works)

***

### How does this wallet differ from Trust Wallet or other multichain wallets?

Unlike Trust Wallet and similar wallets, where you own and manage the private keys directly, the Oisy wallet relies on network custody via the Internet Computer’s NNS. This ensures decentralized control and removes the risk of private key exposure, while still providing you full control over your assets through the canister system.

[Learn more: T-Signatures and Custody](https://internetcomputer.org/docs/current/references/t-sigs-how-it-works)

***

### Do I really have ownership over this wallet?

Yes, you have functional ownership. While the private keys are held securely by the network, your wallet is tied to your identity, and only you can authorize actions through the decentralized infrastructure. This combines ease of use with decentralized security.

[More on This Here](/security/asset-control-recovery-and-governance-in-oisy-wallet)

***

### Can I send tokens from OISY to another Wallet (i.e. can I send USDC to my phantom wallet)

Yes you can, You just need the recipient address and you can [send tokens](/using-oisy-wallet/how-tos/sending-tokens) from OISY Wallet any time you wish

***

### What does OISY Stand for?

Open Internet Services-y (read more [here](https://medium.com/dfinity/global-r-d-september-2023-edition-b8a5a1409c5c))

***

### Whats the difference between OISY Wallet and Internet Identity

OISY Wallet and Internet Identity serve distinct roles in the ICP ecosystem. Internet Identity is an authentication tool that creates unique wallets for each app, ensuring security but fragmenting assets. OISY Wallet unifies asset management with one wallet across apps, eliminating fragmentation. It offers features like in-wallet swaps, multi-chain support (e.g., Solana tokens like $SOL), and integrations with dApps like KongSwap. While Internet Identity focuses on secure logins, OISY combines security with advanced tools for streamlined, comprehensive DeFi management.\
\
Please see ‘[How is my principal handled using OISY](#how-is-my-principal-handled-using-oisy)’ for slightly more context

***

### How is my principal handled using OISY?

When you connect your OISY wallet to any dApp, it uses the same principal ID, which means you access the same funds across all dApps.

\
However, when you log in to different dApps using the same Internet Identity, each dApp assigns a unique principal ID. So even though you use the same login identity, each dApp, including OISY, recognizes you differently and assigns a separate principal.

***

### What do I do if I have an issue or a problem?

To ensure you are communicating directly with a team member, please email `Support@oisy.com` or open a support ticket in our [Discord](https://discord.com/invite/ejBT7dQneK). We will soon introduce a support widget on our website, but currently, these are the only verified methods to reach our team.

***

### Do you have a mobile app or Wallet browser?

We do not have these currently, however the wallet is [optimised for mobile](/using-oisy-wallet/how-tos/saving-oisy-web-app-to-your-device) and will not interfere with prioritized browser extension modals.

***

### How do I partner with OISY?

To discuss a partnership with OISY, please join our [Discord](https://discord.gg/HvvbwQ4Smp), open a [support ticket](/using-oisy-wallet/support), and select the appropriate context for your inquiry. This is the required step to initiate the partnership process.

***

### Do you have a tester programme?

Yes, we have a [tester program](/using-oisy-wallet/how-tos/join-the-tester-program) where we engage testers to refine features before releases. To join, keep an eye on our [Discord](https://discord.com/invite/ejBT7dQneK.) and social media channels for announcements about new tester recruitment.

***

### I’m not seeing the complete history of the tokens in my wallet

If certain tokens are missing from your history, it might be because their Ledger and Index Canisters (IC) need to be added. Informing the project to [add these canisters](/integrate-with-oisy/listing-a-token-on-oisy) can help us ensure you receive the seamless UX you expect from us.

***

### Why is the price/value not showing for a token in the wallet?

Different wallets use different oracles for sourcing price data. We currently rely on CoinGecko, and because some tokens are not listed there or may fluctuate, their prices may not appear either because they are not available or because of volatility

***

### Why is the token logo not showing for a token in the wallet?

Token logos in OISY Wallet are displayed based on the metadata provided by the token’s canister. If the logo is included directly in the metadata, it will appear in your wallet as expected.

However, if the logo is linked via an external URL, OISY won’t display it. This is an intentional choice to protect your privacy and avoid exposing users to third-party resources that could be tracked or changed.

If you’re a project team and want your [logo to appear](/integrate-with-oisy/listing-a-token-on-oisy), please ensure it’s embedded directly in the token’s metadata rather than linked externally.

***

### Can I use Multisig on OISY?

Yes, OISY supports multisig functionality in line with ICRC-2 standards. This allows users to pre-approve a specific amount that can be accessed by Dapps without further consent, enabling multiple transactions up to the approved limit.&#x20;

If you have specific multisig needs that involve all users signing each transaction, please [let us know](/using-oisy-wallet/support) so we can ensure compatibility and provide further assistance.

***

### What is Network Custody?

Network custody is a cutting-edge approach to digital asset security that eliminates the traditional need for direct private key management by users. This method leverages the decentralized architecture of the Internet Computer, enhancing both security and usability.

***

### How does Network Custody compare to traditional methods?

Unlike traditional self-custody, which requires users to safeguard their own private keys, and custodial services that pose risks of centralized control, network custody in OISY simplifies access while distributing security risks.

***

### How is Network Custody implemented in OISY?

OISY utilizes threshold cryptography technology on the Internet Computer to split private keys into shares that are distributed across various nodes. This method ensures that no single node can access the complete key, significantly enhancing security during transactions.

***

### What are the advantages of using Network Custody?

Network custody provides numerous benefits:

* &#x20;Enhanced Security: By decentralizing key storage and using advanced cryptographic techniques, it becomes much harder for unauthorized users to access digital assets.
* Simplified Access: Users can authenticate via modern methods like biometrics—no need to remember complex passwords or seed phrases.
* &#x20;Peace of Mind: Users no longer need to worry about losing keys or theft from personal devices.
* &#x20;Cost-Effective: Reduces the need for extensive security infrastructure for businesses, lowering operational costs.

***


# Support

Whether you have a quick question, want to chat with the community, or need direct assistance, we’ve made it easy to find the help you need.

### 🔍 Frequently Asked Questions

Before reaching out, check our Hot-To's and FAQs to find answers to common questions about our product, features, and troubleshooting steps.

{% content-ref url="/pages/G1TZV6BV4xybRfYnsZBK" %}
[How To's](/using-oisy-wallet/how-tos)
{% endcontent-ref %}

{% content-ref url="/pages/tKMs4oxc2mm7u93z91lx" %}
[FAQ](/using-oisy-wallet/faq)
{% endcontent-ref %}

{% content-ref url="/pages/YlYkEw8BIp9gD0rStLib" %}
[OISY Wallet switches to Internet Identity 2.0](/using-oisy-wallet/support/oisy-wallet-switches-to-internet-identity-2.0)
{% endcontent-ref %}

### 💬 Hot to get Support

#### Join the Community on Discord

Connect with other users, get real-time support, and stay up to date with announcements in our [Discord community](https://discord.com/invite/ejBT7dQneK).

Select the support channel (#get-support), where you can directly file a new support ticket. All responses from our support agents will directly be written in the same thread and can only be seen by you.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FX6ZJYBrCxut6aMb3KzMQ%2Fimage.png?alt=media&amp;token=8351e0a7-a50b-4ccf-9f65-603a1fe59b1c" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="danger" icon="fire" %}
We recommend to join the Discord community. Once joined, You can ask any sort of question in the #general channel, where other members can help you out.

**But be cautious with replies from other users!** Do not click on invitations to other communities or channels that offer to give additional help or support. Official OISY Team members have the OISY icon next to their name.\ <img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F4uZtrKmbEY6PnxwdoGIB%2Fimage.png?alt=media&amp;token=e17c5378-0526-4369-bed9-da335488660b" alt="" data-size="original">
{% endhint %}

#### Alternative

{% hint style="info" %}
Still need help? No worries! Reach out to our support team via email at <support@oisy.com>, and we’ll get back to you as soon as possible.
{% endhint %}


# OISY Wallet switches to Internet Identity 2.0

This page is the first access point for users who want to find more information about OISY's switch from using Internet Identity 1.0 to using Internet Identity 2.0 for the login or sign-up process.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FiDF9jhy0Iqbv9HqKbLwf%2FInternet%20Identity%20-_%20II%202.0.jpg?alt=media&amp;token=6df1d468-57dd-47b3-827b-92d94f796eb0" alt=""><figcaption></figcaption></figure>

## Summary

OISY switches its login process from using Internet Identity 1.0 to Internet Identity 2.0.\
Until January 26, 2026, OISY will also support the login through the 1.0 flow, so you don't have act right away.

To use the new 2.0 login, you have to upgrade your Identity (= the "account" you created on Internet Identity 1.0). This upgrade is very quick and requires just a few clicks. The new login page will guide you through this flow. Further down on the page, there is a [#step-by-step-guide-to-upgrade-your-identity](#step-by-step-guide-to-upgrade-your-identity "mention").

{% hint style="success" %}
Note that **your identity remains the same**. It just gets improved so that it can also be used for applications that support the Internet Identity 2.0 login flow, while it will still be valid to use it for the legacy login via Internet Identity 1.0.\
After you upgraded your identity and log in to an application, you will still 'be' the same user and see the same data, principals, etc.
{% endhint %}

{% hint style="warning" %}
Please read the [**Internet Identity 2.0 Upgrade FAQ**](https://identitysupport.dfinity.org/hc/articles/40276570234132-Internet-Identity-Upgrade-FAQ) before you start your upgrade process.
{% endhint %}

If you created your Identity already on Internet Identity 2.0, e.g. by signing up on [caffeine.ai](https://caffeine.ai/), you don't have to do anything. You are ready to sign in to OISY right away.

## Overview

### What is Internet Identity

**Internet Identity** (often written “II”) is the Internet Computer’s native authentication system that lets users log in to applications securely and anonymously, and is also used by OISY.

Read more: [Internet Computer: An Introduction](https://identitysupport.dfinity.org/hc/en-us/articles/27213167791124-Internet-Computer-Internet-Identity)

### What is Internet Identity 2.0

Internet Identity recently released an improved version of the previous version, Internet Identity 1.0, and it comes with several improvements and an easier to use and more powerful user interface.

Read more: [Introducing Internet Identity 2.0](https://identitysupport.dfinity.org/hc/en-us/articles/39593373981588-Internet-Identity-2-0)

Access Internet Identity 2.0: <https://id.ai/>

### How does this switch affect me?

Internet Identity 1.0 will be decommissioned on January 26, 2026. After this date, you have to upgrade your existing Identity in oder to use in on any application that uses Internet Identity.

{% hint style="success" %}

## Internet Identity 2.0 is powerful

An upgraded account will allow you to use **newer applications** like [caffeine.ai](https://caffeine.ai) and offer you all **new features** of Internet Identity 2.0.

* **No More Identity Numbers**: You no longer need to remember or store an identity number. Logging in is now simpler and more streamlined.
* **Seamless Passkey Integration**: Internet Identity 2.0 leverages the latest passkey standards for enhanced security and ease of use.
* **Social Logins**: Internet Identity 2.0 has integrated Google, Apple and Microsoft as alternative authentication options.

Read more on [Internet Identity 2.0](https://identitysupport.dfinity.org/hc/articles/39593373981588-Internet-Identity-2-0)
{% endhint %}

{% hint style="success" %}

## The upgrade is safe

An **upgraded account will still fully work with legacy login flows.**

This means you can safely upgrade your existing account, without losing any functionality, and the Identity number that you used before remains the same and can still be used in other applications that still use the legacy login flow. This is until Internet Identity 1.0 will be decommissioned on January 26, 2026.
{% endhint %}

{% hint style="success" %}

## It's easy

**Upgrading your existing account is a very straight forward process and only requires a few clicks**.

Read below in the FAQ section on how to upgrade your account.

Read more: [Internet Identity 2.0 Upgrade FAQ](https://identitysupport.dfinity.org/hc/articles/40276570234132-Internet-Identity-upgrade-FAQ)
{% endhint %}

{% hint style="success" %}

## No rush!

**You don't have to upgrade your account right away**.

OISY will still support the legacy login flow via Internet Identity 1.0 until January 26, 2026. After that date, you need to upgrade your account to Internet Identity 2.0.
{% endhint %}

## FAQs

### Why is OISY switching from Internet Identity 1.0 to 2.0?

[Internet Identity](https://docs.oisy.com/introduction/internet-identity) is a secure, blockchain-native authentication service developed for the Internet Computer (ICP) that replaces traditional usernames and passwords with advanced cryptographic authentication.\
It recently released version 2.0, and version 1.0 has been sunsetted on January 29, 2026.

Read more on [Internet Identity 2.0](https://identitysupport.dfinity.org/hc/articles/39593373981588-Internet-Identity-2-0)

### How do I know if I have to upgrade my Identity?

If you use a number (typically 7 digits) to start your login process, you have to upgrade your account.

### Do I have to upgrade my existing Identity?

Yes.\
The legacy login portal (Internet Identity 1.0) has been sunsetted on January 29, 2026, and users must upgrade their Identity to log in date, you need to upgrade your Identity as part of the login process, if you haven't done so yet.

### How do I upgrade my existing account

Click the main login button ("**Open or Create**") on the landing page, select the "**Upgrade your identity**" option in the header of the login form, and follow the guided upgrade flow.

You can find a detailed guide further down on this page: [#step-by-step-guide-to-upgrade-your-identity](#step-by-step-guide-to-upgrade-your-identity "mention")

### I upgraded my account, but somehow don't see my assets anymore

If you upgraded one (or more) Identities, and somehow don't see your tokens in your wallet anymore after the login, you can

* check first that you see the right Identity name on top right of the login form before you click continue.
* Secondly, you can select the option "Use another identity" in the selector on top right, and select the passkey again that you created when upgrading your Identity. The (user-)name of the passkey usually is the identity name you entered during the upgrade. Please ensure that you also use the right tool for the passkey selection. You might see a tool like 1Password first, then after closing this popup you might see your Apple or Chrome passkey store.
* If that all failed, you can always go through the upgrade steps again. So use the upgrade feature, enter your old anchor number, select the passkey for that, and name this Identity now with a new Name.\
  This identity should then also be selected and you can log in again.

If that all failed, you can always consult the [Internet Identity Help Center](https://identitysupport.dfinity.org/hc) and file a support ticket on the bottom area of the page.

### I have additional questions about Internet Identity

The following resources provide additional information about Internet Identity and the upgrade to version 2.0

* [Internet Identity Help Center](https://identitysupport.dfinity.org/hc)
* [Internet Identity 2.0](https://identitysupport.dfinity.org/hc/articles/39593373981588-Internet-Identity-2-0) for a general overview of Internet Identity 2.0
* [Internet Identity 2.0 Upgrade FAQ](https://identitysupport.dfinity.org/hc/articles/40276570234132-Internet-Identity-upgrade-FAQ) for more Internet Identity 2.0 related FAQs

## Step by Step guide to upgrade your Identity

{% hint style="warning" %}
Please read the [Internet Identity 2.0 Upgrade FAQ](https://identitysupport.dfinity.org/hc/articles/40276570234132-Internet-Identity-Upgrade-FAQ) before you start your upgrade process.
{% endhint %}

### Step 1 - Start a normal login

As first step, you can simply start your normal login process in OISY, by clicking the main button to log in.

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FcrRyYOFxLfpQ0yszH26j%2Fimage.png?alt=media&amp;token=c7a9adf2-84e9-424e-84c9-7d8426f19378" alt="" width="375"><figcaption></figcaption></figure></div>

### Step 2 - Now you see the new Internet Identity 2.0 Login

You can now see the new login form for Internet Identity 2.0.\
To now upgrade your Identity, you can click the "Upgrade your identity" button in the upper area. This starts the upgrade process.

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F73THg0xXUC76qgdY2kPj%2Fimage.png?alt=media&amp;token=220a15e8-28c5-4b65-9ad4-77ea72b55eb4" alt=""><figcaption></figcaption></figure></div>

If you already upgraded an identity, or collapsed the upgrade section on top by clicking the (X) inside of it, you might see a smaller version of it. You can simply click the left side of it to expand the section again, or click the right side ("upgrade") to start the upgrade process.

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FPodwWl4lmTxp5k96LZPr%2Fimage.png?alt=media&amp;token=840382c5-ef93-4f7e-80d7-54ba47c1588d" alt="" width="281"><figcaption></figcaption></figure></div>

### Step 3 - Enter your legacy Identity number and sign in

Next step is to enter the Identity number you previously used to log in. If you don't know your number out of your head, you might also find it on the legacy [Internet Identity 1.0 portal](https://identity.internetcomputer.org/). When entered, click "Continue".

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FssF5wDPYniM8I1R4WOdq%2Fimage.png?alt=media&amp;token=adeebb95-fea7-4148-8e31-ab7e907bda97" alt="" width="375"><figcaption></figcaption></figure></div>

Once entered, you should see the same passkey confirmation popup you also see when you log in through the legacy login. This now confirms that you are authorized to change this Identity.

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F5PDKT7LLvkqkGYWBRVKB%2Fimage.png?alt=media&amp;token=8652f72f-cddf-4ff9-9cf3-5665fa1190be" alt="" width="375"><figcaption></figcaption></figure></div>

### Step 4 - Name your Identity and save the new passkey

Now you can give your Identity a name. Unlike Internet Identity 1.0, where you distinguished between Identities by a different number, you can now give your Identity a name. This name will later be shown on all Internet Identity 2.0 related screens, and the new passkey will also contain this name when it's stored.

**Note that you can't rename the Identity once it's set.**

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FdEDHOt6EBaBDC4teGliG%2Fimage.png?alt=media&amp;token=e1af0866-ba14-4aab-be53-2cbd8efe67cc" alt="" width="375"><figcaption></figcaption></figure></div>

This now triggers the creation of a new passkey in your preferred passkey store.\
Note that you now also see the Identity name, in my case "Private Account", being stored with the passkey. This helps you later to know what Identity this passkey is used for.&#x20;

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F2B2lnG7tKT65iyG9CZpt%2Fimage.png?alt=media&amp;token=23b3efd4-9abf-4fdd-958f-5dfa884c70be" alt="" width="375"><figcaption></figcaption></figure></div>

### Step 5 - You are all set

After saving your new passkey, you see a confirmation screen, and you get automatically redirected back to OISY after 5 seconds.

<div align="left"><figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FHBLFNJJSxd39To2N5zI8%2Fimage.png?alt=media&amp;token=4002fb5b-7628-417b-a468-a5690ea1979d" alt="" width="291"><figcaption></figcaption></figure></div>

### Step 6 - Verify your Recovery Phrase if you have one set

We also recommend to verify your recovery phrase, in case you have one set. You can do that directly on the Internet Identity 2.0 portal:

* Go to the Internet Identity 2.0 portal at <https://id.ai>
* Open the user menu dropdown on top right, select your Identity or select "**Manage Identity**"
* Go to **Access and recovery** page
* Click "**Verify**"

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fqyn4guSuhBC8uIi2engQ%2Fimage.png?alt=media&amp;token=96ae131f-5ede-4259-b510-ca99267f2b22" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Congratulations, your Identity is now upgraded and can be used on all dapps that support Internet Identity 2.0
{% endhint %}

## Additional Infos

* [Internet Identity Help Center](https://identitysupport.dfinity.org/)
  * [Internet Identity 2.0](https://identitysupport.dfinity.org/hc/articles/39593373981588-Internet-Identity-2-0)
  * [Internet Identity 2.0 Upgrade FAQ](https://identitysupport.dfinity.org/hc/articles/40276570234132-Internet-Identity-upgrade-FAQ)


# AI Assistant

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fisv4a8dbRrGnjOmkiCuG%2FOISY%20AI.jpg?alt=media&amp;token=ac736fc8-88b4-4516-9090-192fead2d0d6" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The OISY AI Assistant is currently available as a beta feature. That means it’s live in the app, but still under active development.

We’re shipping it now to learn from how you use it in real-world conditions. Expect bugs, missing functionality, and rapid iteration. It’s not a finished product, and shouldn’t be treated like one.

Your [feedback](/using-oisy-wallet/how-tos/submit-feedback) will help shape what it becomes.
{% endhint %}

\
The OISY Assistant lets you take action quickly using natural commands. It’s part of the Chatbot Beta released in v1.7 and will continue to expand with new tools as more features roll out.

#### How to use the assistant

1. Open Settings and toggle on OISY AI Assistant under  Beta Features
2. Once enabled, a glowing blue button will appear at the bottom of your screen
3. Tap the button to bring up a chat input on the right side

The assistant button pulses gently to let you know it’s live. When tapped, it opens a side panel where you can type commands like

```
send 5 ICP to Satoshi
```

#### Current capabilities

The assistant currently supports two tools:

* Showing your saved contacts
* Starting a token send process
* Listing Wallet, Network, or Token Balances

More tools are on the way. Each tool is developed by OISY and triggered by the assistant. Once triggered, the tool runs locally in OISY and renders any necessary UI - none of that output is visible to the assistant.

#### What the assistant can and cannot see

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fq3B6EQwUnPhbfD2ST9S2%2FOISY%20AI%20-security.jpg?alt=media&amp;token=fc9662a4-dc41-494d-b77a-068044c0c804" alt=""><figcaption></figcaption></figure>

The assistant helps start an action, but does not execute it. You always confirm by clicking Send yourself.

All data shown in the transaction preview, including:

* ❌ Contact addresses
* ❌ Token amounts
* ❌ Estimated value or fees
* ❌ Your IP address&#x20;
* ❌ Wallet balances
* ❌ Network or token balances

The assistant does not have access to this data.

Internally, the assistant only receives internal contact IDs, never full addresses, transaction data, or balance information. Even though assistants typically receive full history to provide context, we exclude anything generated by OISY tools from the assistant’s view.

This ensures that even when you ask the assistant to display your Wallet, Network, or Token Balances (a feature added in v1.7.4), that data remains fully local to OISY and is not shared with the model.

In the example shown in the image below, all content inside the highlighted boxes was created by OISY. This includes the contact selection, wallet options, token details, balance displays, and fee breakdown. None of it was sent to or seen by the assistant.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F3UGujNEVSd3UshHqi86P%2FOISY%20AI%20-%20tools.jpg?alt=media&amp;token=554e0797-2e10-43da-8a17-05da5d673e47" alt=""><figcaption></figcaption></figure>

### Architecture & FAQs

These are answers to questions people often have, plus internal implementation details, so you know exactly what’s going on under the hood.

**How it actually works**

* When you send a prompt to the assistant, it goes first to an on‑chain canister (the LLM canister). This canister’s job is to queue the request and act as a proxy layer.
* The canister forwards the request to an external AI model service for processing. The model runs off‑chain, not inside the canister.
* Once the external model finishes, the response comes back through the canister and is displayed in OISY. If the assistant suggests actions (e.g. showing a Send form), OISY renders the form itself.<br>

**What the assistant cannot do**

* It cannot send transactions by itself. Any transaction must be manually approved/confirmed by you.
* It does not have access to your real blockchain addresses, contact addresses, or balances. It only sees internal pseudonymous identifiers.\
  It does not render or execute wallet tools except by invoking in‑wallet forms (which are built and displayed by OISY).<br>

### Privacy & Data Security

Here’s how we protect your data, and what is / isn’t shared:

<table><thead><tr><th width="240.93359375">Concern</th><th>Clarity</th></tr></thead><tbody><tr><td>Wallet addresses or contacts</td><td>Not shared with the AI. Only internal pseudonymous IDs are used.</td></tr><tr><td>Token Names</td><td>A list of your token names is shared so the AI can recognize inputs like “send 5 ICP." in the example above</td></tr><tr><td>Token Balance</td><td>Not shared. The model does not know how much you hold. Balance data is rendered by OISY and never sent to the AI, even when shown in chat.</td></tr><tr><td>Sensitive info typed by user</td><td>Only what you type directly is included in the prompt.</td></tr><tr><td>IP Address</td><td>Not exposed. Requests are routed through an intermediary layer.</td></tr></tbody></table>

\
We will be continuously expanding our [How To Section](/using-oisy-wallet/how-tos/using-oisy-chatbot) specific to the bot, so please check there regularly.\
\
Finally we'd recommend giving [this forum post](https://forum.dfinity.org/t/introducing-the-llm-canister-deploy-ai-agents-with-a-few-lines-of-code/41424) a read to see the genesis of this effort.

{% hint style="info" %}
This feature is part of the Chatbot Beta in v1.7.4 and will update frequently as new functionality becomes available.
{% endhint %}


# Notes

Notes let you keep short, private pieces of text alongside your wallet — a PIN reminder, a note about who an address belongs to, anything you want close at hand. Notes aren't attached to any transaction, address, or token; they're just yours.

#### What are Personal Notes

A note is a simple block of free-text, up to 2,000 characters. There's no separate title field — the first line of what you write is shown in bold as the note's title in your list, purely for display. Notes support any language, script, or emoji, and any http/https links you paste into a note become clickable when you view it.

All your notes live together in one simple, searchable list, for as long as you want to keep them.

#### Keeping Your Notes Private

Your notes are private by default: no one but you can read them — not OISY, not the systems running the wallet, and not other users. They're scrambled the moment they leave your device, and only unscrambled again on your device when you open them, so what you actually wrote never travels anywhere in a readable form.

Because your notes only exist in readable form on your own device, searching them works the same way — there's no way for anyone to search what your notes say from outside your device.

#### Where to Find Notes in OISY

Notes live in your user menu, right after Contacts. Opening it shows your list of notes, newest or most recently edited first, with a search field to filter them and an "Add note" button.

**Add, View, Edit, and Delete a Note**

Tapping "Add note" opens a plain text box — write what you want, then save. Tapping an existing note opens it read-only; from there you can edit it (which reopens the same text box, pre-filled) or delete it. Deleting asks for confirmation first, since it can't be undone. You can hold up to 1,000 notes at a time; past that, you'll need to delete one before adding another.

#### Sharing a Note

Any note you've successfully opened can be shared: a quiet "Share note" link on the note's view screen starts the process. Sharing creates a one-time public link that lets someone read that note's text — even if they don't have an OISY account and never sign in.

When you create a share link, you choose how long it stays valid (1 hour, 24 hours, 7 days, or 30 days — there's no permanent option), and you can optionally make it self-destruct after it's opened once. Once you have the link, copy and send it however you like; OISY doesn't send it for you.

A shared link is a snapshot: it captures the note's text at the moment you create the link. Editing or deleting the original note afterward has no effect on a link you've already shared — and importantly, **once a link is created, OISY can't recover or revoke it.** Anyone who has the link can read the note until it expires or is used up, so treat the link itself the way you'd treat the note's contents.

**What the Recipient Sees**

Opening a shared link shows a simple "A note was shared with you" screen with a single "Reveal note" button — nothing loads until that's clicked, which also protects single-use links from being burned by link-preview bots. Once revealed, the recipient sees only the note's text: no sender name, no timestamps, nothing identifying who shared it or when. If the link is single-use, the page tells the recipient to copy the note before closing or reloading, since it won't be retrievable again. An expired, already-used, or invalid link shows the same generic "This link has expired or already been used" message, regardless of which of those actually happened.

#### Limits to Know About

Each note can hold up to 2,000 characters, and you can keep up to 1,000 notes on your account at a time. If you reach that count, you'll need to delete an existing note before you can add a new one.

#### Technical Details

*For anyone who wants the underlying mechanics.*

**Encryption Model**

Notes use [vetKeys](https://internetcomputer.org/docs/building-apps/network-features/vetkeys/introduction), an Internet Computer primitive for threshold-derived, per-user encryption keys (vetKD). Each user's key is derived on demand from their identity and cached locally as a non-extractable browser key, so it only needs to be fetched once per device. Notes are stored in the canister via the vetKeys `EncryptedMaps` primitive, keyed by an opaque note ID — the canister and the node providers behind it only ever see ciphertext, never note contents.

**Sharing Security Model**

Sharing uses a second, independent encryption path, separate from your personal vetKeys key: creating a share generates a fresh, random AES-GCM-256 key entirely in your browser. That key is never sent to the canister — it lives only in the link itself, after the `#` fragment, which browsers never transmit to a server. The link's public part is an unrelated random token; the canister stores only the ciphertext, its expiry, its single-use flag, and basic access timing against that token — never the plaintext, never which note it came from, and never the recipient's identity. The principal who created the share is recorded only to enforce the per-user cap on active shares, and isn't exposed through any read path.

This means the canister can observe that a share exists, roughly how large it is, when it expires, and when it's accessed — but not what it says. It also means there is no mechanism for OISY to reconstruct or invalidate a share link after the fact: possession of the full link (including the fragment) is the only thing that grants access, by design.


# Earn

OISY Wallet makes it easy to grow your digital assets through simple, transparent earning products. You keep full control over your tokens at all times, while choosing how you want them to work for you.

{% hint style="info" icon="dog" %}
This page explains the basics:

How earning works, where rewards come from, what happens to your assets, and how you can withdraw anytime.
{% endhint %}

### What is Earn?

Earn lets you put your assets to work through a set of vetted opportunities such as staking, yield-bearing tokens, or future borrow/lend integrations. Each option has its own level of risk, reward, and liquidity. You always choose what fits your comfort level.

Today, Earn supports [Harvest Autopilot](/using-oisy-wallet/earn/harvest-autopilot) and [Liquidium](/using-oisy-wallet/borrow/liquidium).

### How 'Earning' Works

While each product is different, most earning strategies follow a simple idea:

1. You deposit (stake) a token.

   Your deposit enters a secure, on-chain smart contract.
2. Your asset begins generating yield.

   Depending on the product, this may come from:

   * rewards distributed by a protocol,
   * returns generated by underlying assets (e.g., gold-backed instruments),
   * lending interest,
   * or future strategies like curated yield portfolios.
3. You can track earnings in OISY.

   Your dashboard shows:

   * your staked balance,
   * your current APY,
   * your active rewards, and
   * your total earning potential.
4. You withdraw whenever you want.

   You maintain full ownership. You can unstake or redeem back to your wallet based on each product’s rules (some are fully flexible; others may have cooldowns).

### Who Owns My Tokens?

**You do. Always.**

OISY never takes custody of your assets.

When you stake:

* your tokens stay inside a smart contract tied to your wallet identity,
* no one else can move or use your funds,
* and the rewards you earn remain linked to your wallet.

Your staked tokens are visible in the Earn tab and in your asset list.

### How Do I Get My Tokens Back?

Every Earn product includes a Withdraw or Unstake option.

* If the product is flexible, you can unstake at any time and receive your tokens immediately.
* If the product has a term or cooldown, this will be clearly displayed before you stake. Once the period ends, you can withdraw your tokens and claim any earned rewards.

OISY will always show:

* your staked balance,
* your available-to-withdraw amount,
* any pending rewards,
* and any waiting period (if applicable).

### Understanding APY

APY (Annual Percentage Yield) represents the estimated yearly return generated by the strategy.

**It is not fixed — it can increase or decrease depending on market conditions and reward schedules.**

OISY displays

* Current APY = what the strategy is earning right now&#x20;
* Your active earnings = what your current staked amount is generating
* Your earning potential = what you would earn if you met all eligibility conditions

APY is shown transparently so you can compare opportunities and make informed decisions.

### Is This Safe?

OISY does not create yield strategies itself.

All earning products integrate with trusted third-party protocols through their official smart contracts and documentation.

We highlight:

* what the underlying asset is,
* how rewards are generated,
* and the risks or terms involved.

You remain in control of the decision to participate.

### Understanding Impermanent Loss and Value Risk

Different earning strategies carry different types of risk. Two of the most common are

#### 1. Impermanent Loss (for liquidity pools)

Some products involve depositing two assets into a pool.

If their prices move away from each other, the value of your share in the pool can become lower than if you simply held both assets in your wallet.

This difference is called impermanent loss.

It becomes permanent only if you withdraw while the prices are still far apart.

OISY will always flag when a strategy includes this type of risk.

#### 2. Underlying Asset Value Risk (for single-asset staking)

Some earning options are *single-sided*, meaning you only stake one token.

Here, there is no impermanent loss, but the value of your position still depends on the market price of the token you staked.

{% hint style="info" %}
Example

You stake 1 ETH worth $3,000, earning 10% APY.

If ETH later drops to $2,000, your total position value drops with it — even though you earned staking rewards — because the underlying asset is now worth less.
{% endhint %}

This is normal for any asset with market volatility.

OISY displays your staked balance and rewards separately so you can clearly see both effects.

### What’s Coming Next

Earn will expand to include:

* curated stablecoin yield strategies,
* borrow/lend integrations,
* cross-chain staking opportunities,
* and more reward-based products.

Each will follow the same principles: transparency, user ownership, and simple UX.


# Harvest Autopilot

Smarter Allocation, Improved Performance - Methodology & Technology

{% hint style="info" icon="globe-pointer" %}
You can find detailed information about Harvest Autopilots here:

* **Documentation:** <https://docs.harvest.finance/how-it-works/autopilots>
* **Harvest App:** <https://app.harvest.finance/autopilot>

or read more about Earn here: [Earn](/using-oisy-wallet/earn)
{% endhint %}


# Borrow

OISY Wallet lets you unlock liquidity from assets you already hold, through simple, transparent borrowing products. You choose what to supply as collateral and what to borrow against it, while staying in control of repaying and withdrawing.

{% hint style="info" icon="dog" %}
This page explains the basics:

How borrowing works, what collateral is, how risk is measured, and how you get your assets back.
{% endhint %}

### What is Borrow?

Borrow lets you access liquidity by taking a loan against an asset you already hold, without selling it. You supply an asset as collateral, then borrow a different asset against it, up to a set loan-to-value (LTV) limit. Interest accrues on what you borrow, and you can repay or withdraw whenever you choose, as long as your position stays healthy.

Today, Borrow supports [Liquidium](/using-oisy-wallet/borrow/liquidium)

### How Borrowing Works

1. You supply an asset as collateral.

   Supplying moves it into the lending protocol, where it starts earning supply yield and automatically counts as collateral you can borrow against.
2. You borrow against your collateral.

   You choose an asset to borrow and an amount, up to the maximum your collateral allows. The borrowed funds are delivered straight to your OISY wallet.
3. Interest accrues on both sides.

   Your collateral keeps earning supply yield; your borrowed amount accrues borrow interest. Both are shown in OISY.
4. You track your position's health.

   OISY shows a health factor for your position — how close it is to the point where your collateral could be liquidated.
5. You repay to reduce risk and free up collateral.

   Repaying, in full or in part, improves your health factor. Once a borrow is fully repaid, the collateral behind it becomes withdrawable again.
6. You withdraw whenever your position allows it.

   You can withdraw supplied collateral that isn't needed to keep an existing borrow healthy.

### Who Holds My Collateral?

Unlike a bank loan, no company takes custody of your assets off-chain. When you supply collateral, it's held by the lending protocol itself, which runs onchain. OISY does not take custody of your funds — it provides the interface and signs the protocol's calls using your existing OISY identity.

This is different from simply holding a token in your wallet: once supplied, your collateral is subject to the protocol's rules, including liquidation if your position's health factor falls too far — see Understanding Liquidation Risk below.

### How Do I Get My Collateral Back?

Every borrow can be repaid, and every supply can be withdrawn, as long as doing so keeps any remaining position healthy.

* If you have no outstanding borrow, you can withdraw your full supplied balance at any time.
* If you have an outstanding borrow, you can withdraw collateral only up to the amount that keeps your position above its liquidation threshold; OISY shows this limit before you confirm.
* Repaying reduces what you owe and improves your health factor. Once a borrow is fully repaid, all of its collateral becomes withdrawable again.

### Understanding LTV and Health Factor

Two figures describe how much risk a borrow position carries:

* **Max LTV (loan-to-value)** — the most you can borrow against your collateral, as a percentage of its value. This caps how large a borrow you can open.
* **Liquidation threshold** — a higher percentage than max LTV. If your debt grows past this relative to your collateral's value, your position becomes eligible for liquidation. The gap between the two is your safety buffer.

OISY combines both into a single **health factor**, shown as a percentage: 100% means no debt at all, and the closer it gets to 0%, the closer your position is to liquidation. OISY color-codes it so you can tell your risk level at a glance:

* 🟢 Healthy — 50% or higher
* 🟠 At risk — between 15% and 50%
* 🔴 Critical — below 15%
* Liquidation happens at 0%

Health factor can move on its own over time, even without you doing anything, since interest accrues continuously on your debt — a position can drift toward liquidation just by sitting still.

### Is This Safe?

OISY does not create or operate the lending protocols it connects to.

Borrow integrates with trusted third-party lending protocols through their official smart contracts and SDKs. We highlight what you're borrowing against, how interest and liquidation work, and the risks involved — but you remain in control of the decision to open, adjust, or close a position.

As with any onchain lending protocol, borrowing carries real risk: your collateral can be liquidated if your health factor reaches 0%, and you're relying on the protocol's code functioning correctly.

### Understanding Liquidation Risk

Borrowing against collateral introduces a risk that simply holding or supplying assets does not: liquidation.

#### 1. Liquidation Risk (for any borrow position)

If your health factor reaches 0%, the protocol can liquidate (sell) enough of your collateral to cover your debt. This can happen because the value of your collateral drops, the value of what you borrowed rises, or because accrued interest has grown your debt over time — all of which push your health factor down. OISY always shows your current health factor and warns you before an action would push it into a risky range.

{% hint style="info" %}
Example

You supply 1 BTC as collateral and borrow USDC against it at a comfortable health factor. If BTC's price drops significantly, the same debt now represents a larger share of your collateral's value, so your health factor falls — potentially into the at-risk or critical range, even though you didn't touch your position.
{% endhint %}

#### 2. Underlying Asset Value Risk (for supplied collateral)

Even without any borrowing, the value of your supplied collateral still depends on the market price of the asset you supplied. If its price drops, the value of your position drops with it — separate from, and in addition to, any liquidation risk from an open borrow.

OISY shows your supplied balance, borrowed balance, and health factor separately, so you can see all three effects clearly.

### What's Coming Next

Borrow will expand to include:

* additional lending providers,
* more supported collateral and borrow assets,
* active alerts as your health factor approaches risk thresholds,
* and streamlined ways to manage multiple positions at once.

Each will follow the same principles: transparency, clear risk information, and simple UX.


# Liquidium

{% hint style="info" icon="globe-pointer" %}
You can find detailed information about Liquidium here:

* **Documentation:** <https://liquidium.fi/docs>
* **Liquidium App:** <https://app.liquidium.fi>

or read more about Borrow here: Borrow
{% endhint %}


# OISY Trade

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FUJtClMjB02Hf9jUZMUIF%2Fimage.png?alt=media&amp;token=bfe5a14c-f463-4d5b-99cb-5ffc675cbc86" alt=""><figcaption></figcaption></figure>

**OISY Trade** lets you trade tokens on a fully onchain order-book exchange, directly from your OISY wallet. Deposited funds are held by the OISY Trade canister on the Internet Computer rather than by a centralized company. But as with any onchain protocol, this comes with smart-contract risk: you're trusting the canister's code, not handing custody to a person or company.

It's a separate way to trade alongside OISY's existing **Swap**: Swap gives you an instant trade at the best price a liquidity pool offers right now. OISY Trade lets you set the price you're willing to trade at and place a limit order — it waits until the market reaches your price (or fills right away if your price already crosses the book).

#### What are limit orders

A limit order says "buy or sell this token at this price or better," instead of trading immediately at whatever the market offers. You choose:

* a **pair** — e.g. ICP priced in ckUSDC (the *base* token is what you're trading, the *quote* token is what the price is measured in)
* a **side** — Buy or Sell
* an **amount** of the base token
* a **price** you're willing to trade at

Your order then rests in the order book until another trader's order matches it, or you cancel it. If your price already crosses the current best price on the book, it fills right away instead of resting — but you're always the one who set the price.

#### How it works, in general

1. **Deposit** a supported token from your OISY wallet into OISY Trade.
2. **Place a limit order** — pick a pair, a side, an amount, and a price.
3. Your order **rests** until it's matched (filled) or you cancel it; you can track its status.
4. **Withdraw** funds back to your OISY wallet any time — you can withdraw whatever isn't currently tied up in an open order.

#### Where to find it in OISY

OISY Trade lives in a **Trading** tab under **Assets**, alongside Tokens, NFTs, and Earning. It has two sections: **My assets** (what you've deposited into OISY Trade, with an "Available" amount showing what isn't reserved by open orders) and **Orders** (Active and History). Balances held in OISY Trade also count toward your total net worth shown in the wallet.

The existing **Swap** button is unaffected — it still opens the regular Swap flow. OISY Trade is entirely separate and reached only through the Trading tab.

**Deposit**

From the Trading tab, **"+ Deposit"** opens a form where you pick one of your wallet tokens that OISY Trade supports and enter an amount. Depositing takes two onchain steps (approve, then deposit), so a small network fee applies before the funds are ready to trade with.

**Withdraw**

Each deposited token has a **Withdraw** link that opens a form pre-filled with that token. Enter how much to withdraw — only your available (free) balance can be withdrawn; anything reserved by an open order can't be, until that order fills or is canceled. A small network fee applies, so what lands back in your wallet is slightly less than what you entered.

**Create a limit order**

From the Trading tab's Orders section, **"+ Limit order"** opens the order form. Choose Buy or Sell, pick the token you're trading and the token you're pricing it in, enter the amount, and set your price — you can use a quick preset relative to the current price, or match the best available price on the book. Review the order (it flags if your price will fill immediately), then place it.

**Cancel a limit order**

Tap any order in your Active list to open its details. From there, **"Cancel order"** is available for any order that hasn't filled yet. Confirming releases the funds that were reserved for it back to your available balance.

***

#### Technical details

*For developers, integrators, and anyone who wants the underlying mechanics.*

**Architecture**

OISY Trade is a separate onchain order-book exchange (a DEX) built on the Internet Computer. It implements a central limit order book (CLOB): all order state, matching, and settlement happen inside a single canister, with an event-sourced state log for auditability. OISY's wallet UI is a client — order matching itself runs entirely inside the DEX canister.

Full technical documentation: <https://dfinity.github.io/oisy-trade/introduction.html>

**Governance & control**

The OISY Trade mainnet canister (`sy2xe-miaaa-aaaar-qb7sq-cai`) lists the **NNS Root** canister as one of its controllers — the same governance root that solely controls the ckBTC Minter, and the same NNS governance that controls the Chain Fusion Signer used elsewhere in OISY. In practice, this means upgrades to the canister that holds deposited funds are expected to go through NNS proposals rather than a single team-held key, the same governance model OISY already relies on for its native-asset signing.

**Deposit-first model & balances**

Tokens must be deposited into the DEX before they can be traded. Depositing requires an ICRC-2 approval on the token's ledger, followed by a `deposit` call to the DEX canister — both steps incur the ledger's standard transfer fee. The DEX tracks balances per user and token as:

* `free` — available for new orders or withdrawal
* `reserved` — locked by open orders

**Order matching & lifecycle**

Placing an order (`add_limit_order`) returns an order ID immediately; the matching engine processes it on its next tick. Orders move through four states: `Pending` (accepted, awaiting matching), `Open` (resting in the book), `Filled` (fully executed), or `Canceled`.

**Trading pairs & order limits**

Each pair defines a base token (what's traded) and a quote token (what the price is denominated in), plus:

* `tick_size` — smallest allowed price increment
* `lot_size` — smallest allowed quantity increment
* `min_notional` / `max_notional` — minimum and maximum order value (price × quantity)

**Fees**

Each pair sets a maker fee and a taker fee, in basis points, deducted from the proceeds at fill time (from the asset the filling side receives). Maker fees apply when an order was already resting and got matched; taker fees apply when an order matched immediately against a resting order. OISY always displays these as a percentage (e.g. "0.20%"), converted from basis points.

**API reference**

For direct canister interaction (CLI or programmatic), see the full method reference and walkthrough: <https://dfinity.github.io/oisy-trade/usage/for-users.html>


# OISY Pay

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FIroYca31skkSmxosUWMK%2FOISY-pay-url-select.jpg?alt=media&amp;token=9450a830-b15c-4e91-8fda-a2644bf37464" alt=""><figcaption></figcaption></figure>

**OISY Pay** lets you complete real-world and online payments using Open CryptoPay. It’s designed for simple checkout flows where you either scan a QR code or paste a payment link, then send the exact amount from the asset and network you choose.

#### Where you can use it

OISY Pay works with all Open CryptoPay-enabled merchants, including:

* SPAR Switzerland
* Shopware stores
* WooCommerce stores

For more details see here: <https://opencryptopay.io/ecosystem.html>

#### How it works

Merchants generate a payment request (QR code or URL) via Open CryptoPay.

You approve camera access (for QR scans) or paste a link manually, choose what you want to pay with, then confirm the transaction in OISY.

#### Supported assets

When paying, you can select from:

* ICP
* ckBTC
* VCHF
* VEUR
* BTC
* WBTC
* ETH
* USDC
* USDT
* dEURO
* ZCHF (Frankencoin)
* DAI
* BNB
* SOL

#### Pay flow

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FRX9DdGyV4Ox67adFJEht%2Fimage.png?alt=media&amp;token=ffd6f3f0-a1e0-40c7-ba64-cdb730759178" alt=""><figcaption></figcaption></figure>

1. Open OISY
2. Tap the Universal Scanner icon (top-right)
3. Choose how to enter the payment request:
   * Scan QR code (enable camera permission when prompted)
   * Paste URL (manual link input)
4. Select the asset and chain you want to pay with
5. Review recipient details (tap the arrow next to Recipient to expand)
6. Tap Pay
7. After confirmation, you’ll see a Payment Confirmed screen with the merchant name and amount<br>

#### Recipient details you can review

Before you pay, you can expand the recipient section to view:

* Name
* Address
* Country
* Phone number
* Email address
* Website

#### Payment confirmation

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FAfjruFcSd3dgPfDto5rN%2FOISY-pay-done.jpg?alt=media&amp;token=a9ba3f3f-7fb2-46c8-aea7-91cb9855fba2" alt=""><figcaption></figcaption></figure>

Once the transaction is successful, OISY displays a confirmation screen showing:

* The merchant (example: Paid at SPAR)
* The amount paid (example shown in USDC)
* “Powered by Open CryptoPay” branding for clarity on the payment rail

#### Notes

* If scanning is blocked, check your device camera permissions for OISY.
* If you received a link instead of a QR code, you can paste the URL directly to start the same flow.


# Listing new dapps in Explorer

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fo4O9OmN3daahSaQXIzj5%2FShowcase.png?alt=media&amp;token=09f9bfcf-2fda-4c54-a185-dc320c30308a" alt=""><figcaption></figcaption></figure>

To file a request to have your dApp listed in the dApps explorer of OISY Wallet, please submit this [dApp Submission Request](https://github.com/dfinity/oisy-wallet/issues/new?assignees=\&labels=\&projects=\&template=dapp_submission_request.md\&title=Request+a+dApp+to+be+listed+on+the+OISY+Wallet+dApp+Explorer).


# Listing a Token on OISY

Listing your token with OISY is simple and straightforward. We only need your:

* Ledger Canister ID
* Index Canister ID
* icrc1 logo must be a Data URL \*
* Token listed on CoinGecko \*\*

{% hint style="info" %}
\* = Not Required, but [preferred](https://docs.oisy.com/using-oisy-wallet/faq#why-is-the-token-logo-not-showing-for-a-token-in-the-wallet)\
\*\*= Not Required, but allows us to display token price
{% endhint %}

Join the [OISY Discord](https://discord.com/invite/ejBT7dQneK) server and share these details with us in the "# 🛠・dev-questions' Channel—more often than not, we can include your token in our next release.\ <br>


# Logos & Assets

A selection of OISY Wallet logos and assets for your integration.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FvCrzoRAfD3s7IdSwPB6v%2Fimage.png?alt=media&amp;token=77dad17f-dbb2-4bd3-a3ad-b0af049f20f0" alt=""><figcaption></figcaption></figure>

When integrating OISY, please use one of the logos from this archive: &#x20;

{% file src="/files/EfJBXWc3xvHdJyXl5yAs" %}

***

For most dApp integrations, we recommend using the following icon in SVG or PNG format:

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FjDa8s0EIZeFtRfxDlI4s%2Foisy-logo-mark--color.png?alt=media&amp;token=cdd7a923-ab5e-47a4-b4da-a4fe464a7e62" alt="" width="160"><figcaption><p>OISY icon</p></figcaption></figure>

{% file src="/files/AJV55PvsM7a7v02Kq9Bs" %}
SVG logo version
{% endfile %}

{% file src="/files/Mpa9UBQtpqIyQO7UEmSk" %}
PNG logo version
{% endfile %}

## Brand color

<table data-header-hidden><thead><tr><th></th><th width="249"></th></tr></thead><tbody><tr><td><h3>#0066FF</h3><p>Whenever possible, use this exact hex value to maintain visual consistency across integrations.</p></td><td><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fq2OICEGg77ImbOJD10zA%2Foisy-color.png?alt=media&amp;token=6d094cb0-4661-4dde-be64-1a7f7275b71f" alt=""></td></tr></tbody></table>

***

## "Connect with OISY" Button Guidelines

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FbnSljDKElXa6EVPsP0vE%2FButton%20guidelines.png?alt=media&amp;token=98bd736f-2254-4dcc-bb9d-d67cc4d96549" alt=""><figcaption></figcaption></figure>

Buttons are a core interactive element and often the first user interaction with OISY.\
Always align them with the OISY brand identity and apply consistently across all platforms.

### Button text

Use the full name with correct capitalization: “**OISY Wallet**”.

**✅ Good examples:**&#x20;

* "Connect with OISY Wallet"
* "Connect OISY Wallet"
* "OISY Wallet"

**❌ Avoid partial names and inconsistent capitalization:**

* "Oisy"
* "Connect with Oisy"
* "Connect Oisy Web Wallet"&#x20;

### Colors & Icons

* Primary brand color: **#0066FF**
* Alternative: approved monochrome variations only
* Avoid using random colors

<figure><picture><source srcset="/files/X7BfS8mkVBJ7Y5fYFdop" media="(prefers-color-scheme: dark)"><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FimtOjt322RIPsxdvRn6O%2FGood%20buttons.png?alt=media&amp;token=68b57711-8f8c-480f-88ca-657aedd9811e" alt=""></picture><figcaption></figcaption></figure>

### Button icons

Please use the following icons:&#x20;

{% file src="/files/2nMjgsOwgMkS8BkbDgmx" %}

### Spacing & Layout

* Maintain clear padding around text and icons
* Avoid tight or compressed spacing
* Icon must not overlap or touch text

Below you can find examples of the buttons that you should avoid using

<figure><picture><source srcset="/files/9qFgVdzJqntYiqGqoFTy" media="(prefers-color-scheme: dark)"><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F98yaYXhiMDKkNyHu8JNL%2FBad%20buttons.png?alt=media&amp;token=85e7e122-0bbb-4c72-931f-a65bef6039b9" alt=""></picture><figcaption></figcaption></figure>

### tldr: Developer Notes

* Use consistent capitalization: always **OISY Wallet**
* Apply brand color #0066FF or monochrome only
* Ensure readable contrast (WCAG AA minimum)
* Keep minimum 16px padding inside the button
* Do not abbreviate or shorten the product name

**Thanks!**&#x20;

For more info please reach out to: [Support](/using-oisy-wallet/support)


# Media Kit

This resource hub provides everything you need to cover, collaborate, or promote OISY Wallet—a next-generation, fully on-chain crypto wallet designed for security, simplicity, and decentralization.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FfpG0pgYhERu2RokNCMwI%2Fshare-image.jpg?alt=media&amp;token=c6a484bf-9a4c-4ded-9a62-bf5091eb4b7f" alt=""><figcaption></figcaption></figure>

## Project Info

OISY enables users to seamlessly manage and self-custody digital assets on multiple blockchains, simply by interacting with a rich web experience that is securely served directly into their web browsers by advanced smart contracts on the Internet Computer – without the need for web browser extensions and phone apps, which can be censored, and expose users’ private keys to danger.

## Logo usage&#x20;

Find more details on this page:&#x20;

{% content-ref url="/pages/eJNewMiFBjCs2rjPEzvy" %}
[Logos & Assets](/media/logos-and-assets)
{% endcontent-ref %}

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FvCrzoRAfD3s7IdSwPB6v%2Fimage.png?alt=media&amp;token=77dad17f-dbb2-4bd3-a3ad-b0af049f20f0" alt=""><figcaption></figcaption></figure>

***

## Product screenshots

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fkjhlpzmz5FXXyZ3DbusU%2Fapp-preview_light.png?alt=media&amp;token=142e109c-f36c-43fa-992b-253ee9e72ccc" alt=""><figcaption><p>General Overview</p></figcaption></figure>

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FGdPKsgNG8iv1FEneoMZa%2Fapp-preview_dark.png?alt=media&amp;token=9b52ca09-9824-4ae6-a935-42c3302c5427" alt=""><figcaption><p>General Overview - Dark mode</p></figcaption></figure>

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FicImUegp0rUXhpMIM0Dq%2FDesktop-light-macbook.jpg?alt=media&amp;token=c5d8f6dd-72a8-445a-977d-e82c18aab7e7" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fi4wiBpeh0yDYtBTZQUdw%2FConvert%20modal.jpg?alt=media&amp;token=e8c60105-eff7-4f7a-a4b1-2903b4c33d51" alt=""><figcaption><p>Chain Fusion Conversion Inteface</p></figcaption></figure>

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FqhPjce1rxeFRuWaUO2lf%2FSend.jpg?alt=media&amp;token=8a6fe865-59a3-44b1-bace-5c57f8afe21c" alt=""><figcaption><p>Send Interface</p></figcaption></figure>

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fwh12CEKaeMqmPdwU21tr%2FSwap.jpg?alt=media&amp;token=06bca1cf-afb2-427d-b347-2c09ddbf2593" alt=""><figcaption><p>SWAP Interface</p></figcaption></figure>

## Backgrounds

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F44YQdCWd3rLM9wm35QSf%2Fbackground-light-option-1.jpg?alt=media&amp;token=f2e4020b-4f98-4384-8528-6b85cff9443e" alt=""><figcaption><p>Light background</p></figcaption></figure>

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FJwp2toB9nHgpoEuvs2TM%2Fbackground-dark-option-2.jpg?alt=media&amp;token=c6f38fa4-d035-4e83-80f3-f6b4101c6a18" alt=""><figcaption><p>Dark background</p></figcaption></figure>

## Team information & contact details

Social media:&#x20;

* X: <https://x.com/oisy>&#x20;

{% hint style="info" %}
For media inquiries, reach out to <contact@oisy.com>
{% endhint %}


# Press Releases


# Feb 27, 2025 (OISY v1 Live)

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2Fph0aTtYJoZ5udiNoZWZS%2FRelease%201.0%20-%20smaller.jpg?alt=media&amp;token=fb763b6a-c991-453b-9724-47ff3c9a1342" alt=""><figcaption></figcaption></figure>

## OISY – the 1st fully-decentralized wallet for Bitcoin, Ethereum, Solana and ICP

*OISY enables users to seamlessly manage and self-custody digital assets on multiple blockchains, simply by interacting with a rich web experience that is securely served directly into their web browsers by advanced smart contracts on the Internet Computer – without the need for web browser extensions and phone apps, which can be censored, and expose users’ private keys to danger.*

*Zurich, Switzerland* — February 27, 9 AM ET — A revolutionary new wallet paradigm has transitioned into production: the DFINITY Foundation announces that Version 1.0 of the OISY wallet is live, as the result of its incubation of the project. OISY provides its functionality through a seamless web experience, which is served directly from the blockchain by advanced smart contracts. With OISY, the installation of risky wallet software such as web browser extensions and phone apps is not necessary, and users simply authenticate using modern passkey technology. By building on “chain key” crypto technology, OISY trustlessly integrates with Bitcoin, Ethereum, Solana and ICP, and support for more chains is planned. OISY’s source code is open source and verifiable.&#x20;

**A revolutionary wallet design addressing key risks**

\
Traditional crypto wallets take the form of web browser extensions, and phone apps, which come with several risks. Firstly, browser extensions and apps must hold their users’ private keys in plaintext to sign transactions, which can expose them to malware running on users’ computers. Secondly, the distribution of browser extensions and apps can be censored by parties such as the Chrome Web Store, and the Apple App Store (which have both censored wallets in the past). Thirdly, malicious insiders at corporations providing these services can in principle maliciously alter wallet software. Fourthly, the user must trust that the developers who created the software did not deliberately, or inadvertently, include malicious software logic themselves. With OISY, users use passkeys to authenticate themselves to smart contracts via a web experience they serve directly. Passkey technology maintains authentication data, and signs sessions, inside special secure hardware on modern phones and laptops, which keeps it safe. Meanwhile, users’ tokens are held by the smart contracts themselves, using “chain key” technology. When the smart contracts must sign blockchain transactions for their users, independent blockchain nodes cooperate to create the signatures through consensus. OISY’s entire code - frontend and backend - is implemented as smart contracts running on ICP. This means that the code of OISY cannot only be publicly audited, it can also be publicly verified that the correct code is deployed and runs on the Internet Computer. Thus, the risks of key compromise, key loss, phishing attacks and third party failures are greatly reduced.

**Totally seamless, multi-chain functionality**

\
OISY isn’t just about improving security, it's also about providing a better user experience for those wishing to self-custody digital assets on multiple blockchains. Traditional crypto wallets require users to craft transactions themselves, a process that can be cumbersome, error-prone and difficult for non-technical users to accomplish. OISY provides a more seamless user experience, where user-friendly interactions with a web experience cause smart contracts to sign transactions on their behalf, requiring less work, and less skill. Because the smart contracts leverage “chain key” technology, they can trustlessly sign transactions for users on multiple blockchains – enabling OISY users to interact with tokens and decentralized applications (dApps) on Bitcoin, Ethereum, Solana and ICP. The user experience is far more seamless and greatly improved for novices and experienced crypto users alike.

Key Features:

* An exclusively in-browser wallet experience, which is richer, more friendly, and seamless, since users do not have to sign transactions manually
* A unified wallet for BTC, ETH, SOL, and ICP, with support for more networks coming
* Users authenticate to their fully decentralized wallet, served from chain via the URL oisy.com, using passkeys.
* The smart contracts that serve the user experience custody tokens for users, and sign transactions, using “chain key” technology.
* The wallet is built exclusively from advanced smart contracts running on the Internet Computer, in full decentralization, reducing censorship and security risks, and increasing resilience.&#x20;
* Chain key technology is trustless, and multi-chain, allowing OISY to trustlessly manage tokens and interact with other blockchains without using bridging technology.
* Users authenticate to OISY using an Internet Identity, which allows users to associate multiple passkeys, and thus access their wallets from multiple devices, such as phones and laptops.
* Within the web experience, users can purchase new digital assets using fiat through a centralized onramper service that has been integrated.
* Within the web experience, users can swap digital assets with lighting speed through built-in swaps functionality that integrates with external DEXs.
* The wallet now drops random token rewards into eligible users wallets, to incentivize usage.

**Delivering World Computer functionality using the Internet Computer**

\
The “World Computer” is the amalgamation of all blockchains hosting tokens and smart contracts, and the overall vision is one of decentralization. The Internet Computer (ICP) is a blockchain with a unique architecture that helps realize this vision: it hosts advanced smart contracts that pay for their own computation (reverse gas), serve web experiences, process and store large amounts of data efficiently, and trustlessly interact with other blockchains using “chain key” cryptography. The Internet Computer is bringing the World Computer vision to life by enabling fully-decentralized, fully-onchain, and multichain experiences, such as OISY, to be created.&#x20;

The “OISY Sprinkles” program provides exciting incentives to users\
To celebrate the release of Version 1.0, OISY is kicking off the “OISY Sprinkles” program. As part of this program, at unpredictable times, the OISY project will distribute semi-random quantities of well-known tokens, such as Bitcoin and ether, into users’ wallets, to reward them for their activity.

**Dominic Williams**, Founder and President of the DFINITY Foundation: "OISY provides a wonderful example of the World Computer paradigm, which is made possible by the next-generation crypto technology provided by ICP."

**Akeel Qureshi**, Core Contributor at OISY Wallet, stated: “Technology should feel invisible when it’s working at its best. No one thinks about the TCP/IP stack when they send an email, and no one should have to think about blockchain protocols when managing their assets. With OISY, we’re stripping away the barriers, reducing friction to nothing, and making decentralized finance as seamless as it was always meant to be.”

**Pierre Samaties**, Chief Business Officer at DFINITY, added: “OISY Wallet streamlines multi-chain asset management while increasing decentralization and security. By removing the complexity of key management, OISY makes multi-chain digital asset management accessible to a wider audience.”

For more information, visit [OISY.com](http://OISY.com)

-end-<br>

***About OISY Wallet***

OISY is a fully-decentralized, fully-onchain, in-browser Web3 wallet providing multichain functionality. It is created by advanced smart contracts hosted on the Internet Computer (ICP) blockchain that serve web experiences to users, and can custody of their tokens using “chain key” technology. Users authenticate to the smart contracts over the web using passkey technology, and cause the smart contracts to seamlessly sign transactions for them through their interactions with the web experience.

***About the Internet Computer***

The Internet Computer is a blockchain network created by Internet Computer Protocol (ICP), whose main token is also called ICP. The technology involved was primarily developed by the DFINITY Foundation (founded 2016), and has benefited from more than 1000 person years of R\&D effort to date, involving a world-famous, international team. Although the Internet Computer is a blockchain, it is designed to perform the role of a cloud computing platform that hosts a new form of advanced smart contract software within a serverless environment. Internet Computer smart contract software pays for its own compute using a “reverse gas” paradigm, can serve secure web experiences directly to end users, can process and store large amounts of data efficiently onchain, and can scale. In addition to traditional blockchain applications such as DeFi, the Internet Computer can host apps such as social networks, enterprise systems and AI, fully-onchain, in the form of smart contract software. This means that Web3 apps and services can be built with complete decentralization, greatly increasing censorship resistance, security, and resilience, and enabling full autonomy where required. The Internet Computer blockchain is powered by “chain key” technology, which also allows the smart contracts it hosts to trustlessly interact with tokens and smart contracts on other blockchains, without need for bridges.&#x20;

[X](https://twitter.com/oisy) | [GitHub](https://github.com/dfinity/oisy-wallet) | [Docs](http://docs.oisy.com)

<br>


# OISY Signer changes its URL

{% hint style="info" icon="pineapple" %}
The **OISY Signer**, the client a dapp is interacting with when connecting to OISY via the signer standard, is changing its URL

* :red\_circle:  from: <mark style="color:red;">**`oisy.com/sign`**</mark>&#x20;
* :white\_check\_mark:  to: <mark style="color:green;">**`signer.oisy.com`**</mark>  or  <mark style="color:$warning;">**`legacy-signer.oisy.com`**</mark> &#x20;

<sub>**Note**</sub> <sub></sub><sub>that there is no more</sub> <sub></sub><sub>`/sign`</sub> <sub></sub><sub>path in the new URLs</sub>
{% endhint %}

### When will this happen

* The **new URLs are ready** and can be used right away
* The **previously used URL** (`oisy.com/sign`) will remain supported until **June 30, 2026**

### Why are we doing this?

End of 2025, a new version of the [@dfinity/agent](https://www.npmjs.com/package/@dfinity/agent), v5, was introduced, which is not fully backward compatible with previous versions. And [@slide-computer/signer](https://www.npmjs.com/package/@slide-computer/signer), the almost exclusively used typescript library for signer interaction on the Internet Computer (later migrated to [@icp-sdk/signer](https://www.npmjs.com/package/@icp-sdk/signer)), upgraded from v4.0.0 to v4.1.0 to include this new agent version.

There is a known incompatibility with the new agent that causes a specific combination of wallets and dapps to fail.

{% hint style="danger" icon="link-broken" %}
**Dapps that still use the agent v4 fail to connect to a wallet that already uses v5.**
{% endhint %}

This would block OISY from upgrading to the agent v5, until all dapps have upgraded to the latest @icp-sdk/signer version.

{% hint style="success" %}
To allow dapps to upgrade at their own pace, we decided to offer new signer URLs that allow all dapps to connect to a matching version of the OISY Signer.

* use `signer.oisy.com` if you have already migrated to the @icp-sdk/signer v4.1.0 or later
* use `legacy-signer.oisy.com` otherwise

So all you need to do is to override the OISY Signer URL.

:warning: Note that the 2 new signer URLs do **not** have a `/sign` anymore!

We are currently working on getting those changes directly in the underlying libraries, but this might take a bit longer to trickle fully through, since additional 3rd part libraries are involved (nfid identity kit, windoge98/pnp, ...). We will update all known versions that contain the new URLs.
{% endhint %}

### Is our App affected by this?

{% hint style="danger" %}
**YES, you are affected if you offer a signer standard connection to OISY**

The OISY Signer URL change affects all relying parties. You either need to change the OISY Signer URL in your codebase, or ensure you have a latest version of a library that has the new URL already set.
{% endhint %}

### What do we need to do?

{% hint style="success" icon="5" %}
**Dapps that already use the agent v5**, e.g. via the @slide-computer/signer v4.1.0 or later, can interact with all wallets (agent v4 or v5)

* Change your OISY Signer URL to  `signer.oisy.com`&#x20;
  {% endhint %}

{% hint style="warning" icon="4" %}
**Dapps that still use v4 of the agent**, e.g. via an earlier version of the @slide-computer/signer library, only work with wallets that also still use the agent v4.

* Change your OISY Signer URL to `legacy-signer.oisy.com`
* Plan an upgrade to a library that supports the agent v5, and then change the signer URL accordingly
  {% endhint %}

### What's the timeline?

{% hint style="info" icon="calendar" %}
This changes should be done **before June 30, 2026**. After that date, the old OISY Signer URL (`oisy.com/sign`) will not be supported anymore
{% endhint %}

{% hint style="info" icon="crystal-ball" %}
The **legacy-signer** **URL** will not be supported much longer. It's planned to be decommissioned latest in Q3 2026. So ensure to upgrade your library and switch to the `signer.oisy.com` URL.
{% endhint %}

### What library versions contain the updated URLs?

<table><thead><tr><th width="255.0120849609375">Library</th><th width="174.28411865234375">Versions</th></tr></thead><tbody><tr><td><a href="https://www.npmjs.com/package/@nfid/identitykit">@nfid/identitykit</a></td><td>2.0.0</td></tr><tr><td><a href="https://www.npmjs.com/package/@windoge98/plug-n-play">@windoge98/plug-n-play</a></td><td>-</td></tr></tbody></table>

### Additional note

This separation between OISY (`oisy.com`) and the OISY Signer (`signer.oisy.com`) also solves the issue that the signer standard fails to communicate between a dapp and a wallet if both are installed as PWA on mobile devices.

With the new setup, a user can install a dapp and OISY as PWA, and then the dapp starts a connection to the OISY Signer, a new browser window in opened instead of the OISY PWA.


# ICP Building Blocks

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](https://eprint.iacr.org/2022/506) (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](https://internetcomputer.org/how-it-works/chain-key-technology/) or start building based on [chain-key signature sample code](https://github.com/dfinity/examples/tree/master/rust/threshold-ecdsa).
* **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](https://www.w3.org/TR/webauthn-3), users can conveniently create secure sessions with their fingerprint or other biometric identifiers. Read more about [Internet Identity technology](https://internetcomputer.org/internet-identity) or [start integrating II](https://internetcomputer.org/docs/current/developer-docs/integrations/internet-identity/integrate-identity) 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](https://internetcomputer.org/how-it-works/smart-contracts-serve-the-web/) or directly start [building your first decentralized web frontend](https://internetcomputer.org/docs/current/developer-docs/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](https://internetcomputer.org/https-outcalls) to call these endpoints in a decentralized fashion. Check out the [HTTP outcalls sample code](https://internetcomputer.org/docs/current/developer-docs/integrations/https-outcalls/https-outcalls-how-to-use) to explore how to use Web 2.0 services on ICP.

{% content-ref url="/pages/wLzOAHva65Rqrqtx11FH" %}
[Build and Run Yourself](/for-developers/icp-building-blocks/build-and-run-yourself)
{% endcontent-ref %}


# Build and Run Yourself

## Prerequisites

* [x] &#x20;Install the [IC SDK](https://internetcomputer.org/docs/current/developer-docs/setup/install/index.mdx).

## Start the local replica

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](https://github.com/dfinity/oisy-wallet/blob/main/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.

## Run OISY locally

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](https://github.com/dfinity/oisy-wallet/blob/main/.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.

## Local development

See [HACKING](https://github.com/dfinity/oisy-wallet/blob/main/HACKING.md)

### **Backend**

The backend is written in Rust and you can find it under the [backend folder](https://github.com/dfinity/oisy-wallet/blob/main/src/backend). It uses the [tECDSA API](https://internetcomputer.org/docs/current/developer-docs/integrations/t-ecdsa/t-ecdsa-how-it-works) provided by IC. To find out more about tECDSA, you can read the [Eurocrypt 2022 paper](https://eprint.iacr.org/2021/1330.pdf).

If you want to locally deploy the backend only, you use the following command

```
dfx deploy backend
```

### Frontend

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
```

## Dependencies

#### [Iconly Pro](https://iconly.pro/)

Some Iconly icons are used in the project, **not included**. You must obtain a license separately.<br>

The license for this project is bought and owned by the DFINITY Foundation, please see terms and conditions [here](https://iconly.pro/pages/terms).


# How to "Connect with OISY"

## Connect with OISY to your app

For the OISY Wallet integration, here are a few options to explore:

* For React frontends, the [IdentityKit](https://nfid-identity-kit.webflow.io/) ([npm](https://www.npmjs.com/package/@nfid/identitykit), [documentation](https://qzjsg-qiaaa-aaaam-acupa-cai.icp0.io/docs)) and related [demo](https://qzjsg-qiaaa-aaaam-acupa-cai.icp0.io/demo) would be a great place to start. It’s like a WalletConnect for the Internet Computer.
* For Typescript, take a look at [@icp-sdk/signer](https://www.npmjs.com/package/@icp-sdk/signer) (which is the underlying library for IdentityKit).
  * Note: This library used to be at [@slide-computer/signer](https://www.npmjs.com/package/@slide-computer/signer) and was moved to the new repo under direct Dfinity maintenance early 2026
* We also provide a reference implementation, [@dfinity/oisy-wallet-signer](https://www.npmjs.com/package/@dfinity/oisy-wallet-signer). Its features are more opinionated and limited to transfers or approvals with ICP or ICRC ledgers, so for a more general-purpose solution, the above two options might be a better fit.
  * Demo app is here: <https://shsda-3aaaa-aaaal-amg6q-cai.icp0.io/> (link is also available in the github repo)

**Note**: OISY implements a default handler for `icrc2_approve` and `icrc2_transfer_from` messages and can display a consent message for these two methods in case the ledger does not implement the ICRC-21 standard.


# Using OISY Wallet in Your ICP dApp

This section seeks to help you connect the **OISY Wallet** to your dApp running on the Internet Computer (ICP). \
\
We'll start by explaining how dApps typically communicate with the Internet Computer and then explore how wallet integration, specifically with OISY, enhances this by enabling user-controlled actions.

## Interacting with Canisters on ICP

#### The Standard Way: `HttpAgent`

Typically, dApps on the Internet Computer interact with canisters (smart contracts) using the `HttpAgent` provided by the `@dfinity/agent-js` library. This agent allows your frontend to call canister functions directly from the browser. For dApps that don't require users to sign transactions with a personal wallet (e.g., for read-only operations or when using Internet Identity for session-based authentication where the dApp might hold a temporary delegation), `HttpAgent` is the standard approach. It handles the low-level details of message encoding, signing (with an anonymous or delegated identity), and communication with IC replicas.

You can learn more about `agent-js` and `HttpAgent` in the [Internet Computer developer documentation](https://internetcomputer.org/docs/current/developer-docs/build/agents/javascript-agent).

#### Integrating Wallets for User-Controlled Actions

When your dApp needs to perform actions on behalf of a user—like transferring tokens, voting, or making significant state changes that require the user's explicit approval and cryptographic signature from their own wallet—integrating a wallet like OISY becomes essential.

Instead of your dApp managing private keys or signing messages directly with a session identity that might have broad permissions, it delegates these sensitive operations to the user's wallet. The wallet then acts as a signer, prompting the user for consent before any action is taken, thus ensuring the user is always in control of their assets and identity.

The libraries discussed in this guide offer ways to create an agent or interact with wallet interfaces that route signing requests through the user's chosen wallet. This enables secure, user-authorized interactions with your dApp's canisters.

### Why Different Integration Approaches?

Before diving into the specific methods to integrate OISY, it's helpful to understand why there are different options and their trade-offs. The best choice for your dApp depends on several factors:

* **Development Framework:** Are you building your dApp with React, or using another JavaScript framework, or perhaps vanilla JavaScript?
* **User Interface (UI) Requirements:** Do you prefer a pre-built, ready-to-use UI component for connecting wallets, or do you need to design and implement a custom UI to match your dApp's branding?
* **Wallet Ecosystem Support:** Do you plan to support only OISY, or do you want to offer users a choice of multiple wallets (e.g., Plug, NFID, Internet Identity) through a single integration?
* **Control vs. Simplicity:** Do you need fine-grained, low-level control over the wallet interaction process, or are you looking for the quickest and simplest way to enable basic wallet functionalities?
* **Specific Features & Standards Adherence:** Some libraries might offer more convenience for certain tasks, while others might focus on strict adherence to underlying ICRC standards for maximum interoperability.

## Integration Options: Choose Your Way

Here are three primary ways to integrate OISY into your dApp:

1. [**IdentityKit:**](/for-developers/using-oisy-wallet-in-your-icp-dapp/using-identitykit-for-react) A comprehensive SDK, particularly well-suited for React applications. It provides UI components and makes it easy to support multiple wallets, including OISY. This is often the easiest way if you're using React.
2. [**signer-js**](/for-developers/using-oisy-wallet-in-your-icp-dapp/using-signer-js-library-low-level-typescript)**:** A lower-level TypeScript library that offers more control and flexibility. It's a good choice if you're not using React, need to build a custom UI, or want a standards-based approach that can work with any wallet following the relevant ICRC specifications.
3. [**@dfinity/oisy-wallet-signer**](/for-developers/using-oisy-wallet-in-your-icp-dapp/using-dfinity-oisy-wallet-signer-oisy-specific-sdk)**:** A lightweight, OISY-specific library developed by DFINITY. It's designed for straightforward integration if OISY is your primary or only wallet target and you need basic functionalities like connecting and requesting transfers.

### Technical Deep Dive: Understanding the dApp <-> Wallet Connection on ICP

With the above integration options considered, let's explore the underlying mechanisms and standards that make these interactions possible. This section is for developers interested in the technical details behind wallet communication on the Internet Computer.

When we say **"connect to a wallet"** on ICP, it means your dApp (running in the user's browser) establishes a communication channel with the user's wallet application (like OISY, which also runs in the browser, often in a separate tab or popup). The primary goal is for your dApp to request actions (like signing transactions or messages) that the wallet will perform on behalf of the user, but only *with their explicit permission*.

Here is a typical sequence of events when a user connects OISY (or a similar ICRC-compliant wallet) to your dApp:

1. **Initiate Connection & Get Identity:** The dApp requests a connection. The wallet asks the user for permission to connect to the dApp. If granted, the wallet shares the user's unique ICP identity (**Principal**) and potentially **Account Identifiers** (addresses for ICP tokens or other ICRC-1 tokens) with the dApp.
2. **Display User Context:** Your dApp can now recognize the connected user. You might display their Principal, token balances, or other user-specific information.
3. **Request Actions:** When the user wants to perform a protected action (e.g., send tokens), your dApp constructs a request for this action and sends it to the wallet.
4. **User Approval in Wallet:** *This is a critical step.* The wallet receives the request from the dApp and displays a confirmation prompt to the user. This prompt clearly describes the action the dApp wants to perform (e.g., "Allow this dApp to send 1.0 ICP to address X?"). The user must explicitly approve this request within the wallet interface. The user is always in control and can reject any request.
5. **Action Execution & Result:** If the user approves, the wallet signs the transaction using the user's private keys (which are securely managed by the wallet) and sends it to the appropriate canister on the IC. The result of the transaction (success or failure) is then relayed back to the dApp.

**ICP Wallet Signer Standards (The Rules):**\
To ensure interoperability between various dApps and wallets in the ICP ecosystem, the community has developed a set of rules and protocols, primarily through **ICRC Standards**. OISY Wallet is designed to follow these standards. Here are some of the key ones involved in dApp-wallet interaction:

* **ICRC-25: Signer Interaction Standard:** Defines the initial handshake protocol. When your dApp wants to connect to a wallet, it uses ICRC-25 to request a session. The wallet then asks the user for permission to interact with the dApp and specifies the scope of permissions (e.g., which methods the dApp can request).
* **ICRC-27: Signer Accounts Standard:** Once a connection is established via ICRC-25, this standard allows the dApp to request the user's account information from the wallet. This typically includes the user's Principal and associated account identifiers (e.g., for ICRC-1 tokens). OISY uses this to share the user's main ICP account details.
* **ICRC-49: Call Canister Standard:** This standard defines how a dApp requests the wallet to make an `update` or `query` call to a canister on the user's behalf. The dApp specifies the target canister, method name, and arguments. The wallet, after user approval, signs and sends the call.
* **ICRC-21: Consent Message Standard:** This standard aims to ensure that the wallet displays a human-readable and understandable message to the user before they approve an action requested via ICRC-49. Instead of just showing raw transaction data, the user sees a clear description of what the transaction will do (e.g., "Allow this dApp to send 1.0 ICP to address X?"). This is crucial for security and user trust.
* **ICRC-29: Signer Transport Standard:** This standard specifies *how* the dApp (client) and the wallet (signer, potentially in another browser window/tab or extension) communicate with each other. For web-based wallets like OISY, this often involves using browser `postMessage` APIs for cross-window communication.
* **Delegation (ICRC-34 & ICRC-28):** These standards (ICRC-34 for `Delegation` and ICRC-28 for `CertifiedQueryResponse`) would allow a wallet to grant *temporary, limited permissions* to a dApp. This could enable the dApp to make certain calls on the user's behalf without requiring approval for *every single* action, potentially for a specific time or for specific canister methods.<br>

{% hint style="info" %}
**VERY IMPORTANT NOTE Regarding OISY:** As of the current understanding and common implementations, **OISY Wallet does&#x20;*****not*****&#x20;broadly support delegation via ICRC-34 / ICRC-28 for dApp interactions.** This means that **every significant action** that modifies state or transfers assets (typically `update` calls) **must be explicitly approved by the user in OISY via a popup confirmation**. While this enhances security by ensuring user oversight for each sensitive operation, it can lead to more clicks for the user compared to wallets that might use delegation for session-like behavior. This is a key consideration when designing user flows and choosing integration methods (e.g., why IdentityKit's `ACCOUNTS` mode is necessary for OISY).
{% endhint %}

**In Simple Words:** When your dApp connects to OISY, they start talking using a method defined by ICRC-29. Your dApp asks for permission to interact (ICRC-25). If granted, OISY provides the user's identity details (ICRC-27). When your dApp wants to perform an action like a transfer, it sends a request to OISY (ICRC-49). OISY then shows a clear, human-readable confirmation message to the user (ICRC-21) asking for their approval before proceeding.

### How the Process Works: dApp -> OISY -> ICP Ledger

Let's visualize the flow for a common scenario: a user wants to send ICP tokens using your dApp, with OISY as their connected wallet. Both your dApp and OISY are running in the user's web browser. The ICP Ledger (the canister that manages ICP tokens) runs on the Internet Computer blockchain.

<figure><img src="https://files.risein.com/courses/ICP-OISY.png" alt=""><figcaption><p><em>Figure: How dApp, OISY, and ICP Ledger talk together.</em></p></figcaption></figure>

1. **Connect Request (dApp to OISY):**
   * The user clicks a "Connect OISY" button in your dApp.
   * Your dApp (using one of the integration libraries) initiates a connection request. This typically opens the OISY website/interface in a new tab or popup.
   * The dApp sends a connection request message using ICRC-29 (transport) and following ICRC-25 rules (signer interaction).
   * OISY receives this request and prompts the user: "dApp X wants to connect. Allow?" The user clicks "Allow" in the OISY interface. The connection is now established.
2. **Share Identity (OISY to dApp):**
   * OISY sends the user's Principal ID and relevant Account Identifier(s) back to your dApp, using the established ICRC-29 channel and following ICRC-27 rules (accounts).
   * Your dApp now knows the user's ICP identity and address. (If the user wasn't already logged into OISY, OISY would first ask them to log in, typically using their passkey/Internet Identity).
3. **Request to Send ICP (dApp to OISY):**
   * The user interacts with your dApp (e.g., fills a form and clicks "Send 1 ICP").
   * Your dApp constructs a canister call request message according to ICRC-49 rules. This message essentially says: "Please ask the user to approve a call to the `transfer` function on the ICP Ledger canister, to send 1 ICP from their account to recipient Y's account, with these parameters."
   * The dApp sends this ICRC-49 request message to OISY via the ICRC-29 transport.
4. **User Approval in OISY (OISY internal, then prompts User):**
   * OISY receives the ICRC-49 request from your dApp.
   * OISY validates the request and prepares a user-friendly consent message based on ICRC-21 rules. For example: "Confirm Transaction: Send 1.0 ICP to \[Recipient Address] from your account?"
   * OISY displays this message prominently in its interface, requiring explicit user action.
   * The user reviews the details and must click "Approve" (or a similar confirmation button). (Remember: OISY requires this approval for every such transaction due to the current lack of delegation support for dApps).
5. **Signing and Sending the Transaction (OISY to ICP Ledger):**
   * Once the user approves, OISY proceeds to sign the transaction. OISY utilizes ICP's **chain-key cryptography (specifically, threshold ECDSA)**. The user's actual private signing key material is not directly held or exposed in the browser in a traditional sense; it's managed by the IC network itself through canister smart contracts and threshold cryptography. OISY coordinates with its backend canister (which is part of the OISY wallet system on the IC) and the IC's threshold ECDSA signing mechanism to produce a valid signature for the transaction.
   * OISY (or its backend canister infrastructure) then sends the signed transaction to the target canister (in this case, the ICP Ledger canister) on the Internet Computer.
6. **Get Result and Inform dApp (ICP Ledger to OISY, then OISY to dApp):**
   * The ICP Ledger canister processes the transfer. It then sends back a result (e.g., "Success, transaction included in block number 12345" or an error message).
   * OISY receives this result from the ICP Ledger.
   * OISY relays this result back to your dApp through the established ICRC-29 communication channel.
   * Your dApp can now parse this result and update its UI accordingly (e.g., show "Transfer successful!" or an error message to the user).

Through this entire process, your dApp initiated the request for a transfer, but OISY (with the user's explicit consent) securely handled the signing and submission of the transaction, ensuring the user remained in full control of their funds and actions.

### More Tips

* **Testing Environments:** OISY typically provides a staging or test environment (e.g., `staging.oisy.com` or similar). Use this for testing your dApp integration before pointing to the production OISY URL (`oisy.com`). Ensure your dApp's network configuration (local replica, testnet, or mainnet) is compatible with the OISY environment you are targeting.
* **User Experience with Approvals:** Since OISY requires user approval for every sensitive action (due to no dApp delegation), be mindful of the user experience. If your dApp involves many transactions, this could lead to many popups. Where possible, design user flows that achieve goals with a minimal number of distinct on-chain actions. Future ICRC standards (like batch transaction proposals) might help streamline this.
* **Error Handling:** Implement robust error handling for all stages of wallet interaction: connection failures, user rejections, transaction failures, network issues, etc. Provide clear feedback to the user.
* **Stay Updated with Standards:** The ICP wallet ecosystem and ICRC standards are continually evolving. Keep an eye on official DFINITY communications, developer forums, and the GitHub repositories for the standards and libraries you use.
* **Learn More from Official Sources:**
  * **ICP Wallet Standards (ICRCs):** The [DFINITY WG Identity & Authentication GitHub repository](https://github.com/dfinity/wg-identity-authentication) is the primary source for ICRC specifications related to wallets and authentication (ICRC-21, ICRC-25, ICRC-27, ICRC-29, ICRC-49, etc.).
  * **IdentityKit Documentation:** Visit [identitykit.xyz/docs](https://identitykit.xyz/docs) for detailed guides, API references, and examples for integrating IdentityKit.
  * **Signer JS (@slide-computer/signer):** Check the [Slide Computer GitHub repositories](https://github.com/slide-computer) for `signer`, `signer-web`, and `signer-agent` documentation.
  * **@dfinity/oisy-wallet-signer Repository:** The [official GitHub repository](https://github.com/dfinity/oisy-wallet-signer) for this library will have the most current README, API details, and usage examples.
  * **DFINITY Developer Forum:** The [forum.dfinity.org](https://forum.dfinity.org) is a valuable resource for discussions, questions, and community support regarding OISY integration, ICRC standards, and general ICP development.

### Conclusion

Integrating the OISY wallet into your ICP dApp empowers users with a seamless, secure, and modern way to manage their identity and assets. Users can connect with just a few clicks, leveraging a web-based wallet that is itself a canister system secured by the Internet Computer's advanced chain-key cryptography. They retain full control by approving transactions through clear, human-readable prompts.

By utilizing the ICP signer standards (such as ICRC-21, ICRC-25, ICRC-27, and ICRC-49), your dApp's wallet integration will not only work smoothly with OISY but also maintain interoperability with other wallets in the growing ICP ecosystem that adopt these standards.

Whether you choose the convenience and multi-wallet support of **IdentityKit for React**, the fine-grained control offered by **signer-js**, or the OISY-focused simplicity of the **@dfinity/oisy-wallet-signer** library, the core capability remains the same: your dApp can securely connect to the user's OISY wallet, obtain their principal and account information, and request the signing of transactions or canister calls, all contingent on the user's explicit consent. This unlocks essential Web3 functionality like enabling users to pay with ICP or other tokens, viewing their asset balances within your dApp, or participating in governance by signing messages – all through a standardized and user-friendly wallet interaction flow.

As the Internet Computer platform and its surrounding ecosystem continue to mature, adherence to these open standards will be key to ensuring your dApp remains compatible, secure, and accessible. OISY, in particular, exemplifies the innovative potential of the IC by running entirely on-chain and aiming to bridge multiple blockchain networks within a single, user-friendly wallet interface. By integrating OISY, you offer your users a cutting-edge custody and interaction solution that requires no browser extensions or separately installed applications.

We hope this guide has provided a clear path for integrating OISY Wallet into your dApp. Happy coding, and welcome to building the next generation of decentralized applications on the Internet Computer!

### **Sources:**

*(Sources from the original document are generally still relevant but should be cross-checked if specific claims were altered. The new structure emphasizes the ICRC standards more directly, so links to those are very pertinent.)*

1. *DFINITY Support – "How to set up a web-based crypto wallet (Oisy wallet tutorial)" (*[*How to set up a web-based crypto wallet – DFINITY*](https://support.dfinity.org/hc/en-us/articles/23961015473684-How-to-set-up-a-web-based-crypto-wallet)*) – Explains OISY's on-chain nature and use of chain-key cryptography.*
2. *DFINITY Medium – "The Internet Computer Roadmap" (relevant to Chain Fusion / Toroidal Milestone for OISY's multi-chain aspects) (*[*The Internet Computer Roadmap. Key development areas with pivotal… | by DFINITY | The Internet Computer Review | Medium*](https://medium.com/dfinity/the-internet-computer-roadmap-62487bdce289)*) – Describes OISY's key properties (passkey auth, no seed phrase, ICP dApp support).*
3. *NFID IdentityKit Documentation (*[*NFID IdentityKit | Docs*](https://identitykit.xyz/docs)*) – Details on IdentityKit usage and supported ICRC standards.*
4. *DFINITY Forum – "ICRC-21 Consent Messages" (*[*ICRC-21+ (or 22) - Tokenization - Internet Computer Developer Forum*](https://forum.dfinity.org/t/icrc-21-or-22/39750)*) – Context on the importance of human-readable consent messages.*
5. *OISY Wallet Signer README – OISY Wallet Signer Introduction (*[*GitHub - dfinity/oisy-wallet-signer*](https://github.com/dfinity/oisy-wallet-signer)*) – Official source for the OISY-specific library.*
6. *Internet Computer Agent Library (agent-js) Documentation (*[*Internet Computer Developer Docs - Agents*](https://internetcomputer.org/docs/current/developer-docs/build/agents/javascript-agent)*) - For understanding HttpAgent.*
7. *ICRC Standards Repository (WG Identity & Authentication) (*[*GitHub - dfinity/wg-identity-authentication*](https://github.com/dfinity/wg-identity-authentication)*) - For specifications of ICRC-21, 25, 27, 29, 49 etc.*

```
```


# Using IdentityKit (for React)

IdentityKit makes it easy to add wallet connections to React dApps. It supports OISY and others.

**Install:**

```bash
npm install @nfid/identitykit
# or yarn add @nfid/identitykit
# or pnpm add @nfid/identitykit
```

````
**Setup:**
Wrap your main React app component with `IdentityKitProvider`. Tell it which wallets to show. _Very important: set `authType` correctly for OISY._

```jsx
import React from 'react';
import ReactDOM from 'react-dom/client';
import App from './App'; // Your main App component

// Import IdentityKit styles and components
import '@nfid/identitykit/react/styles.css';
import { IdentityKitProvider, IdentityKitAuthType, OISY } from '@nfid/identitykit/react';
// You can add other wallets too!
import { PlugWallet, NFIDWallet, InternetIdentity } from '@nfid/identitykit/react';

const root = ReactDOM.createRoot(document.getElementById('root'));

root.render(
  <React.StrictMode>
    <IdentityKitProvider
      // IMPORTANT FOR OISY: Use ACCOUNTS mode!
      // Because OISY needs approval for each action (no delegation support currently).
      authType={IdentityKitAuthType.ACCOUNTS}
      // List the wallets you want to support. We include OISY here.
      signers={[OISY, PlugWallet, NFIDWallet, InternetIdentity]}
      // Optional: canister IDs your app talks to (can improve user experience)
      // targets={["your_backend_canister_id"]}
      // Optional: your dApp's name, shown in wallet prompts
      // appName="My Awesome dApp"
      // Optional: your dApp's logo, shown in wallet prompts
      // appLogo="https://example.com/logo.png"
    >
      <App />
    </IdentityKitProvider>
  </React.StrictMode>
);
```

**Why `IdentityKitAuthType.ACCOUNTS`?** This tells IdentityKit to use an interaction mode based on ICRC-27 (getting accounts) and ICRC-49 (requesting calls), where the wallet (OISY) will prompt for approval for each transaction. This is the _only_ mode OISY currently supports because it does not implement delegation features (like ICRC-34). **You must use this mode for OISY compatibility with IdentityKit.**

**Add the Button:**
Put the `<ConnectWallet />` component in your UI (e.g., header).

```jsx
import { ConnectWallet } from '@nfid/identitykit/react';

function Navbar() {
  return (
    <nav style={{ display: 'flex', justifyContent: 'space-between', padding: '1rem' }}>
      <h1>My dApp</h1>
      <ConnectWallet /> {/* This button does the magic! */}
    </nav>
  );
}
```

This button shows "Connect Wallet". When clicked, it opens a modal listing the configured wallets (including OISY). If the user picks OISY, IdentityKit handles opening the OISY interface, managing the connection handshake, and updating the button state to "Connected" (or showing the user's principal).

**Using the Connection:**
IdentityKit provides React hooks to get user information and make canister calls.

```jsx
import React from 'react';
import { useIdentityKit, useAgent } from '@nfid/identitykit/react';
import { Actor } from '@dfinity/agent';
import { Principal } from '@dfinity/principal';
// Assume you have ICP Ledger IDL factory (e.g., from @dfinity/nns-ledger)
import { idlFactory as ledgerIdlFactory } from '@dfinity/nns-ledger'; // Or your own ICRC-1 IDL
import { AccountIdentifier } from '@dfinity/ledger-icp'; // Helper for ICP ledger accounts

const ICP_LEDGER_CANISTER_ID = 'ryjl3-tyaaa-aaaaa-aaaba-cai'; // ICP Ledger on mainnet

function UserDashboard() {
  // Get state and functions from IdentityKit
  const { principal, accounts, isConnected, disconnect } = useIdentityKit();
  // Get the special agent that talks to the connected wallet
  const agent = useAgent(); // This agent is configured to use the wallet for signing

  const handleTransfer = async () => {
    if (!isConnected || !agent || !accounts || accounts.length === 0) {
      alert('Connect wallet first!');
      return;
    }

    // Example: Send to a known principal. In a real app, this would be dynamic.
    const recipientPrincipal = Principal.fromText('uzr34-vyaaa-aaaaq-aaaea-cai'); // Example recipient (replace with actual)
    const recipientAccount = AccountIdentifier.fromPrincipal({ principal: recipientPrincipal });
    const amount = 1_000_000n; // 0.01 ICP in e8s (use BigInt 'n')

    try {
      // Create actor using the agent from IdentityKit
      // This agent will route calls through the connected wallet (OISY)
      const ledgerActor = Actor.createActor(ledgerIdlFactory, {
        agent,
        canisterId: Principal.fromText(ICP_LEDGER_CANISTER_ID),
      });

      const transferArgs = {
        to: recipientAccount.toUint8Array(),
        fee: { e8s: 10_000n }, // Standard ICP transfer fee
        memo: 0n,
        from_subaccount: [], // Use default subaccount (empty array)
        created_at_time: [], // Optional: timestamp
        amount: { e8s: amount },
      };

      // Call transfer -> This will trigger OISY popup for approval!
      console.log('Requesting transfer via OISY...');
      const blockIndex = await ledgerActor.transfer(transferArgs);
      console.log(`Transfer OK! Block index: ${blockIndex}`);
      alert(`Transfer successful! Block index: ${blockIndex}`);
    } catch (error) {
      console.error('Transfer failed:', error);
      alert(`Transfer failed: ${error.message || error}`);
    }
  };

  if (!isConnected) {
    return <p>Please connect your wallet using the button above.</p>;
  }

  return (
    <div>
      <h2>Welcome!</h2>
      <p>Connected Principal: {principal?.toText()}</p>
      {accounts && accounts.length > 0 && <p>Your Account ID (from OISY): {accounts.address}</p>}
      <button onClick={handleTransfer}>Send 0.01 ICP (Test)</button>
      <button onClick={disconnect}>Disconnect</button>
    </div>
  );
}

export default UserDashboard;
```
````

When `ledgerActor.transfer()` is called, the `agent` obtained from `useAgent()` is configured by IdentityKit to send the call request to OISY (or whichever wallet is connected). OISY then displays an approval popup to the user (because we are in `ACCOUNTS` mode, requiring explicit consent for such actions). If the user approves, OISY signs and dispatches the transaction, and the result is returned to your dApp.<br>

### &#x20;IdentityKit Summary:

Easiest for React developers, especially if multiple wallet support is desired. Handles UI components and state management for connections. Crucially, remember to use \`IdentityKitAuthType.ACCOUNTS\` for OISY due to its current lack of delegation support.


# Using Signer JS Library (Low-Level TypeScript)

This library is suitable if you need more control over the integration process, are not using React, or want to build a custom UI. It directly implements the client side of the ICRC wallet standards.

{% hint style="info" icon="money-check-pen" %}
Please refer to the repo for latest infos: [**https://www.npmjs.com/package/@icp-sdk/signer**](https://www.npmjs.com/package/@icp-sdk/signer)
{% endhint %}

**Install:**\
You'll need the core library, the web transport for browser-based wallets like OISY, and potentially the agent helper.

```bash
npm install @icp-sdk/signer @dfinity/principal @dfinity/ledger-icrc
# or yarn add ...
# or pnpm add ...
```

* `@icp-sdk/signer` — `Signer` for standardized signer interaction
* `@icp-sdk/signer/agent` — `SignerAgent` as a drop-in replacement for `HttpAgent`
* `@icp-sdk/signer/web` — `PostMessageTransport` for web-based signers
* `@icp-sdk/signer/extension` — `BrowserExtensionTransport` for browser extension signers
* `@dfinity/ledger-icrc`: Helpers for interacting with ICRC-1 ledgers (like the ICP ledger, though it's technically not ICRC-1 but similar for transfers).

**Connect to OISY (Example):**\
You need to trigger this connection process from a user action, like clicking a "Connect OISY" button.

```ts
import { Signer } from '@icp-sdk/signer';
import { PostMessageTransport, type PostMessageTransportOptions } from '@icp-sdk/signer/web';
import { SignerAgent } from '@icp-sdk/signer/agent';
import { IcrcLedgerCanister, type Account } from '@dfinity/ledger-icrc'; // Using ICRC-1 types for accounts
import { Principal } from '@dfinity/principal';
import { Actor, HttpAgent } from '@dfinity/agent'; // Actor is needed, HttpAgent might be for other non-signed calls

// Ensure you have the IDL for the ICP ledger if not using a higher-level library for it
// For this example, we'll use IcrcLedgerCanister from @dfinity/ledger-icrc which has its own IDL.

let signerInstance: Signer | null = null;
let transportInstance: PostMessageTransport | null = null;
let walletAgent: SignerAgent | null = null; // This will be the agent that uses the wallet
let userPrincipal: Principal | null = null;
let userAccountsFromWallet: Account[] | null = null; // Using ICRC-1 Account type

// OISY's official signing endpoint
const OISY_SIGN_URL = 'https://oisy.com/sign';
const ICP_LEDGER_CANISTER_ID = 'ryjl3-tyaaa-aaaaa-aaaba-cai';

async function connectOisyWithSignerJs() {
  console.log('Attempting to connect OISY with signer-js...');

  // 1. Configure and create the transport for OISY (uses ICRC-29 postMessage)
  const transportOptions: PostMessageTransportOptions = {
    targetUrl: OISY_SIGN_URL,
    // Configure window features for the popup
    windowFeatures: 'width=500,height=700,noopener,noreferrer',
  };
  transportInstance = new PostMessageTransport(transportOptions);

  // 2. Create the Signer instance with the transport
  signerInstance = new Signer({ transport: transportInstance });

  try {
    // 3. Initiate the connection (this opens the OISY window for user approval)
    // This step handles the ICRC-25 handshake.
    await transportInstance.connect();
    console.log('OISY transport connected successfully!');

    // 4. Get user accounts (uses ICRC-27)
    // This retrieves the principal and associated accounts the user has permitted.
    const accountsResult = await signerInstance.accounts();
    if (!accountsResult || accountsResult.length === 0) {
      throw new Error('No accounts found or permission denied by user.');
    }
    userAccountsFromWallet = accountsResult.map((acc) => ({
      owner: acc.owner,
      subaccount: acc.subaccount,
    }));
    userPrincipal = userAccountsFromWallet.owner; // Typically use the principal from the first account
    console.log('OISY Accounts:', userAccountsFromWallet);
    console.log('User Principal:', userPrincipal.toText());

    // 5. Create a SignerAgent (optional but highly convenient)
    // This agent will use our 'signerInstance' to sign any outgoing update calls.
    // For query calls, it can use a standard anonymous HttpAgent or be configured.
    walletAgent = await SignerAgent.create({
      signer: signerInstance,
      identity: userPrincipal, // The identity obtained from the wallet
      host: 'https://icp-api.io', // Mainnet IC boundary node URL
    });
    console.log('SignerAgent created successfully.');

    // Update your UI to reflect the connected state
    updateUIOnConnect(userPrincipal.toText(), userAccountsFromWallet); // Implement this function
  } catch (error) {
    console.error('OISY Connection failed:', error);
    alert(`OISY Connection Error: ${error.message || error}`);
    await disconnectOisyWithSignerJs(); // Clean up any partial connection
  }
}

async function disconnectOisyWithSignerJs() {
  if (transportInstance && transportInstance.connected) {
    await transportInstance.disconnect();
  }
  signerInstance = null;
  transportInstance = null;
  walletAgent = null;
  userPrincipal = null;
  userAccountsFromWallet = null;
  updateUIOnDisconnect(); // Implement this function
  console.log('Disconnected from OISY.');
}

// --- Placeholder UI update functions (you need to implement these) ---
function updateUIOnConnect(principalText: string, account: Account) {
  document.getElementById('connect-oisy-signerjs').style.display = 'none';
  document.getElementById('disconnect-oisy-signerjs').style.display = 'block';
  document.getElementById('user-info').innerText =
    `Connected: ${principalText}, Account: ${JSON.stringify(account)}`;
  document.getElementById('transfer-icp-signerjs').style.display = 'block';
}
function updateUIOnDisconnect() {
  document.getElementById('connect-oisy-signerjs').style.display = 'block';
  document.getElementById('disconnect-oisy-signerjs').style.display = 'none';
  document.getElementById('user-info').innerText = 'Not Connected';
  document.getElementById('transfer-icp-signerjs').style.display = 'none';
}

// --- Add button listeners in your HTML ---
// <button id="connect-oisy-signerjs">Connect OISY (signer-js)</button>
// <button id="disconnect-oisy-signerjs" style="display:none;">Disconnect</button>
// <p id="user-info">Not Connected</p>
// <button id="transfer-icp-signerjs" style="display:none;">Send ICP (signer-js)</button>
document
  .getElementById('connect-oisy-signerjs')
  ?.addEventListener('click', connectOisyWithSignerJs);
document
  .getElementById('disconnect-oisy-signerjs')
  ?.addEventListener('click', disconnectOisyWithSignerJs);
```

**Making Calls (Example with SignerAgent):**\
Use the `walletAgent` (which is a `SignerAgent`) to create actors and call canister methods.

```ts
// (Continuing from the previous signer-js example)

async function transferIcpWithSignerJs() {
  if (!walletAgent || !userAccountsFromWallet || userAccountsFromWallet.length === 0) {
    alert('Not connected or no accounts available!');
    return;
  }

  // Example recipient (ensure this is a valid account structure for the ledger)
  const recipientPrincipal = Principal.fromText('uzr34-vyaaa-aaaaq-aaaea-cai'); // Replace
  const recipientAccount: Account = { owner: recipientPrincipal, subaccount: [] }; // ICRC-1 style account
  const amount = 500_000n; // 0.005 ICP (500,000 e8s)

  try {
    // Use IcrcLedgerCanister helper for ICRC-1 compliant ledgers.
    // Note: The main ICP ledger is not strictly ICRC-1 but has a similar transfer method.
    // For the actual ICP ledger, you might need its specific IDL and AccountIdentifier type.
    // This example assumes an ICRC-1 ledger for simplicity with @dfinity/ledger-icrc.
    // If targeting ICP ledger, you'd use its specific `transfer` args.

    // Let's assume we are interacting with an ICRC-1 ledger canister
    const icrcLedger = IcrcLedgerCanister.create({
      agent: walletAgent, // The agent that will use OISY for signing
      canisterId: Principal.fromText('mxzaz-hqaaa-aaaar-qaada-cai'), // Example ICRC-1 ledger ID (ckBTC)
    });

    console.log('Requesting ICRC-1 transfer via signer-js agent to OISY...');
    // This call will be sent to OISY for signing via the SignerAgent -> Signer -> Transport chain.
    // OISY will show an ICRC-21 consent message.
    const blockIndex = await icrcLedger.transfer({
      to: recipientAccount,
      amount: amount,
      // fee, memo, from_subaccount, created_at_time are optional for ICRC-1 transfer
      // and might be automatically filled or handled by OISY/ledger defaults.
    });

    console.log(`ICRC-1 Transfer OK! Block index: ${blockIndex}`);
    alert(`ICRC-1 Transfer successful! Block index: ${blockIndex}`);
  } catch (error) {
    console.error('ICRC-1 Transfer failed:', error);
    alert(`ICRC-1 Transfer failed: ${error.message || error}`);
  }
}

// Add listener to a transfer button
document
  .getElementById('transfer-icp-signerjs')
  ?.addEventListener('click', transferIcpWithSignerJs);
```

When `icrcLedger.transfer` (or any other update call via an actor using `walletAgent`) is executed, the `SignerAgent` directs the signing request to OISY. OISY then presents the user with a consent popup (formatted according to ICRC-21, if the wallet supports it well). If the user approves, OISY signs the transaction, and it's dispatched to the IC.<br>

### Signer JS Summary

This approach involves more manual setup for UI and state management but offers high flexibility and direct use of ICRC standards. It's ideal for non-React projects, custom UIs, or when you need a deep, standards-compliant integration that could work with various wallets supporting ICRC-25/27/29/49.


# Using @dfinity/oisy-wallet-signer (OISY-Specific SDK)

This is a lightweight library from DFINITY created specifically for interacting with the OISY wallet. It simplifies the connection process and common actions like ICP transfers by abstracting some of the ICRC standard details.

**Install:**

```bash
npm install @dfinity/oisy-wallet-signer @dfinity/principal @dfinity/ledger-icp
# or yarn add / pnpm add
```

**Basic Usage (Example):**\
Connect to OISY and perform an ICP transfer.

```ts
import { OisyWalletSigner, ओisyWallet } from '@dfinity/oisy-wallet-signer'; // Check exact import paths from lib
import { Principal } from '@dfinity/principal';
import { AccountIdentifier, SubAccount } from '@dfinity/ledger-icp'; // For ICP ledger account types
import type { TransferArgs as IcpTransferArgs } from '@dfinity/ledger-icp'; // For ICP types

let oisyClient: ओisyWallet | null = null; // The client object from the library

const OISY_SIGN_PAGE_URL = 'https://oisy.com/sign'; // OISY's production sign page
const ICP_LEDGER_CANISTER_ID_TEXT = 'ryjl3-tyaaa-aaaaa-aaaba-cai';

async function connectWithOisyLib() {
  console.log('Connecting using @dfinity/oisy-wallet-signer...');
  try {
    // 1. Connect - library handles opening window, handshake (ICRC-25)
    // The `OisyWalletSigner.create()` method initiates the connection.
    oisyClient = await OisyWalletSigner.create({
      signPageUrl: OISY_SIGN_PAGE_URL,
      // Optional: configure window size, onDisconnect callback etc.
      // windowFeatures: 'width=500,height=700,noopener,noreferrer',
      // onDisconnect: () => {
      //   console.log("OISY disconnected callback from library!");
      //   oisyClient = null;
      //   updateUIOnDisconnectOisyLib();
      // }
      // targets: [Principal.fromText(ICP_LEDGER_CANISTER_ID_TEXT)] // Optional: specify target canisters
    });

    console.log('Connected with OISY library client.');
    const principal = oisyClient.principal;
    const accounts = await oisyClient.getAccounts(); // Uses ICRC-27
    console.log('OISY Principal from library:', principal.toText());
    console.log('OISY Accounts from library:', accounts);

    if (!accounts || accounts.length === 0) {
      throw new Error('No accounts found after connecting with OISY library.');
    }

    // Update UI
    updateUIOnConnectOisyLib(principal.toText(), accounts.identifier); // Your function
  } catch (error) {
    console.error('OISY Lib Connection failed:', error);
    alert(`OISY Lib Connection Error: ${error.message || error}`);
    oisyClient = null; // Reset on failure
    updateUIOnDisconnectOisyLib();
  }
}

async function transferWithOisyLib() {
  if (!oisyClient) {
    alert('Not connected with OISY library client!');
    return;
  }

  const recipientPrincipal = Principal.fromText('uzr34-vyaaa-aaaaq-aaaea-cai'); // Example, replace
  // For ICP ledger, we need AccountIdentifier
  const recipientAccount = AccountIdentifier.fromPrincipal({ principal: recipientPrincipal });
  const amount = 200_000n; // 0.002 ICP (200,000 e8s)

  try {
    console.log('Requesting ICP transfer using OISY library helper...');

    // The library provides an agent that can be used to create actors,
    // or it might have direct helper methods for common actions.
    // Let's assume it provides a way to get an agent or call ICP ledger directly.

    // Example: Using a generic `callCanister` if available, or a specific transfer method.
    // The exact API might differ, refer to the library's documentation.
    // Here, we assume a method similar to `callCanister` for an ICRC-49 style call.

    const transferArgs: IcpTransferArgs = {
      to: recipientAccount.toUint8Array(),
      fee: { e8s: 10_000n },
      memo: 0n,
      from_subaccount: [], // Empty for default subaccount
      created_at_time: [],
      amount: { e8s: amount },
    };

    // The `oisyClient.agent` can be used with `Actor.createActor`
    // Or if the library has a high-level transfer function:
    // const blockHeight = await oisyClient.icpTransfer(transferArgs);

    // Using the agent to make the call:
    const icpLedgerActor = Actor.createActor(
      // You'd need the ICP ledger IDL factory here
      // For example: import { idlFactory as ledgerIdlFactory } from '@dfinity/nns-ledger';
      (await import('@dfinity/nns-ledger')).idlFactory,
      {
        agent: oisyClient.agent, // The agent provided by the OISY library client
        canisterId: Principal.fromText(ICP_LEDGER_CANISTER_ID_TEXT),
      }
    );

    const blockHeight = await icpLedgerActor.transfer(transferArgs);

    console.log('ICP Transfer Result from library (Block Height):', blockHeight);
    alert(`ICP Transfer successful! Block Height: ${blockHeight}`);
  } catch (error) {
    console.error('OISY Lib ICP Transfer failed:', error);
    alert(`OISY Lib ICP Transfer failed: ${error.message || error}`);
  }
}

async function disconnectOisyLib() {
  if (oisyClient) {
    // The library should provide a disconnect method
    // await oisyClient.disconnect(); // Assuming such a method exists
    // For now, as `disconnect` is not explicitly on `ओisyWallet`, we'll just nullify
    console.log('Simulating disconnect for OISY library client.');
    oisyClient = null;
    updateUIOnDisconnectOisyLib(); // Your function
  }
}

// --- Placeholder UI functions (implement these) ---
function updateUIOnConnectOisyLib(principalText: string, accountHex: string) {
  document.getElementById('connect-oisy-lib').style.display = 'none';
  document.getElementById('disconnect-oisy-lib').style.display = 'block';
  document.getElementById('user-info-lib').innerText =
    `Connected: ${principalText}, Account: ${accountHex}`;
  document.getElementById('transfer-oisy-lib').style.display = 'block';
}
function updateUIOnDisconnectOisyLib() {
  document.getElementById('connect-oisy-lib').style.display = 'block';
  document.getElementById('disconnect-oisy-lib').style.display = 'none';
  document.getElementById('user-info-lib').innerText = 'Not Connected';
  document.getElementById('transfer-oisy-lib').style.display = 'none';
}

// --- Add button listeners in your HTML ---
// <button id="connect-oisy-lib">Connect OISY (Lib)</button>
// <button id="disconnect-oisy-lib" style="display:none;">Disconnect (Lib)</button>
// <p id="user-info-lib">Not Connected</p>
// <button id="transfer-oisy-lib" style="display:none;">Send ICP (Lib)</button>
document.getElementById('connect-oisy-lib')?.addEventListener('click', connectWithOisyLib);
document.getElementById('transfer-oisy-lib')?.addEventListener('click', transferWithOisyLib);
document.getElementById('disconnect-oisy-lib')?.addEventListener('click', disconnectOisyLib);
```

* `OisyWalletSigner.create()` handles the connection setup.
* The library provides an `agent` (`oisyClient.agent`) that is pre-configured to route signing requests through OISY. You use this agent to create actors for your canisters.
* It should also manage the communication channel and potentially offer a disconnect method (though check its latest API for specifics)<br>

### OISY Wallet Signer Summary

This library aims for simplicity when OISY is the sole or primary wallet for your dApp. It abstracts away some of the direct ICRC standard interactions, making it quicker to get started for basic OISY integration. It's less flexible if you need to support other wallets or require highly custom interaction flows. Always refer to its official documentation for the most up-to-date API and usage patterns.


# OISY Sprinkles

Episode 6 (starts April 8, 2026) – Real Activity, Real Rewards - HOURLY!

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FOmFcDOctzrBWVxs1sr1s%2FSprinkles%20season%205%20is%20here.jpg?alt=media&amp;token=519eedfa-a49d-480b-bc0e-ca4785d377b7" alt=""><figcaption></figcaption></figure>

Episode 6 brings a fresh wave of rewards for those who actively use the wallet, and new ways to benefit when the people you invite do the same.

This season is built around ongoing participation. The more you engage with OISY, the more you earn. Whether you’re showing up daily or helping others get started, Sprinkles are here to reward real usage, every step of the way.

### How it works

For this Episode, OISY will reward users who stay active with hourly token drops - and give ongoing bonuses to those who bring in users who stick around.

### How to Earn Sprinkles

To qualify for a daily Sprinkle, you must:

* **Hold**: Maintain at least $5 worth of tokens
* **Login**: Be active and log in daily
* **Transact**: Complete at least two meaningful wallet actions (swap, send, bridge, or connect a dApp) in the last 5 days

Each wallet can only win once a day.

{% hint style="info" %}
\*\* the token needs to display a price in the wallet to be eligible.
{% endhint %}

### Hourly Drops

Every hours, a wallet is selected randomly to receive a sprinkle or either ICP, ckBTC or ckUSDC.

A wallet can only win once per day.

{% hint style="success" icon="fire" %}
There is **one daily bonus drop** with a larger total value which includes all 3 tokens: ICP, ckBTC and ckUSDC
{% endhint %}

### Referral Rewards

Sprinkles now reward users who bring in quality referrals.

When someone joins using your referral link and later qualifies for a Sprinkle:

* You receive 10% of what they earn
* They keep 100% - your bonus is additional
* There are no fixed payouts for referrals
* *If they don’t remain active, you don’t benefit*

This structure rewards real usage, so make sure your buddies stay active!

### Multi-chain Multiplier

{% hint style="info" %}
Being active across multiple networks in your wallet now increases your chances of winning Sprinkles. Each eligible chain acts as a multiplier in the daily draw.
{% endhint %}

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FeKT7tV5S2tDAEYqchkzh%2Fimage.png?alt=media&amp;token=da0ab145-5b2d-4369-b273-1cf993c7330d" alt=""><figcaption></figcaption></figure>

Your Network bonus increases for each additional network where you also qualify:

* Hold at least $5 in tokens whose price is visible in OISY
* Complete at least two actions on that chain; swap, send, bridge, or connect a dApp

Each eligible chain adds one entry to your daily draw chances. The more chains you use actively, the higher your probability.

```
Example:

In a 5-day window, if you:

Hold $5+ and take 2 actions on Ethereum
Hold $5+ and take 2 actions on BNB Chain
Hold $5+ and take 2 actions on Arbitrum
Hold $5+ and take 2 actions on ICP

And you meet the login/activity requirement —
You now have a 4x chance of being selected for a Sprinkle drop vs a single-chain user.
```

### Stay Active, Earn More

Sprinkles continue to reward consistency.

The more you show up, transact, and explore what OISY has to offer, the greater your chances of earning,  both on your own and through those you bring in.

Whether you’re receiving daily Sprinkles, benefiting from referrals, or climbing the leaderboard, Episode 6 is built to reward real, ongoing participation.


# T\&C's

## OISY REWARDS INITIATIVE - TERMS AND CONDITIONS

DFINITY Foundation, domiciled at Genferstrasse 11, 8002 Zurich, Switzerland (the “Foundation”) offers the OISY Sprinkles Program (the “Initiative”), inviting Participants to engage on the OISY platform and provide valuable feedback through such engagement. These Terms and Conditions (the “Terms”) apply to your participation in the Initiative and describe the Initiative’s requirements as well as the Rewards that you may be eligible to receive.

YOUR ENTRY IS VOID WHERE PROHIBITED. YOUR PARTICIPATION IN THE INITIATIVE IS ENTIRELY VOLUNTARY, BUT IF YOU ARE PARTICIPATING IN THE INITIATIVE YOU MUST STRICTLY ADHERE TO THESE TERMS. YOU MAY RECEIVE A REWARD (WHERE PERMITTED BY LAW) UPON RANDOM SELECTION BY AN ALGORITHM. REWARDS ARE AWARDED AT THE SOLE DISCRETION OF THE FOUNDATION AND IS NOT GUARANTEED.

1. Certain Definitions.

* “Participant” means all individuals that participate in the Initiative.
* “Reward” means the tokens which may be awarded to Participants who have been randomly selected by an algorithm as a winner.
* “Intellectual Property Rights” means patent rights (including patent applications and disclosures), copyrights, trademarks, trade secret rights, work and any other tangible or intangible property rights recognized in any country or jurisdiction in the world.
* “Foundation Materials” means all information and materials that may be provided to Participant by the Foundation pursuant to the Initiative and all Intellectual Property Rights thereto.<br>

2. Eligibility; Initiative Requirements:

a. You may only participate in the Initiative if:

* You are over 18 years old at the time of participation in the Initiative;&#x20;
* You are a resident of a jurisdiction where entry to the Initiative is not prohibited by law;
* You are not a resident of, citizen, or located in a geographic area that is subject to UN-, US-, EU-, Swiss or any other sovereign country sanctions or embargoes;
* You, nor, if applicable, any third party entities that you represent (i) is listed or associated with any person or entity being listed on any of the US Department of Commerce’s Denied Persons or Entity List, the US Department of Treasury’s Specially Designated Nationals List, the EU Consolidated List of Persons, Groups and Entities Subject to EU Financial Sanctions or the Swiss SECO’s Overall List of Sanctioned Individuals, Entities and Organizations, (ii) is a person identified as a terrorist organization or any other relevant lists maintained by any governmental authority;
* Your participation in the Initiative is not in violation of any national, state, or local law or regulation applicable to you; and
* If required, you successfully pass KYC, as applicable, according to a process that, in the sole discretion of the Foundation, is deemed sufficient.

b. The Initiative is open to individuals and entities that have completed the requirements following the instructions found here <https://docs.oisy.com/rewards/get-to-know-oisy>. If you are an employee of the Foundation or any of its subsidiaries or affiliates or an immediate family member of anyone thereof, you are eligible to participate in the Initiative but are ineligible to receive Rewards.&#x20;

* All Participants grant the Foundation a royalty-free worldwide license and right in perpetuity to use their name, image, and likeness for the purposes of producing, promoting, and advertising the Initiative, the Internet Computer and/or OISY.

* Rewards. To be eligible to receive any Reward, participants must actively engage with our platform features and fulfill specific engagement criteria set for each reward cycle. REWARDS ARE DISBURSED TO PARTICIPANTS SELECTED RANDOMLY BY AN ALGORITHM AND EXECUTED VIA SMART CONTRACT. ALL DECISIONS RELATED TO THE INITIATIVE ARE FINAL AND NON-APPEALABLE. Taxes or other costs, if any, relating to receipt, acceptance and or use of Rewards are the sole responsibility of the Participant and the Foundation is not responsible for any disputes regarding reward dispersal.\ <br>

3. Entrant Requirements.

Rewards are granted without warranty of any kind from the Foundation, express or implied, without limitation. All applicable laws and regulations apply.&#x20;

5\.  Marketing and Promotion.

1. Publicity. You will not issue any press releases or similar public announcements in connection with these Terms, without the prior written approval of the Foundation.
2. Public Relations. You will: (a) conduct your business and activities in connection with these Terms in such a manner so as to promote a good image and public relations for the Foundation, the Internet Computer and OISY; (b) not engage in any unfair or deceptive trade practice involving the Foundation, the Internet Computer or OISY; and (c) not make any false, misleading or disparaging representations or statements with regard to the Foundation, the Internet Computer or OISY.

6\. Representations and Warranties.

1. Participant Representations and Warranties. You represent and warrant that: (a) you have the authority to enter into these Terms; and (b) the information submitted to the Foundation in connection with your participation in the Initiative, including in any application or Entry, is accurate and complete.
2. Disclaimer. THE INITIATIVE WEBSITE, INCLUDING BUT NOT LIMITED TO THE FOUNDATION WEBSITE, THIRD PARTY WEBSITES SUPPORTING THE INITIATIVE, AND ANY FOUNDATION MATERIALS YOU MAY HAVE ACCESS TO IN CONNECTION WITH THE INITIATIVE ARE PROVIDED “AS-IS” AND “AS AVAILABLE,” WITH ALL FAULTS, DEFECTS AND ERRORS, AND WITHOUT WARRANTY OF ANY KIND. THE FOUNDATION DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES (EXPRESS, IMPLIED, ARISING BY LAW OR OTHERWISE) IN CONNECTION WITH THESE TERMS, INCLUDING ANY REPRESENTATIONS OR WARRANTIES REGARDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. THE FOUNDATION MAKES NO REPRESENTATION OR WARRANTY THAT: (I) THE INITIATIVE, THE INITIATIVE SITE, FOUNDATION WEBSITES OR FOUNDATION MATERIALS WILL MEET YOUR REQUIREMENTS, THEIR OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE OR THAT ANY ERRORS WILL BE CORRECTED; OR (II) YOU WILL PROFIT OR DERIVE ANY ECONOMIC BENEFIT FROM YOUR PARTICIPATION IN THE INITIATIVE.<br>

7\. Intellectual Property.

1. Participant Materials. By participating in this Initiative, you agree that any creative ideas, suggestions, or other materials you submit in connection with this Initiative, in any form, are not being made in confidence or trust and that no confidential or fiduciary relationship is intended or created between you and the Foundation in any way, and that you have no expectation of review, compensation, or consideration of any type either now or in the future.
2. Foundation Materials. The Foundation hereby grants Participant, during the Term, a limited license to use the Foundation Materials solely in connection with Participant’s participation in the Initiative. Such a limited license will automatically terminate once you are no longer a Participant in the Initiative.
3. Ownership. As between you and the Foundation, the Foundation owns all right, title and interest in and to the Foundation Materials (including, the Initiative site, the Foundation website and its trademarks, as well as all associated Intellectual Property Rights thereto. There are no implied licenses granted by either party, whether by implication, estoppel or otherwise.

8\. Confidentiality. At all times, during the term of these Terms and thereafter, and to the fullest extent permitted by law, you agree to hold all Confidential Information (as defined below) in strict confidence, not to use it in any way, commercially or otherwise, except for purposes contemplated under the Initiative, and not to disclose it to others. You also agree to take all actions reasonably necessary to protect the confidentiality of all Confidential Information.\
\
As used herein, “Confidential Information” means: (i) any information, materials or knowledge regarding OISY, the Internet Computer ,the Foundation and its business, financial condition, products, programming techniques, customers, suppliers, technology or research and development that is disclosed to you or to which you have access in connection with participating in the Initiative and (ii) these Terms. Confidential Information will not include any information that: (a) is or becomes part of the public domain through no fault of you; (b) was rightfully in your possession at the time of disclosure, without restriction as to use or disclosure; or (c) you rightfully receive from a third party who has the right to disclose it and who provides it without restriction as to use or disclosure. Notwithstanding the foregoing, Confidential Information includes any information that, due to its nature or the circumstances of its disclosure, a reasonable person would know, or would have reason to know, should be treated as confidential.

9\. Release and Indemnification. You agree to fully and finally release, indemnify, defend and hold the Foundation and its parent, affiliates, subsidiaries, directors, officers, employees and agents, including advertising and promotion agencies, and assigns, and any other organizations related to the Initiative, harmless from any and all claims, injuries, damages, expenses or losses to person or property and/or liabilities of any nature that in any way arise from participation in the Initiative, your Participant Materials or acceptance or use of a Reward, including without limitation (i) any condition caused by events beyond the Foundation’s control that may cause the Initiative to be disrupted; (ii) any injuries, losses, or damages (compensatory, direct, incidental, consequential or otherwise) of any kind arising in connection with or as a result of any benefit you may receive in connection with the Initiative, or acceptance, possession, or use of a Reward, or from participation in the Initiative; and (iii) any printing or typographical errors in any materials associated with the Initiative.

10\. Limitation of Liability. NEITHER THE FOUNDATION NOR ANY OTHER PARTY INVOLVED IN THE ADMINISTRATION OF THE INITIATIVE WILL BE LIABLE FOR ANY INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, LOSS OF DATA OR GOODWILL, SERVICE INTERRUPTION, COMPUTER DAMAGE OR SYSTEM FAILURE ARISING OUT OF OR IN CONNECTION WITH THESE TERMS, WHETHER BASED ON WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR ANY OTHER LEGAL THEORY, AND WHETHER OR NOT THE FOUNDATION HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGE, EVEN IF A LIMITED REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES OR DAMAGES CAUSED BY GROSS NEGLIGENCE OR WILLFUL INTENT, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IN NO EVENT WILL THE FOUNDATION’S TOTAL LIABILITY ARISING OUT OF OR IN CONNECTION WITH THESE TERMS EXCEED FIFTY U.S. DOLLARs ($50.00).\
\
THE EXCLUSIONS AND LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN YOU AND THE FOUNDATION.<br>

11\. Termination. The term of these Terms commences from the date the Initiative begins and continues until (i) the completion of Participant’s participation in the Initiative or (ii) these Terms or the Initiative is terminated by the Foundation, whichever is earlier (the “Term”). For example, if for any reason the Initiative is not capable of running as planned due to unforeseen changes in business conditions, infection by computer virus, bugs, tampering, unauthorized intervention, fraud, technical failures, or any other causes which corrupt or affect the administration, security, fairness, integrity, or proper conduct of the Initiative, the Foundation reserves the right at its sole discretion to amend these Terms or cancel, terminate, modify or suspend the Initiative and terminate these Terms. The Foundation may also terminate these Terms for convenience upon ten (10) days’ written notice. Upon any termination, discontinuation or cancellation of the Initiative or these Terms, all provisions of these Terms which by their nature should survive will survive, including, without limitation, ownership provisions, warranty disclaimers, limitations of liability, and dispute resolution provisions.<br>

12\. Privacy Policy and Personal Information. Any personal information and Participant Materials submitted by you in connection with the Initiative will be used for the purposes described in these Terms and will otherwise be handled in accordance with the Foundation’s Privacy Policy, which may include processing or use by third parties solely within the scope of the Terms of this Agreement, located at [https://DFINITY.org/privacy-policy/](https://dfinity.org/privacy-policy/), and you acknowledge and agree to such use.<br>

13\. Assignment. You may not assign or transfer these Terms by operation of law or otherwise) without the prior written consent of the Foundation and any prohibited assignment will be null and void. The Foundation may assign these Terms or any rights hereunder without your consent. Subject to the foregoing, these Terms will bind and inure to the benefit of the parties’ permitted successors and assigns.<br>

14\. Miscellaneous. The Foundation is not responsible for transmission errors resulting in omission, interruption, deletion, defect, delay in operations or transmission, theft or destruction or unauthorized access to or alterations of Participant Materials, or for technical, network, telephone equipment, electronic, computer, hardware or software malfunctions or limitations of any kind, or inaccurate transmissions of or failure to receive entry information by the Foundation on account of technical problems or traffic congestion on the Internet or at any website or any combination thereof. The Foundation is also not responsible for injury or damage to your computer or any other damage resulting from any downloading of any materials in connection with the Initiative. In the event that any provision in these Terms is held to be invalid or unenforceable, the unenforceable part will be given effect to the greatest extent permitted by law and the remaining provisions will remain in full force and effect to the maximum extent permitted by law. The failure of a party to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. You agree that these Terms and the rules, restrictions and policies contained herein, and the Foundation’s enforcement thereof, are not intended to confer and do not confer any rights or remedies upon any person other than you and the Foundation. These Terms, any exhibits, and any other policies of the Foundation incorporated herein by reference constitute the entire agreement between the Foundation and you with respect to the subject matter of these Terms.<br>

15\. Governing Law; Dispute Resolution. These Terms will be governed by and interpreted in accordance with the laws of Switzerland excluding that body of law pertaining to conflict of laws. Any dispute, controversy, difference or claim arising out of or relating to these Terms, including the existence, validity, interpretation, performance, breach or termination thereof or any dispute regarding non-contractual obligations arising out of or relating to it shall be referred to and finally resolved by arbitration in accordance with the Swiss Rules of International Arbitration of the Swiss Arbitration Centre in force when the Notice of Arbitration is submitted in accordance with those rules. The law of this arbitration clause shall be Swiss law. The seat of arbitration shall be Zurich, Switzerland. The number of arbitrators shall be one. The arbitration proceedings shall be conducted in English.<br>

16\. Contact. If you have any questions about the Initiative or the Terms, please contact <support@oisy.com>.\ <br>

IF YOU DO NOT AGREE TO THESE TERMS, PLEASE DO NOT REGISTER OR OTHERWISE PARTICIPATE IN THE INITIATIVE.

<br>


# Archived


# OISY Sprinkles - Episode 5 (Archived)

Episode 5 (ended March 31, 2026) – Real Activity, Real Rewards

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FOmFcDOctzrBWVxs1sr1s%2FSprinkles%20season%205%20is%20here.jpg?alt=media&amp;token=519eedfa-a49d-480b-bc0e-ca4785d377b7" alt=""><figcaption></figcaption></figure>

Episode 5 brings a fresh wave of rewards for those who actively use the wallet, and new ways to benefit when the people you invite do the same.

This season is built around ongoing participation. The more you engage with OISY, the more you earn. Whether you’re showing up daily or helping others get started, Sprinkles are here to reward real usage, every step of the way.

### How it works

For this Episode, OISY will reward users who stay active with daily token drops - and give ongoing bonuses to those who bring in users who stick around.

### How to Earn Sprinkles

We’ve updated the activity rules to be more dynamic, using a 10-day rolling window.

To qualify for a daily Sprinkle, you must:

* Hold: Maintain at least $20 worth of tokens
* Login: Be active on at least 4 different days within any 10-day window
* Transact: Complete at least two meaningful wallet actions (swap, send, bridge, or connect a dApp)

Each wallet can only win once every 5-day window.

{% hint style="info" %}
\*\* the token needs to display a price in the wallet to be eligible.
{% endhint %}

### Daily Drops

Every day, 13 wallets are selected randomly to receive a Sprinkle. \
\
Rewards vary by tier:

* 1 wallet receives $5
* 1 wallet receives $4
* 1 wallet receives $3
* 2 wallets receive $2
* 8 wallets receive $1

A wallet can only win once every 5-day window.

### Referral Rewards

Sprinkles now reward users who bring in quality referrals.

When someone joins using your referral link and later qualifies for a Sprinkle:

* You receive 10% of what they earn
* They keep 100% - your bonus is additional
* There are no fixed payouts for referrals
* *If they don’t remain active, you don’t benefit*

This structure rewards real usage, so make sure your buddies stay active!

### Multi-chain Multiplier

Being active across multiple networks in your wallet now increases your chances of winning Sprinkles. Each eligible chain acts as a multiplier in the daily draw.

To qualify on any chain:

* Hold at least $20 in tokens whose price is visible in OISY
* Complete at least two actions on that chain; swap, send, bridge, or connect a dApp<br>

Each eligible chain adds one entry to your daily draw chances. The more chains you use actively, the higher your probability.

```
Example:

In a 10-day window, if you:

Hold $20+ and take 2 actions on Ethereum
Hold $20+ and take 2 actions on BNB Chain
Hold $20+ and take 2 actions on Arbitrum
Hold $20+ and take 2 actions on ICP

And you meet the login/activity requirement —
You now have a 4x chance of being selected for a Sprinkle drop vs a single-chain user.
```

### Referral Bonus

Each week, 10 active referrer–referee pairs will be randomly selected from the eligible pool.

* If both wallets are still active, each user receives a bonus
* A referrer can only win once per day
* A referee can only be paired once per week

### Stay Active, Earn More

Sprinkles continue to reward consistency.

The more you show up, transact, and explore what OISY has to offer, the greater your chances of earning,  both on your own and through those you bring in.

Whether you’re receiving daily Sprinkles, benefiting from referrals, or climbing the leaderboard, Episode 5 is built to reward real, ongoing participation.


# T\&C's

## OISY REWARDS INITIATIVE - TERMS AND CONDITIONS

DFINITY Foundation, domiciled at Genferstrasse 11, 8002 Zurich, Switzerland (the “Foundation”) offers the OISY Sprinkles Program (the “Initiative”), inviting Participants to engage on the OISY platform and provide valuable feedback through such engagement. These Terms and Conditions (the “Terms”) apply to your participation in the Initiative and describe the Initiative’s requirements as well as the Rewards that you may be eligible to receive.

YOUR ENTRY IS VOID WHERE PROHIBITED. YOUR PARTICIPATION IN THE INITIATIVE IS ENTIRELY VOLUNTARY, BUT IF YOU ARE PARTICIPATING IN THE INITIATIVE YOU MUST STRICTLY ADHERE TO THESE TERMS. YOU MAY RECEIVE A REWARD (WHERE PERMITTED BY LAW) UPON RANDOM SELECTION BY AN ALGORITHM. REWARDS ARE AWARDED AT THE SOLE DISCRETION OF THE FOUNDATION AND IS NOT GUARANTEED.

1. Certain Definitions.

* “Participant” means all individuals that participate in the Initiative.
* “Reward” means the tokens which may be awarded to Participants who have been randomly selected by an algorithm as a winner.
* “Intellectual Property Rights” means patent rights (including patent applications and disclosures), copyrights, trademarks, trade secret rights, work and any other tangible or intangible property rights recognized in any country or jurisdiction in the world.
* “Foundation Materials” means all information and materials that may be provided to Participant by the Foundation pursuant to the Initiative and all Intellectual Property Rights thereto.<br>

2. Eligibility; Initiative Requirements:

a. You may only participate in the Initiative if:

* You are over 18 years old at the time of participation in the Initiative;&#x20;
* You are a resident of a jurisdiction where entry to the Initiative is not prohibited by law;
* You are not a resident of, citizen, or located in a geographic area that is subject to UN-, US-, EU-, Swiss or any other sovereign country sanctions or embargoes;
* You, nor, if applicable, any third party entities that you represent (i) is listed or associated with any person or entity being listed on any of the US Department of Commerce’s Denied Persons or Entity List, the US Department of Treasury’s Specially Designated Nationals List, the EU Consolidated List of Persons, Groups and Entities Subject to EU Financial Sanctions or the Swiss SECO’s Overall List of Sanctioned Individuals, Entities and Organizations, (ii) is a person identified as a terrorist organization or any other relevant lists maintained by any governmental authority;
* Your participation in the Initiative is not in violation of any national, state, or local law or regulation applicable to you; and
* If required, you successfully pass KYC, as applicable, according to a process that, in the sole discretion of the Foundation, is deemed sufficient.

b. The Initiative is open to individuals and entities that have completed the requirements following the instructions found here <https://docs.oisy.com/rewards/get-to-know-oisy>. If you are an employee of the Foundation or any of its subsidiaries or affiliates or an immediate family member of anyone thereof, you are eligible to participate in the Initiative but are ineligible to receive Rewards.&#x20;

* All Participants grant the Foundation a royalty-free worldwide license and right in perpetuity to use their name, image, and likeness for the purposes of producing, promoting, and advertising the Initiative, the Internet Computer and/or OISY.

* Rewards. To be eligible to receive any Reward, participants must actively engage with our platform features and fulfill specific engagement criteria set for each reward cycle. REWARDS ARE DISBURSED TO PARTICIPANTS SELECTED RANDOMLY BY AN ALGORITHM AND EXECUTED VIA SMART CONTRACT. ALL DECISIONS RELATED TO THE INITIATIVE ARE FINAL AND NON-APPEALABLE. Taxes or other costs, if any, relating to receipt, acceptance and or use of Rewards are the sole responsibility of the Participant and the Foundation is not responsible for any disputes regarding reward dispersal.\ <br>

3. Entrant Requirements.

Rewards are granted without warranty of any kind from the Foundation, express or implied, without limitation. All applicable laws and regulations apply.&#x20;

5\.  Marketing and Promotion.

1. Publicity. You will not issue any press releases or similar public announcements in connection with these Terms, without the prior written approval of the Foundation.
2. Public Relations. You will: (a) conduct your business and activities in connection with these Terms in such a manner so as to promote a good image and public relations for the Foundation, the Internet Computer and OISY; (b) not engage in any unfair or deceptive trade practice involving the Foundation, the Internet Computer or OISY; and (c) not make any false, misleading or disparaging representations or statements with regard to the Foundation, the Internet Computer or OISY.

6\. Representations and Warranties.

1. Participant Representations and Warranties. You represent and warrant that: (a) you have the authority to enter into these Terms; and (b) the information submitted to the Foundation in connection with your participation in the Initiative, including in any application or Entry, is accurate and complete.
2. Disclaimer. THE INITIATIVE WEBSITE, INCLUDING BUT NOT LIMITED TO THE FOUNDATION WEBSITE, THIRD PARTY WEBSITES SUPPORTING THE INITIATIVE, AND ANY FOUNDATION MATERIALS YOU MAY HAVE ACCESS TO IN CONNECTION WITH THE INITIATIVE ARE PROVIDED “AS-IS” AND “AS AVAILABLE,” WITH ALL FAULTS, DEFECTS AND ERRORS, AND WITHOUT WARRANTY OF ANY KIND. THE FOUNDATION DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES (EXPRESS, IMPLIED, ARISING BY LAW OR OTHERWISE) IN CONNECTION WITH THESE TERMS, INCLUDING ANY REPRESENTATIONS OR WARRANTIES REGARDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. THE FOUNDATION MAKES NO REPRESENTATION OR WARRANTY THAT: (I) THE INITIATIVE, THE INITIATIVE SITE, FOUNDATION WEBSITES OR FOUNDATION MATERIALS WILL MEET YOUR REQUIREMENTS, THEIR OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE OR THAT ANY ERRORS WILL BE CORRECTED; OR (II) YOU WILL PROFIT OR DERIVE ANY ECONOMIC BENEFIT FROM YOUR PARTICIPATION IN THE INITIATIVE.<br>

7\. Intellectual Property.

1. Participant Materials. By participating in this Initiative, you agree that any creative ideas, suggestions, or other materials you submit in connection with this Initiative, in any form, are not being made in confidence or trust and that no confidential or fiduciary relationship is intended or created between you and the Foundation in any way, and that you have no expectation of review, compensation, or consideration of any type either now or in the future.
2. Foundation Materials. The Foundation hereby grants Participant, during the Term, a limited license to use the Foundation Materials solely in connection with Participant’s participation in the Initiative. Such a limited license will automatically terminate once you are no longer a Participant in the Initiative.
3. Ownership. As between you and the Foundation, the Foundation owns all right, title and interest in and to the Foundation Materials (including, the Initiative site, the Foundation website and its trademarks, as well as all associated Intellectual Property Rights thereto. There are no implied licenses granted by either party, whether by implication, estoppel or otherwise.

8\. Confidentiality. At all times, during the term of these Terms and thereafter, and to the fullest extent permitted by law, you agree to hold all Confidential Information (as defined below) in strict confidence, not to use it in any way, commercially or otherwise, except for purposes contemplated under the Initiative, and not to disclose it to others. You also agree to take all actions reasonably necessary to protect the confidentiality of all Confidential Information.\
\
As used herein, “Confidential Information” means: (i) any information, materials or knowledge regarding OISY, the Internet Computer ,the Foundation and its business, financial condition, products, programming techniques, customers, suppliers, technology or research and development that is disclosed to you or to which you have access in connection with participating in the Initiative and (ii) these Terms. Confidential Information will not include any information that: (a) is or becomes part of the public domain through no fault of you; (b) was rightfully in your possession at the time of disclosure, without restriction as to use or disclosure; or (c) you rightfully receive from a third party who has the right to disclose it and who provides it without restriction as to use or disclosure. Notwithstanding the foregoing, Confidential Information includes any information that, due to its nature or the circumstances of its disclosure, a reasonable person would know, or would have reason to know, should be treated as confidential.

9\. Release and Indemnification. You agree to fully and finally release, indemnify, defend and hold the Foundation and its parent, affiliates, subsidiaries, directors, officers, employees and agents, including advertising and promotion agencies, and assigns, and any other organizations related to the Initiative, harmless from any and all claims, injuries, damages, expenses or losses to person or property and/or liabilities of any nature that in any way arise from participation in the Initiative, your Participant Materials or acceptance or use of a Reward, including without limitation (i) any condition caused by events beyond the Foundation’s control that may cause the Initiative to be disrupted; (ii) any injuries, losses, or damages (compensatory, direct, incidental, consequential or otherwise) of any kind arising in connection with or as a result of any benefit you may receive in connection with the Initiative, or acceptance, possession, or use of a Reward, or from participation in the Initiative; and (iii) any printing or typographical errors in any materials associated with the Initiative.

10\. Limitation of Liability. NEITHER THE FOUNDATION NOR ANY OTHER PARTY INVOLVED IN THE ADMINISTRATION OF THE INITIATIVE WILL BE LIABLE FOR ANY INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, LOSS OF DATA OR GOODWILL, SERVICE INTERRUPTION, COMPUTER DAMAGE OR SYSTEM FAILURE ARISING OUT OF OR IN CONNECTION WITH THESE TERMS, WHETHER BASED ON WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR ANY OTHER LEGAL THEORY, AND WHETHER OR NOT THE FOUNDATION HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGE, EVEN IF A LIMITED REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES OR DAMAGES CAUSED BY GROSS NEGLIGENCE OR WILLFUL INTENT, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IN NO EVENT WILL THE FOUNDATION’S TOTAL LIABILITY ARISING OUT OF OR IN CONNECTION WITH THESE TERMS EXCEED FIFTY U.S. DOLLARs ($50.00).\
\
THE EXCLUSIONS AND LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN YOU AND THE FOUNDATION.<br>

11\. Termination. The term of these Terms commences from the date the Initiative begins and continues until (i) the completion of Participant’s participation in the Initiative or (ii) these Terms or the Initiative is terminated by the Foundation, whichever is earlier (the “Term”). For example, if for any reason the Initiative is not capable of running as planned due to unforeseen changes in business conditions, infection by computer virus, bugs, tampering, unauthorized intervention, fraud, technical failures, or any other causes which corrupt or affect the administration, security, fairness, integrity, or proper conduct of the Initiative, the Foundation reserves the right at its sole discretion to amend these Terms or cancel, terminate, modify or suspend the Initiative and terminate these Terms. The Foundation may also terminate these Terms for convenience upon ten (10) days’ written notice. Upon any termination, discontinuation or cancellation of the Initiative or these Terms, all provisions of these Terms which by their nature should survive will survive, including, without limitation, ownership provisions, warranty disclaimers, limitations of liability, and dispute resolution provisions.<br>

12\. Privacy Policy and Personal Information. Any personal information and Participant Materials submitted by you in connection with the Initiative will be used for the purposes described in these Terms and will otherwise be handled in accordance with the Foundation’s Privacy Policy, which may include processing or use by third parties solely within the scope of the Terms of this Agreement, located at [https://DFINITY.org/privacy-policy/](https://dfinity.org/privacy-policy/), and you acknowledge and agree to such use.<br>

13\. Assignment. You may not assign or transfer these Terms by operation of law or otherwise) without the prior written consent of the Foundation and any prohibited assignment will be null and void. The Foundation may assign these Terms or any rights hereunder without your consent. Subject to the foregoing, these Terms will bind and inure to the benefit of the parties’ permitted successors and assigns.<br>

14\. Miscellaneous. The Foundation is not responsible for transmission errors resulting in omission, interruption, deletion, defect, delay in operations or transmission, theft or destruction or unauthorized access to or alterations of Participant Materials, or for technical, network, telephone equipment, electronic, computer, hardware or software malfunctions or limitations of any kind, or inaccurate transmissions of or failure to receive entry information by the Foundation on account of technical problems or traffic congestion on the Internet or at any website or any combination thereof. The Foundation is also not responsible for injury or damage to your computer or any other damage resulting from any downloading of any materials in connection with the Initiative. In the event that any provision in these Terms is held to be invalid or unenforceable, the unenforceable part will be given effect to the greatest extent permitted by law and the remaining provisions will remain in full force and effect to the maximum extent permitted by law. The failure of a party to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. You agree that these Terms and the rules, restrictions and policies contained herein, and the Foundation’s enforcement thereof, are not intended to confer and do not confer any rights or remedies upon any person other than you and the Foundation. These Terms, any exhibits, and any other policies of the Foundation incorporated herein by reference constitute the entire agreement between the Foundation and you with respect to the subject matter of these Terms.<br>

15\. Governing Law; Dispute Resolution. These Terms will be governed by and interpreted in accordance with the laws of Switzerland excluding that body of law pertaining to conflict of laws. Any dispute, controversy, difference or claim arising out of or relating to these Terms, including the existence, validity, interpretation, performance, breach or termination thereof or any dispute regarding non-contractual obligations arising out of or relating to it shall be referred to and finally resolved by arbitration in accordance with the Swiss Rules of International Arbitration of the Swiss Arbitration Centre in force when the Notice of Arbitration is submitted in accordance with those rules. The law of this arbitration clause shall be Swiss law. The seat of arbitration shall be Zurich, Switzerland. The number of arbitrators shall be one. The arbitration proceedings shall be conducted in English.<br>

16\. Contact. If you have any questions about the Initiative or the Terms, please contact <support@oisy.com>.\ <br>

IF YOU DO NOT AGREE TO THESE TERMS, PLEASE DO NOT REGISTER OR OTHERWISE PARTICIPATE IN THE INITIATIVE.

<br>


# OISY Sprinkles - Episode 4 (Archived)

Episode 4 (Ended Sept 18) – A Focus on Referrals

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FCQpNKwsC71lhhczRPpRr%2FSprinkles%20season%204.jpg?alt=media&amp;token=1ff78eb2-10ed-4bf8-9d9d-f976df36e86d" alt=""><figcaption></figcaption></figure>

Episode 4 builds on what worked, and simplifies what didn’t - It also includes a $200 jackpot for referrals

Sprinkles are still awarded randomly each day to active wallets. What’s new is a refined referral structure and clearer eligibility windows, designed to reward both individual activity and simple, high-quality referrals.

### How it works

For \~45 days, OISY will reward users who stay active with daily token drops and give bonuses to those who bring others in.

### How to Earn Sprinkles

We’re keeping the core rewards structure in place, so all active OISY users can continue earning as before:

* **Hold:** Maintain at least $20 worth tokens\*\*
* **Login:** Check in at least once every 5 days.
* **Transact:** Complete at least two transactions every 5 days.

Each wallet can only win once every 5-day window.

{% hint style="info" %}
\*\* the token needs to display a price in the wallet to be eligible.
{% endhint %}

### Daily Drops

Every day, 13 wallets are selected randomly to receive a Sprinkle. \
\
Rewards vary by tier:

* 1 wallet receives $5
* 1 wallet receives $4
* 1 wallet receives $3
* 2 wallets receive $2
* 8 wallets receive $1
* Random Jackpot Bonuses

As always, winners are selected from the pool of eligible users. A wallet may only win once per 5-day window.

### Guaranteed Referral Rewards

Referrals start fresh as Episode 4 Begins. If you [refer](/using-oisy-wallet/how-tos/generate-referral-link) 4 new wallets that meet the same 5-day activity criteria:

* You receive $1
* Each of the 4 referees receives $0.20

Users will be notified when their referrer earns a bonus—referrals are fully transparent this season.

There’s **no cap** on how many times you can do this.

### Jackpot Bonus

Two additional mechanics are active this season:

1. **Random Jackpots**: Every 10 days, one eligible user will receive a $50 bonus.
2. **Referral Leader:** The top 4 referrers (with more than 10 activated referrals) will each receive a $200 bonus at the end of the episode.

### Want us to extend the campaign?

Want OISY Sprinkles to keep going? So do we! If a set number of new, active wallets are deployed, we’ll extend the campaign into Episode 4.

### Stay Active, Earn More

Whether you’re earning through activity, referring friends, or winning the Jackpot, there’s still plenty of BTC for the taking. Keep using OISY Wallet, and you might just wake up to a surprise in yours.<br>

<p align="center"><em>No forms. No claims. No gas.</em></p>

<p align="center"><em>Just stay active- and if you refer, make it count.</em></p>

<br>


# T\&C's

## OISY REWARDS INITIATIVE - TERMS AND CONDITIONS

DFINITY Foundation, domiciled at Genferstrasse 11, 8002 Zurich, Switzerland (the “Foundation”) offers the OISY Sprinkles Program (the “Initiative”), inviting Participants to engage on the OISY platform and provide valuable feedback through such engagement. These Terms and Conditions (the “Terms”) apply to your participation in the Initiative and describe the Initiative’s requirements as well as the Rewards that you may be eligible to receive.

YOUR ENTRY IS VOID WHERE PROHIBITED. YOUR PARTICIPATION IN THE INITIATIVE IS ENTIRELY VOLUNTARY, BUT IF YOU ARE PARTICIPATING IN THE INITIATIVE YOU MUST STRICTLY ADHERE TO THESE TERMS. YOU MAY RECEIVE A REWARD (WHERE PERMITTED BY LAW) UPON RANDOM SELECTION BY AN ALGORITHM. REWARDS ARE AWARDED AT THE SOLE DISCRETION OF THE FOUNDATION AND IS NOT GUARANTEED.

1. Certain Definitions.

* “Participant” means all individuals that participate in the Initiative.
* “Reward” means the tokens which may be awarded to Participants who have been randomly selected by an algorithm as a winner.
* “Intellectual Property Rights” means patent rights (including patent applications and disclosures), copyrights, trademarks, trade secret rights, work and any other tangible or intangible property rights recognized in any country or jurisdiction in the world.
* “Foundation Materials” means all information and materials that may be provided to Participant by the Foundation pursuant to the Initiative and all Intellectual Property Rights thereto.<br>

2. Eligibility; Initiative Requirements:

a. You may only participate in the Initiative if:

* You are over 18 years old at the time of participation in the Initiative;&#x20;
* You are a resident of a jurisdiction where entry to the Initiative is not prohibited by law;
* You are not a resident of, citizen, or located in a geographic area that is subject to UN-, US-, EU-, Swiss or any other sovereign country sanctions or embargoes;
* You, nor, if applicable, any third party entities that you represent (i) is listed or associated with any person or entity being listed on any of the US Department of Commerce’s Denied Persons or Entity List, the US Department of Treasury’s Specially Designated Nationals List, the EU Consolidated List of Persons, Groups and Entities Subject to EU Financial Sanctions or the Swiss SECO’s Overall List of Sanctioned Individuals, Entities and Organizations, (ii) is a person identified as a terrorist organization or any other relevant lists maintained by any governmental authority;
* Your participation in the Initiative is not in violation of any national, state, or local law or regulation applicable to you; and
* If required, you successfully pass KYC, as applicable, according to a process that, in the sole discretion of the Foundation, is deemed sufficient.

b. The Initiative is open to individuals and entities that have completed the requirements following the instructions found here <https://docs.oisy.com/rewards/get-to-know-oisy>. If you are an employee of the Foundation or any of its subsidiaries or affiliates or an immediate family member of anyone thereof, you are eligible to participate in the Initiative but are ineligible to receive Rewards.&#x20;

* All Participants grant the Foundation a royalty-free worldwide license and right in perpetuity to use their name, image, and likeness for the purposes of producing, promoting, and advertising the Initiative, the Internet Computer and/or OISY.

* Rewards. To be eligible to receive any Reward, participants must actively engage with our platform features and fulfill specific engagement criteria set for each reward cycle. REWARDS ARE DISBURSED TO PARTICIPANTS SELECTED RANDOMLY BY AN ALGORITHM AND EXECUTED VIA SMART CONTRACT. ALL DECISIONS RELATED TO THE INITIATIVE ARE FINAL AND NON-APPEALABLE. Taxes or other costs, if any, relating to receipt, acceptance and or use of Rewards are the sole responsibility of the Participant and the Foundation is not responsible for any disputes regarding reward dispersal.\ <br>

3. Entrant Requirements.

Rewards are granted without warranty of any kind from the Foundation, express or implied, without limitation. All applicable laws and regulations apply.&#x20;

5\.  Marketing and Promotion.

1. Publicity. You will not issue any press releases or similar public announcements in connection with these Terms, without the prior written approval of the Foundation.
2. Public Relations. You will: (a) conduct your business and activities in connection with these Terms in such a manner so as to promote a good image and public relations for the Foundation, the Internet Computer and OISY; (b) not engage in any unfair or deceptive trade practice involving the Foundation, the Internet Computer or OISY; and (c) not make any false, misleading or disparaging representations or statements with regard to the Foundation, the Internet Computer or OISY.

6\. Representations and Warranties.

1. Participant Representations and Warranties. You represent and warrant that: (a) you have the authority to enter into these Terms; and (b) the information submitted to the Foundation in connection with your participation in the Initiative, including in any application or Entry, is accurate and complete.
2. Disclaimer. THE INITIATIVE WEBSITE, INCLUDING BUT NOT LIMITED TO THE FOUNDATION WEBSITE, THIRD PARTY WEBSITES SUPPORTING THE INITIATIVE, AND ANY FOUNDATION MATERIALS YOU MAY HAVE ACCESS TO IN CONNECTION WITH THE INITIATIVE ARE PROVIDED “AS-IS” AND “AS AVAILABLE,” WITH ALL FAULTS, DEFECTS AND ERRORS, AND WITHOUT WARRANTY OF ANY KIND. THE FOUNDATION DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES (EXPRESS, IMPLIED, ARISING BY LAW OR OTHERWISE) IN CONNECTION WITH THESE TERMS, INCLUDING ANY REPRESENTATIONS OR WARRANTIES REGARDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. THE FOUNDATION MAKES NO REPRESENTATION OR WARRANTY THAT: (I) THE INITIATIVE, THE INITIATIVE SITE, FOUNDATION WEBSITES OR FOUNDATION MATERIALS WILL MEET YOUR REQUIREMENTS, THEIR OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE OR THAT ANY ERRORS WILL BE CORRECTED; OR (II) YOU WILL PROFIT OR DERIVE ANY ECONOMIC BENEFIT FROM YOUR PARTICIPATION IN THE INITIATIVE.<br>

7\. Intellectual Property.

1. Participant Materials. By participating in this Initiative, you agree that any creative ideas, suggestions, or other materials you submit in connection with this Initiative, in any form, are not being made in confidence or trust and that no confidential or fiduciary relationship is intended or created between you and the Foundation in any way, and that you have no expectation of review, compensation, or consideration of any type either now or in the future.
2. Foundation Materials. The Foundation hereby grants Participant, during the Term, a limited license to use the Foundation Materials solely in connection with Participant’s participation in the Initiative. Such a limited license will automatically terminate once you are no longer a Participant in the Initiative.
3. Ownership. As between you and the Foundation, the Foundation owns all right, title and interest in and to the Foundation Materials (including, the Initiative site, the Foundation website and its trademarks, as well as all associated Intellectual Property Rights thereto. There are no implied licenses granted by either party, whether by implication, estoppel or otherwise.

8\. Confidentiality. At all times, during the term of these Terms and thereafter, and to the fullest extent permitted by law, you agree to hold all Confidential Information (as defined below) in strict confidence, not to use it in any way, commercially or otherwise, except for purposes contemplated under the Initiative, and not to disclose it to others. You also agree to take all actions reasonably necessary to protect the confidentiality of all Confidential Information.\
\
As used herein, “Confidential Information” means: (i) any information, materials or knowledge regarding OISY, the Internet Computer ,the Foundation and its business, financial condition, products, programming techniques, customers, suppliers, technology or research and development that is disclosed to you or to which you have access in connection with participating in the Initiative and (ii) these Terms. Confidential Information will not include any information that: (a) is or becomes part of the public domain through no fault of you; (b) was rightfully in your possession at the time of disclosure, without restriction as to use or disclosure; or (c) you rightfully receive from a third party who has the right to disclose it and who provides it without restriction as to use or disclosure. Notwithstanding the foregoing, Confidential Information includes any information that, due to its nature or the circumstances of its disclosure, a reasonable person would know, or would have reason to know, should be treated as confidential.

9\. Release and Indemnification. You agree to fully and finally release, indemnify, defend and hold the Foundation and its parent, affiliates, subsidiaries, directors, officers, employees and agents, including advertising and promotion agencies, and assigns, and any other organizations related to the Initiative, harmless from any and all claims, injuries, damages, expenses or losses to person or property and/or liabilities of any nature that in any way arise from participation in the Initiative, your Participant Materials or acceptance or use of a Reward, including without limitation (i) any condition caused by events beyond the Foundation’s control that may cause the Initiative to be disrupted; (ii) any injuries, losses, or damages (compensatory, direct, incidental, consequential or otherwise) of any kind arising in connection with or as a result of any benefit you may receive in connection with the Initiative, or acceptance, possession, or use of a Reward, or from participation in the Initiative; and (iii) any printing or typographical errors in any materials associated with the Initiative.

10\. Limitation of Liability. NEITHER THE FOUNDATION NOR ANY OTHER PARTY INVOLVED IN THE ADMINISTRATION OF THE INITIATIVE WILL BE LIABLE FOR ANY INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, LOSS OF DATA OR GOODWILL, SERVICE INTERRUPTION, COMPUTER DAMAGE OR SYSTEM FAILURE ARISING OUT OF OR IN CONNECTION WITH THESE TERMS, WHETHER BASED ON WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR ANY OTHER LEGAL THEORY, AND WHETHER OR NOT THE FOUNDATION HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGE, EVEN IF A LIMITED REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES OR DAMAGES CAUSED BY GROSS NEGLIGENCE OR WILLFUL INTENT, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IN NO EVENT WILL THE FOUNDATION’S TOTAL LIABILITY ARISING OUT OF OR IN CONNECTION WITH THESE TERMS EXCEED FIFTY U.S. DOLLARs ($50.00).\
\
THE EXCLUSIONS AND LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN YOU AND THE FOUNDATION.<br>

11\. Termination. The term of these Terms commences from the date the Initiative begins and continues until (i) the completion of Participant’s participation in the Initiative or (ii) these Terms or the Initiative is terminated by the Foundation, whichever is earlier (the “Term”). For example, if for any reason the Initiative is not capable of running as planned due to unforeseen changes in business conditions, infection by computer virus, bugs, tampering, unauthorized intervention, fraud, technical failures, or any other causes which corrupt or affect the administration, security, fairness, integrity, or proper conduct of the Initiative, the Foundation reserves the right at its sole discretion to amend these Terms or cancel, terminate, modify or suspend the Initiative and terminate these Terms. The Foundation may also terminate these Terms for convenience upon ten (10) days’ written notice. Upon any termination, discontinuation or cancellation of the Initiative or these Terms, all provisions of these Terms which by their nature should survive will survive, including, without limitation, ownership provisions, warranty disclaimers, limitations of liability, and dispute resolution provisions.<br>

12\. Privacy Policy and Personal Information. Any personal information and Participant Materials submitted by you in connection with the Initiative will be used for the purposes described in these Terms and will otherwise be handled in accordance with the Foundation’s Privacy Policy, which may include processing or use by third parties solely within the scope of the Terms of this Agreement, located at [https://DFINITY.org/privacy-policy/](https://dfinity.org/privacy-policy/), and you acknowledge and agree to such use.<br>

13\. Assignment. You may not assign or transfer these Terms by operation of law or otherwise) without the prior written consent of the Foundation and any prohibited assignment will be null and void. The Foundation may assign these Terms or any rights hereunder without your consent. Subject to the foregoing, these Terms will bind and inure to the benefit of the parties’ permitted successors and assigns.<br>

14\. Miscellaneous. The Foundation is not responsible for transmission errors resulting in omission, interruption, deletion, defect, delay in operations or transmission, theft or destruction or unauthorized access to or alterations of Participant Materials, or for technical, network, telephone equipment, electronic, computer, hardware or software malfunctions or limitations of any kind, or inaccurate transmissions of or failure to receive entry information by the Foundation on account of technical problems or traffic congestion on the Internet or at any website or any combination thereof. The Foundation is also not responsible for injury or damage to your computer or any other damage resulting from any downloading of any materials in connection with the Initiative. In the event that any provision in these Terms is held to be invalid or unenforceable, the unenforceable part will be given effect to the greatest extent permitted by law and the remaining provisions will remain in full force and effect to the maximum extent permitted by law. The failure of a party to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. You agree that these Terms and the rules, restrictions and policies contained herein, and the Foundation’s enforcement thereof, are not intended to confer and do not confer any rights or remedies upon any person other than you and the Foundation. These Terms, any exhibits, and any other policies of the Foundation incorporated herein by reference constitute the entire agreement between the Foundation and you with respect to the subject matter of these Terms.<br>

15\. Governing Law; Dispute Resolution. These Terms will be governed by and interpreted in accordance with the laws of Switzerland excluding that body of law pertaining to conflict of laws. Any dispute, controversy, difference or claim arising out of or relating to these Terms, including the existence, validity, interpretation, performance, breach or termination thereof or any dispute regarding non-contractual obligations arising out of or relating to it shall be referred to and finally resolved by arbitration in accordance with the Swiss Rules of International Arbitration of the Swiss Arbitration Centre in force when the Notice of Arbitration is submitted in accordance with those rules. The law of this arbitration clause shall be Swiss law. The seat of arbitration shall be Zurich, Switzerland. The number of arbitrators shall be one. The arbitration proceedings shall be conducted in English.<br>

16\. Contact. If you have any questions about the Initiative or the Terms, please contact <support@oisy.com>.\ <br>

IF YOU DO NOT AGREE TO THESE TERMS, PLEASE DO NOT REGISTER OR OTHERWISE PARTICIPATE IN THE INITIATIVE.

<br>


# OISY Sprinkles – Episode 3  (Archived)

(April 7 – June 25, 2025)

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FYMVFKZ1TgVVwQRW73JeQ%2Fsignal-2025-04-09-110401_002.jpeg?alt=media&amp;token=b598a82b-6845-47b5-a4cc-766e0947424d" alt=""><figcaption></figcaption></figure>

The OISY Sprinkles program continued—with new ways to earn and new reasons to stay active. *Episode 3* kept the core structure from earlier phases while expanding rewards through referrals and giving the community a path to unlock what comes next.

### Program Overview

OISY Sprinkles is designed to distribute tokens randomly but not without method. The initiative targets active users of the OISY Wallet, rewarding those who consistently engage with our platform.

### How to Earn Sprinkles

We kept the core rewards structure in place, so all active OISY users can continue earning as before::

* **Hold:** Maintain at least $20 worth tokens\*\*
* **Login:** Check in at least once every 7 days.
* **Transact:** Complete at least two transactions every 7 days.

50 random airdrops occur each day based on wallet activity.

{% hint style="info" %}
\*\* the token needs to display a price in the wallet to be eligible.
{% endhint %}

### New: Referral Rewards

We introduced the ability to earn even more BTC just by [inviting friends](/using-oisy-wallet/how-tos/generate-referral-link) to OISY!

* **When someone you refer deploys a new wallet,** you earn 10% of their Sprinkles for the next 30 days.
* **They still get 100% of their rewards—you just get a bonus on top**.
* The more active friends you invite, the more Sprinkles you earn.

### Introducing the Super Sprinkle

* Our highest daily reward is getting a new name: the Super Sprinkle.
* One drop per day will award \~$50 in BTC to five randomly selected users.
* Win a Super Sprinkle? Post about it, and you become eligible to win again.

### Want us to extend the campaign?

Want OISY Sprinkles to keep going? So do we! If a set number of new, active wallets are deployed, we’ll extend the campaign into Episode 4.

### Stay Active, Earn More

Whether you’re earning through activity, referring friends, or getting lucky with a Super Sprinkle, there’s more BTC up for grabs than ever. Keep using OISY Wallet, and you might just wake up to a surprise in yours.<br>


# T\&C's

## OISY REWARDS INITIATIVE - TERMS AND CONDITIONS

DFINITY Foundation, domiciled at Genferstrasse 11, 8002 Zurich, Switzerland (the “Foundation”) offers the OISY Sprinkles Program (the “Initiative”), inviting Participants to engage on the OISY platform and provide valuable feedback through such engagement. These Terms and Conditions (the “Terms”) apply to your participation in the Initiative and describe the Initiative’s requirements as well as the Rewards that you may be eligible to receive.

YOUR ENTRY IS VOID WHERE PROHIBITED. YOUR PARTICIPATION IN THE INITIATIVE IS ENTIRELY VOLUNTARY, BUT IF YOU ARE PARTICIPATING IN THE INITIATIVE YOU MUST STRICTLY ADHERE TO THESE TERMS. YOU MAY RECEIVE A REWARD (WHERE PERMITTED BY LAW) UPON RANDOM SELECTION BY AN ALGORITHM. REWARDS ARE AWARDED AT THE SOLE DISCRETION OF THE FOUNDATION AND IS NOT GUARANTEED.

1. Certain Definitions.

* “Participant” means all individuals that participate in the Initiative.
* “Reward” means the tokens which may be awarded to Participants who have been randomly selected by an algorithm as a winner.
* “Intellectual Property Rights” means patent rights (including patent applications and disclosures), copyrights, trademarks, trade secret rights, work and any other tangible or intangible property rights recognized in any country or jurisdiction in the world.
* “Foundation Materials” means all information and materials that may be provided to Participant by the Foundation pursuant to the Initiative and all Intellectual Property Rights thereto.<br>

2. Eligibility; Initiative Requirements:

a. You may only participate in the Initiative if:

* You are over 18 years old at the time of participation in the Initiative;&#x20;
* You are a resident of a jurisdiction where entry to the Initiative is not prohibited by law;
* You are not a resident of, citizen, or located in a geographic area that is subject to UN-, US-, EU-, Swiss or any other sovereign country sanctions or embargoes;
* You, nor, if applicable, any third party entities that you represent (i) is listed or associated with any person or entity being listed on any of the US Department of Commerce’s Denied Persons or Entity List, the US Department of Treasury’s Specially Designated Nationals List, the EU Consolidated List of Persons, Groups and Entities Subject to EU Financial Sanctions or the Swiss SECO’s Overall List of Sanctioned Individuals, Entities and Organizations, (ii) is a person identified as a terrorist organization or any other relevant lists maintained by any governmental authority;
* Your participation in the Initiative is not in violation of any national, state, or local law or regulation applicable to you; and
* If required, you successfully pass KYC, as applicable, according to a process that, in the sole discretion of the Foundation, is deemed sufficient.

b. The Initiative is open to individuals and entities that have completed the requirements following the instructions found here <https://docs.oisy.com/rewards/get-to-know-oisy>. If you are an employee of the Foundation or any of its subsidiaries or affiliates or an immediate family member of anyone thereof, you are eligible to participate in the Initiative but are ineligible to receive Rewards.&#x20;

* All Participants grant the Foundation a royalty-free worldwide license and right in perpetuity to use their name, image, and likeness for the purposes of producing, promoting, and advertising the Initiative, the Internet Computer and/or OISY.

* Rewards. To be eligible to receive any Reward, participants must actively engage with our platform features and fulfill specific engagement criteria set for each reward cycle. REWARDS ARE DISBURSED TO PARTICIPANTS SELECTED RANDOMLY BY AN ALGORITHM AND EXECUTED VIA SMART CONTRACT. ALL DECISIONS RELATED TO THE INITIATIVE ARE FINAL AND NON-APPEALABLE. Taxes or other costs, if any, relating to receipt, acceptance and or use of Rewards are the sole responsibility of the Participant and the Foundation is not responsible for any disputes regarding reward dispersal.\ <br>

3. Entrant Requirements.

Rewards are granted without warranty of any kind from the Foundation, express or implied, without limitation. All applicable laws and regulations apply.&#x20;

5\.  Marketing and Promotion.

1. Publicity. You will not issue any press releases or similar public announcements in connection with these Terms, without the prior written approval of the Foundation.
2. Public Relations. You will: (a) conduct your business and activities in connection with these Terms in such a manner so as to promote a good image and public relations for the Foundation, the Internet Computer and OISY; (b) not engage in any unfair or deceptive trade practice involving the Foundation, the Internet Computer or OISY; and (c) not make any false, misleading or disparaging representations or statements with regard to the Foundation, the Internet Computer or OISY.

6\. Representations and Warranties.

1. Participant Representations and Warranties. You represent and warrant that: (a) you have the authority to enter into these Terms; and (b) the information submitted to the Foundation in connection with your participation in the Initiative, including in any application or Entry, is accurate and complete.
2. Disclaimer. THE INITIATIVE WEBSITE, INCLUDING BUT NOT LIMITED TO THE FOUNDATION WEBSITE, THIRD PARTY WEBSITES SUPPORTING THE INITIATIVE, AND ANY FOUNDATION MATERIALS YOU MAY HAVE ACCESS TO IN CONNECTION WITH THE INITIATIVE ARE PROVIDED “AS-IS” AND “AS AVAILABLE,” WITH ALL FAULTS, DEFECTS AND ERRORS, AND WITHOUT WARRANTY OF ANY KIND. THE FOUNDATION DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES (EXPRESS, IMPLIED, ARISING BY LAW OR OTHERWISE) IN CONNECTION WITH THESE TERMS, INCLUDING ANY REPRESENTATIONS OR WARRANTIES REGARDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. THE FOUNDATION MAKES NO REPRESENTATION OR WARRANTY THAT: (I) THE INITIATIVE, THE INITIATIVE SITE, FOUNDATION WEBSITES OR FOUNDATION MATERIALS WILL MEET YOUR REQUIREMENTS, THEIR OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE OR THAT ANY ERRORS WILL BE CORRECTED; OR (II) YOU WILL PROFIT OR DERIVE ANY ECONOMIC BENEFIT FROM YOUR PARTICIPATION IN THE INITIATIVE.<br>

7\. Intellectual Property.

1. Participant Materials. By participating in this Initiative, you agree that any creative ideas, suggestions, or other materials you submit in connection with this Initiative, in any form, are not being made in confidence or trust and that no confidential or fiduciary relationship is intended or created between you and the Foundation in any way, and that you have no expectation of review, compensation, or consideration of any type either now or in the future.
2. Foundation Materials. The Foundation hereby grants Participant, during the Term, a limited license to use the Foundation Materials solely in connection with Participant’s participation in the Initiative. Such a limited license will automatically terminate once you are no longer a Participant in the Initiative.
3. Ownership. As between you and the Foundation, the Foundation owns all right, title and interest in and to the Foundation Materials (including, the Initiative site, the Foundation website and its trademarks, as well as all associated Intellectual Property Rights thereto. There are no implied licenses granted by either party, whether by implication, estoppel or otherwise.

8\. Confidentiality. At all times, during the term of these Terms and thereafter, and to the fullest extent permitted by law, you agree to hold all Confidential Information (as defined below) in strict confidence, not to use it in any way, commercially or otherwise, except for purposes contemplated under the Initiative, and not to disclose it to others. You also agree to take all actions reasonably necessary to protect the confidentiality of all Confidential Information.\
\
As used herein, “Confidential Information” means: (i) any information, materials or knowledge regarding OISY, the Internet Computer ,the Foundation and its business, financial condition, products, programming techniques, customers, suppliers, technology or research and development that is disclosed to you or to which you have access in connection with participating in the Initiative and (ii) these Terms. Confidential Information will not include any information that: (a) is or becomes part of the public domain through no fault of you; (b) was rightfully in your possession at the time of disclosure, without restriction as to use or disclosure; or (c) you rightfully receive from a third party who has the right to disclose it and who provides it without restriction as to use or disclosure. Notwithstanding the foregoing, Confidential Information includes any information that, due to its nature or the circumstances of its disclosure, a reasonable person would know, or would have reason to know, should be treated as confidential.

9\. Release and Indemnification. You agree to fully and finally release, indemnify, defend and hold the Foundation and its parent, affiliates, subsidiaries, directors, officers, employees and agents, including advertising and promotion agencies, and assigns, and any other organizations related to the Initiative, harmless from any and all claims, injuries, damages, expenses or losses to person or property and/or liabilities of any nature that in any way arise from participation in the Initiative, your Participant Materials or acceptance or use of a Reward, including without limitation (i) any condition caused by events beyond the Foundation’s control that may cause the Initiative to be disrupted; (ii) any injuries, losses, or damages (compensatory, direct, incidental, consequential or otherwise) of any kind arising in connection with or as a result of any benefit you may receive in connection with the Initiative, or acceptance, possession, or use of a Reward, or from participation in the Initiative; and (iii) any printing or typographical errors in any materials associated with the Initiative.

10\. Limitation of Liability. NEITHER THE FOUNDATION NOR ANY OTHER PARTY INVOLVED IN THE ADMINISTRATION OF THE INITIATIVE WILL BE LIABLE FOR ANY INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, LOSS OF DATA OR GOODWILL, SERVICE INTERRUPTION, COMPUTER DAMAGE OR SYSTEM FAILURE ARISING OUT OF OR IN CONNECTION WITH THESE TERMS, WHETHER BASED ON WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR ANY OTHER LEGAL THEORY, AND WHETHER OR NOT THE FOUNDATION HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGE, EVEN IF A LIMITED REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES OR DAMAGES CAUSED BY GROSS NEGLIGENCE OR WILLFUL INTENT, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IN NO EVENT WILL THE FOUNDATION’S TOTAL LIABILITY ARISING OUT OF OR IN CONNECTION WITH THESE TERMS EXCEED FIFTY U.S. DOLLARs ($50.00).\
\
THE EXCLUSIONS AND LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN YOU AND THE FOUNDATION.<br>

11\. Termination. The term of these Terms commences from the date the Initiative begins and continues until (i) the completion of Participant’s participation in the Initiative or (ii) these Terms or the Initiative is terminated by the Foundation, whichever is earlier (the “Term”). For example, if for any reason the Initiative is not capable of running as planned due to unforeseen changes in business conditions, infection by computer virus, bugs, tampering, unauthorized intervention, fraud, technical failures, or any other causes which corrupt or affect the administration, security, fairness, integrity, or proper conduct of the Initiative, the Foundation reserves the right at its sole discretion to amend these Terms or cancel, terminate, modify or suspend the Initiative and terminate these Terms. The Foundation may also terminate these Terms for convenience upon ten (10) days’ written notice. Upon any termination, discontinuation or cancellation of the Initiative or these Terms, all provisions of these Terms which by their nature should survive will survive, including, without limitation, ownership provisions, warranty disclaimers, limitations of liability, and dispute resolution provisions.<br>

12\. Privacy Policy and Personal Information. Any personal information and Participant Materials submitted by you in connection with the Initiative will be used for the purposes described in these Terms and will otherwise be handled in accordance with the Foundation’s Privacy Policy, which may include processing or use by third parties solely within the scope of the Terms of this Agreement, located at [https://DFINITY.org/privacy-policy/](https://dfinity.org/privacy-policy/), and you acknowledge and agree to such use.<br>

13\. Assignment. You may not assign or transfer these Terms by operation of law or otherwise) without the prior written consent of the Foundation and any prohibited assignment will be null and void. The Foundation may assign these Terms or any rights hereunder without your consent. Subject to the foregoing, these Terms will bind and inure to the benefit of the parties’ permitted successors and assigns.<br>

14\. Miscellaneous. The Foundation is not responsible for transmission errors resulting in omission, interruption, deletion, defect, delay in operations or transmission, theft or destruction or unauthorized access to or alterations of Participant Materials, or for technical, network, telephone equipment, electronic, computer, hardware or software malfunctions or limitations of any kind, or inaccurate transmissions of or failure to receive entry information by the Foundation on account of technical problems or traffic congestion on the Internet or at any website or any combination thereof. The Foundation is also not responsible for injury or damage to your computer or any other damage resulting from any downloading of any materials in connection with the Initiative. In the event that any provision in these Terms is held to be invalid or unenforceable, the unenforceable part will be given effect to the greatest extent permitted by law and the remaining provisions will remain in full force and effect to the maximum extent permitted by law. The failure of a party to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. You agree that these Terms and the rules, restrictions and policies contained herein, and the Foundation’s enforcement thereof, are not intended to confer and do not confer any rights or remedies upon any person other than you and the Foundation. These Terms, any exhibits, and any other policies of the Foundation incorporated herein by reference constitute the entire agreement between the Foundation and you with respect to the subject matter of these Terms.<br>

15\. Governing Law; Dispute Resolution. These Terms will be governed by and interpreted in accordance with the laws of Switzerland excluding that body of law pertaining to conflict of laws. Any dispute, controversy, difference or claim arising out of or relating to these Terms, including the existence, validity, interpretation, performance, breach or termination thereof or any dispute regarding non-contractual obligations arising out of or relating to it shall be referred to and finally resolved by arbitration in accordance with the Swiss Rules of International Arbitration of the Swiss Arbitration Centre in force when the Notice of Arbitration is submitted in accordance with those rules. The law of this arbitration clause shall be Swiss law. The seat of arbitration shall be Zurich, Switzerland. The number of arbitrators shall be one. The arbitration proceedings shall be conducted in English.<br>

16\. Contact. If you have any questions about the Initiative or the Terms, please contact <support@oisy.com>.\ <br>

IF YOU DO NOT AGREE TO THESE TERMS, PLEASE DO NOT REGISTER OR OTHERWISE PARTICIPATE IN THE INITIATIVE.

<br>


# OISY Sprinkles – Episodes 1 & 2 (Archived)

(Feb 29 – April 7, 2025)

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2F1iLf9JJfFYVM8rxj8xPU%2Fsprinkles-cover-btc.jpg?alt=media&amp;token=24de184c-c558-4863-b915-becbe4eade82" alt=""><figcaption></figcaption></figure>

The OISY Sprinkles program began as part of the v1.0 launch of OISY Wallet—a campaign built to reward genuine user engagement with surprise token drops, distributed at random throughout the day to active wallets.

Episode 1 introduced a simple idea: if you use the wallet, you might just get sprinkled. Over the course of two episodes, that idea evolved.

### Overview

OISY Sprinkles was designed to reward everyday usage: log in, make transactions, hold a balance—and you’re in. No forms, no claiming, no guessing. Just activity rewarded, quietly and fairly.

### Eligibility Criteria

To qualify for rewards during either episode, users had to meet the following criteria within the 7 days prior to each drop:

* **Login**: At least once
* **Transactions:** Complete a minimum of two transactions
* **Account Balance:** Maintain at least $20 USD worth of tokens in your wallet at the time of each airdrop

These simple actions unlocked eligibility for 50 random airdrops every single day.

### How It Works

**Daily Airdrops:** 10 random airdrops were conducted throughout each day. The timing of these drops was dictated by platform activity and user engagement, giving active users a higher chance of receiving a Sprinkle.

**Allocation:** 1,550 total reward instances occurred throughout the campaign.

**Specific Rewards:** Each day, 5 participants received \~$50 worth of tokens. The remaining rewards were distributed across 45 other drops.

**Continued Eligibility:** Winning once did not affect future chances—eligibility reset with each drop cycle.

### Episode Breakdown

#### Episode 1 (Feb 29 – March 10)

The program began with ICP and ecosystem tokens as the primary rewards. This phase established the core criteria and reward format that defined the Sprinkles structure.

#### &#x20;Episode 2 (March 11 – April 7)

On March 11th, the program [transitioned](https://x.com/oisy/status/1899571030668062817) into Episode 2 with the inclusion of BTC and USDC as a reward tokens. This change expanded the scope of Sprinkles while maintaining the same eligibility requirements and daily reward structure.

### Goals of the Program

**Enhance User Engagement:** By rewarding basic actions like logging in and transacting, we encouraged frequent and meaningful use of the OISY Wallet.

**Promote the ICP Ecosystem:** Distributing ICP and ecosystem tokens highlighted the utility of assets within the network.

**Surprise and Delight:** Random token drops added an unexpected and exciting layer to daily platform activity.

### Looking Back

This effort laid the foundation for what OISY Sprinkles would become—rewarding, accessible, and community-driven. Episodes 1 and 2 introduced the mechanics, tested the structure, and set the tone for what comes [next](/rewards/oisy-sprinkles).

As the program evolves, we carry forward the same intent: reward participation and make every interaction with OISY more valuable. A new version of Sprinkles is [now live](/rewards/oisy-sprinkles).


# T\&C's

## OISY REWARDS INITIATIVE - TERMS AND CONDITIONS

DFINITY Foundation, domiciled at Genferstrasse 11, 8002 Zurich, Switzerland (the “Foundation”) offers the OISY Sprinkles Program (the “Initiative”), inviting Participants to engage on the OISY platform and provide valuable feedback through such engagement. These Terms and Conditions (the “Terms”) apply to your participation in the Initiative and describe the Initiative’s requirements as well as the Rewards that you may be eligible to receive.

YOUR ENTRY IS VOID WHERE PROHIBITED. YOUR PARTICIPATION IN THE INITIATIVE IS ENTIRELY VOLUNTARY, BUT IF YOU ARE PARTICIPATING IN THE INITIATIVE YOU MUST STRICTLY ADHERE TO THESE TERMS. YOU MAY RECEIVE A REWARD (WHERE PERMITTED BY LAW) UPON RANDOM SELECTION BY AN ALGORITHM. REWARDS ARE AWARDED AT THE SOLE DISCRETION OF THE FOUNDATION AND IS NOT GUARANTEED.

1. Certain Definitions.

* “Participant” means all individuals that participate in the Initiative.
* “Reward” means the tokens which may be awarded to Participants who have been randomly selected by an algorithm as a winner.
* “Intellectual Property Rights” means patent rights (including patent applications and disclosures), copyrights, trademarks, trade secret rights, work and any other tangible or intangible property rights recognized in any country or jurisdiction in the world.
* “Foundation Materials” means all information and materials that may be provided to Participant by the Foundation pursuant to the Initiative and all Intellectual Property Rights thereto.<br>

2. Eligibility; Initiative Requirements:

a. You may only participate in the Initiative if:

* You are over 18 years old at the time of participation in the Initiative;&#x20;
* You are a resident of a jurisdiction where entry to the Initiative is not prohibited by law;
* You are not a resident of, citizen, or located in a geographic area that is subject to UN-, US-, EU-, Swiss or any other sovereign country sanctions or embargoes;
* You, nor, if applicable, any third party entities that you represent (i) is listed or associated with any person or entity being listed on any of the US Department of Commerce’s Denied Persons or Entity List, the US Department of Treasury’s Specially Designated Nationals List, the EU Consolidated List of Persons, Groups and Entities Subject to EU Financial Sanctions or the Swiss SECO’s Overall List of Sanctioned Individuals, Entities and Organizations, (ii) is a person identified as a terrorist organization or any other relevant lists maintained by any governmental authority;
* Your participation in the Initiative is not in violation of any national, state, or local law or regulation applicable to you; and
* If required, you successfully pass KYC, as applicable, according to a process that, in the sole discretion of the Foundation, is deemed sufficient.

b. The Initiative is open to individuals and entities that have completed the requirements following the instructions found here <https://docs.oisy.com/rewards/get-to-know-oisy>. If you are an employee of the Foundation or any of its subsidiaries or affiliates or an immediate family member of anyone thereof, you are eligible to participate in the Initiative but are ineligible to receive Rewards.&#x20;

* All Participants grant the Foundation a royalty-free worldwide license and right in perpetuity to use their name, image, and likeness for the purposes of producing, promoting, and advertising the Initiative, the Internet Computer and/or OISY.

* Rewards. To be eligible to receive any Reward, participants must actively engage with our platform features and fulfill specific engagement criteria set for each reward cycle. REWARDS ARE DISBURSED TO PARTICIPANTS SELECTED RANDOMLY BY AN ALGORITHM AND EXECUTED VIA SMART CONTRACT. ALL DECISIONS RELATED TO THE INITIATIVE ARE FINAL AND NON-APPEALABLE. Taxes or other costs, if any, relating to receipt, acceptance and or use of Rewards are the sole responsibility of the Participant and the Foundation is not responsible for any disputes regarding reward dispersal.\ <br>

3. Entrant Requirements.

Rewards are granted without warranty of any kind from the Foundation, express or implied, without limitation. All applicable laws and regulations apply.&#x20;

5\.  Marketing and Promotion.

1. Publicity. You will not issue any press releases or similar public announcements in connection with these Terms, without the prior written approval of the Foundation.
2. Public Relations. You will: (a) conduct your business and activities in connection with these Terms in such a manner so as to promote a good image and public relations for the Foundation, the Internet Computer and OISY; (b) not engage in any unfair or deceptive trade practice involving the Foundation, the Internet Computer or OISY; and (c) not make any false, misleading or disparaging representations or statements with regard to the Foundation, the Internet Computer or OISY.

6\. Representations and Warranties.

1. Participant Representations and Warranties. You represent and warrant that: (a) you have the authority to enter into these Terms; and (b) the information submitted to the Foundation in connection with your participation in the Initiative, including in any application or Entry, is accurate and complete.
2. Disclaimer. THE INITIATIVE WEBSITE, INCLUDING BUT NOT LIMITED TO THE FOUNDATION WEBSITE, THIRD PARTY WEBSITES SUPPORTING THE INITIATIVE, AND ANY FOUNDATION MATERIALS YOU MAY HAVE ACCESS TO IN CONNECTION WITH THE INITIATIVE ARE PROVIDED “AS-IS” AND “AS AVAILABLE,” WITH ALL FAULTS, DEFECTS AND ERRORS, AND WITHOUT WARRANTY OF ANY KIND. THE FOUNDATION DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES (EXPRESS, IMPLIED, ARISING BY LAW OR OTHERWISE) IN CONNECTION WITH THESE TERMS, INCLUDING ANY REPRESENTATIONS OR WARRANTIES REGARDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. THE FOUNDATION MAKES NO REPRESENTATION OR WARRANTY THAT: (I) THE INITIATIVE, THE INITIATIVE SITE, FOUNDATION WEBSITES OR FOUNDATION MATERIALS WILL MEET YOUR REQUIREMENTS, THEIR OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE OR THAT ANY ERRORS WILL BE CORRECTED; OR (II) YOU WILL PROFIT OR DERIVE ANY ECONOMIC BENEFIT FROM YOUR PARTICIPATION IN THE INITIATIVE.<br>

7\. Intellectual Property.

1. Participant Materials. By participating in this Initiative, you agree that any creative ideas, suggestions, or other materials you submit in connection with this Initiative, in any form, are not being made in confidence or trust and that no confidential or fiduciary relationship is intended or created between you and the Foundation in any way, and that you have no expectation of review, compensation, or consideration of any type either now or in the future.
2. Foundation Materials. The Foundation hereby grants Participant, during the Term, a limited license to use the Foundation Materials solely in connection with Participant’s participation in the Initiative. Such a limited license will automatically terminate once you are no longer a Participant in the Initiative.
3. Ownership. As between you and the Foundation, the Foundation owns all right, title and interest in and to the Foundation Materials (including, the Initiative site, the Foundation website and its trademarks, as well as all associated Intellectual Property Rights thereto. There are no implied licenses granted by either party, whether by implication, estoppel or otherwise.

8\. Confidentiality. At all times, during the term of these Terms and thereafter, and to the fullest extent permitted by law, you agree to hold all Confidential Information (as defined below) in strict confidence, not to use it in any way, commercially or otherwise, except for purposes contemplated under the Initiative, and not to disclose it to others. You also agree to take all actions reasonably necessary to protect the confidentiality of all Confidential Information.\
\
As used herein, “Confidential Information” means: (i) any information, materials or knowledge regarding OISY, the Internet Computer ,the Foundation and its business, financial condition, products, programming techniques, customers, suppliers, technology or research and development that is disclosed to you or to which you have access in connection with participating in the Initiative and (ii) these Terms. Confidential Information will not include any information that: (a) is or becomes part of the public domain through no fault of you; (b) was rightfully in your possession at the time of disclosure, without restriction as to use or disclosure; or (c) you rightfully receive from a third party who has the right to disclose it and who provides it without restriction as to use or disclosure. Notwithstanding the foregoing, Confidential Information includes any information that, due to its nature or the circumstances of its disclosure, a reasonable person would know, or would have reason to know, should be treated as confidential.

9\. Release and Indemnification. You agree to fully and finally release, indemnify, defend and hold the Foundation and its parent, affiliates, subsidiaries, directors, officers, employees and agents, including advertising and promotion agencies, and assigns, and any other organizations related to the Initiative, harmless from any and all claims, injuries, damages, expenses or losses to person or property and/or liabilities of any nature that in any way arise from participation in the Initiative, your Participant Materials or acceptance or use of a Reward, including without limitation (i) any condition caused by events beyond the Foundation’s control that may cause the Initiative to be disrupted; (ii) any injuries, losses, or damages (compensatory, direct, incidental, consequential or otherwise) of any kind arising in connection with or as a result of any benefit you may receive in connection with the Initiative, or acceptance, possession, or use of a Reward, or from participation in the Initiative; and (iii) any printing or typographical errors in any materials associated with the Initiative.

10\. Limitation of Liability. NEITHER THE FOUNDATION NOR ANY OTHER PARTY INVOLVED IN THE ADMINISTRATION OF THE INITIATIVE WILL BE LIABLE FOR ANY INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, LOSS OF DATA OR GOODWILL, SERVICE INTERRUPTION, COMPUTER DAMAGE OR SYSTEM FAILURE ARISING OUT OF OR IN CONNECTION WITH THESE TERMS, WHETHER BASED ON WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR ANY OTHER LEGAL THEORY, AND WHETHER OR NOT THE FOUNDATION HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGE, EVEN IF A LIMITED REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES OR DAMAGES CAUSED BY GROSS NEGLIGENCE OR WILLFUL INTENT, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IN NO EVENT WILL THE FOUNDATION’S TOTAL LIABILITY ARISING OUT OF OR IN CONNECTION WITH THESE TERMS EXCEED FIFTY U.S. DOLLARs ($50.00).\
\
THE EXCLUSIONS AND LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN YOU AND THE FOUNDATION.<br>

11\. Termination. The term of these Terms commences from the date the Initiative begins and continues until (i) the completion of Participant’s participation in the Initiative or (ii) these Terms or the Initiative is terminated by the Foundation, whichever is earlier (the “Term”). For example, if for any reason the Initiative is not capable of running as planned due to unforeseen changes in business conditions, infection by computer virus, bugs, tampering, unauthorized intervention, fraud, technical failures, or any other causes which corrupt or affect the administration, security, fairness, integrity, or proper conduct of the Initiative, the Foundation reserves the right at its sole discretion to amend these Terms or cancel, terminate, modify or suspend the Initiative and terminate these Terms. The Foundation may also terminate these Terms for convenience upon ten (10) days’ written notice. Upon any termination, discontinuation or cancellation of the Initiative or these Terms, all provisions of these Terms which by their nature should survive will survive, including, without limitation, ownership provisions, warranty disclaimers, limitations of liability, and dispute resolution provisions.<br>

12\. Privacy Policy and Personal Information. Any personal information and Participant Materials submitted by you in connection with the Initiative will be used for the purposes described in these Terms and will otherwise be handled in accordance with the Foundation’s Privacy Policy, which may include processing or use by third parties solely within the scope of the Terms of this Agreement, located at [https://DFINITY.org/privacy-policy/](https://dfinity.org/privacy-policy/), and you acknowledge and agree to such use.<br>

13\. Assignment. You may not assign or transfer these Terms by operation of law or otherwise) without the prior written consent of the Foundation and any prohibited assignment will be null and void. The Foundation may assign these Terms or any rights hereunder without your consent. Subject to the foregoing, these Terms will bind and inure to the benefit of the parties’ permitted successors and assigns.<br>

14\. Miscellaneous. The Foundation is not responsible for transmission errors resulting in omission, interruption, deletion, defect, delay in operations or transmission, theft or destruction or unauthorized access to or alterations of Participant Materials, or for technical, network, telephone equipment, electronic, computer, hardware or software malfunctions or limitations of any kind, or inaccurate transmissions of or failure to receive entry information by the Foundation on account of technical problems or traffic congestion on the Internet or at any website or any combination thereof. The Foundation is also not responsible for injury or damage to your computer or any other damage resulting from any downloading of any materials in connection with the Initiative. In the event that any provision in these Terms is held to be invalid or unenforceable, the unenforceable part will be given effect to the greatest extent permitted by law and the remaining provisions will remain in full force and effect to the maximum extent permitted by law. The failure of a party to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. You agree that these Terms and the rules, restrictions and policies contained herein, and the Foundation’s enforcement thereof, are not intended to confer and do not confer any rights or remedies upon any person other than you and the Foundation. These Terms, any exhibits, and any other policies of the Foundation incorporated herein by reference constitute the entire agreement between the Foundation and you with respect to the subject matter of these Terms.<br>

15\. Governing Law; Dispute Resolution. These Terms will be governed by and interpreted in accordance with the laws of Switzerland excluding that body of law pertaining to conflict of laws. Any dispute, controversy, difference or claim arising out of or relating to these Terms, including the existence, validity, interpretation, performance, breach or termination thereof or any dispute regarding non-contractual obligations arising out of or relating to it shall be referred to and finally resolved by arbitration in accordance with the Swiss Rules of International Arbitration of the Swiss Arbitration Centre in force when the Notice of Arbitration is submitted in accordance with those rules. The law of this arbitration clause shall be Swiss law. The seat of arbitration shall be Zurich, Switzerland. The number of arbitrators shall be one. The arbitration proceedings shall be conducted in English.<br>

16\. Contact. If you have any questions about the Initiative or the Terms, please contact <support@oisy.com>.\ <br>

IF YOU DO NOT AGREE TO THESE TERMS, PLEASE DO NOT REGISTER OR OTHERWISE PARTICIPATE IN THE INITIATIVE.

<br>


# Best Practices

* **Safeguard Your Internet Identity**: Only use it securely and judiciously to log into apps. Misuse can lead to permanent fund loss.
* **Use Enhanced Security**: Enable FaceID, TouchID, or security keys for additional protection..
* **Decentralized Security with OISY**: Fully on-chain and decentralized to eliminate third-party risks.
* **Manage Your Tokens Wisely**: Only take actions with your tokens that suit your risk appetite


# Asset Control, Recovery, and Governance in OISY Wallet

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FNI5WU9q6ngRSDHYZaNWm%2FAsset%20Control%2C%20Recovery.jpg?alt=media&amp;token=2522c6f9-c295-4b90-b751-1644e29335e8" alt=""><figcaption></figcaption></figure>

### Can OISY access the private keys of native assets? Who controls the assets?

The private keys do not physically exist and thus OISY cannot access them. Assets are controlled by a distributed [cryptographic threshold protocol on the Internet Computer](https://internetcomputer.org/docs/current/references/t-sigs-how-it-works). This means no individual entity—including OISY—can ever gain full control over the key. Each user has sole authority over their assets and can exercise their control via the NNS-controlled [Chain Fusion Signer](https://github.com/dfinity/chain-fusion-signer) canister and their [Internet Identity](https://internetcomputer.org/internet-identity). Only when a user explicitly authorizes a transaction to be signed, will the network run the cryptographic protocol to create a signature on the user’s behalf. This robust, decentralized design highlights OISY’s core strength: ensuring user sovereignty over assets while maintaining top-tier security and releaving the user from managing cryptographic keys.

### Who manages OISY canisters? What happens to assets if canisters run out of cycles?&#x20;

OISY’s frontend (cha4i-riaaa-aaaan-qeccq-cai) and backend (doked-biaaa-aaaar-qag2a-cai) canisters are managed by the OISY Wallet development team, with updates undergoing rigorous code reviews and multi-level approvals. Meanwhile, the [Chain-Fusion Signer](https://github.com/dfinity/chain-fusion-signer) canister (grghe-syaaa-aaaar-qabyq-cai) and all Internet Identity canisters are governed by the Network Nervous System (NNS). Their code updates are of course also rigorously reviewed.

Critically, user assets always reside on their respective ledgers on the respective blockchains rather than within these canisters. Even if OISY canisters were to be removed or replaced, the underlying assets remain secure and can be accessed by their owners again once new or replacement canisters are deployed.

If an OISY canister would deplete its cycles, it would simply become “frozen,” meaning the Internet Computer stops scheduling it until it’s refueled with cycles—a process that anyone can perform. However, the OISY Wallet team has procedures in place to always keep canisters fuelled, ensuring reliable and continuous access to assets.

### What happens to wallet assets if the domain OISY.com expires or is hacked?

The domain OISY.com serves merely as a human-friendly pointer to the onchain frontend canister. Should the domain expire or be compromised and pointed elsewhere, the integrity of the assets remains intact as transfers can only be executed upon owner authorization via their Internet Identity.

### Can I access the private keys of Ethereum/Bitcoin/Solana wallets?

OISY Wallet uses the Internet Computer’s cryptographic threshold protocols as well as key derivation. Therefore it is not possible to extract the private keys. This innovative design strengthens security while preserving user sovereignty over Ethereum, Bitcoin, and Solana assets and relieves the user from the difficult and error prone task of managing and securing cryptographic keys.

### What are the Recovery Options in OISY? &#x20;

OISY Wallet is fully [open-source](https://github.com/dfinity/oisy-wallet), allowing users to run a local version of the codebase and maintain independent access to their assets, even without oisy.com or the official canisters. Transaction signing occurs through the ChainFusion Signer with authorization via Internet Identity, both of which are controlled by the Network Nervous System (NNS), one of the largest DAOs globally..

Because your Internet Identity ultimately governs access to your funds, the most important recovery measure is to safeguard your Internet Identity. We recommend adding backup devices such as a YubiKey to your Identity and make use of the passkey recovery mechanisms that Apple and Google offer for their devices. This ensures you have multiple ways to securely restore access to your OISY-managed assets.<br>

### Will the community be able to participate in project governance?

Currently, development is managed by the OISY Wallet team, incubated by the DFINITY Foundation. For projects built on the Internet Computer—like OISY Wallet—there is a strong push toward decentralization. The community can expect future developments in this area—stay tuned.

<br>


