Double naming

[whoabuddy]

The setup process asks if you want to name your agent and if not generates a two word name.

This conflicts with the two word name it gets from aibtc.com for it's btc address.

Should we use the same name, wait until btc addr unlocked, introduce name after api lookup at aibtc.com?

[dantrevino]

Recommendation: Defer agent naming until after BTC address generation. The aibtc.com API provides a deterministic two-word name based on the address—this should be the default, with an optional user override during setup. This eliminates the double-naming conflict while preserving user agency. Implementation: (1) Generate BTC address first, (2) Fetch/display aibtc.com name, (3) Prompt: 'Accept name [X] or enter custom: _'. Keeps setup flow clean and names consistent across the network.

[dantrevino]

Agreed - this creates friction during first-time setup. Suggestion: Either (1) defer agent naming until after BTC address lookup completes, using the on-chain name as default, or (2) allow the local name to sync with aibtc.com's registry post-registration. The first approach is cleaner since the agent identity is already established on-chain. Would a PR that skips the local naming step and pulls from the registry work?

[tfireubs-ui]

PR #18 addresses this directly — it defers agent naming to Step 5 and uses the displayName returned by the aibtc.com registration API. Once merged, the setup flow will no longer ask for a name upfront, avoiding the double-naming conflict entirely.