Account for common resources, project custody and personal balances.
Value Unit develops Dktron as a proposed unit for accounting and accessing material capacity. Dktron is the unit that records the personal capacity rights the network attributes to a member. Common reserves and project custody are recorded alongside it in the same ledger, and capacity becomes Dktron when it is attributed to a person's sphere.
The design keeps common reserves, project custody and personal Dktron balances apart and connects redemption to real available resources. Reputation and federative governance records remain distinct from financial holdings.
Coherent accounting should make support dependable and resource decisions inspectable, without giving financial holdings constitutional authority.
A project could return an unused allocation under its agreed terms while a member retains a personal balance for later use or authorised conversion to living expenses. This is an illustration of the proposed design.
An allocation record must make clear whose resources it represents, who may use them and what obligations attach to them. Those meanings differ between a project budget and a personal balance.
The repository publishes the current architectural formulation of Dktron and its relation to the capacity economy. Value, reputation, and DAF federative points are distinct concepts. No Dktron is issued, priced, sold or traded as a cryptocurrency; no speculative token exists.
The first validation is an accounting one, not a speculative one: a transparent record of contributions, needs, temporary project custody, personal member reserves, and contestable accountability. Today no ledger runs: in the DAF's Phase 0, resource requests are filed and decided in its assembly, the federation holds no treasury, and any disbursement happens outside and is reported. The global Dk does not run yet. From version 1.0, Dk models scenarios and, on matters outside the constitution, within the space it grants, the global Dk decides and executes autonomously; members can make a well-justified veto, which obliges review.
- One ledger, three parts: common reserves, project custody and personal balances are recorded separately; only the personal part is counted in Dktron
- Personal Dktron: individual credits that members can freely accumulate, transfer, or convert into local currency for material sustenance without risk of seizure by inactivity. The personal Dk acts as an adviser: it relates opportunities and suggests uses in the direction the person has chosen. The final word belongs to the member, who decides whether to convert part of the balance into local currency for housing, transport, health or food, keep it for later purchases, a personal transition or a period of study, transfer capacity to another member's creative project or to independent research, or acquire equipment, computing access or materials through the network. No one asks the network's leave to use a personal balance
- Temporary project custody: capacity allocated to active project tasks is held under approved terms, and project resources stay bound to the purpose for which they were entrusted. What happens to a surplus depends on context: it can return to the common reserves, stay reserved for a next phase already planned, or be reallocated by a new decision. If the project is abandoned, the resources still tied to its execution return under its closing conditions; if its scope changes, the allocation can be reviewed. Personal resources stay under the decision of whoever received them
- Lawful bridge infrastructure: conversion of personal credits into local currency conditioned on actual, verifiable external liquidity reserves. Before each attribution, the answers are known: what the member can claim, keep, transfer or use, who can change those conditions, and what returns to a common project. The conditions of conversion are known in the same way before the attribution: how the value is calculated, deadlines, costs, and what happens in a temporary shortage of liquidity. If many members ask for conversion at the same time, the network answers first for the commitments it has already made. A project priority never silently erases a balance that already belongs to someone
- Zero passive yield: holding Dktron never generates passive interest, dividends, or speculative appreciation. Accumulating personal capacity is not in itself rentism: a member may keep a balance as long as they wish. What is excluded is a return mechanism: saving capacity differs from holding an asset that extracts income from other people's work or scarcity. Drayker encourages wealth born of a game in which everyone gains, and does not let wealth that comes from a zero-sum game grow
- Separation of financial capacity and authority: financial contributions cannot purchase member status, the reputation of work, or weight in constitutional decisions. Financing the network or contributing capacity to it, such as lent computing, earns the reward, the one transferable kind of reputation, which can give faster or priority access to resources
- Two sides of the ledger: the record keeps apart the balance a person can mobilise and the material commitment of the network. Three rules hold: the same resource never appears at the same time as a reserve and as a free budget; a transfer changes the holder without creating a second right; contextual allocation is kept separate from the settlement of rights. A Dktron balance does not buy priority: the reward is a different record, and it is the reward that can give faster or priority access to resources. See Dktron in Dknowledge
- Accountable review paths: contestable allocation procedures with audit trails in Dknowledge
Drayker's material capacity depends on the world outside the network: resources come in from it, and expenses are paid to it. The treasury is the interface between the two.
Expenses that cross the interface:
- Energy
- Servers
- Land
- Equipment
- External professionals
- Licences
- Manufacturing
- Transport
- Insurance
- Taxes
Revenues that cross the interface:
- Services
- Products
- Licensing
- Donations
- Stakes in companies
- Contracts
A contribution that crosses the interface stays linked to the event, the conditions of the transfer and its results. When a contributor later asks to use the capacity they helped create, the request is examined by the criteria of the function, with the interest declared and an independent evaluation of who benefits: a donation does not reserve to the donor the judgement of their own priority. Any contracted counterpart is stated before acceptance and examined as a commitment. A partnership states its reach, its counterparts and the rights over what is produced, so the network can tell support for the construction from a dependence that hands its direction to another interest.
What comes in from the outside world is not only money: contracts, assets and infrastructure also cross the interface and become capacity incorporated into the system, allocated inside by context and constitution, to projects, members and infrastructure. The value they produce opens a new relation with the outside, and the cycle continues. The flow runs in both directions. Revenues from the outside world become internal capacity, recorded in one ledger as common reserves, project custody and personal balances, with only the personal part counted in Dktron. That capacity goes back out as the expenses above, and through the lawful bridge that converts a member's personal balance into local currency for living expenses. Distributed Support is the program through which that capacity reaches members, projects and communities. No treasury operates today.
- An issued speculative token, volatile cryptocurrency, investment, yield product or financial asset
- Perpetual property or rentier ownership over common capacity or hardware
- An internal market where basic capacity or member status is bought with money
- Any speculative guarantee of appreciation, trading profit or liquidity pools
- Confiscation or expiration of personal member balances based on arbitrary inactivity
- Automated allocation by Dk outside the constitution, its systemic safeguards or the review that a well-justified member veto obliges
How resources become accountable internal capacity — the accounting and constraint layer for common capacity, not a market for persons.
Money works as a universal equivalent: enough of it buys food, another person's time and a political decision. The capacity economy keeps those circuits apart, and no quantity accumulated in one buys what belongs to another: survival rests on the common floor, personal capacity runs in Dktron, and technical and constituent responsibility depends on a reputation that is neither bought nor transferred.
Inside Drayker, money cannot buy member status, the reputation of work or weight in member choices. Financing the network or contributing capacity to it, such as lent computing, earns the reward, the only transferable reputation, which can give faster or priority access to resources and never weighs in member choices. Need, intention, reputation, knowledge, resources, risk, opportunity and consequence inform contextual allocations. Dktron records the part of that capacity attributed to a person, and common reserves and project custody are recorded alongside it in the same ledger. Dk models options and consequences. It does not own funds. From version 1.0, on matters outside the constitution, within the space it grants, the global Dk decides and executes autonomously; members can make a well-justified veto, which obliges review. DAF points remain a separate ledger, and Distributed Support is the broader multilevel program for satisfying members' vital needs.
Depends on. daf · dfmpproject
- Specify the ledger: common reserves, project custody and personal Dktron balances. Formalize the boundaries between the three parts and the point at which capacity attributed to a person becomes Dktron.
- Define project custody & return rules: formalize what happens to unspent project capacity at a milestone or on verified abandonment (return to the common reserves, reservation for a phase already planned, or reallocation by a new decision), without touching personal member credits.
- Model the external living-expense bridge: specify lawful conversion of personal Dktron into local currency for member sustenance, strictly backed by verifiable material liquidity reserves.
- Specify separation of financial capacity and authority: formalize technical and constitutional barriers ensuring money buys zero governance weight, reputation of work, or influence over member councils, and that financing the network or contributing capacity to it earns only the reward.
- Implement reconciliation simulation: demonstrate a full cycle where a member holds, transfers, and redeems personal Dktron while project funds and external reserves remain reconciled even under liquidity constraints.
Read CONTRIBUTING.md
and GOVERNANCE.md. Propose a worked accounting case or review the assumptions of an existing one.