Recurring Payments on Chain: How Payroll Would Work with pallet-subscription and DUSD

Let us be precise about the frame: there is no payroll product on EmpoorioChain, no business paying salaries in DUSD, and no partner doing so. What exists is a set of native primitives that make a recurring-payment product straightforward to build. This post is the design, written so that whoever builds it — or evaluates whether to — knows exactly what is there.

The primitive

pallet-subscription (runtime index 73) models a recurring obligation: payer, payee, asset, amount, period, next due date, and rules for cancellation and renewal. It is the native equivalent of what on Ethereum needs a streaming-payment contract plus a keeper network to trigger it. On EmpoorioChain the due date is checked against consensus time — the block timestamp inherent — and the transfer executes in the runtime when due.

A payroll on top of it

1. The employer funds a payroll account in DUSD.
2. For each employee, it creates a subscription: payee = the employee's Eoonia account, asset = DUSD, amount = net pay, period = monthly.
3. Each period the runtime moves the amount. The employee sees it in Eoonia as included and then finalized — roughly 3.5 and 17 seconds on the testnet benchmark.
4. Adjustments are subscription updates; termination is a cancellation.

Cost per payment: a native transfer is about 0.000025 DMS on the testnet, and the target for any transfer is around $0.001. A hundred employees paid monthly is a rounding error.

What the chain guarantees

• Execution when due, without an off-chain scheduler that can fail.
• A stable unit: DUSD targets one dollar, so the amount the employee receives is the amount agreed. Target, not guarantee — the ecosystem does not call the peg risk-free.
• A verifiable record: every payment is an event indexed by EmpooScan.
• Compliance hooks, if required: pallet-compliance and pallet-identity-ssi can require the payee to hold a KryptoOS credential — proof of a right to work, for example — without revealing identity on chain.

What would have to be built

• An employer interface (there is none).
• Off-ramps, so an employee can turn DUSD into local currency — the ecosystem has none and does not partner with any exchange.
• Tax and reporting integration, jurisdiction by jurisdiction.
• The first real payment, on the live testnet, reported with a block number.

Why write the design without the product

Because the previous version of this page described a payroll partnership that did not exist, and the honest replacement is not silence — it is the actual state: a primitive in the runtime, a wallet that can receive, and a list of what is missing. If a team wants to build this, the testnet grants programme reserves a DeFi category for exactly this kind of pilot, once its prerequisites (a faucet, a stable explorer) are deployed.

Based on PALLET_REFERENCE.md, TOKENOMICS.json and TESTNET_GRANTS_PROGRAM.md.