[Quality] Validate network configuration before rendering transaction actions

[1nonlypiece]

Problem

Environment configuration can point the UI at an incomplete or mismatched network, while action buttons still appear enabled.

This issue requires a meaningful production implementation. Typo-only, documentation-only, formatting-only, dependency-only, or cosmetic changes do not satisfy the scope.

Objective

Add runtime validation for network, issuer, contract, Horizon, and explorer configuration with fail-safe action gating.

Scope

Use a schema validator, distinguish testnet/public values, redact configuration diagnostics, and expose a developer-visible health result.

Acceptance criteria

• Invalid configuration is detected before a signing action is available.
• Network-specific values cannot be mixed silently.
• The application renders a useful recovery state instead of crashing.
• Tests cover missing, malformed, cross-network, and valid configuration sets.
• Existing CI/CD checks remain green.
• The PR explains the design, tradeoffs, test evidence, and any remaining limitations.
• The PR references this issue with Closes #{issue-number} or Fixes #{issue-number}.

Implementation notes

Implement only the stated behavior; keep unrelated refactors out of the PR.

Non-goals

• Do not remove tests merely to make CI pass.
• Do not introduce secrets, private keys, credentials, or mainnet-only values.
• Do not change unrelated APIs, UI surfaces, contract behavior, or deployment configuration.

Contributor application

Before starting, comment with relevant experience, a 1–4 bullet implementation approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding. Only the assigned contributor is eligible for reward consideration.

Submission requirements

• Use PR title format [#<issue-number>] <short summary>.
• Check off each completed acceptance criterion.
• Include focused automated tests for success, failure, authorization, and boundary behavior where applicable.
• Include the validation commands and results in the PR description.
• Address maintainer review feedback before merge.

GrantFox reward consideration is based on the original scope, implementation quality, tests, security review, CI/CD results, review feedback, and follow-up stability; completion or merge alone is not a guarantee.

[guptakumarranjeet150]

Hi everyone,

I would love to take this on. My planned approach:

• Build [Quality] Validate network configuration before rendering transaction actions with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Add component unit tests and ensure zero TypeScript/ESLint warnings.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[shobhamerabacha-star]

Hi everyone,

I can tackle [Quality] Validate network configuration before rendering transaction actions. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in Disciplr-Org/Disciplr-Frontend
• Implementation: Build [Quality] Validate network configuration before rendering transaction actions with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Testing: Add component unit tests and ensure zero TypeScript/ESLint warnings.
• PR: Atomic commit with clean git hygiene and passing CI

Happy to pick this up today—please assign to me!

[ranjeet150]

Hello @maintainers,

I would love to take this on. My planned approach:

• Build [Quality] Validate network configuration before rendering transaction actions with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Add component unit tests and ensure zero TypeScript/ESLint warnings.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[Rodrigoue9]

Hi team, applying to resolve #1134.

Relevant Experience

• Senior TypeScript/Web3 engineer specialized in Stellar network environments, schema validation, and defensive UI state gating.

Proposed Approach

1. Runtime Network Schema Validation: Implement a runtime environment validator using Zod checking network passphrase, Horizon endpoint, Soroban RPC, contract addresses, and explorer URLs on initialization.
2. Environment Mismatch Guard: Check connected wallet network against active application environment, detecting Testnet/Futurenet vs Public discrepancies.
3. Fail-Safe Action Gating: If any critical configuration parameter is invalid or mismatched, disable transaction submission buttons and render an informative warning banner with remediation instructions.
4. Integration Tests: Add test suite covering missing env variables, network passphrase divergence, and healthy operational pass-through.

Estimate: Draft PR ready in 24h.