Formalizing and Securing Relationships on Public Networks.¶
Szabo, N. (1997). Formalizing and Securing Relationships on Public Networks. First Monday, 2(9).
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Contract
- and the incomplete-contracting frame from economics maps directly onto them. Organizational governance. Service-level agreements, charters, and governance documents bind units within an organization, with an HR or audit function as the enforcement regime. Algorithmic and ledger settings. Smart contracts encode the obligation-and-consequence structure as executable code, with a blockchain as the enforcement substrate.
This sourceIntroduces smart contracts: obligation-and-consequence structures encoded as executable code with the network as enforcement substrate.
- and the incomplete-contracting frame from economics maps directly onto them. Organizational governance. Service-level agreements, charters, and governance documents bind units within an organization, with an HR or audit function as the enforcement regime. Algorithmic and ledger settings. Smart contracts encode the obligation-and-consequence structure as executable code, with a blockchain as the enforcement substrate.
- Future Or Promise
- The explicit pending/fulfilled/rejected state machine, articulated in software futures, was imported into smart-contract languages and off-chain settlement protocols.
This sourceIntroduces smart contracts, importing explicit conditional-fulfillment state machines and third-party-authority escrow patterns into cryptographic protocols.
- The explicit pending/fulfilled/rejected state machine, articulated in software futures, was imported into smart-contract languages and off-chain settlement protocols.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:0fd27e5a8e6c · see in the full table