DUBYT ECONOMICS
Real activity.
Useful work.
Accountable rewards.
The economic model connects payment demand to the cost of reliable network services. Wallet adoption creates use; accepted work earns an allocation from a defined budget.
Product documentation · Edition 1 ·
THE ECONOMIC CYCLE
Start with people using wallets.
- 01
Make payments useful
People and businesses choose DueByte to settle real obligations. More addresses alone do not create revenue or prove demand.
- 02
Pay for the work
Fees fund the verification, execution and data services required by accepted activity. Different resource constraints belong to different service classes.
- 03
Allocate to accepted service
An operator earns from eligible assignments and verified results. A copied process, an idle key or a self-reported cost creates no entitlement.
TARIFF SCHEDULE
A small base fee. Bounded adjustment.
FOR AGREEMENT · TARIFF PROPOSAL
Coloured values are editorial proposals for approval. They do not override the amount quoted by the wallet or activate a network policy. The sender must agree the actual fee before signing.
| Parameter | Proposed value | Calculation rule |
|---|---|---|
| Standard transfer rate | 0.05% of the transfer amount | Apply the minimum fee below before any load adjustment. |
| Minimum transfer fee | 0.01 DUBYT | Covers a small standard operation; not a minimum payment amount. |
| Load multiplier | 1.0–5.0 | Adjust only the affected service class, using authenticated accepted load and capacity. |
| Adjustment boundary | At most 10% per 60-second accounting period | Smooth changes; existing signed commitments keep their agreed fee. |
| Accounting precision | 1 DUBYT = 1,000,000 accounting units | Round a final fee upward once, using integer arithmetic. |
| Expiry charge | The accepted minimum service fee | Charge no more than the signed fee budget; never charge settlement and expiry twice. |
Proposed standard fee = round up(max(0.01 DUBYT, amount × 0.0005) × load multiplier). At normal load: 10 DUBYT → 0.01; 100 DUBYT → 0.05; 1,000 DUBYT → 0.50. At multiplier 2, the 100 DUBYT example costs 0.10 DUBYT.
Storage, archival retrieval and separately assigned availability need their own measured units and service terms. They must not be silently bundled into an unlimited promise to retain data forever.
OPERATOR INCOME
Explain every allocation.
The reward-accounting rules require a statement of role, accepted units, tariff or pool weight, gross allocation, deductions and payment period. Ordinary connection or registration is not a paid assignment.
| Source | Meaning | How to report it |
|---|---|---|
| Ordinary fees | Eligible fees paid for network services. | Separate real customer activity from operator-funded circulation. |
| Bootstrap programme | A finite programme pays for defined start-up activity. | Show its fees separately from organic demand. |
| Issuance addition | New DUBYT within the authorised period budget and lifetime ceiling. | Report separately from collected fees. |
| Reserve support | A permitted transfer of existing DUBYT. | Show the source, amount, end condition and remaining reserve. |
Period reward pool = eligible fee income + permitted issuance + authorised reserve support. The allocation to an operator follows accepted work in its role; one result cannot be claimed twice.
An allocation example
If eligible fees are 190 DUBYT and the permitted issuance addition is 10 DUBYT, the pool is 200 DUBYT. A role allocation of 20 DUBYT and an operator share of 10% of that role produce 2 DUBYT. These numbers illustrate the calculation; they do not promise a fixed share or return.
Your operating result
Net operating result = realisable value of rewards − hosting − electricity − traffic and storage − maintenance − equipment depreciation − conversion and other applicable costs. Compare the same period and currency. Locked or unpayable rewards are not cash income.
More operators share a workload; they do not automatically enlarge its budget. A scarce service may command a higher tariff within the policy limits. Buying equipment is a separate decision from being admitted to paid work.
ISSUANCE & RESERVES
Finite support. No hidden replenishment.
FOR AGREEMENT · ECONOMIC PARAMETERS
| Parameter | Proposed value | Meaning |
|---|---|---|
| Maximum issuance share | 5% of fee-plus-issuance rewards | For eligible net fees F, issuance E is no more than F / 19, also capped by the period budget and remaining lifetime allowance. |
| Lifetime issuance ceiling | 100 billion DUBYT | A ceiling, not a target or an instruction to issue the full amount. |
| Bootstrap fund | 50 million DUBYT | A finite allocation within the supply rules, not an extra allowance above the ceiling. |
| Reserve contribution | Up to 5% of collected eligible fees | Deduct before calculating the distributable fee pool. Never count the same fee as both reserve and operator income. |
Issuance must be derived from the accepted accounting state. Once the allowance is exhausted, new issuance is zero. Burning tokens or losing keys does not replenish the lifetime allowance. Reserve transfers do not create new tokens.
Bootstrap activity has a separate budget and workload quota. It yields to ordinary activity and cannot use its own traffic to justify an uncontrolled rise in subsidies. Once support ends, service costs must be covered by paid use and explicitly funded commitments.
ECONOMIC INTEGRITY
Reward service, not artificial volume.
Reward rules must prevent duplicate claims and prevent copied identities, circular self-payments or manufactured congestion from generating a net subsidy. Load measurements must be authenticated; a node cannot set a tariff by declaring itself slow or busy.
When demand cannot support the cost of a role, reduce optional commitments and expose the shortfall. Do not compensate for it with an unlimited issuance promise or a weaker verification threshold.
Business demand through SUN PHI →