> 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/risks-and-invalidation/key-risks.md).

# Key Risks

Records eight identified design, adoption, market, competitive, regulatory, and multi-chain execution risks for the proposed GetPaid model.

The risk register reflects the dependencies of a pre-testnet protocol. Risk levels retain the current project assessment and do not represent probability estimates.

| Risk                                                 | Level  | Exposure                                                                                                                                               |
| ---------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Pons V2 delay or cancellation                        | High   | Pons V2 is a key intended Robinhood Chain launchpad integration. A delay or cancellation could reduce access to the expected Robinhood Chain fee flow. |
| Robinhood Chain volume decline after gas sponsorship | High   | Gas sponsorship is expected to end on September 29, 2026. A decline exceeding 70% is a stated risk scenario, not a forecast.                           |
| Multi-social proof fraud                             | Medium | Social proof relies on wallet ownership and social identity evidence, creating potential for spoofing or fraudulent claims.                            |
| Token utility over-engineering                       | Low    | The four proposed utilities, burn, buyback, staking, and governance, may not provide sufficient value relative to their complexity.                    |
| Cold start versus a native launchpad                 | Medium | A launchpad may prefer retaining more of its own fee economics. The proposed 60% creator allocation may compete with a 70% alternative.                |
| Launchpad builds fee routing in-house                | Medium | A launchpad could develop its own routing system, reducing the need for an external fee layer.                                                         |
| Regulatory action                                    | Low    | Fee routing connected to social media and creator payouts may face regulatory scrutiny.                                                                |
| Multi-chain complexity                               | Medium | Supporting five chains and seven launchpad ecosystems broadens coverage while increasing implementation complexity.                                    |

### Dependency and design risks

Pons V2 is an intended integration path, not a confirmed partnership. Its timing and availability affect access to the anticipated Robinhood Chain fee flow.

The proposed social payout model depends on social identity evidence. Fraud risk remains relevant while this component stays at the design stage.

The token model and multi-chain scope are product-design choices. Their value depends on whether the added utility and ecosystem reach justify their operational complexity.

### Market and external risks

Launchpads can retain fee economics or implement routing internally. These are competitive substitution risks that could limit demand for GetPaid.

Robinhood Chain activity and regulatory conditions also sit outside the protocol's control. Production adoption has not yet been established.


---

# 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/risks-and-invalidation/key-risks.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.