# Evidence · The arsenal, and what it replaced · tracker items A.00 to A.02 at c7a2f8fed166

Tracker items copied whole from `ISIS_CHROMA_RUNPOD_MVP_TODOS_2026-09-11.md` at commit `c7a2f8fed166b8b63e679d8655af4886602319ac` (`git show c7a2f8fed166b8b63e679d8655af4886602319ac:ISIS_CHROMA_RUNPOD_MVP_TODOS_2026-09-11.md`), each with its line range in that file. Nothing was run to produce this.

## A.00.03 · lines 5085 to 5117

````text
- [x] **A.00.03** Pull order and path, fixed here so no session improvises: (1)
      **S3 PUT for everything under ~3 GB** (C.02.09's
      `runpod-volume-s3-put.mjs`, $0, download on the Mac, `shasum -a 256`
      against the hash in the row first): SAM 3.1, Depth Anything 3, every
      Civitai LoRA, the LTX-2.5 IC-LoRAs and upscalers, the SCAIL-2 LoRAs, the
      SeedVR2 VAE; (2) **one loader-pod run** (V.02.04's recipe, CPU pod
      EU-RO-1, ~86.7 MB/s measured, so ~430 GB ≈ 85 min ≈ $0.09 of pod time —
      _superseded 2026-09-13 by option B: pulls stream through the pod to
      Hetzner, whose measured upload is 37.8 MB/s with 8 parts, so ~430 GB ≈ 3.2
      h ≈ $0.19_) for every Hugging Face heavyweight and the three Civitai
      checkpoints — the loader already handles `source: civitai` rows with
      `CIVITAI_API_KEY` (C.02 pulled UnCanny and Photonic that way); (3) nothing
      is retired until its replacement has rendered (A.01.04, A.01.06, A.02.07,
      A.02.08). Retire-before-pull is **not** required at 1024 GB — the peak
      fits — so the order is about cost and proof, not space. Record wall clock
      and pod cost as V.02.04 did. _2026-09-13 later, superseded in part by
      option B: the destination of every pull is the **Hetzner library**, not
      the volume. The loader leg becomes L.01.04's `library-pull`; the "download
      on the Mac and S3 PUT" leg uploads to Hetzner, not to RunPod's volume API.
      Files reach the cache only through L.04's sync._ _**Done 2026-09-14
      06:00Z.** Every A-row went to the Hetzner library by library-pull pods (no
      Mac download leg was needed: the loader streams Hugging Face and Civitai
      sources straight into multipart uploads). Six pods from 21:51Z to 06:06Z,
      0.49 USD of pod time at 0.06/hour, recorded pod by pod with result files
      under the A.00 evidence section. Three loader defects surfaced and were
      fixed on the way: a dropped source read threw away the whole upload (Range
      resume), a timed-out source open was never retried, and a stalled part had
      five quick attempts (now twelve, with a landed object recognised after a
      Complete errors); the start loop also reruns a killed loader. Library: 117
      objects, 813.38 GB of the 900 GB alarm line. One row is not in it: the
      CyberRealistic Z-Image bf16 file, whose Civitai download answers 403 to
      the account's key (A.03.02). Nothing was retired before its replacement
      rendered._
````

## A.00.04 · lines 5118 to 5155

