From 56dbc140ab26c83b2777f0a45b393a1da41be1d0 Mon Sep 17 00:00:00 2001 From: Lizzy brainz Date: Sun, 30 Aug 2026 16:13:10 +0100 Subject: [PATCH] fix(web): correct the wallets page copy on adding an additional wallet MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The dashboard told developers to "claim a handle from it in the Identity Registry" to link an additional wallet, but claim() rejects that: it binds a *new* handle to a *new* wallet, so claiming from a second wallet creates a separate, orphaned profile rather than adding to the existing one — undoable only via release + a re-claim. Describe the actual path instead: additional deploy wallets attach to the existing profile via `npx @signet/cli link` from the terminal. --- apps/web/app/(dashboard)/app/wallets/page.tsx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/apps/web/app/(dashboard)/app/wallets/page.tsx b/apps/web/app/(dashboard)/app/wallets/page.tsx index 0b4a022..29db132 100644 --- a/apps/web/app/(dashboard)/app/wallets/page.tsx +++ b/apps/web/app/(dashboard)/app/wallets/page.tsx @@ -84,8 +84,10 @@ export default async function WalletsPage() {

- To link an additional wallet, claim a handle from it in the Identity Registry — bindings are - created on-chain, never from this dashboard. + Your handle is bound to one primary wallet on-chain — claiming again from another wallet + creates a separate, unrelated profile rather than adding to this one. To attach an + additional deploy wallet to this profile, run{' '} + npx @signet/cli link from the terminal.

);