Notes from engineering and research.
Smart-contract design, manufacturing settlement, optical metrology, and what running the Fairbuild platform has taught us.
61 tests — what they cover, why it matters
Settlement happy paths, funding conservation, SVT monotonicity, auth violations, fee-rounding edges. The full suite runs in 0.15s. Here's the map of what each test class actually proves about the contract.
The smart contract behind a 48-hour settlement
From funded state to factory settlement instruction — the actual on-chain state machine. Five lifecycle stages, three roles, two contracts on Stellar Soroban. With the Rust that runs each transition.
Why we picked Stellar Soroban
EVM was the obvious choice. We didn't pick it. A short note on what mattered for an OEM↔Factory settlement layer that uses fiat banking rails on the front end and an on-chain audit trail on the back.
What Rolls-Royce figured out in 1962
Power-by-the-Hour reframed jet-engine sales as outcome contracts and forced every other engine OEM to follow. The same principle applies to contract manufacturing — and the smart contract makes per-service settlement actually administrable.
Why your factory gets paid in 120 days
Net-120 isn't a processing delay. It's five sequential structural layers stacked on top of a deliberate AP optimization. Spec ambiguity, data flow, OEM re-verification, dispute drag, and treasury policy — broken down.
Ready to stop reconciling QA spreadsheets before every payment cycle?
Bring one source file and one milestone. Fairbuild will map the gates, review path, and settlement consequence.