[Bug]: UI encodes the old 4-field Registration struct, so registration reverts

Component

Registration

Priority

P1

What happened?

The UI's generated contract types in packages/ui/.cdm (produced by cdm install from cdm.json) model the DotnsRegistrarController Registration struct with four fields: label, owner, secret, reserved. The deployed controller takes six, adding maxPrice and pricingVersion. The four-field encoding produces a different function selector, so makeCommitment, register, and registerReserved match no function on the deployed contract and revert with empty data. Registration through the UI cannot complete.

Expected behavior

The UI encodes the six-field Registration struct, reads the current cost-model version, and completes a commit-reveal registration.

Reproduction

Start a registration in packages/ui against the paseo-next deployment and observe the empty-data revert on makeCommitment.

Selector check against the deployed controller 0xBdaA01bD1bA67d709F2b1fF286Da0d854977EA30:

• makeCommitment((string,address,bytes32,bool,uint256,uint256)) = 0x7d0450f0 is present.
• makeCommitment((string,address,bytes32,bool)) = 0x7a23df1d is absent, and reverts with empty data like any unknown selector.

Additional context

cdm.json pins @dotns/* at latest, which resolves to a release predating the struct change. The six-field struct ships in v0.5.8-rc1.

Two on-chain rules accompany the new fields, and the UI has to honour both:

• commit() stamps the current cost-model version onto the commitment, and register() rejects a reveal whose pricingVersion differs from that stamp. The UI must read currentVersion() from the cost-model registry, resolved via protocolRegistry().get(bytes32("costModel")), and seal it into the commitment.
• register() reverts with PriceExceedsMax when the charged price exceeds maxPrice, and maxPrice is part of the commitment preimage, so it must be sealed at commit time and reused unchanged at reveal.

The SDK ABIs carry the same drift and need the same release bump. The UI needs the equivalent: regenerate the cdm types against the deployed ABI and thread maxPrice and pricingVersion through the registration flow.

Start in packages/ui/.cdm and cdm.json, then trace the UI registration flow that calls makeCommitment, register, and registerReserved. Regenerate the cdm types against the deployed six-field Registration ABI and inspect the SDK ABIs for the matching release bump. Done means the UI reads currentVersion(), preserves maxPrice and pricingVersion through commit and reveal, and completes registration against the paseo-next deployment.