
In the context of Web3, the meaning of “friend” refers to a verifiable, portable relationship that is not controlled by a single platform and can be carried across different applications. You can think of it as “putting your contact list in your backpack”—wherever you go, you can use it in any app.
This concept utilizes your “wallet address,” which functions like an online account or bank card number, used for sending/receiving assets and verifying identity. Relationships are typically established through “mutual consent” or “one-way following,” with these connections recorded by the system.
When these relationships can be accessed by multiple applications, they collectively form a “social graph.” This social graph maps out your network—who you follow, who follows you, and how often you interact.
On-chain friendships can be recorded via smart contract events or specialized credentials, and verified using “digital signatures.” A digital signature is similar to a handwritten signature but happens within your mobile device or hardware wallet, proving that actions are genuinely initiated by you.
In some social protocols, a follow relationship may be logged in a contract event log or minted as a credential (such as an NFT), representing your connection—think of it like an admission ticket. Applications can read these on-chain records to confirm if two users are friends.
Verification usually involves two steps: the application reads the record, and the user signs to authorize access to this relationship. This approach ensures both confirmation of the relationship and user control over who can view it.
The key differences are “portability” and “ownership.” On traditional platforms, your friends list is controlled by the platform—if you switch services, you typically start from scratch. On-chain relationships, however, belong to you; you can take them with you across multiple applications.
Another distinction is “verifiability.” On-chain relationships and their timestamps can be publicly audited, making it easier to identify “long-time friends” or verify authentic interactions.
Additionally, users gain more control over privacy. You can choose to expose certain relationships only in specific applications or during particular activities.
Friendship in Web3 is commonly leveraged for permissions, rewards, and collaboration.
For permissions, “token gating” is widely used. Only users holding a certain token or credential can join groups or participate in votes—similar to swiping an access card to enter a meeting room.
For rewards, projects may distribute airdrops to “old friends.” An airdrop involves sending tokens to eligible users based on past relationships and interaction records.
For collaboration, teams may assign tasks and share profits within trusted friend networks, reducing risks and communication costs that come with collaborating with strangers.
In exchange scenarios—such as Gate’s invitation and community interactions—participation eligibility or trust levels may be limited to familiar networks, making it easier to organize joint activities and share information. Always check the activity rules to see if your relationship records need to be public or verified.
A DID (Decentralized Identifier) acts like a digital business card—linking your wallet address and public profile so others can recognize you without relying on any single platform.
SBTs (Soulbound Tokens) are non-transferable credentials that function like badges of honor—you can’t transfer them. They might represent having accomplished something together or passing a specific verification process.
Combining friendship with DID and SBTs allows for more nuanced expression of relationships: for example, awarding an SBT to a long-term collaborator as proof of being an “old friend,” or using DID to display only the social links you wish to make public while keeping sensitive connections private.
Following is usually one-way—like subscribing to someone; fans are the group being followed. Friendship emphasizes a “trusted relationship,” which may require mutual confirmation or stronger conditional validation.
As a result, friendships typically grant higher permissions and stricter privacy settings. For example, only “friends” may be able to view certain on-chain notes or access specific groups.
Making friendships public may expose you to social engineering scams. Attackers might impersonate friends to trick you into clicking malicious links or granting unauthorized access.
There’s also the risk of “signature misuse”—some pop-ups may request not just login but actual asset authorization. Never sign transactions if you’re unclear about their purpose.
From a privacy perspective, revealing too many connections can expose your transaction habits and social circles, making you susceptible to targeted attacks.
Best practices include:
Step 1: Prepare a wallet address. Treat it as your online account; create and back it up securely in a safe environment, keeping your seed phrase well protected.
Step 2: Choose a social protocol or application that supports Web3 relationships. Decide whether to import existing connections or try things out within a limited circle.
Step 3: Set visibility for your relationships. Allow access only for specific events or authorize reading only for whitelisted apps.
Step 4: Categorize your friends. Assign trust levels so important matters are restricted to your most trusted connections.
Step 5: Regularly review and audit permissions. Revisit your authorization history and revoke any unnecessary access rights to avoid long-term exposure.
In recent years, social infrastructure and application ecosystems have continued expanding, making cross-application relationship portability smoother. Industry trends include: interoperable social graphs across chains and protocols (reducing data silos); using zero-knowledge proofs for privacy-preserving relationship verification; improved anti-sybil mechanisms and reputation systems to combat fake accounts; and ongoing efforts to integrate with real-world identity compliance. (Source: Public industry research and project announcements, ongoing as of recent years.)
In Web3, the concept of friendship is a verifiable, portable relationship under your control regarding visibility. This enhances permission management, activity rewards, and collaboration—but also introduces privacy risks and the potential for social engineering attacks. By carefully considering which relationships should be public—and where—and managing authorization levels appropriately, you can turn your friend network into a sustainable trust asset.
A true friend is characterized by mutual trust, long-term companionship, and unconditional support. Key indicators include whether they help you in difficult times, respect your privacy and choices, and interact sincerely rather than for personal gain. In Web3 social contexts, on-chain interaction records and SBT credentials can partially reflect these qualities—but ultimately, genuine friendship is verified through real-life interaction.
Pure friendship is an emotional bond based on equality and independence, without economic dependence or romantic involvement. Unlike family ties (which are determined by blood) or business relationships (which are transactional), friendship is voluntarily chosen and emotionally driven. In Web3 environments, this distinction becomes more transparent since on-chain records objectively reveal whether there are any hidden economic interests between parties.
True friendship provides emotional support, companionship, and spiritual comfort—things money cannot directly buy. During tough times in life, a friend’s encouragement can be more valuable than material aid. Over time, high-quality friendships increase life satisfaction, whereas excessive pursuit of money may lead to isolation. In Web3 social communities, this is especially true—trust-based relationships form the foundation of decentralized communities.
Healthy friendships require clear boundaries: respecting each other’s privacy, not forcing beliefs on one another, avoiding excessive dependence, and clarifying financial dealings. Friends can help each other but should not compromise principles or be manipulated through guilt. In Web3 social networks, these boundaries can be maintained via privacy settings, permission management, and transparent interaction rules—helping protect both parties’ interests.
Long-term friendship requires regular communication, proactive care, and genuine action. Digital tools like instant messaging and video calls help bridge physical distance but cannot fully replace face-to-face interaction. On Web3 social platforms, participating in community activities together, verifying each other’s identities, and building on-chain interaction records strengthen credibility within friendships. Ultimately, sincerity matters most—technology should enhance trust rather than replace it.


