fix(studio, webapp, shinzohub): chain switching by VanishMax · Pull Request #290 · shinzonetwork/web

VanishMax · 2026-07-13T10:17:10Z

Deploying ShinzoHub to testnet produced new chain id. This update broke Studio view deployment feature - wallets like Metamask or Rabby weren't able to use the correct chain, thus failing in any transaction sending actions.

This PR creates the testnet global var in Shinzohub package and reuses it in Studio, Webapp, Explorer, and Faucet.

Adds new SHINZOHUB_CHAIN=testnet | internal | devnet | local env variable to every mentioned app.

Steps to test:

Open up https://fix-chain-switching-shinzo-studio.shinzo-492.workers.dev/
Connect your wallet, deploy a view. Requesting data for a view might not be available, this is expected
Open internal faucet https://fix-chain-switching-faucet-internal.shinzo-492.workers.dev
Try requesting funds for your wallet that has "testnet-internal" shinzohub chain added
Check that funds arrived to your testnet-internal address, but the Explorer opens up 404 transaction - this is expected until we haven't deployed internal explorer.
Open up internal registration https://fix-chain-switching-shinzo-webapp-staging.shinzo-492.workers.dev and current registration staging https://registration-staging.shinzo.network/. Check that the numbers and data are exactly the same - it would mean the deploy is correct

cloudflare-workers-and-pages · 2026-07-13T10:17:16Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	shinzo-studio	`609b3a0`	Commit Preview URL Branch Preview URL	Jul 14 2026, 10:27 AM

cloudflare-workers-and-pages · 2026-07-13T10:17:16Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	shinzo-webapp-staging	`609b3a0`	Commit Preview URL Branch Preview URL	Jul 14 2026, 10:28 AM

cloudflare-workers-and-pages · 2026-07-13T10:17:18Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	shinzo-explorer	`609b3a0`	Commit Preview URL Branch Preview URL	Jul 14 2026, 10:28 AM

cloudflare-workers-and-pages · 2026-07-13T10:17:19Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	faucet-internal	`e50f0a0`	Commit Preview URL Branch Preview URL	Jul 14 2026, 10:59 AM

johnnymatthews · 2026-07-13T10:30:20Z

Ran into an issue. Here's what I did:

Went to https://fix-chain-switching-shinzo-studio.shinzo-492.workers.dev/
Clicked Connect wallet. Followed MetaMask prompts.
Wallet address wasn't show at the top right, had to refresh the page. This worked fine.
Clicked ERC 20 Transfers. Selected WBTC.
Clicked Switch to Shinzo. Got the following error:

User rejected the request. Details: Expected an array with at least one valid string HTTPS url 'rpcUrls', Received: http://testnet.shinzo.network:8545 Version: viem@2.48.7

It's probably worth noting that I'm on Firefox.

… allowed

VanishMax · 2026-07-13T11:06:03Z

@johnnymatthews thanks for this report! I've made a fix to point 3 in your list.

As for the HTTP not allowed in Metamask, I've made a workaround. Studio will now show an error in case their wallet doesn't allow switching to a chain with HTTP-based RPC, and prompt users to add the chain manually. For wallets like Rabby, chain switching should be automatic as intended.

Can you try adding the chain manually and proceeding with view deployment?

