/ 06 /The Mechanics of a New Economy

In a blockchain system, transaction validity depends on network consensus. In a Unyt transaction, validity is established through a signed handshake between the specific parties. Rather than co-signing a single shared action (as described in the original HoloFuel paper), each party validates and signs their counterparty’s action when committing to their own chain — with the result published to the distributed hash table for universal verifiability.

Completing a transaction takes only the two agents involved — but they remain accountable to the group: each validates both sides, so neither can commit an invalid action without being warranted and blocked by the peers who check it.

In the simplest sequence the first agent pays some units (committing a payment to their chain), then their counterparty accepts them (committing an acceptance to their chain which references the payment to validate). The most complex handshake sequence is for two-way trades, which run through four signed steps — propose, send, accept, and receipt — to get all the unit balances updated and sent in both directions. Any of these can be completed by two parties connected only to each other, with no access to the wider network; the rest of the network validates their actions once either agent reconnects.

Attempted double-spends are detectable: the initiator’s chain history is published, and any validator can check for conflicting entries, and for forking of their chain. Sybil resistance is addressed through the relationship between agent keys and the validation rules in each application’s DNA, so you cannot join a network you haven’t demonstrated the right to join. And there is no 51% attack vector because there is no global consensus to capture. What can be attacked is an individual agent’s connection to honest peers: a colluding group can isolate an agent and feed it invalid data, and an agent that builds on it is warranted for doing so. That exposure is targeted rather than global — the shared record is never corrupted for everyone at once — but it is real, and it is not currently reversible.

Credit is what makes a mutual credit currency a currency. Without it, balances only describe what each agent has earned; there is no medium to circulate, no purchase made before payment received, no economy. Credit architecture is economic architecture.

This is structurally different from credit in conventional finance, where bank credit is the privilege of currency creation, gated by institutions, tied to collateral, with rents extracted as interest. Mutual credit operates on the opposite principle. The currency is created at the moment of transaction. Credit limits are tied to demonstrated productive capacity rather than wealth on hand. No interest accrues, because no one is profiting from issuance. Credit, here, is not like bearing debt. It is the operational permission to participate in exchange before having generated the balance to do so.

One of the harder problems in distributed infrastructure: how do you pay for services costing fractions of a cent without the payment infrastructure costing more than the service? A Stripe transaction costs 2.9% plus $0.30. That fee structure makes a $0.00025 compute payment economically impossible. This fee floor is what blocks the machine economy — IoT, DePIN, automated service ecosystems requiring billions of micropayments — from existing at scale on conventional payment rails.

Holochain’s solution is cryptographically countersigned service logs and aggregated proof-of-service invoicing — the distinction from conventional batched settlement being that neither party can fabricate or dispute the logs unilaterally.

Each service log is cryptographically signed by both provider and recipient. Neither party can fabricate logs — the countersignatures make unilateral fraud detectable against the other party’s chain history. Logs accumulate until reaching the billing threshold, designed to keep billing costs below approximately 1% of transaction value. The Proof-of-Service invoice includes payor ID, amount, application ID, and the sequence IDs of the service logs it covers. Pre-authorisation tokens allow frequent small transactions to proceed without per-transaction validation overhead — a running tab settling at threshold. This enables genuine microtransaction economics for machine-to-machine payments where individual transactions may be worth thousandths of a cent.

This holds at the transaction volumes real applications generate. At extreme volume the constraint moves from fee economics to storage: the more data a network accumulates, the more capable the hardware needed to participate as a full node. Sharding defers that ceiling rather than removing it.