Signing Server & Inheritance Key features should be disabled on Testnet.

[cakesoft-swati]

• Description:
  On Testnet environment, the app currently allows access to Signing Server (Server Key) and Inheritance Key features. However, since the dev instance for Signing Server has been terminated, these features are no longer supported on Testnet.

• Expected Result:

  1. Signing Server and Inheritance Key features should be disabled or hidden in Testnet
  2. Users should not be able to access unsupported flows

[antuz123]

Feature Title

Disable Server Key and Inheritance Key Access on Testnet

Context

GitHub issue #6931 states that on the Testnet environment, Keeper currently allows access to Signing Server / Server Key and Inheritance Key features. The dev instance for Signing Server has been terminated, so these features are no longer supported on Testnet. Expected result: disable or hide these features and prevent users from accessing unsupported flows. 

Decision for this package: Option B. Keep the entries visible on Testnet but disabled, with short explanatory helper copy.

Keeper terminology should use Server Key in user-facing copy unless older UI specifically says Signing Server. Server Key should be treated as an assisted key, not a custodial key. 

Testnet and dev-mode behavior must be clearly separated from production UX. Testnet screens should be clearly marked, and Testnet must not look like Mainnet. 

Goal

Prevent users on Testnet from entering unsupported Server Key and Inheritance Key flows while still showing why those options are unavailable.

Non-Goals

• Do not change Mainnet Server Key behavior.
• Do not change Mainnet Inheritance Key behavior.
• Do not remove existing Server Key or Inheritance Key code paths.
• Do not add a new Testnet Signing Server.
• Do not introduce subscription or donation logic.
• Do not rename production features.

User Flow

Testnet user enters a signer / key selection area

• User opens a flow where Server Key or Inheritance Key can normally be selected.
• App detects current network/environment as Testnet.
• Server Key and Inheritance Key cards remain visible but disabled.
• Disabled cards show clear helper copy.
• User cannot tap through into setup, policy, signing, inheritance, or request flows.

Mainnet user enters the same area

• Server Key and Inheritance Key behave exactly as they currently do.
• No disabled state is shown due to this issue.

Deep link or stale navigation into unsupported Testnet flow

• If a Testnet user reaches a Server Key or Inheritance Key screen through stale state, deep link, cached navigation, or debug route, block access.
• Show a bottom sheet explaining the feature is unavailable on Testnet.
• User can only dismiss and return to the previous safe screen.

Screens / States

State: Disabled Server Key Card on Testnet

Screen type: Existing signer/key selection card state

Title:
“Server Key”

Body copy:
“Not available on Testnet.”

Helper text:
“Server Key is currently supported only on Mainnet.”

Button labels:
None. The card is disabled and non-actionable.

Warnings/info text:
None beyond helper text.

Error text:
None.

Success text:
None.

Behaviours:

• Show the Server Key card in its normal position.
• Apply existing disabled visual styling.
• Do not allow tap, long press, or keyboard accessibility activation to open the flow.
• If the card already has an icon, reuse the existing icon in disabled state.
• Accessibility label should read: “Server Key. Not available on Testnet.”
• Accessibility role should not imply it is actionable.

Navigation transitions:

• No navigation on tap.
• User remains on the current screen.

State: Disabled Inheritance Key Card on Testnet

Screen type: Existing signer/key selection card state

Title:
“Inheritance Key”

Body copy:
“Not available on Testnet.”

Helper text:
“Inheritance Key is currently supported only on Mainnet.”

Button labels:
None. The card is disabled and non-actionable.

Warnings/info text:
None beyond helper text.

Error text:
None.

Success text:
None.

Behaviours:

• Show the Inheritance Key card in its normal position.
• Apply existing disabled visual styling.
• Do not allow tap, long press, or keyboard accessibility activation to open the flow.
• Accessibility label should read: “Inheritance Key. Not available on Testnet.”
• Accessibility role should not imply it is actionable.

Navigation transitions:

• No navigation on tap.
• User remains on the current screen.

State: Blocked Deep Link / Stale Navigation

Screen type: Bottom sheet or modal using existing Keeper pattern

Title:
“Not Available on Testnet”

Body copy:
“This feature is currently supported only on Mainnet.”

Button labels:

• “Got It”

