Indexer assertion by NiranjanaBinoy · Pull Request #196 · shinzonetwork/web

NiranjanaBinoy · 2026-04-30T19:42:39Z

Pull Request

Description

Indexer assertion

New /indexer-assertion route and page wiring through page components.
Form for assertion fields (including 32-character delegate digest, wallet Sign for digest → signature, submit path).
.env.example documents client-side env vars used for assertion RPC / signing where applicable.

Registration

Separate routes: host-registration and indexer-registration (plus existing registration entry) with shared registration page shell.
Entity is path-driven for v2: Host vs indexer comes from the URL; users switch flows via header navigation, not in-form role toggles. V1 registration still uses the Host/Indexer radio when v2 flag is off.
RegistrationContext exposes registrationEntity, derived from usePathname() in the provider.
useRegistrationFormV2 resets form state when route-driven entity changes; handleInputChange ignores entity so it cannot be overridden from inputs.
Indexer connection string: regex validation + helper, integrated into indexer field validation.
Transaction v2 hook and register ABIs aligned with host/indexer registration payloads; shared types updates for v2 form data.

Widgets

Added a shared InputField (widget) used from registration (and related flows); optional description + tooltip pattern where needed.
Header uses menu componentry for register / nav; popover / theme tokens adjusted where menus looked transparent.
Menubar styling for selected/hover states (bg-muted-foreground / text-muted) where applicable.

Related Issue

fixes #184
The landing page is currently blank it will be updated in the next PR.

Steps to Test

Pull branch locally
Add the admin key and cosmos rpc url to the .env
Run the app or service

Checklist

Code compiles / runs
Tests added / updated
Documentation updated if needed
PR is self-contained and focused
Code does not break any existing features
Code passes personal internal testing

Notes

cloudflare-workers-and-pages · 2026-04-30T19:43:14Z

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	`f5c9969`	Commit Preview URL Branch Preview URL	May 15 2026, 08:12 PM

cloudflare-workers-and-pages · 2026-05-04T19:32:44Z

Deploying with Cloudflare Workers

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

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	shinzo-webapp-staging	`8a88e45`	May 06 2026, 08:34 PM

VanishMax · 2026-05-11T15:32:04Z

@@ -28,6 +28,25 @@ export const isRegistrationV2 = () => {
  return process.env.NEXT_PUBLIC_SHINZOHUB_V2_REGISTRATION_FLAG === "true";
 };


suggestion: add NEXT_PUBLIC_SHINZOHUB_V2_REGISTRATION_FLAG to env.example to not lose it

VanishMax · 2026-05-11T15:40:32Z

+  if (!isRegistrationV2()) {
+    return redirect("/registration");
+  }
+  return <Header />;


VanishMax · 2026-05-11T15:56:07Z

+import { isRegistrationV2 } from "@/shared/lib";
+import { AddressCopy } from "@/widget";
+
+export default function IndexerAssertion() {


feedback (ui): it'd be nice to rethink the page structure the way we present and explain the form to users.

User address could go to header to be a standard connection button that transforms into an address. Copy button is probably redundant as users know their address and can take it from the wallet.

Subtitle on the page could be more informative and explain what an assertion actually is and why people might need it.

Delegate address is prefilled automatically on connection – maybe then hide it from UI? Plus, its tooltip says it should accept "shinzo_"-prefixed addresses, and we prefill a EVM address - UI mismatch.

"Source chain" field - should it have Sepolia/Poligon that we already support?

Source chain ID is prefilled - can easily be removed

Consensus public key should probably have a tooltip that explains in simple language what it is

"Sign and submit" - can it be a non-red button please? :)

great feedback Max

VanishMax · 2026-05-11T15:57:11Z

+async function getChainId(rpc: string): Promise<string> {
+  const res = await fetch(`${rpc}/status`);
+  const json = (await res.json()) as any;
+  return json.result.node_info.network;
+}


question: do we need it? ShinzoHub chain is static and doesn't change often. Can be an env var

concur: there will be between 2 & 3 different options that we can use for the chain id and can be set in an env var.

This function is returning the chainId for the Shinzohub, so I have moved that to a constant variable.

don't see the changes. Did you commit them?

VanishMax · 2026-05-11T16:00:22Z