````text
- [x] **A.00.04** Manifest rows for every A-item **before** any byte moves
      (V.02.02's pattern): Hugging Face rows carry the 40-hex revisions from the
      2026-09-13 facts block and the LFS oid as `sha256`; Civitai rows carry
      `modelVersionId`, `fileId`, the version API's SHA-256, `gated: true`,
      `auth: CIVITAI_API_KEY`; shared files use `sharedBy` and add no bytes
      (`ae.safetensors`, `qwen_3_4b.safetensors`, umt5, `clip_vision_h`). Add
      `geometry_estimation` to the lint's `ALLOWED_TOP_FOLDERS` with a comment
      naming the Depth Anything 3 core node that reads it, and a `--strict` lint
      run green with every row present (that is the 22.0 % headroom the 1024 GB
      size buys). Add an `id` prefix per family (`ltx25-`, `wan22-animate2-`,
      `seedvr2-`, `sam31-`, `zimage-`, `da3-`, `hidream-o1-`, `klein4b-`,
      `qwen-image-`, `scail2-`, `civitai-`) so the inventory page groups them.
      _2026-09-13 later: each A-row also gets its family ids (L.02.01), and its
      library key is `isis/models/` plus `destPath` (L.01.01)._ _**Done
      2026-09-13 21:50Z: 62 rows, 112 in all, 825.94 GB; strict lint 0 errors, 0
      warnings; cache 238.71 GB pinned plus LTX-2.5 92.19 GB of 380 GB
      allowed.** Sizes and SHA-256 were read again from the Hugging Face tree
      API at each pinned revision and from the Civitai version API, and exact
      Civitai byte counts from a one-byte ranged download (the version API
      reports kilobytes). Reading the ComfyUI templates before writing rows
      changed four things: LTX-2.5 loads the plain video VAE (the conv variant
      is not taken) and a second Gemma 4 E2B encoder; HiDream-O1 loads a Gemma 4
      E4B encoder (the facts block said none); the Z-Image controlnet patches
      live in the model patches folder, which the lint now allows beside the
      geometry estimation folder; both encoders come from Comfy-Org gemma-4 at
      bf16, Apache-2.0, because the templates ship int8 and fp8 builds. The
      Animate-2 and SCAIL-2 templates name a bf16 Wan VAE; per A.01.05 the
      volume's Wan 2.1 VAE is tried first, so no row. Shared files gain families
      and sharers rather than duplicate rows (umt5, CLIP vision H, the Wan 2.1
      VAE, the Flux ae, Qwen3 4B, SAM 3.1, the Qwen-Image encoder and VAE, the
      SeedVR2 VAE). Fifteen new families, one pinned (SAM 3.1); the Chroma set
      and the Wan LoRA pairs join their pinned families. Gated rows: the LTX-2.5
      repos answered 403 until the user accepted the three licence gates on
      2026-09-13; the rows carry auth HF ACCESS TOKEN, and the loader now sends
      it (it never had) while the provisioner injects it only when a gated row
      is in the manifest. One open risk: the CyberRealistic bf16 file's download
      link answered 403 to a ranged probe, so its size is the API's kilobyte
      figure and the pull will refuse loudly if that is wrong. Commit below._
````

## A.01.04 · lines 5286 to 5318

````text
- [x] **A.01.04** Retire LTX-2.3 after A.01.02 has rendered: remove the rows
      `ltx23-22b-dev`, `ltx23-spatial-x2`, `ltx23-temporal-x2`,
      `gemma3-12b-it-bf16`, `ltx23-distilled-lora-1.1`,
      `ltx23-ic-lora-union-control`, `ltx23-ic-lora-motion-track` (80.38 GB)
      from the manifest, delete the files over the volume's S3 API (add a
      guarded `rm` to `runpod-volume-s3-put.mjs`: `models/` prefix only, refuses
      unless the manifest row is already gone, needs `--yes`), delete the
      `ltx23-av` catalog entry and its goldens in the same commit (an entry
      pointing at absent weights is a fabricated capability), lint, evidence.
      V.12.02 and V.12.03 close as superseded when this does. If the 2.5
      Union-Control IC-LoRA has appeared by then, it replaces V.12.02's 2.3-only
      control set under A.01.02, not here. _2026-09-13 later: under option B the
      retirement deletes the object from the Hetzner library and evicts the
      family from the cache through L.04; the volume-side `rm` helper is not
      built._ _2026-09-14, retirement, catalog and manifest half, after LTX-2.5
      rendered t2v with audible audio, Ingredients and pixel x2 (A.01.02,
      A.01.03): the `ltx23-av` workflow, its eight goldens and golden spec,
      registry and taxonomy entries, motion caps, Studio preset and video
      inventory entries are gone, and the seven rows (80.37 GB) and the ltx23
      family are out of the manifest (100 rows, 707.29 GB, 28 families), with
      the register regenerated. Specs that used it as the real sfw_only or
      two-family example now use ltx25-av, wan22-t2v or wan21-vace-edit; the
      V.11 live-proof harness's LTX stage runs LTX-2.5 distilled. Capability
      given up: LTX canny, depth, pose and motion-track control (no LTX-2.5
      union-control row exists); Wan VACE still offers depth, pose and canny.
      The ltx-av-options renderer module is now used by no catalog workflow.
      V.12.02 and V.12.03 are superseded (noted on them). Stays open for
      deleting the seven files from the Hetzner library, which waits on the
      user's confirmation._ _**Done 2026-09-14 20:41Z.** On the user's go, the
      seven LTX-2.3 files (80,373,783,346 B) are deleted from the Hetzner
      library by exact key, and an 8.72 GB partial Gemma 3 download left on the
      cache volume by an interrupted pull is deleted with them. A re-listing
      shows nothing left (evidence A.05.03)._
