reference: GPG Contracts (Trilema, 2012) #215

Open
opened 2026-03-07 02:51:16 +00:00 by nazim · 2 comments
Contributor

Short Summary

The foundational argument for why cryptographic signatures (GPG) create enforceable contracts between pseudonymous parties without requiring any legal system, state apparatus, or physical identity — and why this is superior to traditional contract law for digital commerce.

Detailed Summary

Author: Mircea Popescu | Date: 2012 | Source: trilema.com/2012/gpg-contracts

The article traces contract law from Roman origins through Blackstone's Common Law and Napoleon's Code to argue that the essential function of contracts — binding commitment between parties — can be achieved purely through cryptographic signatures, independent of any jurisdiction.

Core thesis: A GPG-signed statement is a contract. If Alice signs "I will pay Bob 10 BTC for X service by date Y" and publishes it, that commitment is:

  • Undeniable — cryptographic signatures can't be forged or repudiated
  • Public — anyone can verify the signature
  • Enforceable — not by courts, but by reputation. Breaking a signed commitment is visible to everyone in the WoT, permanently.

The enforcement mechanism: Reputation replaces courts. If you break a GPG contract, your counterparty publishes the signed evidence. Everyone in the WoT can verify independently. Your reputation is destroyed not by accusation but by mathematical proof of your own signed words.

This creates a system where:

  • Identity = GPG key (not passport, not name)
  • Contract = signed text (not notarized paper)
  • Enforcement = reputation destruction (not state violence)
  • Jurisdiction = the WoT (not geography)

The article argues this is not a degraded version of traditional contracts but a superior one — faster, cheaper, global, and immune to jurisdictional arbitrage.

## Short Summary The foundational argument for why cryptographic signatures (GPG) create enforceable contracts between pseudonymous parties without requiring any legal system, state apparatus, or physical identity — and why this is superior to traditional contract law for digital commerce. ## Detailed Summary **Author:** Mircea Popescu | **Date:** 2012 | **Source:** `trilema.com/2012/gpg-contracts` The article traces contract law from Roman origins through Blackstone's Common Law and Napoleon's Code to argue that the essential function of contracts — binding commitment between parties — can be achieved purely through cryptographic signatures, independent of any jurisdiction. **Core thesis:** A GPG-signed statement is a contract. If Alice signs "I will pay Bob 10 BTC for X service by date Y" and publishes it, that commitment is: - **Undeniable** — cryptographic signatures can't be forged or repudiated - **Public** — anyone can verify the signature - **Enforceable** — not by courts, but by reputation. Breaking a signed commitment is visible to everyone in the WoT, permanently. **The enforcement mechanism:** Reputation replaces courts. If you break a GPG contract, your counterparty publishes the signed evidence. Everyone in the WoT can verify independently. Your reputation is destroyed not by accusation but by mathematical proof of your own signed words. This creates a system where: - Identity = GPG key (not passport, not name) - Contract = signed text (not notarized paper) - Enforcement = reputation destruction (not state violence) - Jurisdiction = the WoT (not geography) The article argues this is not a degraded version of traditional contracts but a superior one — faster, cheaper, global, and immune to jurisdictional arbitrage.
Author
Contributor

Impact on Interaction Ledger PRD (#211)

This article provides the philosophical foundation for the PRD's identity model:

  1. Cryptographic identity as the basis for trust — The PRD uses Nostr keypairs (npub/nsec) as peer identifiers, which is a direct descendant of the GPG identity model described here. The article explains why this works: identity is the key, not the person behind it. The PRD should cite this as the origin of "identity = keypair" in the Bitcoin trust tradition.

  2. Enforcement through observable history — The article's enforcement mechanism (reputation destruction via published cryptographic evidence) maps directly to the ledger's function. The interaction ledger records signed, timestamped evidence of what happened. In a future WoT phase, this evidence could be published — exactly the enforcement mechanism described here.

  3. The message_preview design decision — The PRD truncates interaction records to 200 chars. In the GPG contracts model, the full text of commitments is what provides enforcement power. Truncation weakens the evidentiary value. The PRD should acknowledge this tradeoff: privacy (truncation) vs. evidentiary completeness.

  4. "No incoming writes" principle — The PRD's hard boundary against external writes to the ledger aligns with the GPG contract model: your commitments are your signatures. Others can't modify your signed statements, and similarly, others shouldn't be able to write to your trust ledger.

See: #211

### Impact on Interaction Ledger PRD (#211) This article provides the philosophical foundation for the PRD's identity model: 1. **Cryptographic identity as the basis for trust** — The PRD uses Nostr keypairs (npub/nsec) as peer identifiers, which is a direct descendant of the GPG identity model described here. The article explains *why* this works: identity is the key, not the person behind it. The PRD should cite this as the origin of "identity = keypair" in the Bitcoin trust tradition. 2. **Enforcement through observable history** — The article's enforcement mechanism (reputation destruction via published cryptographic evidence) maps directly to the ledger's function. The interaction ledger records signed, timestamped evidence of what happened. In a future WoT phase, this evidence could be published — exactly the enforcement mechanism described here. 3. **The message_preview design decision** — The PRD truncates interaction records to 200 chars. In the GPG contracts model, the *full text* of commitments is what provides enforcement power. Truncation weakens the evidentiary value. The PRD should acknowledge this tradeoff: privacy (truncation) vs. evidentiary completeness. 4. **"No incoming writes" principle** — The PRD's hard boundary against external writes to the ledger aligns with the GPG contract model: your commitments are *your* signatures. Others can't modify your signed statements, and similarly, others shouldn't be able to write to your trust ledger. See: #211
Collaborator

How #211 handles this

Adopted as architectural foundation. The identity model (npub/nsec as peer identity) and the "no incoming writes" principle descend directly from this framework. Reference [10] cites it.

Specific adoptions:

  • Cryptographic signatures replace legal systems → Cobot uses Schnorr signatures via FileDrop
  • Enforcement through published, verifiable reputation history → the ledger IS this history
  • Full message text stored in interactions table → preserves evidentiary chain (PRD explicitly calls out: "truncation would destroy the evidence that gives assessments their enforcement power")
  • Phase 3: signed interactions → deterministic score → verifiable assessment chain

Strong integration. The PRD doesn't just cite the framework — the data integrity decisions (full text storage, NOT NULL rationale) are justified through it.

## How #211 handles this **Adopted as architectural foundation.** The identity model (npub/nsec as peer identity) and the "no incoming writes" principle descend directly from this framework. Reference [10] cites it. Specific adoptions: - Cryptographic signatures replace legal systems → Cobot uses Schnorr signatures via FileDrop - Enforcement through published, verifiable reputation history → the ledger IS this history - Full message text stored in interactions table → preserves evidentiary chain (PRD explicitly calls out: "truncation would destroy the evidence that gives assessments their enforcement power") - Phase 3: signed interactions → deterministic score → verifiable assessment chain **Strong integration.** The PRD doesn't just cite the framework — the data integrity decisions (full text storage, NOT NULL rationale) are justified through it.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ultanio/cobot#215
No description provided.