Decentralised News · 2027 planning series · Reviewed 21 November 2026
What Matters
A salary stream can show a growing token amount while the employee still lacks money to pay a bill. The missing step might be funding, withdrawal, conversion or bank delivery. The useful question is how much of the agreed payment is available, when, and through which route.
Streaming also changes the employer’s funding discipline. A monthly transfer has a visible payment date. An ongoing stream needs enough usable funding throughout its operation. A large deposit arriving late can leave an earlier shortfall even when the end-of-month arithmetic looks comfortable.
This guide separates payroll obligations, protocol accrual and usable cash. Its original DN calculator tests a declared funding schedule with one possible top-up. It does not connect to a wallet, calculate legal wages or certify a payroll deployment.
The Signal: a faster balance display does not complete the payment
Money streaming is a real technical mechanism. Superfluid’s documentation describes continuous token flows with a rate expressed per second. That establishes a payment primitive. It does not establish that every employer can replace its payroll process, that every recipient can withdraw without cost, or that a stablecoin amount has already reached a bank account.
The most useful improvement may be a better account of what is outstanding. An employer can see its funding horizon. A contributor can distinguish a funded claim from an unfunded balance. Both can reconcile the same observation instead of arguing about two dashboards showing different quantities.
DN Alpha Thesis
The durable payroll opportunity is reliable access to an agreed amount with a clear exception process. Measure the route from authorized compensation to usable funds, including interruptions and remaining work. A per-second interface earns its place when that complete route improves the recipient’s experience and the payer’s control.
DN’s proposed decision rule has two parts: preserve the legal and accounting payment record, and test whether declared funding remains sufficient at every relevant point before the next top-up. A positive closing balance alone does not satisfy the second condition.
1. Keep five amounts in separate columns
| Amount | Question it answers | Evidence to preserve |
|---|---|---|
| Compensation owed | What does the employment or services arrangement require? | Approved payroll or invoice record, period and applicable deductions |
| Protocol accrual | What does the configured stream record over time? | Product, deployment, rate changes and observation reference |
| Available to withdraw or transfer | What can this recipient actually obtain at the observation? | Funded amount, current state and relevant permissions |
| Tokens received | What reached the intended recipient’s control? | Observed transfer or balance change and asset identity |
| Usable local money | What arrived through the recipient’s chosen spending route? | Conversion, fees, bank delivery and availability |
These columns may agree in a simple arrangement, but agreement should be demonstrated. An invoice can be due before a stream starts. A stream can accrue at the wrong rate. A withdrawal can reach the intended wallet while a bank conversion remains pending. Each mismatch points to a different owner and corrective action.
Use one observation time when comparing quantities. Keep the original payroll record intact when correcting a stream configuration. A new rate fixes future technical behavior; it does not explain an earlier underpayment by itself.
2. Choose the payment model before comparing products
Sablier Flow describes an open-ended debt-tracking model. Its documentation distinguishes total debt, covered debt and uncovered debt; covered debt is the withdrawable amount supported by the stream balance. Funding can arrive over time. This makes an outstanding token amount different from an immediately collectible one.
That is different from a pre-funded vesting allocation. Sablier Lockup uses a deposited amount and schedule. DN’s separate payment-stream change record examines its cancellation authority and deposited, vested and withdrawn inventory. That worksheet should not be repurposed as a funding forecast for open-ended salary flows.
Superfluid has another operational boundary. Its solvency documentation describes a buffer associated with opening a stream and the consequences of reaching critical or insolvent states. A buffer can be consumed and lost through liquidation. It is not a payroll reserve that an employer should plan to spend routinely.
Choose the model that fits the agreed obligation, then inspect the specific deployment. Product names are insufficient evidence of cancellation powers, available balances, fees or recipient rights. Record what happens when funding stops, not only what happens during a successful demonstration.
3. Define the time unit and amount explicitly
A promise of 3,000 tokens per month needs a calendar convention before it becomes a per-second rate. Is the instruction a fixed 30-day period, the actual calendar month, or an annual amount divided into a display convention? Those choices produce different rates.
Superfluid’s flow-rate examples use 365/12 days to translate a displayed monthly amount into seconds. A business should not silently substitute that interface convention for the agreed payroll period. Preserve the chosen period, start time, rate and rounding method together.
The calculator below uses the number of days the reader explicitly supplies. Its 3,000-over-30 example means 100 tokens per day. It does not claim that all months have 30 days or generate transaction-ready integer token amounts. Any deployment needs its own token precision and contract-level calculation.
Variable compensation needs a separate approved adjustment. Do not let a model infer a bonus from an ambiguous performance signal and change the stream automatically. An agent can prepare a proposed adjustment with its evidence; an authorized process determines whether the amount is owed.
4. Fund outstanding accrual before counting future runway
DN’s funding model starts with the current balance allocated to the payment, removes a declared reserve, and protects the unpaid amount that has already accrued. Only the remainder supports new accrual.
Let B be the current balance, R the reserve, D the accrued but unpaid amount, and q the continuing amount per day. Usable funding is U = B − R. The current uncovered amount is max(0, D − U). When q is positive, runway before additional funding is max(0, U − D) ÷ q.
This avoids a common double claim: presenting the whole pool as available for next month’s pay while it also backs an amount already owed. Withdrawing an already accrued amount reduces both the pool and the outstanding obligation; it should not create a new funding requirement for that same amount.
Use balance labels carefully. Include an accrued amount in D only if that obligation still needs funding from the entered pool. An amount already transferred to a recipient, or already debited from the reported balance, must not be charged to that pool again. If a displayed available balance already excludes a protocol buffer, enter zero for that same buffer in the reserve field. Subtracting it twice understates available funds. Combining several assets or recipient pools without a valid allocation rule creates a different problem that this one-token model cannot solve.
5. Stress the top-up date as well as its amount
A treasury forecast often shows monthly inflows and outflows in one column. Streaming makes the path within the month relevant. Ask what happens if the next deposit arrives after the existing runway expires, even if it eventually replenishes the account.
The DN instrument accepts one hypothetical top-up and its arrival day. It calculates the uncovered amount just before that deposit and again at the chosen horizon. A top-up after the horizon is excluded from the closing resources. A proposed deposit is an assumption, not cash observed onchain.
For operational use, attach an owner to the top-up and define the evidence of completion. “Finance approved it” and “the stream received spendable tokens” are separate events. Include the time needed for signing, transfer, confirmation and any conversion in the team’s actual process.
The tool’s mathematics treats an entered deposit as available instantly at its specified time. It therefore cannot establish a safe scheduling margin. An exact match between arrival and exhaustion leaves no modeled tolerance for delay.
6. Worked synthetic case: solvent at month-end, short on day sixteen
Consider an invented arrangement accruing 3,000 TOK over 30 days. At the review, the allocated balance is 2,000 TOK, a separately declared reserve is 100 TOK, and 500 TOK has already accrued without being paid. The usable pool is 1,900 TOK, leaving 1,400 TOK after covering the outstanding amount. At 100 TOK per day, the remaining runway is 14 days.
A proposed 1,800 TOK top-up arrives on day 14. Across the following 30 days, the model must cover the existing 500 TOK plus 3,000 TOK of new accrual. Resources are 1,900 + 1,800 = 3,700 TOK, leaving 200 TOK after those obligations. Arrival at the exact runway boundary leaves zero timing margin.
Now move the same top-up to day 16. The closing surplus remains 200 TOK, but the obligation immediately before funding is 500 + 1,600 = 2,100 TOK against 1,900 TOK of usable funding. There is a temporary 200 TOK uncovered amount. The positive closing result has not erased that interruption.
A treasury team could compare an earlier deposit, a larger initial balance or a shorter review interval. Which response is appropriate depends on actual authority, cash availability and the deployment. The example demonstrates arithmetic only; it is not a payroll trial, provider benchmark or forecast of employee outcomes.
DN Salary Stream Funding Planner
Enter one token, one allocated payment pool and one constant accrual rate from a common observation. The model separates existing uncovered accrual, time to exhaustion and a temporary gap before the proposed top-up. Use aliases in your own supporting records; no names, wallet addresses or salary documents are needed here.
DN Salary Stream Funding Planner
Change the illustrative assumptions below. This worksheet runs locally in your browser. It records your declarations; it does not verify evidence, connect to accounts, submit instructions or grant approval.
The initial numbers are synthetic. Unknown evidence remains unresolved. Downloads contain the values you enter; use aliases and avoid private or identifying information.
7. Measure the recipient’s withdrawal and cash route
The employee’s practical benefit depends on the next step. Can the recipient spend the asset directly, withdraw it to a wallet, redeem it, or convert it through an eligible provider? Who pays each cost, and what happens when a destination account rejects the transfer?
Sablier’s fee documentation separates interface charges from network gas and describes withdrawal fees that depend on product release and route, with possible sender subsidization. Continuous accrual should not be described as cost-free cash access. Check the current interface quote and the exact deployment before choosing a withdrawal frequency.
Suppose a recipient in a second invented scenario converts 1,000 tokens at a quoted 0.998 local-currency units per token, pays a 4-unit service fee and a 2-unit delivery fee. The resulting 992 units differ from the 1,000-token starting quantity. If a separately paid network charge is 1 unit, total economic proceeds after all declared costs are 991 units. The bank receipt and total cost are related but distinct measures.
This arithmetic does not supply a live quote. DN’s stablecoin payment-cost framework provides the wider route comparison. For a payroll pilot, record the amount actually available by the employee’s required date and investigate every unresolved difference.
8. Keep payroll approval and legal treatment outside the stream
Technical accrual cannot determine whether a person is an employee, how much compensation is legally due, or which deductions are permitted. Those decisions belong to the relevant payroll and legal process before the payment route is enabled.
The US example illustrates the distinction. IRS digital-asset guidance, including FAQ 61, treats digital assets paid as employee wages as subject to applicable withholding and employment-tax reporting, measured in US dollars. That tax treatment does not by itself authorize a particular wage-payment method.
Separately, 29 CFR 531.27 addresses prescribed wages under the Fair Labor Standards Act in cash or negotiable instruments payable at par, with specified statutory treatment of other facilities. An employer should not infer universal permission to pay statutory wages in tokens from a protocol’s payroll use case. Other jurisdictions and state requirements need their own review.
Record whether the route is intended for authorized contractor payments, a permitted compensation component, or another specifically reviewed arrangement. A zero-knowledge proof may support a defined data claim; it does not choose the governing law or calculate every payroll obligation.
9. Give an agent a bounded treasury job
An agent can prepare a daily funding comparison, flag a missed top-up, reconcile approved rates and draft an exception report. Keep the authority to add recipients, change compensation, withdraw reserves or move payroll funds into lending protocols separately controlled.
Use three linked records: the approved payment obligation, the stream configuration and the observed settlement history. A changed destination should trigger an independent recipient check. An uncertain transaction should trigger reconciliation before a retry. A stop instruction should state whether it changes future accrual, technical funding or an offchain obligation.
Sablier Flow’s state documentation distinguishes paused, streaming, solvent, insolvent and voided conditions. It also describes the removal of uncovered protocol debt on voiding. That contract behavior should not be reported as extinguishing an employment or services obligation outside the protocol.
Test the proposed process on a bounded authorized payment before expanding it. Measure successful receipt, exception frequency, remaining review time, total costs and funding margins. Avoid judging a pilot solely by how smoothly the displayed counter moves.
Methodology and limitations
DN reviewed the linked primary documentation on 21 November 2026 and compared this scope with its existing payment-stream change and payment-cost articles. The analysis is an operational decision method, not a live provider ranking. No payroll, wallet, account, tax return or contract deployment was executed or audited for this article.
The calculator assumes one token, one allocated pool, a constant nonnegative accrual rate, a fixed observation, a constant declared reserve and at most one top-up. It excludes price changes, fees, protocol-specific liquidation, incoming streams, pauses, refunds, rate changes, tax, legal wages and investment returns. It uses ordinary browser arithmetic for planning, with rounded displays; it is not suitable for producing contract transaction amounts.
For a real review, assign a named operational owner to each unresolved quantity in the organization’s private records. Date the funding observation, preserve the payroll-period convention and record the next review deadline. Update the comparison after any rate change, reserve movement, withdrawal or missed deposit. An unchanged spreadsheet is not a current funding monitor, even when its formulas remain correct.
All numerical cases are synthetic. Unknown input values must remain unresolved instead of becoming invented zeroes. A funded model is not proof of recipient access, legal compliance, asset value or future payment. The practical next step is a documented comparison against the organization’s current payment process using actual authorized observations.
Sources and evidence register
Primary sources reviewed on 21 November 2026. The article distinguishes documented facts, DN analysis and synthetic examples. Recheck changeable rules and configurations before acting.
- Superfluid: Money Streaming overview — Per-second flow mechanics and explicit monthly-rate conversion convention; not a payroll-law opinion.
- Superfluid: Liquidations and TOGA — Protocol buffer, critical/insolvent states and liquidation boundaries; no universal buffer amount assumed.
- Sablier: Flow overview — Open-ended debt tracking, covered and uncovered debt, funding and withdrawal distinctions.
- Sablier: Flow statuses — Paused/streaming solvency and voiding mechanics; protocol state does not determine external legal obligations.
- Sablier: Fees — Interface fees, gas, deployment-version scope and possible sender subsidization; no fixed quoted fee used in model.
- IRS: Digital-asset transactions FAQ — US federal tax treatment of digital-asset employee wages, particularly FAQ61; not permission to use a particular wage medium.
- eCFR: 29 CFR 531.27 — Current official text reviewed 21 November 2026: prescribed wage-payment medium under the FLSA, with statutory qualifications; not universal permission for token wages.
Frequently asked questions
Does salary streaming mean an employee receives cash every second?
No. A protocol can accrue or transfer tokens continuously while withdrawal, conversion and bank availability remain separate steps. Reconcile the recipient's actual route and costs.
Is an accrued token amount always withdrawable?
No. Sablier Flow, for example, distinguishes covered debt supported by the stream balance from uncovered debt. Check the exact product, deployment and current state.
Why can a funded month still contain a payment gap?
A deposit can arrive after existing resources are exhausted. The calculator checks the amount uncovered before a proposed top-up as well as the closing horizon balance.
Is a Superfluid buffer the same as an employer's payroll reserve?
No. The documented buffer supports protocol solvency and liquidation incentives. A business should record it separately and avoid counting it twice or treating it as freely spendable payroll funding.
Does stopping or voiding a stream settle unpaid wages?
A technical state change does not decide employment or services obligations. Preserve the approved payment record and separately reconcile protocol state and any amount still owed outside it.
Does this planner calculate taxes or tell an employer whether crypto payroll is lawful?
No. It models declared token funding only. Wage medium, deductions, withholding and reporting depend on the arrangement and jurisdiction and need a separate reviewed process.