> For the complete documentation index, see [llms.txt](https://pulse-network.gitbook.io/pulse-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pulse-network.gitbook.io/pulse-whitepaper/7.-the-social-layer.md).

# 7. The Social Layer

The Social Layer transforms everyday interactions into measurable on-chain value through a decentralized social mining system — without sacrificing speed, usability, or scale.

It is designed to feel as fast and natural as mainstream social apps, while ensuring that **value, reputation, and ownership remain on-chain**.

#### **The Core Idea** <a href="#h-the-core-idea" id="h-the-core-idea"></a>

Every interaction contributes to Pulse’s social graph and influences the Pulse Credit Score (PCS).\
High-quality interactions are rewarded. Low-quality or abusive behavior is naturally suppressed through incentive alignment. Rather than relying on manual moderation, the ecosystem self-regulates through shared economic and reputational outcomes.

#### **What Users Can Do** <a href="#h-what-users-can-do" id="h-what-users-can-do"></a>

**Content Creation ("Casts")**

• Post content — Share thoughts, insights, updates

• Discover & promote — Find valuable casts and amplify them

**Social Interactions**

| Activity             | Description                                    |
| -------------------- | ---------------------------------------------- |
| Private Messaging    | Chat with friends and other users in real time |
| Group Discussions    | Participate in topic-based communities         |
| Comments & Reactions | Engage with and evaluate content               |
| Referrals            | Invite new users and expand the network        |
| Feedback             | Help improve the product and ecosystem         |

#### The Technology Behind the Social Layer

Pulse is built on a **hybrid architecture** designed to optimize both decentralization and real-time user experience.

**A Hybrid Architecture: Assets on-chain (AA Wallet), Messages off-chain (Instant RTC). The best of both worlds.**

* **On-chain** Identity, assets, and reputation (PCS) are secured by smart wallets and verifiable on-chain logic.
* **Off-chain** Messaging, reactions, and group conversations are delivered via **Enterprise-Grade RTC (Real-Time Communication) Infrastructure**, ensuring low latency, high reliability, and global scalability.

This approach allows Pulse to support real-time social interaction at scale, while anchoring all meaningful value and reputation directly on-chain.

#### **Why It Matters** <a href="#h-why-it-matters" id="h-why-it-matters"></a>

Social activity directly strengthens PCS through:

* Consistent engagement
* Constructive feedback
* Creative contributions
* Support for healthy community behavior

The Social Layer ensures that meaningful interaction is not just social — it becomes **reputational capital and economic opportunity**, without forcing users to trade usability for decentralization.

{% hint style="info" %}
*Disclaimer: Pulse (Pulse Social Wallet) is a standalone Web3 application built on Account Abstraction technology. We are independent and not affiliated with the PulseChain Layer 1 blockchain.*
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pulse-network.gitbook.io/pulse-whitepaper/7.-the-social-layer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.