Defensive Acceleration (d/acc)

Defensive acceleration (d/acc) is a strategic stance — articulated most prominently by Vitalik Buterin — that occupies the middle path between unrestricted technological development (e/acc, “effective accelerationism”) and techno-pessimist restriction. Rather than slowing AI broadly, d/acc proposes actively accelerating defensive technologies that inherently favor protection over exploitation.

The AI Safety Atlas (Ch.3.6) treats d/acc as one of the five socio-technical-strategies.

Three Principles

Defensive

Prioritize technologies making protection easier than threat creation. Unlike purely restrictive approaches requiring global coordination, defensive technologies provide tangible resilience that doesn’t depend on adversaries also adopting safety norms.

Differential

Accelerate beneficial technologies while exercising caution about harmful ones. The development sequence matters: advancing cybersecurity measures before autonomous hacking systems creates protective layers beforehand. This shares the strategic logic of differential-development (capability vs. safety research) but applies broadly across technology classes.

Decentralized

Distribute capabilities and governance across diverse stakeholders. Prevents single points of failure and unilateral control over transformative technologies. Anti-power-concentration as design principle, not just outcome.

Practical Applications

The Atlas catalogs concrete d/acc applications:

  • Cybersecurity — AI for vulnerability detection, system monitoring, automated patching
  • Biodefense — advanced air filtration, rapid pathogen detection, early-warning systems
  • Information integrity — blockchain-verified information systems, watermarking, provenance attestation
  • Resilient infrastructure — distributed energy generation, localized manufacturing
  • Anti-deepfake / anti-scam — AI-powered scam call detection (e.g., chatbot Daisy, Jolly Roger Telephone services that engage scammers in unproductive conversations)

Offense-Defense Balance

D/acc’s effectiveness depends on maintaining favorable offense-defense balances in each domain.

Historical patterns:

  • Cybersecurity often favors defenders (patches deploy faster than attacks scale)
  • Biosecurity traditionally favors attackers (creating a virus costs ~1B)

D/acc’s strategy is to shift each domain toward defender-favorable balance through deliberate investment. Where offense and defense use similar technology, d/acc pulls forward defense’s deployment.

Distinction from Pure Acceleration / Pure Pause

  • e/acc (effective accelerationism) — accelerate everything; trust that benefits outweigh harms
  • Pause / restriction — slow or stop AI development entirely
  • d/acc — accelerate defensively useful AI while exercising caution about offense-favoring applications

D/acc is compatible with differential-development but slightly different in scope. Differential development is mostly about safety-research vs. capability-research within AI; d/acc is about the broader technology landscape, asking which technologies (across all domains) make humanity more resilient to AI risks.

Critiques

The Atlas notes structural problems:

  • Domain dependence — d/acc requires per-domain offense-defense analysis; not all domains favor defenders
  • Capability dual-use — defensive technologies often have offensive applications too (vulnerability scanning ↔ exploitation; cyber-defense AI ↔ cyber-offense AI)
  • Coordination assumptions — accelerating defensive AI requires capable actors to actually invest in defense; market signals may not deliver this
  • Open-source tension — decentralization principle may conflict with the access-control needs of frontier safety

Connection to Wiki

D/acc connects to multiple wiki concepts:

Sources cited

Primary URLs harvested from this page’s summary references. Auto-generated by scripts/backfill_citations.py; edit by re-running, not by hand.