Skip to content

WIRE-439: align node-owner scenarios with new-account-only registration - #188

Draft
joshglogau wants to merge 1 commit into
masterfrom
fix/WIRE-439-new-node-owner-accounts
Draft

joshglogau wants to merge 1 commit into
masterfrom
fix/WIRE-439-new-node-owner-accounts

Conversation

@joshglogau

@joshglogau joshglogau commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Changes

Align the canonical scenarios with the admin-approved WIRE-439 policy: node-owner NFT registration creates new accounts only.

  • Use one nodeownreg for valid NFT claims and slashing voters; remove their separate account-creation steps.
  • Keep explicit pre-existing-account fixtures to verify ACCOUNT_EXISTS (7) for matching and different public keys. Preserve the production BAR → OPP registration path and other rejection cases.
  • Retain privileged newnameduser helpers for setup, remove the unused slashing creation wrapper, and document the required ROA/MSGCH contract pair. No SDK, payload or dependency changes.

Verification

Affected NFT/slashing project typechecks, targeted ESLint, and the ROA action suite (3 tests) pass with pinned pnpm 10.32.1. Full lint and TypeScript build also pass. GitHub Build and test / Jest CI is green. Local macOS still fails unchanged StartScriptRenderer (1) and BindConfigNetwork (4) cases, including with host permissions; those unrelated paths are untouched. Full multi-chain NFT/slashing runs are not claimed; they need the companion contracts.

Companion

Wire-Network/wire-sysio#767 — required ROA/MSGCH contract pair.

Wire-Network/wire-hub-webapp#242 — new-account-only onboarding, stacked on Wire-Network/wire-hub-webapp#241.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant