The Distribution Engine

The heart of 3.Finance's closed-loop economy. Watch how revenue flows from protocol operations to each Purpose-Oriented Distributor (POD), creating a self-sustaining financial ecosystem.

Revenue Sources

Treasury yields, AMN profits, and protocol fees flow into the engine

Distribution Engine

Automatically allocates revenue based on coded rules, not votes

PODs

Purpose-Oriented Distributors that fund specific protocol needs

Self-Sustaining

Revenue reinvested creates a flywheel effect for growth

Interactive Distribution Engine

Watch how revenue flows from the protocol to each Purpose-Oriented Distributor (POD). Click on any POD to learn more.

Distributed:$0
DistributionEngine
Treasury Yield
AMN Profits
Protocol Fees
Settlement25%
Creditors20%
Developers15%
Reserve20%
Liquidity15%
Creatives5%
Settlement Pledge25%
Creditors POD20%
Developers POD15%
Reserve Booster POD20%
Liquidity Booster POD15%
Creatives POD5%

How the Flow Works

1

Revenue Generation

The protocol generates revenue from multiple sources: yields from the Treasury's stablecoin holdings, profits from the Automated Market Navigator (AMN), and various protocol fees. This creates a diversified income stream.

2

Automatic Distribution

Revenue flows into the Distribution Engine, which automatically allocates funds to each POD based on pre-coded percentages. No governance votes needed—the system runs itself according to its design.

3

Purpose-Driven Allocation

Each POD has a specific purpose: maintaining stability (Settlement Pledge), rewarding early supporters (Creditors), funding development (Developers), building reserves (Reserve Booster), ensuring liquidity (Liquidity Booster), and supporting community (Creatives).

4

Flywheel Effect

As the protocol grows, it generates more revenue, which strengthens all PODs, which makes the protocol more robust, which attracts more users, which generates more revenue. This is the self-sustaining flywheel at the heart of 3.Finance.

The Redirect Variable: Self-Healing in Action

When the Settlement Pledge comes under pressure (too many redemptions), the Redirect Variable automatically adjusts the distribution percentages. Revenue that would normally go to other PODs gets redirected to refill the Settlement Pledge—like an immune system responding to a threat.

Automatic Protection

  • →Normal conditions: PODs receive their standard percentages
  • →Under pressure: Revenue redirects to Settlement Pledge
  • →Recovery: Once refilled, normal distribution resumes
  • →No human intervention required—it's all in the code