From 74e4c02d54c7e328bba4f2ceef826e373d3069a1 Mon Sep 17 00:00:00 2001
From: Dan Connolly <connolly@agoric.com>
Date: Tue, 21 Dec 2021 16:59:19 -0600
Subject: [PATCH] docs(vats): prune refs to python provisioning service

Is there anything left that's worth saying about "scenario #1"?
---
 packages/vats/src/bootstrap.js | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/packages/vats/src/bootstrap.js b/packages/vats/src/bootstrap.js
index 42073d9a666e..6ed912660bab 100644
--- a/packages/vats/src/bootstrap.js
+++ b/packages/vats/src/bootstrap.js
@@ -1033,10 +1033,6 @@ export function buildRootObject(vatPowers, vatParameters) {
       );
 
       console.debug(`${ROLE} bootstrap starting`);
-      // scenario #1: Cloud has: multi-node chain, controller solo node,
-      // provisioning server (python). New clients run provisioning
-      // client (python) on localhost, which creates client solo node on
-      // localhost, with HTML frontend. Multi-player mode.
       switch (ROLE) {
         // REAL VALIDATORS run this.
         case 'chain': {