Installing Wallet Connect

• A working Bicrypto install — backend, frontend and cron running under PM2
• Redis reachable and answering PING (the core already requires it)
• Shell access to the project root — the rebuild has no admin-panel equivalent
• The purchase code for Wallet Connect (product ID 37548018), from your MashDiv dashboard
• An admin account holding view.extension and edit.extension
• Outbound HTTPS from the backend to rpc.walletconnect.org

1. Sign up at cloud.reown.com.

2. Create a new project. Choose type App, and set the homepage URL to the domain your platform is served from — the same origin as NEXT_PUBLIC_SITE_URL.

3. Copy the Project ID. It is a 32-character hex string shown on the project dashboard.

4. Restrict it to your domains. In the project's settings, add your production origin to the allowed-domains list. The project ID is compiled into the public JavaScript bundle and is visible to anyone who loads your site, so domain restriction is the only thing that stops it being used elsewhere against your quota.

NEXT_PUBLIC_WALLET_CONNECT_PROJECT_ID="your_32_character_project_id"

Nothing at start-up complains about an empty value, on any release. The two halves of the platform then fail separately.

The frontend has no fallback. The id is compiled into the browser bundle, and a build without one cannot open the wallet picker at all. From Core 6.7.5 every wallet screen — Sign in with wallet, the profile's Wallet tab, the NFT wallet actions and the Swap terminal — renders a "Wallet connection is not set up yet" card in its place, an admin viewing it is shown the variable to set, and the frontend prints a warning at build and on every start. On Core 6.6.2 – 6.7.4 those same screens were the platform's whole-page 500 "Something went wrong!" card, with the cause visible only in the browser console; up to Core 6.6.1 a hard-coded fallback id was compiled in instead, so the picker worked and only signing failed — see Troubleshooting.

The backend has no fallback either. With the id compiled into the frontend but absent from the backend's environment, the picker opens and a wallet connects, and POST /api/auth/login/wallet returns 500 "Wallet connect project ID is not defined" the moment the user signs. That is a working Connect wallet and a broken Sign in with wallet, which reads like a signature problem rather than a missing variable.

grep NEXT_PUBLIC_WALLET_CONNECT_PROJECT_ID .env

1. The Wallet Connect card — click it to open the product page
2. Its switch stays disabled until the licence is activated

1. Open the Extension Manager. Go to Admin → System → Extension Manager — the page heading reads Add-ons & Integrations. On the Extensions tab (or by searching for Wallet) find the Wallet Connect card — product ID 37548018 — and click it. Until its licence is activated the card's chip reads Activate and its switch is disabled, with a tooltip that says Activate license first.

2. Activate the licence. On the product page press Activate License. Paste the purchase code from your MashDiv dashboard, optionally an email address for update notifications, and press Activate License. The screen confirms License Activated! and sends you back to the product page a couple of seconds later. If the server has no outbound access, the License File tab on the same screen takes the licence certificate downloaded from your MashDiv dashboard instead.

   1. Paste the purchase code here
   2. Activate License — then wait for the redirect back to the product page
   3. The offline route, for a server with no outbound HTTPS

3. Install the release. Back on the product page, now licensed, the Overview tab has a release panel. If it offers Install v…, press it; if it says Up to date on a product you have only just licensed, press Check for Updates once, then install whatever it offers. The Releases tab holds the notes for the version you are being offered — read them first.

   Install downloads the release, verifies it and extracts it over the project root. It runs no migrations, builds nothing and restarts nothing, so finish it from a shell on the server:

   pnpm updator

   If the panel still says Up to date after the check there is nothing to download — the release already on the server is current — and you go straight to the switch.

   1. Check for Updates, then Install v… when it is offered
   2. Releases — the notes for the version you are about to install
   3. The Enabled switch — the final step, not yet

4. Switch it on. Turn the Enabled switch on — in the product page heading, or on the card in the Extension Manager, which is usable now that the licence is verified. It takes effect without a restart, and it is what makes the Sign in with wallet option appear below the password form on the login page and the Wallet tab appear in the user profile. Turning the extension off later is the same switch; it leaves the licence in place, so switching back on needs no reactivation.

Most extensions are enforced by route prefix — /api/p2p is refused unless P2P is licensed. Wallet Connect has no route prefix of its own. Its endpoints live under /api/auth and /api/user/profile, both of which are deliberately exempt from licence enforcement so that login keeps working while a core licence is being re-activated.

Enforcement therefore happens inside the handlers instead. Each one checks that the extension is enabled and that lic/37548018.lic exists on disk, and returns 403 if either is untrue. Deleting the .lic file disables wallet sign-in immediately, without touching the toggle.

pnpm updator

pnpm build:frontend
pnpm restart

The variable name begins with NEXT_PUBLIC_, so Next.js inlines its value into the JavaScript bundle at build time. Editing .env and restarting the frontend changes nothing — the old value is already compiled in. You must rebuild.

The backend reads the same variable at module load, once, when the route file is first imported. Editing .env without restarting the backend changes nothing there either.

Together these produce the confusing middle state: a rebuild without a restart gives you a frontend on the new project ID and a backend still verifying against the old one.

1. The button exists. Open the login page signed out. Below the password form there should be a Sign in with wallet option. If it is absent, the extension is not in the /api/settings extensions list — go back to step 3.

2. The picker opens. Click it, then Connect wallet. The Reown modal should list MetaMask, WalletConnect, Coinbase and the rest, and the header should show your site name rather than "Bicrypto".

3. A nonce is issued. From the server, unauthenticated:

   curl -i https://yourdomain.com/api/auth/login/nonce

   A 32-character hex string means the extension is enabled and licensed. A 403 means it is not. Note that this consumes one of five requests in the fifteen-minute rate-limit window.

4. Link a wallet. Sign in with an existing email account, go to /user/profile?tab=wallet, and connect. Your wallet prompts for a signature; on success the tab shows the address as active.

5. Sign in with it. Sign out, choose Sign in with wallet, connect the same wallet and sign. You should land back on the dashboard signed in as the same user.