````

## A.01.06 · lines 5329 to 5381

````text
- [x] **A.01.06** `wan22-animate-2` catalog workflow: driving video and
      reference image in, **no** `OnnxDetectionModelLoader` /
      `PoseAndFaceDetection` / `DrawViTPose` stage, a `viewpoint` text input,
      `speed_mode: distilled` (10 steps, no CFG, euler). Validated, then one
      live clip at the V.11 minimum shape and one at the shape that once killed
      a worker (896-class); `wan22-animate` stays until both have rendered, then
      Animate-1's two rows (35.99 GB) and the `wan22-animate` entry retire by
      the A.01.04 procedure. `content_policy: adult_ok`. _2026-09-14, offline
      half done; stays open for the two live clips. Built from the distilled
      Animate-2 template: 10 steps, the LCM sampler (not euler as written
      above), CFG 1, shift 5, reference image and driving clip in, no pose or
      face preprocessing stage, output at the clip's rate with its audio. Only
      the distilled schedule exists: the base template needs the lightx2v I2V
      distill LoRA, which has no manifest row, and the template has no viewpoint
      conditioning. The volume's Wan 2.1 VAE and fp16 umt5 stand in for the
      template's bf16 VAE and fp8 encoder. The family also pulls the 32.79 GB
      base row, which no graph loads. The Studio now asks for a length in frames
      for graphs whose rate follows the clip; seconds times an unknown rate had
      written length 0. Adult content allowed, validated, sticker cost._
      _2026-09-14, decision: the unused Animate-2 base bf16 is out of the
      wan22-animate2 cache family (user chose to keep it in the library but stop
      syncing it), in a library-only family no workflow requires; an Animate-2
      sync now copies 45.67 GB instead of 78.46 GB. Adding a lightx2v I2V
      distill LoRA row later would let a base schedule use it._ _2026-09-14: the
      lightx2v I2V distill LoRA row this note names is E.03.01._ _2026-09-14,
      live clip at the minimum shape: 33 frames at 482 by 854 requested, 480 by
      848 out (88646ae9, 244.1 s cold, 0.4021 USD), the reference identity
      preserved; the driving clip showed the same person, so it proves the
      graph, not motion transfer. Stays open for the 896-class clip and the
      Animate-1 retirement._ _2026-09-14, the 896-class clip: 33 frames at 512
      by 896 exactly (37528cd3, 253.5 s cold, 0.4174 USD, under the 275 s the
      catalog rate predicts), with the reference woman following the driver.
      Both clips have rendered, so `wan22-animate` may now retire; stays open
      for that retirement (A.05.03)._ _2026-09-14, retirement, catalog and
      manifest half: the `wan22-animate` workflow, its two goldens and golden
      spec, registry and taxonomy entries, motion caps, Studio preset and video
      inventory entry are gone; the specs that used it as an example now use
      Animate-2 or SCAIL-2, and the V.11 live-proof harness's Animate stage runs
      Animate-2. Animate-1's transformer and relight LoRA rows and the
      wan22-animate family are out of the manifest (107 rows, 787.66 GB, 29
      families), and the shared umt5, Wan VAE and clip_vision_h rows no longer
      list it; the register is regenerated. The snapshot spec excuses the
      Animate-1 transformer the recaptured build still offers, and fails once a
      later snapshot drops it. The YOLOv10m and ViTPose rows (1.30 GB) that only
      Animate-1's pose pass loaded stay as a library-only family no workflow
      requires, and the WanAnimatePreprocess pack stays in the image until a
      rebuild. Stays open for deleting the two retired files from the Hetzner
      library (35.99 GB), which waits on the user's confirmation._ _**Done
      2026-09-14 20:41Z.** On the user's go, Animate-1's transformer
      (34,549,787,368 B) and relight LoRA (1,436,673,432 B) are deleted from the
      Hetzner library by exact key; the cache held neither. The two pose models
      Animate-1 alone loaded stay in the library as an unrequired family until
      someone says otherwise (evidence A.05.03)._
