.
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.
WARNING
No GetPaid contract is deployed or audited. The components below are proposed only.
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.