You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ce2aeac
Browse filesBrowse the repository at this point in the historyBrowse files
A wallet's DashPay identity gets its username in the DashPay tab, as the
mobile wallets do. UsernameFlow checks the label with the SDK's DPNS rule,
refuses a contested (premium) label before anything is funded, and
resolves it: a free label is registered with one registerName call,
signed with the identity's enabled AUTHENTICATION/HIGH key, chosen by
purpose and level rather than by id. A wallet without an identity creates
it first through IdentityFlow, with the same exact-fee confirmation, and
the identity and the name are signed under one passphrase.
Nothing is persisted. The identity's names are read whenever it is found:
the tab header shows the first one, and a name write that was dropped or
failed is not sent again; the next read shows whether it landed.
One write at a time per wallet holds across both flows through
PlatformService::writing(): no top-up or Continue starts while a name
write is in flight, and a free label meeting another write in flight is
refused, since that write's unlock would relock the wallet under the
name's.
The unlock scope and the dropped-call token move to PlatformUi for both
flows to share. FakePlatformClient records the identity and key of each
registerName and can deliver one answer at a time.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments