FB Pixel
The Kambria DAOs Framework (KDF)

KDF Terms

Estimated reading: 9 minutes 36 views

The words you'll meet in the Kambria DAOs Framework pages, explained simply. They are in learning order: each step builds on the one before, so if you're new, read from the top.

 

Step 1 · The basics: money on a blockchain

  1. Wallet Your personal account for crypto money, like a bank account that you control yourself. In DEP 3 you use MetaMask. Your wallet address is how the DAO knows where to pay you.
  2. Blockchain, and on-chain vs off-chain A blockchain is a public record book that no one can secretly change. On-chain means something is written in that public book, so anyone can check it. Off-chain means it is handled outside the book, for example tracked in the DAO's own spreadsheet.
  3. Polygon The blockchain DEP 3 uses. It's fast and cheap to use.
  4. USDT A digital dollar: 1 USDT is worth about 1 US dollar. All money in the framework is in USDT.
  5. Polygonscan A public website where anyone can look up a payment on Polygon and see that it really happened.

 

Step 2 · Where your DAO’s money lives

  1. DAO Treasury Your DAO's shared bank account. It belongs to the DAO as a group, not to any one person.
  2. XDAO and multisig XDAO is the platform where your DAO's treasury and votes live. The treasury is a multisig: moving money out needs approval from several people, never just one.
  3. GT (Governance Token) Your voting token. You use it to vote on your DAO's decisions in XDAO, and one GT equals one vote.
  4. Revenue Vault Your DAO's cash register: the account where customers' payments arrive. Money also waits here until the people it belongs to collect it (see Claim, Step 6).

 

Step 3 · The framework and who does what

  1. Kambria DAOs Framework (KDF) The system that handles your DAO's money. Every payment follows the same five steps: Receive the payment → Categorise it → Split it into shares → Pay out each share → Record everything. Because everything is recorded on the blockchain, nobody has to take anyone's word for the numbers.
  2. KDF app The website where you use the framework. You create payment requests there, see where money went, and collect what you're owed.
  3. Approved member A DAO member whose wallet the DAO has approved in the KDF app. You need to be approved to handle orders and to be paid for tasks.
  4. The three roles These describe jobs, not people: one person can hold several roles.
  • Order Handler. Looks after a sale. Creates the payment request, adds teammates who helped, and marks the order done. Any approved member can do this.
  • Operator. Runs the money rounds (see Cycle, Step 5): splits the revenue and prepares payments.
  • Organizer. Sets up the DAO's rules in the app (how revenue is split, what kinds of revenue exist), manages members, and approves payment rounds before they go out.

 

