> 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/technical-architecture/smart-contracts.md).

# Smart Contracts

Provides an overview of six proposed GetPaid contracts for fee routing, token functions, staking, governance, recipient controls, and social-proof verification.

This page summarizes six planned contract components in the proposed architecture.

{% hint style="warning" %}
No GetPaid contract is deployed or audited. The components below are proposed only.
{% endhint %}

### Planned contract components

| Contract          | Role                                 |
| ----------------- | ------------------------------------ |
| `FeeRouter.sol`   | Fee interception and routing         |
| `GETToken.sol`    | $GET token                           |
| `Staking.sol`     | Staking and related benefits         |
| `Governance.sol`  | Governance and treasury decisions    |
| `AntiVamping.sol` | Recipient change controls            |
| `SocialProof.sol` | Wallet and social proof verification |

#### FeeRouter.sol

The proposed FeeRouter is a Uniswap V4 hook. It is intended to intercept fees and route them according to a configured split.

#### GETToken.sol

The proposed $GET token is an ERC-20 with a fixed supply of 1 billion tokens. Minting is disabled after deployment, and the design uses a burn path through transfer to a dead address.

#### Staking.sol

The proposed staking component would support locking $GET, a fee discount, and yield distribution.

#### Governance.sol

The proposed governance component would support votes on selected protocol parameters and treasury allocation.

#### AntiVamping.sol

The proposed anti-vamping component would cover cooldowns, maximum recipient changes, and lock logic.

#### SocialProof.sol

The proposed social-proof component would use wallet signatures and social-proof verification.

### Implementation scope

Interfaces, function names, storage, access control, ownership, upgradeability, proxy architecture, emergency functions, multisig arrangements, pausability, and security measures will be finalized during implementation.


---

# 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/technical-architecture/smart-contracts.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.