Usernames, profiles & PayString
A verified wallet identity with persistent public profile details.
Browse all 38 guides
Verify wallet ownership
Open Profile or Username and choose Xaman, Ledger USB or CROSSMARK. Xaman uses its normal sign-in authorization; the server verifies its signed identity without an AccountSet request, ledger submission or XRP fee. Ledger and CROSSMARK use a one-time signed memo-only ownership proof that XRPFrontend verifies without submitting to the ledger. Alternate Ledger USB is available if the standard connection fails.
Your protected profile session is remembered for up to 30 days in this browser. Open the header wallet menu to select an already connected account; profile records and transaction tools follow the selected wallet. Switching does not require a new ownership proof while its verified session remains valid. Xaman signing connections are retained separately per account in this tab until their authorization expires. A page reload can require a signing reconnection for accounts whose connection was not restored, while a valid profile session can still be reused. Sign-out removes access for the selected account, preserving other verified accounts. Always check the selected account before approving a purchase.
Register a username
Verify your Mainnet wallet, choose an available name and reserve it. Names use 3–18 letters or numbers and start with a letter.
Review the reservation, payer, full recipient, exact 5 XRP amount and unique memo. Reservations last 24 hours.
Acknowledge the nonrefundable purchase, choose your wallet and approve only after comparing the transaction there. The network fee is separate.
Wait for validation and registration. If interrupted, use the existing transaction hash to verify instead of paying again. If the reservation expires, use Recover paid username with the existing hash.
What the 5 XRP buys
The 5 XRP is sent permanently to rDRqy6rzRbrnaxV9dh6NodP5ZMqGyGX8Ey for the username registration. It is not a refundable deposit, a native XRPL name, a domain purchase or an investment. Each additional workspace username needs its own registration; an existing personal username can be linked to one workspace without another purchase. Renaming and transfer are not currently offered. Non-waivable legal rights still apply.
Edit your public profile
Display name, bio and supported HTTPS social links are optional and editable. They are stored by XRPFrontend and do not alter ledger account properties. A wallet-verified badge proves wallet control, not a person’s legal identity or ownership of their social accounts. Illustrative names on the welcome page are examples.
Registered wallet badges
Founding and numbered community badges require a completed username registration. A validated paid registration or a successfully claimed free username coupon qualifies. Connecting, verifying, looking up a wallet, editing a display name, creating a profile or reserving an unpaid username does not qualify and never consumes a number.
Each registered wallet counts once, even if it has several workspace usernames. Numbers follow the earliest completed registration recorded for each wallet; tied timestamps are ordered by wallet address. Positions 1–100 receive the founding badge and 101–500 receive the numbered community badge. Later registrations do not display an early-wallet number. Old numbers are corrected to exclude unregistered accounts. Wallet-age information is separate and is shown on registered profiles when ledger history is available. A badge is not identity verification, an investment benefit or an endorsement.
Enable PayString
After registering a username, enable PayString in Profile and optionally supply a required destination tag. The identifier is username$the-current-site-host. The public resolver maps it to your Mainnet classic address and tag. The sender must resolve and compare those details before approving.
The Send form resolves PayStrings hosted by this site only. External clients require a publicly reachable HTTPS host; an owner-private preview cannot function as a public resolver. A different deployment domain produces a different identifier.
PayString versus browser payment link
You must purchase and register a username before enabling PayString. The server checks for the paid registration, not just a displayed name. Enable it in Profile. Changes save automatically; wait for the saved status before sharing your payment identifier.
A PayString identifier uses the registered username and the current site host. It is not an ordinary web URL; a browser address bar may search for it. Use the profile’s share action to copy a clickable payment page or public profile. The payment link works only when the username has enabled PayString. The sender must review the resolved wallet address and optional tag before signing.
Connect and finish verification
From the Explore page, choose Connect and start my profile. Select Xaman, Ledger, or CROSSMARK, then approve sign-in in your wallet. Xaman uses its standard sign-in authorization; the server verifies the signed provider identity and creates a protected browser session. There is no extra AccountSet login request, ledger transaction or XRP network fee. Ledger and CROSSMARK use a one-time signed ownership proof that is not submitted to XRPL. A paid username is optional and offered after your free profile is ready.
The verified profile session is shared across pages on the same site and remembered in protected HttpOnly cookies for up to 30 days. Saved verified wallets are restored without another signature when switching back. Your Xaman signing authorization can expire independently; reconnecting it does not submit a ledger transaction. Sign-out, expired sessions, clearing browser data or using another browser can require sign-in again. XRPFrontend and the GPT-hosted review site have separate browser sessions. If mobile authorization returns to another browser, return to the original browser. Pending legacy ownership proofs are recovered without creating another request.
Profile links and tips
You can add a full HTTPS YouTube channel link alongside your website, X, Instagram, GitHub and Telegram links. They open from your public profile. If your paid tip activation is ON, visitors see a heart tip action at the top of your profile and can review the recipient and transaction before sending XRP.
Your public profile#
Your username page presents your display name, bio, social links, chosen cover style, verified wallet address, and enabled payment actions. Edit these through Profile after verifying ownership with your signing wallet. Share uses the native mobile share sheet when available or copies the direct profile URL. The activity area shows recent validated on-chain transactions; there is no private message, follower, or social post feed in this release.
The public Assets section reads the current validated XRP balance and nonzero issued-asset trust lines. It models the current holdings against XRP market OHLC candles for 1D, 7D, or 1M in USD, EUR, or JPY. Priced tokens use their current market quote, with unavailable quotes excluded. This is not historical wallet value or account performance. Owners can hide the estimated asset chart and values in Profile; balances and transactions remain publicly accessible on the XRPL and elsewhere on this account page. External social accounts are owner-supplied links and are not verified.