Warnings/info text:
None.

Error text:
None.

Success text:
None.

Behaviours:

• Show this only when a Testnet user somehow reaches an unsupported Server Key or Inheritance Key route.
• Do not attempt API calls to the terminated dev Signing Server instance.
• Do not show retry.
• Do not show setup options.
• On dismiss, return user to the previous valid Testnet screen.
• If previous screen is unavailable, return to the wallet home or relevant key selection screen.

Navigation transitions:

• Tap “Got It” → dismiss and return to previous safe screen.

State: Mainnet

Screen type: Existing Server Key / Inheritance Key flows

Title:
Existing production titles.

Body copy:
Existing production copy.

Button labels:
Existing production button labels.

Warnings/info text:
Existing production warnings.

Error text:
Existing production errors.

Success text:
Existing production success states.

Behaviours:

• No change.
• Existing Mainnet API calls remain unchanged.
• Existing signing, setup, and inheritance flows remain unchanged.

Navigation transitions:

• No change.

Copy Requirements

Use these exact user-facing strings:

• “Not available on Testnet.”
• “Server Key is currently supported only on Mainnet.”
• “Inheritance Key is currently supported only on Mainnet.”
• “Not Available on Testnet”
• “This feature is currently supported only on Mainnet.”
• “Got It”

Do not use:

• “Signing Server” in new user-facing copy unless matching an existing legacy label.
• “crypto”
• “custodial”
• “Keeper key”
• “server backup key”
• “recovery key” when referring to Server Key.

Design Requirements

• Use existing disabled card styling.
• Keep disabled cards visually readable but clearly non-actionable.
• Do not hide the cards completely.
• Do not use a destructive or warning color unless existing disabled patterns require it.
• Text must fit on small iPhone and Android widths.
• Do not shrink fonts to make copy fit.
• Do not truncate “Not available on Testnet.”
• Disabled card helper text can wrap to two lines if required.
• If cards are in a grid, ensure disabled labels do not break layout.
• If the existing layout cannot fit helper text cleanly, show only “Not available on Testnet.” on the card and use an info icon or disabled tap-block bottom sheet only if existing Keeper patterns support it.

Existing Components

Reuse:

• Existing signer/key card component.
• Existing disabled card state.
• Existing bottom sheet/modal component.
• Existing typography, spacing, icons, colors, and accessibility patterns.
• Existing Testnet environment detection.

Existing Assets

Reuse:

• Existing Server Key icon.
• Existing Inheritance Key icon.
• Existing disabled state treatment.

No new assets required.

Assets & References

Relevant issue:

• GitHub issue Signing Server & Inheritance Key features should be disabled on Testnet. #6931: Signing Server & Inheritance Key features should be disabled on Testnet. 

SVG Requirements

None.

Implementation Notes

• Add an environment guard wherever Server Key and Inheritance Key entry points are rendered.
• Guard should check Testnet/dev network state, not wallet name or visible label.
• On Testnet:
  • Render Server Key and Inheritance Key as disabled.
  • Block navigation to the underlying flows.
  • Prevent API calls to Signing Server endpoints.
  • Prevent inheritance setup/request routes from loading.
• On Mainnet:
  • Preserve existing behavior.
• Add route-level protection in addition to UI disabling.
• This avoids relying only on the disabled card UI.
• If older code still uses “Signing Server” internally, do not rename internal services unless required. Only user-facing copy should prefer “Server Key.”
• This issue is environment gating, not feature removal.

Acceptance Criteria

• On Testnet, Server Key is visible but disabled.
• On Testnet, Inheritance Key is visible but disabled.
• On Testnet, tapping either disabled card does not open setup or signing flows.
• On Testnet, helper copy clearly says the feature is supported only on Mainnet.
• On Testnet, deep links or stale navigation into Server Key or Inheritance Key flows are blocked.
• On Testnet, no API request is made to the terminated dev Signing Server instance.
• On Mainnet, Server Key behavior remains unchanged.
• On Mainnet, Inheritance Key behavior remains unchanged.
• Disabled cards follow existing Keeper visual patterns.
• Copy is mobile-safe and not truncated.
• Accessibility labels identify the feature and say it is not available on Testnet.
• Automated or manual QA covers both Testnet and Mainnet.

Open Questions

None.