# 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 **May 31, 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 May 17, 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>-</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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.oisy.com/for-developers/oisy-signer-changes-its-url.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.