Add validated address entry to the trusted-address manager

[knytcomics-ui]

Category

Good First

Summary

Complete the existing trusted-address management UI so users can add valid Stellar addresses.

Current Behavior

src/utils/storageHelper.ts provides addTrustedAddress(), but TrustedAddressesManager.tsx only lists and removes addresses.

Problem

Users cannot create a trusted-address entry through the extension.

Why This Matters

A complete address-management workflow is necessary before trusted-address policies can become useful.

Proposed Scope

Add an address input and Add action. Validate Stellar account addresses, normalize input consistently, reject duplicates, and show actionable errors.

Acceptance Criteria

• Valid Stellar addresses can be added.
• Invalid addresses are rejected without changing storage.
• Duplicate addresses are handled idempotently.
• Added addresses appear immediately.
• Keyboard and screen-reader interaction works.
• Tests cover validation, duplicates, and persistence.

Technical Considerations

Use the existing Stellar SDK and addTrustedAddress(); do not introduce another validator.

Testing Requirements

Test valid, invalid, duplicate, and persisted entries.

Cross-Repository Impact

None identified.

Out of Scope

Automatically bypassing warnings or defining trust policy semantics.

Complexity

Good First — one UI component, existing storage helper, and focused tests.

Impact

Medium — completes an incomplete product capability.

Suggested Labels

good first issue, enhancement

[nighshift-labs]

I inspected the existing TrustedAddressesManager and addTrustedAddress() path. The smallest implementation is a labelled form that trims/uppercases input, validates with the already-installed StrKey.isValidEd25519PublicKey(), rejects invalid values without storage writes, then reloads the list after a valid add. I tested that slice in a disposable clone: 6 focused Vitest tests pass (valid normalization, invalid rejection, duplicate idempotency, persistence/removal), plus npm run typecheck and npm run lint.

I have not opened a speculative PR. Does the existing duplicate-safe behavior (silent idempotency) match the intended UX, or should the UI show a non-error status when an address is already trusted?