Article summary
Separate wallet, member, phone and Telegram identifiers in Web3 communities, using TG registration and activity observations without treating token ownership or group membership as messaging permission.
The easiest identity mistake in a Web3 community is drawing wallet address, Telegram username, phone and “person” as one node. One member can use several wallets and accounts, a treasury wallet can have several operators, and usernames change. TG number checking can add registration or activity observations; it cannot prove wallet ownership, token wealth or community contribution.
Begin with four node types
| Node | Example | Natural limitation |
|---|---|---|
| member_id | Internal community record | Meaning exists inside the project |
| wallet_address | Public on-chain address | Not a natural person |
| telegram_identity | UserID and username | Can change or be absent |
| phone_contact | Normalized phone | Can migrate, be shared or expire |
An edge requires an explicit event
A wallet-to-member edge may come from signature verification, a Telegram-to-member edge from login or voluntary linking, and a phone from user submission with a stated purpose. Do not merge on nickname, avatar or on-chain transfer. Store source_event, created_at, revoked_at and confidence_state for every edge.
The narrow role of TG Registration
AIPUSH TG Registration returns phone and registration result, describing observed platform state at batch time. It cannot determine group membership, token holdings, bot status, KYC completion or willingness to receive a project message.
Questions TG Activity may support
TG Activity can export phone, TG UserID, Telegram username, user offline time, active days, First Name, Last Name, TG VIP status and frozen status. It can support constrained member-data maintenance or a support queue. Offline time is not activity inside a named group, and username is not a stable primary key.
Create a data domain for each operation
| Operation | Acceptable dependency | Forbidden inference |
|---|---|---|
| Member support | Voluntary ticket and linked identity | Wealth determines service priority |
| Governance notice | Member-selected notification channel | Token holding permits a DM |
| Anti-scam work | Official accounts, signatures and risk process | Number checking detects scammers |
| Community analysis | Aggregated, minimized data | Publishing profiles in a group |
A TXT carries one controlled question
Generate a one-phone-per-line TXT from an approved phone_contact set. Never upload wallet address, token balance, username, chat content or member tier. The internal crosswalk links batch_row to member_id. Returned Excel enters an observation domain and never writes directly to the on-chain identity master.
Manage username change and frozen status
Store UserID and username separately. A username change creates alias history rather than erasing audit evidence. Frozen status is a dated observation with a documented business meaning. An anomaly should not automatically remove member rights or become a public label; route it to human support.
Separate token gating from message permission
A signature shows control of an address at a moment, and a Token Gate demonstrates a defined on-chain condition. Neither grants Telegram direct-message or marketing permission. Members select notification channel, purpose, frequency and opt-out separately.
Activity is not a contribution score
Platform activity, group posts, code commits, proposal votes and support contributions are different events. If a community needs reputation, build it from transparent rules and verifiable actions. Do not secretly convert offline time or TG VIP status into standing.
Deletion when a member leaves
A member can revoke edges among wallet, Telegram and phone. Necessary transaction or governance records remain separate from marketing profiles. Expired TG observations, upload files and temporary Excel follow a deletion schedule. Removing an edge does not erase public chain facts, but it stops use for contact.
A healthy Web3 identity graph
It allows multiple revocable relationships per member, explains the evidence and time for each, and reduces access when purpose changes. TG number checking is one observation source in that graph. Community trust still comes from transparent rules, voluntary linking and auditable behavior—not the number of columns collected.