+export async function adminIndexerAssertion(
+  opts: AdminIndexerAssertionOptions
+) {


thought: that function seems super complicated and is extremely difficult to read, mostly because the tx encoding is done manually here. Why not use Viem/Wagmi as you had in v1? Creating and sending transaction is much easier with it. At least it could remove much of the logic from the file.

The registration transactions are evm based transactions that is why we are using viem/wagmi there. But the request for assertion is on cosmos, I have switched all the conversions to use viem but still we need to use cosmos sdk for creating and sending the request.

dvncan · 2026-05-11T20:13:47Z

Extra: we are going to need to remove the references to v1 after migrating to v2. Good to keep in mind and not focus on both working at the same time.

dvncan · 2026-05-11T19:33:48Z

+import { isRegistrationV2 } from "@/shared/lib";
+import { AddressCopy } from "@/widget";
+
+export default function IndexerAssertion() {


great feedback Max

dvncan · 2026-05-11T19:36:08Z

+async function getChainId(rpc: string): Promise<string> {
+  const res = await fetch(`${rpc}/status`);
+  const json = (await res.json()) as any;
+  return json.result.node_info.network;
+}


concur: there will be between 2 & 3 different options that we can use for the chain id and can be set in an env var.

dvncan · 2026-05-11T20:16:11Z

+  return {
+    consensusPubKey: "",
+    delegateAddress: connectedAddress,
+    sourceChain: "ethereum" as SOURCE_CHAIN,


nitpick: should be a env var

dvncan · 2026-05-12T00:26:03Z

+    try {
+      const preDigest = randomHexString32();
+      const msgBytes = stringToBytes(preDigest);
+      const prefix = `\x19Ethereum Signed Message:\n${msgBytes.length}`;


use the Ethereum ENV to build this

As we have discussed, I have added this comment #196 (comment)

dvncan · 2026-05-12T00:26:40Z

+/** Delegate digest is a fixed-length payload (32 characters). */
+export const DELEGATE_DIGEST_MAX_LENGTH = 32;
+
+export type SOURCE_CHAIN = "ethereum" | "shinzohub";


removed this type as we can extract the type from SOURCE_CHAIN_ID_MAP

dvncan · 2026-05-12T00:33:06Z

+export const SOURCE_CHAIN_ID_MAP: Record<SOURCE_CHAIN, number> = {
+  ethereum: 1,
+  shinzohub: 91273002,
+};


nitpick: consider a separate file which can be used across the app

Moved to constants in shared folder

dvncan · 2026-05-12T01:50:02Z

+  "host-registration": {
+    title: "/ Register Host on the Shinzo Network",
+    description:
+      "Sign up your host to be recognized by the Shinzo Network and contribute to the ecosystem.",


nitpick: sentence structure is awkward.

suggestion: Register your host to participate within the Shinzo Network

same for below

@soniasingla or @johnnymatthews can you review the grammar/sentences before we deploy? I am going to create an issue.

NiranjanaBinoy · 2026-05-13T20:00:41Z

While submitting assertion request, we are including a evm signature along with the digest (string that is used for sigining) and the address, which will be verifies in the cosmos env. In a evm wallet according to EIP-191, the messages that has to signed need to be prefixed with \x19Ethereum Signed Message:\n${msgBytes.length} , for a successful verification of teh signature currently we are prefixing the digest we are sending the reuest with the above prefix string. This will ensure the verification will be successful evm wallets following EIP-191 - verified this in MetaMask and Rabby- but there is a potential of it might failure for a wallet that does not follow this. We would want to make a note of this in the docs.
@dvncan @johnnymatthews

cloudflare-workers-and-pages · 2026-05-13T21:06:39Z

Deploying with Cloudflare Workers

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

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	shinzo-studio	`5e03fff`	May 13 2026, 09:26 PM

cloudflare-workers-and-pages · 2026-05-13T21:06:41Z

Deploying with Cloudflare Workers

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

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	faucet	`5e03fff`	May 13 2026, 09:26 PM

cloudflare-workers-and-pages · 2026-05-13T21:06:43Z

Deploying with Cloudflare Workers

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

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	shinzo-explorer	`5e03fff`	May 13 2026, 09:26 PM

cloudflare-workers-and-pages · 2026-05-13T21:06:43Z

Deploying with Cloudflare Workers

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

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	metrics-dashboard	`5e03fff`	May 13 2026, 09:26 PM

… sign to delegate signature, extract input field to widget

…e to be processed initernally

VanishMax · 2026-05-14T12:12:51Z

+export const getSourceChainMap = () => {
+  return JSON.parse(process.env.NEXT_PUBLIC_AVAILABLE_SOURCE_CHAINS ?? "{}");
+};


chore: add return type to the functions, default value returns, and example of this env in the .env.example

thought: it's really unexpected to have a stringified JSON as an env. To me it can be a static value

I made that update based on a review comment. I think whether it is in env or static, we would have to update when we add a new chain.

Moved chain related constant values to a separate constant file

VanishMax · 2026-05-14T12:15:27Z

+    label: "Consensus Public Key",
+    isTextarea: false,
+    isSelect: false,
+    description: "The consensus public key of the indexer",


chore: update description to make the text useful and let users understand where to get this data from in case they don't come with a link

I need some help with proper the titles and tooltips texts, so I have created a separate Pr to track that #210.
I have left a message in the fe channel for the same.

I think we can have @johnnymatthews + @soniasingla review for titles, grammar and general sentence structure. I created a ticket here: #213

VanishMax

Good to go! I didn't go through all the user journey, but it is definitely time to go forward and fix outstanding issues (if any) in the future work.

@dvncan need your approval too to remove "changes requested" badge

dvncan · 2026-05-15T12:46:15Z

+  "host-registration": {
+    title: "/ Register Host on the Shinzo Network",
+    description:
+      "Sign up your host to be recognized by the Shinzo Network and contribute to the ecosystem.",


@soniasingla or @johnnymatthews can you review the grammar/sentences before we deploy? I am going to create an issue.

dvncan · 2026-05-15T13:02:26Z

+    label: "Consensus Public Key",
+    isTextarea: false,
+    isSelect: false,
+    description: "The consensus public key of the indexer",


I think we can have @johnnymatthews + @soniasingla review for titles, grammar and general sentence structure. I created a ticket here: #213

NiranjanaBinoy self-assigned this Apr 30, 2026

NiranjanaBinoy added the enhancement New feature or request label Apr 30, 2026

NiranjanaBinoy force-pushed the feat/indexer-assertion branch from 903b85c to cdbf344 Compare May 4, 2026 06:42

NiranjanaBinoy changed the base branch from main to feat/registration-form-v2 May 4, 2026 07:04

NiranjanaBinoy linked an issue May 4, 2026 that may be closed by this pull request

Enabling Indexer assertion #184

Closed

NiranjanaBinoy marked this pull request as ready for review May 4, 2026 07:29

NiranjanaBinoy requested review from VanishMax, WrungCodes and dvncan May 4, 2026 07:30

NiranjanaBinoy force-pushed the feat/indexer-assertion branch from 119dd26 to 8cb652e Compare May 6, 2026 19:33

Base automatically changed from feat/registration-form-v2 to main May 6, 2026 20:11

NiranjanaBinoy force-pushed the feat/indexer-assertion branch from 8cb652e to 8a88e45 Compare May 6, 2026 20:32

VanishMax reviewed May 11, 2026

View reviewed changes

dvncan reviewed May 11, 2026

View reviewed changes

dvncan requested changes May 12, 2026

View reviewed changes

NiranjanaBinoy force-pushed the feat/indexer-assertion branch from 31fedd3 to f0d0b89 Compare May 13, 2026 21:06

NiranjanaBinoy added 6 commits May 13, 2026 17:19

adding indexer assertion form and route

ed7f457

auto load delegate address, sign delegate digest with wallet and load…

d7b3d5e

… sign to delegate signature, extract input field to widget

assertion submission

a6392a0

fixing assertion and adding validations for delegate digest

6928742

updating the header styles

3005d94

prefill data

69e19b2

NiranjanaBinoy added 15 commits May 13, 2026 17:20

prettier break

535b4d5

restoring the old header and /registration path for v1

2b7b50c

updating button styles

eb2e1af

updating the assertion form to move assertion id, digest and signatur…

8507396

…e to be processed initernally

extracting wallet address display and copy

6bf01bd

readig=ng connected wallet address as delegate address

06cad4e

fixing the signature verification error

e7d7463

adding feedback comments on UI

b43d533

changing source chain in registration to dropdown

ee3cea6

updating header

2f4912f

addressing review comments

99160b1

updating connection dtring pattern

d5e70d5

resolving conflict and updating menu and popover background

ee61be1

fixing build failue

6b44590

resolving merge conflict with pnpm-lock

5e03fff

NiranjanaBinoy force-pushed the feat/indexer-assertion branch from f0d0b89 to 5e03fff Compare May 13, 2026 21:26

updated pnpm-lock

ac6af8c

NiranjanaBinoy requested review from VanishMax and dvncan May 14, 2026 05:45

VanishMax reviewed May 14, 2026

View reviewed changes

moving chain related consts to a separate file

2f917ec

NiranjanaBinoy force-pushed the feat/indexer-assertion branch from 008938f to 2f917ec Compare May 15, 2026 04:19

NiranjanaBinoy requested a review from VanishMax May 15, 2026 04:19

NiranjanaBinoy mentioned this pull request May 15, 2026

Verifying that the indexer assertion is done #208

Merged

6 tasks

VanishMax approved these changes May 15, 2026

View reviewed changes

dvncan approved these changes May 15, 2026

View reviewed changes

NiranjanaBinoy added 2 commits May 15, 2026 15:05

removing a stray paranthesis that is breaking the app

85206b4

updating chain for select option

f5c9969

NiranjanaBinoy merged commit 38280ff into main May 19, 2026
2 checks passed

NiranjanaBinoy deleted the feat/indexer-assertion branch May 19, 2026 14:07

		@@ -28,6 +28,25 @@ export const isRegistrationV2 = () => {
		return process.env.NEXT_PUBLIC_SHINZOHUB_V2_REGISTRATION_FLAG === "true";
		};

Conversation

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

Uh oh!

Pull Request

Description