Bob LearnHNS

HNS addresses, TLD coins, and privacy

Same wallet is enough. You do not need extra HNS sitting on the TLD’s owner address in order to renew.

Short answer

For privacy, keep extra spendable HNS on a different receive address in the same Bob wallet. Do not park liquid HNS on the address that owns the TLD. Explorers already show that address as the name owner.

On renew, the locked name coin stays on the same TLD owner address (same amount). The miner fee is paid from other spendable coins in the wallet. Any change from that fee payment goes to a new internal change address, not back onto the TLD address.

Two different coins

Name coin — the locked bid value attached to the TLD. Handshake keeps it on the same owner address through REGISTER, UPDATE, and RENEW. Changing that address is a TRANSFER, not a renew.
Spendable HNS — normal coins you can send. Bob pays the renew miner fee from these. Change from that spend goes to a fresh change address Bob generates.

Extra HNS you send to the TLD owner address does not become the name coin and is not required for renewal. It just sits there, publicly linked to the name, until you spend it.

What to do in Bob

Leave the TLD where it is. Do not send extra HNS to that owner address on purpose.
Use Receive and copy a current address for extra HNS you want to hold or receive. That address is still the same wallet (same seed).
Keep some spendable HNS in the wallet for future renew fees. Any address Bob controls is fine.
When you renew, Bob spends a little HNS for the miner fee and creates change on a new change address automatically.

Does fee change go to a never-used address?

Yes, in the usual case. Bob/hsd keeps a separate internal change address chain (not the Receive address you copy, and not the TLD owner address). Each funded transaction that needs change uses the wallet’s current unused change index. After that change UTXO is recorded, the next change address is a new unused one on that chain. You do not pick it, and it does not show as the Receive address.

It is still the same wallet (same seed). It is not a random new wallet. If two sends are built before the first change is recorded, they can theoretically share the same unused change index — Bob does not expose that, and normal one-at-a-time use gets a fresh unused change address each time.

UTXO / coin control

Bob LearnHNS does not have UTXO management or coin control in the UI. You cannot pick which coins to spend, freeze a UTXO, or send change to an address you choose. The wallet selects spendable coins automatically when you send or renew.

That is why receiving extra HNS on a different Receive address still helps privacy at deposit time, even though later spends may combine coins the wallet picks. Coin control is not a current Bob feature.

Related: FAQ · TLD renewal