````

## A.01.08 · lines 5388 to 5427

````text
- [x] **A.01.08** `seedvr2-upscale` motion workflow (7B, video endpoint) beside
      `flashvsr-upscale`, and a `seedvr2_3b` option on C.12.02's still-upscale
      tail beside RealESRGAN x2 (image endpoint, 6.78 GB). One live clip and one
      live still; write both rates. RealESRGAN's row stays until the still tail
      has rendered on SeedVR2 3B, then retires. _2026-09-14, offline half done;
      stays open for one live clip and one live still. The third-party SeedVR2
      templates needed a node pack the worker does not have, so both are built
      on the int8 SeedVR2 templates, which use only the core SeedVR2 nodes the
      snapshot lists, with the fp16 rows substituted (7B for the clip upscaler,
      3B for the still tail; the core loader's default dtype keeps fp16). Clip
      upscaler: one step, CFG 1, tiled encode and decode, keeps the source rate,
      audio and bit depth, the FlashVSR caps; its sticker borrows FlashVSR's
      rate and probably understates. Still tail: the Chroma upscale enum is now
      none, x2 or seedvr2_3b, at 2x for the same output limit as RealESRGAN; the
      existing goldens render byte-identical. Families are per workflow, so the
      two Chroma workflows now require the SeedVR2 3B family, pinned beside
      RealESRGAN (pinned closure 246.00 GB) so an eviction can never stall a
      Chroma still behind its re-sync. RealESRGAN stays._ _2026-09-14: the still
      tail rendered live on SeedVR2 3B (9de9bb72, 2048 square, 79.2 s, 0.0348
      USD; no banding in the file, 3,963 distinct colours in a smooth patch).
      Stays open for the clip and RealESRGAN's retirement._ _2026-09-14, live
      clip: SeedVR2 7B upscaled a 33-frame 480 by 832 clip 2x to 960 by 1664
      (07f38e2a, 129.1 s with the model load, 0.2127 USD); seedvr2-upscale is
      rendered with a measured per-output-megapixel-frame rate. Both proofs are
      now in; stays open only for RealESRGAN's retirement (A.05.03)._
      _2026-09-14, retirement, catalog and manifest half: the x2 tail is gone
      from chroma-txt2img and chroma-img2img (upscale is none or seedvr2_3b; a
      job naming x2 is refused at render with the options it may use, tested),
      both require only chroma-core and seedvr2-3b, the x2 golden is deleted and
      the others render unchanged; the RealESRGAN row and its pinned family are
      out of the manifest (109 rows, 823.65 GB, 30 families, 10 pinned, pinned
      closure 245.93 GB), the register is regenerated and the image endpoint
      inventory no longer requires it. A stale spec that expected no cache when
      only the volume variable was unset (the manifest has named the cache
      volume since L.06.05) now also hides the manifest. Stays open for deleting
      the file from the Hetzner library and the cache volume, which waits on the
      user's confirmation._ _**Done 2026-09-14 20:41Z.** On the user's go,
      `RealESRGAN_x4plus.pth` (67,040,989 B) is deleted from the Hetzner library
      and, with its hash sidecar, from the cache volume, by exact key; the cache
      database marks the realesrgan family evicted (evidence A.05.03)._
````

## A.01.09 · lines 5428 to 5471

````text
- [x] **A.01.09** SAM 3.1 on core nodes: row
      `checkpoints/sam3.1_multiplex_fp16.safetensors` (1.75 GB, S3 PUT); switch
      `sam3-video-track`, `sam3-track-then-vace`, `sam3-segment` and
      `sam3-segment-inpaint` from the ComfyUI-SAM3 / ComfyUI-RMBG vendored nodes
      to `SAM3_Detect`, `SAM3_VideoTrack`, `SAM3_TrackToMask`; validated, then
      one live re-render of `sam3-video-track` and one of `sam3-segment`. Only
      after those render: drop ComfyUI-SAM3 (`de0ff5d2`) and RMBG's `sam3/`
      import from the image (a rebuild; the pycocotools and dangling-symlink
      fixes become dead weight) and close V.12.01 as superseded. The
      `sam3/sam3.safetensors` and `sam3.pt` rows (6.9 GB) retire with the packs.
      _2026-09-13, offline half done; stays open for the two live re-renders and
      the pack removal. All four graphs now load SAM 3.1 through the core
      checkpoint loader and run the core detect, video-track and track-to-mask
      nodes (core in ComfyUI 0.34.0, the version on the worker). Inputs with no
      core equivalent were removed rather than left ignored: the start frame and
      direction on video track, the track frame on track-then-VACE; the core
      node's object cap and detect interval were added. All four are validated,
      not rendered. The snapshot predates the SAM 3.1 row, so its one combo
      value is excused by name in the snapshot spec, which fails once a
      recaptured snapshot lists it._ _2026-09-14: sam3-segment re-rendered live
      on SAM 3.1 core nodes (4f43f8b2; mask is the subject's silhouette, cut-out
      alpha 0 on the background and 255 on the subject) and is rendered with
      measured cost. Stays open for the sam3-video-track clip and the pack
      removal._ _2026-09-14, live clip: sam3-video-track on SAM 3.1 core nodes
      (129e7f2e, 33 frames, mask aligned on the named object; a first run with a
      prompt naming nothing in the clip returned a false positive at the default
      threshold, recorded). Both re-renders are in; stays open for the pack
      removal rebuild and the old SAM 3 rows' retirement._ _2026-09-14, pack
      removal and rows: ComfyUI-SAM3 and ComfyUI-RMBG's SAM 3 still node (with
      pycocotools, the sam3 folder, its symlink and path key) are out of the
      image, and the two SAM 3 rows and their pinned family are out of the
      manifest (98 rows, 9 pinned families, pinned closure 239.03 GB). Build
      a350cf59 (commit 440d66abc) completed and auto-released to both endpoints;
      its smoke fails the build if a removed class registers again, the
      recaptured snapshot has none of them, and a live sam3-segment on the new
      image (270f413b, 0.0081 USD) returned a mask identical to the earlier SAM
      3.1 run. V.12.01 is superseded. Stays open for deleting the two files
      (6.90 GB) from the Hetzner library and the cache volume, which waits on
      the user's confirmation._ _**Done 2026-09-14 20:41Z.** On the user's go,
      `sam3/sam3.pt` and `sam3/sam3.safetensors` (6,899,922,873 B) are deleted
      from the Hetzner library and, with their hash sidecars, from the cache
      volume; the cache database marks the sam3 family evicted (evidence
      A.05.03)._

