> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/multi-chain-and-multi-rail/social-payouts.md).

# Social Payouts

Explores conceptual social-identity claims for USDG payouts, including wallet verification, undefined integrations, and social-proof fraud risks.

The proposed social-payout model can reference a creator before their payout wallet is known. It combines a social identity reference with wallet ownership proof.

### Proposed claim flow

For example, a creator such as `@alice` on Instagram could be named as a token's intended fee recipient.

{% stepper %}
{% step %}

#### Reference the creator

The token launch includes a reference to the creator's social identity.
{% endstep %}

{% step %}

#### Claim with a wallet

GetPaid generates a claim page. The creator connects a wallet and signs a message confirming the social identity.
{% endstep %}

{% step %}

#### Check the social proof

The proposed process checks for the wallet address on the creator's social profile. It also confirms that the wallet controls the signing key.
{% endstep %}

{% step %}

#### Route the payout

The verified wallet receives USDG through the proposed EIP-3009 gasless payout flow. The creator may use an external offramp, such as MoonPay, for bank access.
{% endstep %}
{% endstepper %}

### Scope and limitations

The creator need not be identified solely by an on-chain address at the start of routing. The proposed model uses a social reference, wallet signature, and profile-based wallet-address check.

{% hint style="danger" %}
Support for verification across 10 or more social platforms remains conceptual. Fraud through social proof is an identified risk.
{% endhint %}

The proposal does not define social APIs, OAuth, identity providers, KYC, automated ownership checks, or fraud-prevention guarantees.

{% hint style="warning" %}
This flow is conceptual and untested in production. GetPaid remains pre-testnet, and social payouts are not deployed or audited.
{% 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://whitepaper.getpaid.family/multi-chain-and-multi-rail/social-payouts.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.