Anything that writes to the chain — saving records, changing a resolver, granting roles, deploying a subregistry, creating a subname — opens the Transaction Manager over the page. It lists the steps, estimates the gas, and walks you through signing.

Not started. Each step shows its estimated gas. Nothing has been sent. Click Start to begin, or close the dialog to walk away at no cost.

Waiting. The transaction is with your wallet. Sign to continue, reject to cancel. A progress bar fills as it broadcasts and confirms. On a slow network this can sit for a while.

Confirmed. The step turns to a tick with a link out to Etherscan. On the last step the button becomes Done.

Rejected. You turned it down in your wallet. Nothing was sent and you paid nothing. Try again restarts the flow.

Deploying a subregistry and deploying a new permissioned resolver each take two transactions. You sign once per step. After the first confirms, the button changes to Next — click it to send the second. Rejecting either step stops the flow there; anything already confirmed stays done.

Explorer is catching up with the chain. Your change has already landed. If a value still reads the old state a minute later, refresh the page.

No. A rejected transaction never reaches the chain, so there's no gas to pay.

Yes. Steps that already confirmed stay confirmed. Reopen the action to finish the rest.