• Home
• Build
• How To
• Create and deploy Views in Shinzo Studio

Create and deploy Views in Shinzo Studio

Shinzo Studio covers the same create, deploy, and query flow as Viewkit for developers who prefer a browser UI. Nothing installs locally; you need a browser wallet and some testnet SHNZ.

Connect your wallet

1. Get testnet SHNZ from the faucet if you do not have any. Deploying a View and funding a query balance are on-chain transactions, so the wallet needs a small balance for network fees on top of whatever you spend.
2. Open studio.shinzo.network and click Connect Wallet.
3. Choose a wallet from the list and approve the connection.
4. Studio asks you to switch to the Shinzo network. Confirm the network change in your wallet when prompted. The network uses chain ID 91273001; depending on the Studio deployment, your wallet may label it Shinzo testnet or Shinzo devnet.

Once connected, Studio shows your wallet balance and query balance, and the View catalog becomes available.

Create a View

1. Start a new View from the catalog. Studio offers templates for the common cases, built on the same prebuilt lenses the CLI uses: Decode Contract Events (decodes verified event logs for one contract on Ethereum mainnet), ERC20 Transfers (normalized transfer rows for one token contract), and ERC20 Balances (account balances and transfer counts for one token contract).
2. Enter what the template asks for. For the decode template that is the contract address, for example 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 for USDC. Studio fetches the contract's verified ABI from Sourcify and picks out the event definitions, so the ABI has to be verified there. If Sourcify has no verified ABI for the contract, Studio tells you and stops.
3. Review the generated View definition: the source query, the SDL, and the lens definition with its arguments. This is exactly the bundle Viewkit would produce for the same inputs, and it is worth reading before you sign anything.

Deploy the View

1. Click Deploy View. Studio validates the definition, builds the View bundle, and asks your wallet to sign the registration transaction.
2. Confirm in your wallet. Studio sends the transaction and waits for confirmation.
3. Wait for registration to complete. Registration on ShinzoHub finishes asynchronously, so Studio polls until the View reaches REGISTERED status. This can take a short while; you can inspect the View definition in the meantime.

After registration, Studio prompts you to back the View with demand. Creating demand bonds SHNZ to the View's pool and is how Host clients see that the View should be served. The first demand creates the pool, and the pool becomes active once at least 3 Hosts have joined it. Until then Studio shows the pool as waiting for Hosts.

Fund your query balance

1. Open your View and click Add query funds (also shown as Add to query balance).
2. Enter an amount of SHNZ and approve the deposit transaction in your wallet.
3. Wait for the Query balance funded confirmation.

Query the View

1. Open the View and click Query this view.
2. Pick a Host with Select direct query host. Studio lists the Hosts currently serving the View's pool, so choose one of those; a Host outside the pool does not have the View's data.
3. Write or adjust the GraphQL query in the editor and run it. Each run asks your wallet for one signature and spends from your prepaid query balance, so keep an eye on the balance Studio shows. If it runs out, Studio refuses to send and tells you to add funds first.

The results come straight from the Host you picked. To script the same flow outside the browser, see Query your first View. To build the same View from the terminal instead, see Create your first View.

Need help

• For onboarding and technical support, join the Shinzo Discord.
• To report a documentation bug or request a feature, open an issue in the docs repo.
• For a technical issue with the Shinzo SDK client, open an issue in the web repo.