Expand description
Inbox handles on the client.
A handle is a short public name that an inbox claims in its identity log
(xmtp_id::associations::handle). Only the backend answers which inbox
holds a handle, so every path from a handle to an inbox goes through one
resolver. It looks the handle up, loads the answered inbox’s identity
updates, and keeps the answer only when a state the client derived holds
the handle. The client reports a changed display handle with the
handle.changed event (identity_updates::store_association_state), and
group members carry the handles of the newest state the client holds.
The client applies no handle policy. The backend alone refuses reserved, short, taken, or too frequent claims, and the client never applies the published minimum name length.
Enums§
- Handle
Error - A handle operation that the client refuses.
- Identity
Target - Someone a caller wants to reach: an account identifier, which resolves as it always has, or a handle, which resolves only through the verified handle resolver.
Constants§
- HANDLE_
SEARCH_ CODES - How many random codes
Client::available_handleschecks for a name without a code. With the name itself, one lookup holds 101 handles.
Functions§
- resolve_
handles_ with_ verifier - The verified handle resolver for a caller with no client, such as an SDK static helper. It stores the states it derives, with no event.