FB Pixel
The Kambria DAOs Framework (KDF)

Order Handler Revenue Sharing

Estimated reading: 2 minutes 199 views

Some revenue comes from orders that members handle — and the framework can share revenue with the people who handled them, fairly and automatically, through the Order Handler pool.

The key idea is attribution at the moment an order is created: the Order Handler who creates the Payment Request is recorded on the order, and can add co-handlers for anyone else who worked it (see Receiving Revenue) before the order is marked completed. When that order's revenue is split, the Order Handler pool is divided equally among the handlers attributed to it. Handlers must still be approved members when the cycle runs; any rounding remainder goes to the last handler. Because attribution is captured up front — not reconstructed later — the sharing is unambiguous and on the record.

When an order has no valid handler. If an order has no handler who can be paid — because it was recorded as direct revenue, or because its handler’s role has been revoked — the Order Handler share (15%) goes to the DAO Treasury instead. It appears on the Payout Ledger as a separate, labelled line, so it’s clear why that share didn’t go to a handler. The cycle Preview warns the Operator about these orders, and the Operator must confirm before the cycle can go ahead.

This gives a DAO a clean way to reward the members who bring in and manage orders, without anyone having to tally it by hand.

In this first cohort the Operator runs each cycle with manual checks, and each handler claims their share in My earnings.

Claiming your share. In My earnings, the claim line is labelled “Order Handler · LP Holder”: your Order Handler share and any LP Holders share you hold are claimed together, in one step.

Screenshot: an order with its attributed handler(s), and the resulting Order Handler share.