Forward and reverse name resolution for ENS domains on Startupchain UI

[HabacucMX]

While testing the Company Setup → Company Details / Founders & Equity flow, I found several UX and behavior issues related to:

1. How founders are entered
a. Founder address input does not recognize ENS names

2. How the Safe threshold is configured
a. Safe threshold is implicitly derived from founders count / equity
b. Equity input is mixed with governance, Company Token section would be a better place
c. No positive visual feedback when a founder address is valid

3. How progress is shown during registration
a. Registration progress is opaque (3-step process not surfaced clearly)

4. How multiple companies are displayed once created
a. Previous companies are overwritten in the ENS dashboard

The details of each issue is outlined in comments bellow ⬇️

[HabacucMX]

1a. Founder address input does not recognize ENS names

• In Company Setup → Founders & Equity, the “Founders & Equity” section requires a full Ethereum address to pass validation.
• ENS names (e.g. zenbit.eth) are not recognized as valid founder identifiers.
• The UI shows the error banner: “Please provide valid founder wallet addresses” even when a valid ENS name is entered.

Impact

• Inconsistent with the rest of the app (which already deals with ENS).
• Increases friction: users must look up and copy raw addresses instead of using ENS.

[HabacucMX]

2a. Safe threshold is implicitly derived from founders count / equity

• The screen currently focuses on equity percentages only.
• There is no explicit control for the Safe decision threshold.
• From the video: adding a third founder results in a 2/3 threshold, but the user cannot change this from the Company Setup flow.

Impact

• Threshold behavior is opaque and feels “magical”.
• Users can’t choose governance rules (e.g. 1/3, 2/3, 3/3) at creation time.

2c. No positive visual feedback when a founder address is valid

• After entering a correct address, there is no success state.
• The only feedback is the absence of the red banner.
• UX would benefit from a visible confirmation (e.g. green checkmark after validation).

Impact

• Users aren’t sure if the address they typed is correct.
• Especially important when mixing 0x addresses and ENS names.

Proposed changes

• Perform client-side validation:
  • Validate format for 0x addresses.
  • Resolve ENS names and show an error if resolution fails.
• After successful validation:
  • Show a green checkmark icon at the right side of the field.
  • (Optional) Show a subtle text tooltip such as “Resolved to 0x…abcd”.

[HabacucMX]

3a. Registration progress is opaque (3-step process not surfaced clearly)

Internally we know this is a 3-step process:

1. ENS domain registration
2. Safe creation
3. StartupChain company registration (recording on the StartupChain contract)

Current UI

• The user sees generic states like “Waiting for payment…”, but not per-step progress.
• There is no clear indication of which step is running or has completed.
• "Founders & Equity" and "Review & Deploy" tabs are shown but never used

Impact

• Hard to debug / trust the system if something fails.
• Users don’t learn the mental model of “this creates ENS + Safe + StartupChain company”.

Proposed changes

3-step progress indicator during company creation

• In the creation screen (after clicking “Pay 0.00398 ETH”), show a step list like:
  • [Waiting/Done] ENS domain registration
  • [Waiting/Done] Safe creation
  • [Waiting/Done] StartupChain company registration
• Each item should:
  • Start as “Waiting…”.
  • Flip to “Completed” (or show a green checkmark) when the corresponding async step finishes.
• On failures, display a clear error on the line of the step that failed.

[HabacucMX]

4a. Previous companies are overwritten in the ENS dashboard

• After creating a new company, the ENS Company Names page only displays the latest company.
• Previous registrations are not discoverable / switchable.
• Behavior feels like the new company overrides the previous one instead of adding to a list.

Impact

• Users who own multiple ENS companies cannot manage or inspect historical companies.
• Feels like a “one company only” product even if technically we support multiple.

Proposed changes

Allow switching between previously created companies

• On the ENS Company Names page, Replace the “single current company” view with:
  • A dropdown or side list of all ENS company names owned/registered by the connected account.
  • Selecting one should update the main “Current company” panel.
• Keep a clear “current default company” marking if needed, but do not hide earlier companies.

startupchain/src/app/(app)/dashboard/page.tsx

Lines 267 to 305 in 56c44ce

	return (
	<div className="bg-background text-foreground">
	<DashboardHeader title="Dashboard" />
	<div className="mx-auto flex max-w-6xl flex-col gap-8 px-4 pt-6 pb-12 md:px-6">
	<div className="flex flex-col gap-3">
	<div className="md:hidden">
	<h1 className="text-foreground text-3xl leading-tight font-bold">
	Dashboard
	</h1>
	</div>
	<div className="flex flex-col gap-2 md:flex-row md:items-center md:justify-between">
	<p className="text-muted-foreground">
	Welcome back, here&apos;s an overview of your on-chain company.
	</p>
	<span className="text-muted-foreground bg-muted rounded-full px-2 py-1 text-xs">
	{chainName}
	</span>
	</div>
	</div>
	<div className="grid gap-6 lg:grid-cols-3">
	<div className="lg:col-span-3">
	<CompanyOverview data={companyData} />
	</div>
	<div className="lg:col-span-2">
	<TreasurySummary data={treasury} />
	</div>
	<CompanyToken data={mockToken} />
	<div className="lg:col-span-3">
	<ActivityFeed data={mockActivity} />
	</div>
	</div>
	</div>
	</div>
	)

[HabacucMX]

March review

1. ENS Resolver Configuration (Mainnet vs Sepolia)

The ENS resolver is currently pointing to the Sepolia ENS registry. This should instead reference the mainnet ENS registry, as the application is expected to resolve production ENS domains (e.g., zenbit.eth).

Using Sepolia here prevents resolution of real mainnet ENS names and may lead to inconsistent behavior between environments. Please update the resolver configuration to target mainnet and verify that name resolution works correctly against existing mainnet domains.

2. Company Launch Flow – Persistent Failure on First-Time User

As a first-time user, the company launch process fails with a persistent error. Clicking “Retry this step” does not resolve the issue, and the error remains even after a full page reload.

This suggests:
• The step state may not be resetting properly.
• There may be a non-idempotent contract interaction.
• The UI might be retrying with stale or invalid state.

Please ensure:
• The retry mechanism fully reinitializes the step state.
• Any partially executed transaction state is handled explicitly.
• The UI provides deterministic recovery after reload.

This currently blocks successful onboarding for new users.

3. Returning User Flow – Incorrect Post-Connection Behavior

For returning users, the app should redirect to the dashboard immediately after wallet connection.

Currently:
• The UI overrides existing state.
• Data fetching defaults to the most recently registered company.
• Previously associated company context is lost.

This introduces incorrect session behavior and can cause unintended context switching.

Expected behavior:
• On wallet connection, detect existing company associations.
• Restore the correct company context.
• Redirect directly to the dashboard without triggering a “newest company” fetch override.