.
Treasury
Defines the proposed treasury role for protocol-controlled resources, operational support, security work, development, and ecosystem growth.
The proposed GetPaid treasury is intended to receive the protocol allocation from routed fees and support the broader protocol ecosystem.
It is not a current funded treasury. GetPaid is pre-testnet, and no treasury balance has been established.
Intended functions
| Area | Intended support |
|---|---|
| Operations | Gas, infrastructure, and monitoring. |
| Insurance | A potential pool for fraud, bugs, or exploits. |
| Development | Audits, security work, and feature development. |
| Grants | Ecosystem, integration, and community initiatives. |
These are proposed uses. Final allocation parameters will be established before implementation.
Protocol funds and buyback holdings
The proposed design distinguishes protocol treasury funds from $GET acquired through buybacks.
| Resource | Proposed source | Intended role |
|---|---|---|
| Protocol treasury funds | Protocol allocation from routed fees | Support operations, insurance, development, security, and grants. |
| $GET buyback holdings | Buyback allocation used to purchase $GET | Hold $GET in treasury as a potential source for staking yield. |
Buyback allocation
↓
Purchase $GET
↓
Hold $GET in treasury
↓
Potential source for staking yield
The proposed buyback mechanism does not define a staking-yield formula or guarantee yield. Protocol treasury funds and $GET buyback holdings should not be treated as the same accounting pool unless final specifications establish that treatment.
Governance
Governance is intended to control treasury allocation. Detailed execution mechanics will be established before implementation.
INFO
The treasury model is proposed. It does not represent existing funds, active controls, or current spending.