Skip to content

Model 2 — Tradeoff Table

Candidate comparison from the Model 2 optimizer. The recommended_safe layout is the only one that survives every protected scenario; candidates that show a higher raw net value do so by failing required protected failures and are therefore not feasible.

Candidate Status Validators AWS_A AWS_B AWS_C GCP_A GCP_B HOME GCP roles Protected failed Net CTN/yr
3 AWS nodes with 15 validators each fails_some_protected 45 15 15 15 0 0 0 off, off 10 98.36
optimized validator count on 3 AWS nodes only fails_some_protected 63 21 21 21 0 0 0 off, off 10 145.16
3 AWS nodes + home VC fails_some_protected 42 12 12 12 0 0 6 off, off 16 81.44
3 AWS nodes + 2 GCP VC-only nodes fails_some_protected 40 8 8 8 8 8 0 vc_only, vc_only 16 76.09
3 AWS nodes + 1 GCP full + 1 GCP VC-only fails_some_protected 40 8 8 8 8 8 0 combined, vc_only 11 77.13
3 AWS nodes + 2 GCP combined nodes fails_some_protected 40 8 8 8 8 8 0 combined, combined 11 77.46
3 AWS + 2 GCP combined + home VC survives_protected 48 8 8 8 8 8 8 combined, combined 0 86.52
maximum safe reward under budget optimal 48 8 8 8 8 8 8 combined, combined 0 86.52
optimizer-discovered superior fixed-budget layout optimal 48 8 8 8 8 8 8 combined, combined 0 86.52

How to read this

  • cheaper_riskier (45 validators, 98.36 CTN/yr) shows the highest raw net value but fails 10 protected scenarios — it is AWS-only, with no provider-independent beacon path. Higher number, not feasible.
  • GCP VC-only expansion adds validators but preserves AWS beacon dependency, so it fails AWS-beacon-degradation cases (16 protected failures). Only GCP combined nodes remove that dependency.
  • recommended_safe is the first row that reaches 0 protected failures, and the maximum-reward and optimizer-discovered rows converge on the same 48-validator layout.

See the Optimizer Summary and Economics for the binding constraints and the full cost build-up.