Step 4 · When money comes in

  1. Order One sale your DAO makes, such as a session, a product or a sponsorship.
  2. Payment Request A "please pay us" page for one order: the amount, where to send it, and a pay button. The Order Handler creates it, and the customer signs in with their email and pays from their wallet.
  3. Revenue Category A label for what kind of money it is, such as Service or Product. You pick it from a fixed list (in the app it's called Revenue Type), so every DAO's reports read the same way.Revenue item The record of one valid payment, created automatically when it matches its request.
  4. Payment status and order status Two simple trackers:
  • Payment: Awaiting payment → Confirmed (has the money arrived?). Confirmed happens automatically when the payment matches the request.
  • Order: Open → Pending delivery → Completed (has the DAO delivered?)
  1. Auto-complete If no one marks an order as completed, the app does it automatically a set number of days after payment. Each DAO chooses the number of days, or turns this off.
  2. Co-handler A teammate who helped with an order. The Order Handler adds them before the order is completed, and they share the Order Handler reward equally.
  3. Direct revenue Money recorded without an Order Handler. The share that would have gone to a handler goes to the DAO Treasury instead.

 

Step 5 · How money is shared

  1. Cycle A money round, weekly or monthly. Instead of splitting every payment the moment it arrives, the DAO gathers a period's revenue and shares it out together.
  2. Pool One "bucket" the revenue is divided into, like slices of a pie. Each pool is for a different group of people or purposes.
  3. LP and LP Holders LP is a token showing that someone put money in, such as seed funding or a cash sponsorship (roughly 1 USDT put in = 1 LP). LP Holders are the people or partners holding LP, and they share their pool according to how much LP each holds.
  4. The six pools
  • Order Handler: for the members who brought in and looked after the orders.
  • Microjob (also called Service Provider): for those who did the work.
  • Organizer: for the organising party, currently Kambria. (This is not the same thing as the Organizer role.)
  • Dev Partner: for whoever built the platform the service runs on, only where there is one, as Kambria built CED. In DEP 3 this share goes to the Treasury.
  • LP Holders: for those who put money in.
  • Treasury: the DAO's own savings, for running costs and future plans.
  1. Split rule (Split Configuration) Your DAO's recipe for how big each slice is. It's agreed in your Master Plan and set in the app before any money comes in, then applied the same way every time. If the rule changes, the old version is kept, so past rounds can always be checked.
  2. Standard split The starting recipe Kambria provides so all DEP 3 DAOs work the same way. A participant-proposed DAO uses 15% Order Handler, 25% Microjob, 11% Organizer, 15% LP Holders and 34% Treasury.
  3. Preview The "check before you confirm" screen when the Operator closes a round. It shows the total and how much goes into each pool. Nothing is final yet, so mistakes can still be fixed.
  4. Distribute (and lock) Confirming the round. Once the Operator saves or distributes it, the round's numbers are locked and can't be changed.
  5. Settled off-chain In this cohort, only the Order Handler and LP Holders shares are paid through the blockchain. The Organizer, Dev Partner and Treasury shares are set aside and settled outside it, and recorded in the DAO's books.

 

Step 6 · How you get paid

  1. Pay-per-task You're paid for finished work that passes review, not for hours spent or for how busy you were.
  2. Task (deliverable) One complete, checkable piece of work, such as a profile documented and approved, a class run from start to finish, or a partner signed. A task is not a small odd job. Your lane's deliverables are its paid tasks.
  3. Definition of Done The checklist a task must meet to count as finished and be paid.
  4. Pay-Per-Task Scheme Your DAO's price list for its tasks, set in the Master Plan: which tasks are paid, how much each pays, and how many are planned.
  5. task_id A task's ID code. It links the plan, the price and the payment record, so one piece of work can be followed from start to payment.
  6. Verified A task that has been checked against its Definition of Done and confirmed. From that moment the payment is owed to you, even if you later leave the DAO.
  7. Microjob The part of the app that runs task payments, in its own money round, separate from the revenue split.
  8. Contributor allocation The "who gets paid what" list for a Microjob round, made by the Operator from verified tasks. Anyone on the list who isn't an approved member is flagged, and the list can't go ahead until that's fixed.
  9. Session log For DAOs with their own platform, such as CED: instead of typing in tasks one by one, the completed sessions are brought in automatically from the platform's records, and the platform's Guides are paid for them.
  10. Shared task A task done by more than one person. Each person gets their own share of its price and collects it themselves.
  11. Claim How you collect your money. The framework doesn't push money into your wallet: it sets your share aside for you, and you click to collect it.
  12. My earnings Your personal page in the KDF app, where you see what you're owed and claim it. It has two buttons:
  • Claim Vault collects your Order Handler and LP Holders shares together.
  • Claim Microjob collects your task payments.
  1. Operating costs DAO expenses that aren't one person's task, such as a tool, a venue or a small community grant. Members vote to release the money from the Treasury to the DAO Lead or treasurer, who spends it and keeps the receipts.
  2. Managed process How payouts run in this first cohort: the framework prepares everything, and Kambria carries it out with extra manual checks while the system is being proven.

 

Step 7 · Recognition

  1. KAT A recognition token that keeps a record of your contributions and your standing in Kambria. In DEP 3 it has no money value. It recognises things that aren't paid tasks, such as helping a teammate or welcoming a new member.

 

Step 8 · Checking the numbers

  1. Transparency view The page in the KDF app where anyone in the DAO can see where the money went (DAO › Revenue Items › Transparency).
  2. Revenue Ledger The list of every payment that came in.
  3. Payout Ledger The list of every payment that went out, to whom, and how much.
  4. Reconciliation Checking that your DAO's own records (the Cashbook in the DAO Workbook) match what the framework shows. If they don't match, something needs fixing.

 

Step 9 · Protecting your DAO’s creative work (only for DAOs that create IP)

  1. IP Declaration A written record of a piece of work your DAO created, such as a recipe collection or a method: what it is and who made it.
  2. Fingerprint A unique code calculated from that record. If anyone changes even one letter of the record, the code changes, so it proves the record hasn't been altered.
  3. IPFS A public online storage network where the declaration is kept.
  4. IP NFT A certificate on the blockchain, kept in your DAO's Treasury, that stores the declaration's link and fingerprint. It proves who made the work and when. It's a record only: it doesn't sell, license or earn anything.

 

Behind the scenes (you won’t use these directly)

Three programs on the blockchain do the work automatically:

  • Revenue Vault, which receives payments;
  • Revenue Splitter, which works out each pool's share;
  • Payout Executor, which carries out the payments.