// A HENCEFORTH WHITEPAPER · IN DEVELOPMENT
Scripted Supply
Legible, replayable contracts for procurement on Bitcoin SV.
Where EDI ends, the ledger begins.
// THE PROBLEM
Procurement runs on polite fictions.
Every B2B transaction today exchanges four documents: a purchase order, a shipping notice, an invoice, and a payment instruction. All four are syntactically correct. Any combination of them can be false. The system that produced them — EDI, designed in the early 1980s — has no way of telling.
EDI does not fail when it transmits incorrect information. It fails when it successfully transmits well-formed lies.
Reconciling the fiction against reality consumes an estimated five to ten percent of every B2B transaction value, in labour, dispute, and audit. For a mid-market business handling 1,000 purchase orders per month, the total cost runs to ~$90,000 per year.
// THE FIX
What if validation and execution were the same act?
Scripted Supply replaces the EDI settlement moment with cryptographically enforced state transitions on Bitcoin SV. Every purchase order is an on-chain UTXO. Its locking script encodes the exact conditions under which payment may move and ownership may transfer — opcode by opcode, enforced by consensus.
Delivery is not a confirmation email; it is a cryptographic attestation signed by the warehouse and a scan-preimage produced by the customer at the moment of physical receipt. Payment is not a separate banking instruction; it is the same transaction that consumes the purchase order, atomically.
LEGACY EDI
Payment can move without delivery. Delivery can be recorded without payment. The two facts live in two databases and disagree silently.
SCRIPTED SUPPLY
Payment and delivery are bundled into one Bitcoin transaction. Either both settle, or neither does. The pathology is structurally impossible.
// THE DIFFERENTIATOR
Contracts a procurement officer can read.
Bitcoin Script is a wall of hex to non-developers. An immutable contract nobody can read is a faith-based ritual, not a contract. Scripted Supply lets you write the contract in a restricted Forth dialect that compiles, deterministically, to the Script the chain enforces.
acme-widget-500-v1.ssforth
CONTRACT-BEGIN scripted-supply.po.v1
s" [email protected]" counterparty
s" [email protected]" customer
10000 unit-price-max
500 quantity
30 days-net payment-terms
s" SKU-WIDGET-A" sku
: ACCEPT-DELIVERY ( -- )
require-warehouse-sig
require-customer-scan-preimage
delivery-attest ;
: RELEASE-PAYMENT ( -- )
require-customer-receipt
require-after-delivery
payment-release ;
: DISPUTE ( reason -- )
require-customer-sig
7 days-after-delivery within
dispute-flag ;
CONTRACT-END SCRIPT-SAVE acme-widget-500-v1The same artefact a CFO reads is, byte-for-byte, the artefact the chain executes. The compiler emits the source, the compiled hex, a source map between them, auto-generated tests, and a dry-run trace — bundled as one auditable record.
// CAPABILITIES
What the platform does.
01
Atomic delivery-versus-payment
Payment moves only when delivery is cryptographically proven, in a single Bitcoin transaction. No half-completed trades, no invoices for goods never shipped, no goods delivered against invoices that get lost.
02
Zero-install supplier portal
Suppliers receive an email link, open it in any browser, and sign acceptance and delivery attestations with WebCrypto. The signing key lives in their device's IndexedDB. No wallet, no seed phrase, no install.
03
Audit-replay artefacts
Every saved contract emits Forth source, compiled Script hex, a source map linking them, auto-generated positive/negative test fixtures, and a dry-run trace — as one legal record a court can examine.
04
Type42 per-PO privacy
Fresh on-chain key for every purchase order, derived via BRC-42. Two POs from the same buyer-seller pair are structurally unlinkable to passive observers. Unlinkability falls out of ECDH, not storage discipline.
05
GDPR right-to-erasure
Encrypted payloads live off chain; only their SHA-256 hash is committed on chain. Destroying the off-chain ciphertext honours erasure obligations even though the ledger is immutable.
06
Cryptographic dispute trail
Disputes resolve against a non-repudiable cryptographic record: warehouse signature, customer scan-preimage, on-chain timing. Not against four EDI documents that disagree.
// THE WHITEPAPER
22 pages. The full architecture.
The thesis, the architectural fix, the asymmetric deployment, the Forth contract language, the privacy model, the worked economic example, and the pilot terms. Build on Craig Wright's foundational paper, expanded with the adoption and legibility layers it leaves open.
// PILOT
Looking for anchor customer #1.
One trading-partner relationship, migrated to Scripted Supply in eight weeks from contract signature. Real production purchase orders, on Bitcoin SV mainnet.
Three months free
Zero subscription. Customer pays chain fees only (~$30/month at pilot volume).
75% ROI exit gate
If measured savings at month three fall below 75% of projection, customer exits at no cost — chain fees refunded.
Eight-week build
From contract signature to working bilateral channel: Forth contract authoring, supplier portal, first production POs.
BUILT ON HENCEFORTH — A BITCOIN SV PLATFORM FOR IOS AND MACOS
// scripted supply is in development. nothing on this page is a commitment to ship.