162 lines
8.2 KiB
Org Mode
162 lines
8.2 KiB
Org Mode
:PROPERTIES:
|
|
:ID: c2d3e4f5-a6b7-8901-2cde-f01234567890
|
|
:CREATED: [2026-05-25 Mon]
|
|
:END:
|
|
#+title: Phase 2 — Impact
|
|
#+filetags: :passepartout:strategy:adoption:impact:
|
|
|
|
Phase 2 spans 10⁴ to 10⁶ users. The protocol's economic weight becomes
|
|
measurable. See the [[id:92ccd074-04a0-4e45-a44f-9da24ea20a9b][Impact]] overview for context.
|
|
|
|
**Verification:** First regulator encode makes adoption mandatory in a
|
|
domain. Cloud revenue decelerates as Lisp machines replace racks of x86
|
|
servers. Compliance industry sees 30-50% paper audit reduction.
|
|
Insurance differentiates on verification — actuarial wedge forms.
|
|
|
|
**Social protocol:** Contract marketplace reaches critical mass.
|
|
Freelancers and cross-border workers use the protocol for verifiable
|
|
contracts and escrow, bypassing Upwork's 20% fee and jurisdictional
|
|
legal uncertainty. The reputation graph from Phase 0-1 communities now
|
|
carries real economic weight — a proven history of verified transactions
|
|
is more valuable than any platform's rating system. Cross-jurisdiction
|
|
transactions execute with no reference to any state's legal system.
|
|
|
|
**Impact on platforms:** The unbundling accelerates. Stripe loses
|
|
payment volume in protocol communities — Lightning is free, Stripe takes
|
|
2.9% + $0.30. DocuSign loses contract volume — SCAL contracts are
|
|
native to the protocol, not a separate subscription. Upwork and Fiverr
|
|
lose freelancers who bypass the platform fee by contracting directly
|
|
through the protocol. Discord loses communities that migrate to
|
|
cryptographically owned Social Spaces. These are not competitive
|
|
responses the incumbents can match — Stripe cannot offer social and
|
|
contracts, Discord cannot offer zero-fee payments and portable identity.
|
|
|
|
**Financial services:**
|
|
|
|
*Insurance differentiation — the actuarial wedge:*
|
|
|
|
This is the first structural impact on a core financial service.
|
|
Insurers who adopt verification (using gate logs for underwriting)
|
|
develop a pricing advantage over insurers who rely on self-reported data.
|
|
The wedge works as follows:
|
|
|
|
- A verified insurer attests property condition, security system status,
|
|
driver behaviour, or inventory integrity through gate logs. The data
|
|
is cryptographically proven and cannot be fabricated.
|
|
- An unverified insurer relies on customer statements, paper forms, and
|
|
spot audits. Their data is noisy and expensive to collect.
|
|
- The verified insurer prices 15-30% lower because their risk model is
|
|
better. Policyholders migrate. The unverified insurer bleeds
|
|
low-risk customers and is left with a riskier pool — classic adverse
|
|
selection in reverse.
|
|
- At scale, the wedge widens as the verified insurer accumulates more
|
|
data and refines their gate rules. After 2-3 years, the unverified
|
|
insurer cannot compete on price without adopting verification
|
|
themselves.
|
|
|
|
This is not a regulatory mandate — it is a competitive dynamic that
|
|
drives adoption without requiring a regulator to act. Insurance
|
|
differentiation is the most organically potent force for verification
|
|
adoption in the financial sector at this phase.
|
|
|
|
*Mutual insurance — first social protocol pools:*
|
|
|
|
Phase 2 is where the first mutual insurance pools form on the social
|
|
protocol. These are small-scale, community-level arrangements, but
|
|
they demonstrate the structural difference the protocol enables.
|
|
|
|
The three problems that have always limited mutual insurance:
|
|
|
|
1. **Adverse selection** — high-risk members join, low-risk members
|
|
leave, the pool collapses.
|
|
2. **Fraud** — members claim for events that did not happen or inflate
|
|
losses.
|
|
3. **Governance overhead** — someone must collect contributions, verify
|
|
claims, manage reserves. This either costs money (killing small-pool
|
|
economics) or concentrates power (creating insider risk).
|
|
|
|
The protocol addresses all three at the architecture level:
|
|
|
|
- **Adverse selection:** The pool queries the reputation graph — how
|
|
long has a member's DID existed, how many contracts have they
|
|
fulfilled, have they been party to an arbitration dispute? A newcomer
|
|
with a fresh DID and no history pays higher contributions until they
|
|
have enough verified history for standard rates. This mirrors social
|
|
insurance where community members vouch for each other, except the
|
|
vouching is verifiable.
|
|
- **Fraud:** A claim requires a gate attestation. For some events this
|
|
is direct (a weather oracle attests to flood damage in a postal code).
|
|
For others it requires social attestation (two pool members with
|
|
verified DIDs attest they witnessed the damage). Any fraud requires
|
|
collusion across multiple verified identities, each of whom loses
|
|
reputation if detected. The cost of successful fraud exceeds the
|
|
benefit for most cases.
|
|
- **Governance:** The pool is a Collective Persona. Contributions are
|
|
automatic on schedule. Payouts execute automatically when a claim
|
|
gate rule passes. The reserve balance is transparent on the proof
|
|
log. Disputes go to the protocol's arbitration guilds. Overhead drops
|
|
from "hire a part-time administrator" to "define the contribution
|
|
and claim rules once."
|
|
|
|
At Phase 2, mutual pools are small — neighbourhood risk-sharing
|
|
(appliance failure, minor medical bills, income disruption), hobbyist
|
|
guilds (equipment damage for a shared workshop), or community groups
|
|
(shared liability for a community garden or event). Members know each
|
|
other socially, which is a strong check on adverse selection and fraud
|
|
independently of the protocol. The protocol handles the mechanics that
|
|
would otherwise require a treasurer and a spreadsheet.
|
|
|
|
These pools would never be economical as conventional insurance products
|
|
— the premium is too small to justify administrative cost. The protocol
|
|
makes them viable because the marginal cost of running a pool is near
|
|
zero once the gate rules are defined. This is the first demonstration
|
|
that the protocol enables risk-sharing arrangements that the market
|
|
cannot serve.
|
|
|
|
*Cross-border payments:*
|
|
|
|
The contract marketplace enables a new kind of cross-border payment. A
|
|
worker in Kenya receives payment as a Lightning transaction through a
|
|
protocol contract. The employer in Germany sends euros; the contract
|
|
executes a currency conversion gate rule and delivers satoshis to the
|
|
worker's DID. The cost is near-zero. The settlement is instant. The
|
|
worker needs no bank account, no remittance service, no Western Union.
|
|
This is Phase 2 because it requires the contract marketplace to have
|
|
critical mass, which it reaches at this phase.
|
|
|
|
**Governance and law — first hints:**
|
|
|
|
The arbitration guilds that handle contract marketplace disputes are the
|
|
first proto-legal institution built on the protocol. A dispute between a
|
|
freelancer in Nigeria and a client in Germany goes to a guild rather
|
|
than to either country's courts. The guild's jurisdiction is neither
|
|
territorial nor contractual in the conventional sense — it is consented
|
|
to by both parties through the contract's arbitration clause. The guild
|
|
applies its own procedural rules, renders a decision, and the escrow
|
|
gate executes the outcome automatically.
|
|
|
|
This is a new legal phenomenon: private law that is both trans-
|
|
jurisdictional and self-executing. No state court enforces the guild's
|
|
judgment — the protocol does. The guild's legitimacy comes from its
|
|
reputation on the protocol, not from a state's delegation of authority.
|
|
At Phase 2, this is limited to small-value commercial disputes, but
|
|
the structural precedent is set.
|
|
|
|
Separately, the first dissident communities and opposition organizers in
|
|
authoritarian regimes begin using the protocol for secure coordination.
|
|
The repression they face is the first evidence that the protocol's
|
|
censorship resistance is a political fact, not a technical curiosity.
|
|
These early political users are invisible to most of the protocol's
|
|
user base, but they matter disproportionately to the long-term
|
|
trajectory — they create a use case that no consumer application can
|
|
match and no government can tolerate.
|
|
|
|
**Economics:**
|
|
|
|
On the destruction side: cloud revenue deceleration in regulated
|
|
markets, compliance industry revenue loss ($60-100B of the $200B market
|
|
affected), early platform revenue loss at Stripe, DocuSign, and Upwork.
|
|
On the creation side: contract marketplace fees ($20-100M), gate rule
|
|
consulting, insurance differentiation revenue. Capital begins
|
|
reallocating from intermediation to infrastructure.
|