There is no visible reference to pricing, payment, or any integration with Fragment or Stars within the client code. The user hints presented—such as “checking” and “available”—are reused from the main username process, and all validation or error messages are relayed directly from the server. Notably, this update streamlines bot setup by enabling assignment of a second username during creation, which previously required a separate follow-up screen. The field itself lacks UI labeling or user-facing prompts, and the reason for its introduction is not documented.
How the Second Username Field Works
The new "additional_username" field is optional and independently validated. It is submitted to the server with the rest of the form data. At the time of review, this field is visible only on one of four server deployments. Editing the field triggers a validation either 400 milliseconds after typing stops or immediately upon leaving the field, calling a server-side checkBotAdditionalUsername method. The response—“checking,” “available,” or an error—is shown to the user with error messages provided verbatim from the server.
Leaving the additional field empty allows smooth form submission, but entering an invalid secondary username blocks progress. There are no new interface instructions or purchase prompts in the Mini App. Whether payment is required is not indicated—such logic, if present, is handled server-side and invisible at the client level. All user-facing feedback for this field matches that of standard username selection.
Telegram accounts and channels already support secondary usernames, so this aligns Telegram bots with this capability. What’s new is the ability to add a second username during the initial creation process. The rationale, specific use cases, or any connection to future commercialization is not revealed in the current code or UI.
Technical Details: Validation and Submission
The additional_username field, when used, triggers its own server validation method during bot creation. If the field is non-empty, the Mini App queries the server with checkBotAdditionalUsername. Users receive real-time feedback—“checking,” “available,” or direct server error text. Only an invalid, non-empty second username blocks bot creation. No new field labeling or interface explanation accompanies this field.
Validation is tightly managed on the server: any future requirements, such as eligibility checks or payment, would appear as server error messages with no advance warning in the UI. Because this feature’s constraints are entirely server-controlled, bot creators should be aware that error text at form submission is the only indicator of current restrictions or changes.
For bot developers, the immediate benefit is a smoother setup: a second username can be attached right from the creation screen, instead of through a later step. Any other implications, such as premium status or integration with paid collectibles, are undetermined based on current Mini App and protocol analysis.
Outstanding Questions
Key unknowns remain about this experimental deployment. The interface does not explain why a second username can be entered, what benefits it might provide, or if it will connect to premium or collectible name services. There is also no evidence in the visible code or network traffic about costs, payment prompts, or integration with Fragment or Stars. The only clear, enforced rule is that the secondary username—if present—must pass server validation.
The feature is available on just one of four distribution servers, with no accompanying announcement. Whether this is part of staged rollout, A/B testing, or internal testing remains unspecified. Users do not receive information about potential benefits, pricing, or policy changes before encountering possible server error messages.
TON Drop Hub take: Bot creators can currently submit a second optional username at creation with no visible payment requirement or collectible connection. The second username’s value, policy, and future terms remain undefined unless new server-side rules are introduced or official details are published.
Bot builders benefit from having a more streamlined and flexible workflow—two usernames at launch, with feedback managed directly from the server. However, all further implications for premium use, special naming, or monetization are still undocumented.
For more Telegram and TON bot infrastructure updates, visit Latest TON news.
For related TON Drop Hub coverage, see Latest TON news.
Source reference: original source.