````

## A.02.07 · lines 5637 to 5665

````text
- [x] **A.02.07** Depth Anything 3 swap (licence fix): row
      `geometry_estimation/depth_anything_3_mono_large.safetensors` (1.34 GB, S3
      PUT, Apache-2.0); repoint every graph whose depth preprocessor is
      `controlnet_aux`'s `DepthAnythingV2Preprocessor` (the motion control
      graphs and A.02.02's) to the core Depth Anything 3 node; validated, one
      live re-render of one depth-controlled workflow; then remove the
      `Depth-Anything-V2-Large` row (CC-BY-NC-4.0) and file. The volume must not
      carry a non-commercial weight once its replacement renders. _2026-09-13,
      offline half done; stays open for the live re-render and the V2 row's
      removal. The LTX-2.3 depth mode and the VACE depth control now run the
      core Depth Anything 3 load, inference and render nodes (mono, V2-style
      near-white depth). The worker's model path file gains the geometry
      estimation folder (and the model patches folder A.02.02 needs), without
      which the loader lists nothing; it ships with the A.05.01 build.
      Composition and mandala graphs are not RunPod catalog workflows and were
      left alone._ _2026-09-14: the live re-render is done:
      zimage-txt2img-control with control depth ran the core Depth Anything 3
      nodes (742ff7f7, evidence A.05.02) and the output keeps the source's
      layout. Stays open for the Depth-Anything-V2-Large row and file removal._
      _2026-09-14, manifest half: the row is gone (110 rows, 823.71 GB; the
      controlnet-aux family keeps DWPose and Depth Anything 3), the register is
      regenerated, and no RunPod catalog graph loads the V2 weight (only the
      non-RunPod composition and mandala graphs name the small V2 checkpoint).
      The endpoint licence gate still denies the V2 file by name. Stays open for
      deleting the file from the Hetzner library, which waits on the user's
      confirmation._ _**Done 2026-09-14 20:41Z.** On the user's go ("proceed on
      all"), the `depth_anything_v2_vitl.pth` file (1,341,395,338 B) is deleted
      from the Hetzner library by its exact key; the cache volume held no copy.
      A re-listing shows nothing left (evidence A.05.03)._