NiranjanaBinoy · 2026-07-13T14:27:07Z

 import {
  getView,
  listViews,
+  shinzoHubTestnet as shinzoChain,


Question: If we use the hardcoded chain details specific to testnet here, wont that add unnecessary rework when we release mainnet ? or when we need to switch between chain during dev?

I think this is a necessary step at the moment. The env that used to be here was not configured dynamically enough to allow simple switching. I'd plan this as a separate feature for all apps: studio, webapp, faucet, etc.

NiranjanaBinoy · 2026-07-13T14:44:00Z

-
-    void (async () => {
-      try {
-        const chain = await fetchShinzoHubChain(controller.signal);


Curious: Do we have to replace the dynamic fetching for chainId in webapp?, This might cause connecting to testnet from https://registraion-staging.shinzo.network. It is configured to use http://testnet-internal.shinzo.network

I've changed this to SHINZOHUB_CHAIN env in all application. Static data now

cloudflare-workers-and-pages · 2026-07-14T10:26:48Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	faucet	`e50f0a0`	Commit Preview URL Branch Preview URL	Jul 14 2026, 11:00 AM

NiranjanaBinoy · 2026-07-14T17:12:30Z

 } as const;

 /** Builds a live ShinzoHub viem chain definition from RPC endpoints. */
 export async function shinzoHubChain({


[nit]: It looks like we are not using this anywhere, may be we can remove it.

NiranjanaBinoy · 2026-07-14T20:46:20Z

 }

 /** Fetches the live ShinzoHub chain definition through the webapp API proxy. */
 export async function fetchShinzoHubChain(


With new chain switching changes, I think we no longer need these. We could remove this whole page and use the shinzoChain directly where we are calling the resolveShinzoHubChain()

I have added some comments in webapp to remove some deadcodes after the new changes. I am currently doing a cleanup PR for registration v2 feature flag. If you want to go ahead merge this PR, I can include the dead code removal in my PR. Let me know what works better for you.

This sounds good. I'd appreciate if you could take on removing dead code

NiranjanaBinoy · 2026-07-14T20:48:38Z

 export async function fetchShinzoHubChain(
  signal?: AbortSignal
 ): Promise<Chain> {
  const response = await fetch("/api/shinzohub/chain", { signal });


I think we could also remove the route at this path, I did a quick search and could not find fetch from this route.

NiranjanaBinoy · 2026-07-14T21:13:56Z

+/** Proxies browser EVM requests to the selected chain's HTTP RPC without mixed-content errors. */
+export async function POST(request: Request) {
+  try {
+    const response = await fetch(


This will help to resolve the CORS error we are facing in the browser for the rpc urls, right? Once this merge can we remove the rpc-proxy and staging-rpc-proxy workers from our projects?

Yes, this is exactly why I made it

NiranjanaBinoy · 2026-07-14T21:28:50Z

Note:-

Not sure if it is currently valid since we do not have a internal app for the explorer ( actually I am not sure if need one since explorer is only fetching the data from the network not altering or updating the network) , but the txnhash and the address data after the faucet transaction is currently connecting to https://explorer.shinzo.network which is showing wrong data in the case of show my balance link and loading or error page in the case of txnhash.

NiranjanaBinoy

I have added some comments but nothing major mostly clean up. but let me know how you want to handle the clean up in webapp. I can add that as part of #185

NiranjanaBinoy · 2026-07-14T21:32:05Z

I did not test the studio, since we do not have the internal app yet and I did not want to add test data to the testnet.

VanishMax · 2026-07-15T09:13:18Z

Not sure if it is currently valid since we do not have a internal app for the explorer ( actually I am not sure if need one since explorer is only fetching the data from the network not altering or updating the network) , but the txnhash and the address data after the faucet transaction is currently connecting to https://explorer.shinzo.network/ which is showing wrong data in the case of show my balance link and loading or error page in the case of txnhash.

@NiranjanaBinoy yes, this is expected for now. We will create internal explorer deployments soon, and the links will start working as expected

VanishMax added 3 commits July 13, 2026 12:10

feat(shinzohub): add testnet info

da770ab

fix(webapp): set correct shinzohub testnet chain id

ac10345

fix(studio): switch to correct shinzohub chain id

8908a5e

VanishMax requested a review from NiranjanaBinoy July 13, 2026 10:17

VanishMax self-assigned this Jul 13, 2026

VanishMax requested a review from johnnymatthews July 13, 2026 10:24

VanishMax added 2 commits July 13, 2026 12:44

fix(studio): update wallet connection and chain switching

dd7f83c

fix(studio): prompt users to add a custom network in case of HTTP not…

e8e72f6

… allowed

NiranjanaBinoy reviewed Jul 13, 2026

View reviewed changes

VanishMax added 5 commits July 14, 2026 12:08

feat(shinzohub): standardize chain selection process

19b1ac0

feat(studio): standardize chain selection process

e1ce726

feat(explorer): standardize chain selection, add evm-rpc native proxy

41ab671

feat(webapp): standardize chain selection process

5f6bae2

feat(faucet): standardize chain selection, default to testnet

609b3a0

VanishMax added 2 commits July 14, 2026 12:42

feat(faucet): add internal CF env

3673863

fix(faucet): wrangler config

e50f0a0

VanishMax requested a review from NiranjanaBinoy July 14, 2026 11:58

NiranjanaBinoy reviewed Jul 14, 2026

View reviewed changes

NiranjanaBinoy approved these changes Jul 14, 2026

View reviewed changes

VanishMax merged commit d5f19f6 into main Jul 15, 2026
3 checks passed

VanishMax deleted the fix/chain-switching branch July 15, 2026 09:13

VanishMax mentioned this pull request Jul 15, 2026

Internal testnet faucet #291

Closed

6 tasks

Capteur-SN mentioned this pull request Jul 16, 2026

[Faucet]: Deploy Internal testnet Faucet #292

Closed

Uh oh!

Conversation

VanishMax commented Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cloudflare-workers-and-pages Bot commented Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

cloudflare-workers-and-pages Bot commented Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

cloudflare-workers-and-pages Bot commented Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

cloudflare-workers-and-pages Bot commented Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

johnnymatthews commented Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

VanishMax commented Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

NiranjanaBinoy Jul 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cloudflare-workers-and-pages Bot commented Jul 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

NiranjanaBinoy commented Jul 14, 2026

Uh oh!

NiranjanaBinoy left a comment

Choose a reason for hiding this comment

Uh oh!

NiranjanaBinoy commented Jul 14, 2026

Uh oh!

VanishMax commented Jul 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

VanishMax commented Jul 13, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented Jul 13, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented Jul 13, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented Jul 13, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented Jul 13, 2026 •

edited

Loading

johnnymatthews commented Jul 13, 2026 •

edited

Loading

VanishMax commented Jul 13, 2026 •

edited

Loading

NiranjanaBinoy Jul 13, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented Jul 14, 2026 •

edited

Loading