````

## A.02.08 · lines 5666 to 5684

````text
- [x] **A.02.08** Drop RMBG-2.0: remove the `RMBG/RMBG-2.0/model.safetensors`
      row (0.88 GB, non-commercial without a BRIA agreement, and the model that
      fails C.12.20) and the file; remove `rmbg-2.0` from every matting enum
      (the three BiRefNet rows stay); C.12.20 closes as moot with a note
      pointing here. _2026-09-13, manifest half done: the row and its family are
      gone (111 rows, 825.06 GB, 29 families, 10 pinned, pinned closure
      unchanged at 238.71 GB since the family was never pinned), no matting
      option or preset offers it, the RMBG-only resolution input is removed, and
      the register is regenerated. Stays open for the file deletion from the
      library and the cache, and C.12.20's note._ _**Done 2026-09-14 07:54Z.**
      On the user's instruction ("delete as planned", after weighing keeping it
      for personal non-commercial use) the files are gone: the weight and its
      three companion files from the Hetzner library, and those four plus their
      four hash sidecars from the cache volume, each listing empty afterwards;
      the BiRefNet folder beside it is untouched (6 library objects, 12 on the
      cache). The manifest row, family and every matting option had already gone
      on 2026-09-13, and nothing but explanatory comments names it. C.12.20 was
      already closed; with the model gone its failure has nothing left to fix._

````

## The routing decision and the Qwen-Image still (lines 5620 to 5636 and 5585 to 5596)

The brief cites 18.2 s and 31.7 s per megapixel-frame, job 8140f060, and the 57 GB load of job b94bedff. They are in these two passages of the same file.

````text
      _2026-09-14: the lightx2v LoRA the turbo path needs is E.03.01._
      _2026-09-14, live clip, one character in animation mode at 480 by 832, 20
      steps (dc178886, 417.1 s cold, 0.6870 USD): new frames that follow the
      driving pose (26.2 dB mean PSNR against the driver, not a copy). Stays
      open for the multi-character clip and the routing decision._ _**Done
      2026-09-14.** Two characters (8140f060, 832 by 480, 33 frames, 20 steps,
      358.0 s, 0.5896 USD): the reference held two different women, the driver
      two copies of one clip, and the output puts both reference women in the
      driver's scene and poses in left-to-right order, so transfer to a
      different character is shown. Routing decision: Animate-2 is the default
      animation route for one performer, SCAIL-2 the route for more than one
      character or for replacement. Why: Animate-2 measured 18.2 s per
      megapixel-frame on its 10-step distilled schedule against SCAIL-2's 31.7 s
      at half its 40-step default, and its 81-frame default fits the 900 s cap
      where SCAIL-2 has to stop at 33 frames; SCAIL-2 is the only graph that
      pairs several characters with several performers. Both stay, and the
      Studio preset notes say which is for what._
````

````text
      the no-LoRA values of the sibling templates, since the Lightning LoRA has
      no row; takes a ready control map because the template's Lotus depth model
      has no row either) and the InstantX inpainting mode. A spec resolves the
      real catalog entries to the video ledger and inventory. Sticker costs at
      the video rate, SFW only, validated, not rendered._ _2026-09-14: the
      Qwen-Image-Edit 2511 Lightning row is E.04.01, which adds it as a speed
      mode on `qwen-edit` and `qwen-edit-control`._ _2026-09-14, live still on
      the video endpoint: qwen-txt2img at 1328 square (b94bedff, 373.3 s
      including loading 57 GB of weights, 0.6148 USD, billed on the video ledger
      as routed). Stays open for qwen-edit and qwen-edit-control._ _**Done
      2026-09-14.** qwen-edit with one reference (c432e401, 282.5 s including
      swapping in the Edit 2511 transformer, 0.4652 USD) changed the dress to a
````

## Animate-1 bytes

The brief gives 35,986,460,800 bytes deleted for Animate-1. A.01.06 records the two files: 34,549,787,368 B and 1,436,673,432 B. Their sum is 35,986,460,800.
