From 6e53fb48e7d59ee9e73e698dd0413c6eeff50f9c Mon Sep 17 00:00:00 2001 From: dmarzzz Date: Tue, 18 Mar 2025 11:17:25 -0400 Subject: [PATCH 1/7] first stab --- ...ad-testing-acceptance-criteria-template.md | 97 +++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 docs/load-testing-acceptance-criteria-template.md diff --git a/docs/load-testing-acceptance-criteria-template.md b/docs/load-testing-acceptance-criteria-template.md new file mode 100644 index 00000000..1d01e407 --- /dev/null +++ b/docs/load-testing-acceptance-criteria-template.md @@ -0,0 +1,97 @@ +# Rollup Boost - Load Testing Acceptance Criteria + +## Overview +This document serves as a generic acceptance criteria checklist for deploying a **block builder** on any blockchain network. Copy this checklist and fill it out with the appropriate data for your specific chain before proceeding to mainnet deployment. + +## Environment +- **Network:** [Specify the blockchain network] +- **RPC:** [Specify the blockchain network] +- **Contender Scenarios:** [Specify scenarios used for load testing] +- **Block Builder Version:** [Github link to release] +- **OP Stack Version:** [Github link to release] +- **Test Period:** [YYYY-MM-DD] + +## Acceptance Criteria Checklist + +### **1. Transaction Throughput & Latency** +✅ **Peak Transactions per Second (TPS)** + - Expected: ≥ X,XXX TPS + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **Average Transaction Latency** + - Expected: ≤ XXX ms + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **Max Transaction Latency (P99)** + - Expected: ≤ XXX ms + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **RPC Response Latency** + - Expected: ≤ XXX ms + - Measured: `____` + - Supporting Data: [Link to results] + +### **2. Block Production Performance** +✅ **Average Block Time** + - Expected: ≤ XX seconds + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **Missed Blocks Rate** + - Expected: ≤ X% of total blocks + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **Internal Block Builder Latency** + - Expected: ≤ XXX ms + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **Latency from Chain RPC to Block Builder** + - Expected: ≤ XXX ms + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **100% Transaction Forwarding Acceptance** + - Expected: All transactions sent should be logged in both the chain operator’s environment and the block builder’s environment + - Measured: `____` + - Supporting Data: [Link to results] + +### **3. Instance Health & Deployment Readiness** +✅ **Chain Operator Health Checks** *(CPU, Memory, Disk, Networking)* + - Expected: No resource exhaustion or anomalies + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **Block Builder Health Checks** *(CPU, Memory, Disk, Networking)* + - Expected: No resource exhaustion or anomalies + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **RPC Endpoint Stability** + - Expected: No downtime or crashes + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **Able to Trace Transaction Hash End-to-End** + - Expected: Transactions can be fully traced from submission to inclusion in a block + - Measured: `____` + - Supporting Data: [Link to results] + +✅ **Verification of Non-Tx Related RPC Methods** + - Expected: No failures in non-transaction-related RPC calls + - Measured: `____` + - Supporting Data: [Link to results] + +--- + +## **Final Decision** +✅ **All criteria met (Yes/No)?** + - Decision: `____` + - Date: `____` + +## **Notes & Recommendations** +- `[Add additional observations, issues, or follow-ups]` \ No newline at end of file From 49854a69ffa108ad915a137384a65d53a3748b1d Mon Sep 17 00:00:00 2001 From: dmarzzz Date: Tue, 18 Mar 2025 11:26:29 -0400 Subject: [PATCH 2/7] update copy --- docs/load-testing-acceptance-criteria-template.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/load-testing-acceptance-criteria-template.md b/docs/load-testing-acceptance-criteria-template.md index 1d01e407..3613c961 100644 --- a/docs/load-testing-acceptance-criteria-template.md +++ b/docs/load-testing-acceptance-criteria-template.md @@ -1,7 +1,7 @@ # Rollup Boost - Load Testing Acceptance Criteria ## Overview -This document serves as a generic acceptance criteria checklist for deploying a **block builder** on any blockchain network. Copy this checklist and fill it out with the appropriate data for your specific chain before proceeding to mainnet deployment. +This document serves as a generic acceptance criteria checklist for load testing a **block builder** on a Layer 2 network. It's designed to be used with [Contender](https://github.com/flashbots/contender), a high-performance Ethereum network testing tool for benchmarking and stress-testing clients and networks. Copy this checklist and fill it out with the appropriate data for your specific chain before proceeding to mainnet deployment. ## Environment - **Network:** [Specify the blockchain network] @@ -56,7 +56,7 @@ This document serves as a generic acceptance criteria checklist for deploying a - Supporting Data: [Link to results] ✅ **100% Transaction Forwarding Acceptance** - - Expected: All transactions sent should be logged in both the chain operator’s environment and the block builder’s environment + - Expected: All transactions sent should be logged in both the chain operator's environment and the block builder's environment - Measured: `____` - Supporting Data: [Link to results] From 566ee6f6784067636bcfdfecbd29a09845fc7f04 Mon Sep 17 00:00:00 2001 From: dmarzzz Date: Thu, 20 Mar 2025 16:48:54 -0400 Subject: [PATCH 3/7] update acceptance criteria --- ...ad-testing-acceptance-criteria-template.md | 322 +++++++++++++----- 1 file changed, 229 insertions(+), 93 deletions(-) diff --git a/docs/load-testing-acceptance-criteria-template.md b/docs/load-testing-acceptance-criteria-template.md index 3613c961..605426dd 100644 --- a/docs/load-testing-acceptance-criteria-template.md +++ b/docs/load-testing-acceptance-criteria-template.md @@ -1,97 +1,233 @@ -# Rollup Boost - Load Testing Acceptance Criteria - -## Overview -This document serves as a generic acceptance criteria checklist for load testing a **block builder** on a Layer 2 network. It's designed to be used with [Contender](https://github.com/flashbots/contender), a high-performance Ethereum network testing tool for benchmarking and stress-testing clients and networks. Copy this checklist and fill it out with the appropriate data for your specific chain before proceeding to mainnet deployment. - -## Environment -- **Network:** [Specify the blockchain network] -- **RPC:** [Specify the blockchain network] -- **Contender Scenarios:** [Specify scenarios used for load testing] -- **Block Builder Version:** [Github link to release] -- **OP Stack Version:** [Github link to release] -- **Test Period:** [YYYY-MM-DD] - -## Acceptance Criteria Checklist - -### **1. Transaction Throughput & Latency** -✅ **Peak Transactions per Second (TPS)** - - Expected: ≥ X,XXX TPS - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **Average Transaction Latency** - - Expected: ≤ XXX ms - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **Max Transaction Latency (P99)** - - Expected: ≤ XXX ms - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **RPC Response Latency** - - Expected: ≤ XXX ms - - Measured: `____` - - Supporting Data: [Link to results] - -### **2. Block Production Performance** -✅ **Average Block Time** - - Expected: ≤ XX seconds - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **Missed Blocks Rate** - - Expected: ≤ X% of total blocks - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **Internal Block Builder Latency** - - Expected: ≤ XXX ms - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **Latency from Chain RPC to Block Builder** - - Expected: ≤ XXX ms - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **100% Transaction Forwarding Acceptance** - - Expected: All transactions sent should be logged in both the chain operator's environment and the block builder's environment - - Measured: `____` - - Supporting Data: [Link to results] - -### **3. Instance Health & Deployment Readiness** -✅ **Chain Operator Health Checks** *(CPU, Memory, Disk, Networking)* - - Expected: No resource exhaustion or anomalies - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **Block Builder Health Checks** *(CPU, Memory, Disk, Networking)* - - Expected: No resource exhaustion or anomalies - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **RPC Endpoint Stability** - - Expected: No downtime or crashes - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **Able to Trace Transaction Hash End-to-End** - - Expected: Transactions can be fully traced from submission to inclusion in a block - - Measured: `____` - - Supporting Data: [Link to results] - -✅ **Verification of Non-Tx Related RPC Methods** - - Expected: No failures in non-transaction-related RPC calls - - Measured: `____` - - Supporting Data: [Link to results] +## **Environment** + +• **Network:** Unichain Sepolia Experimental + +• **RPC Endpoint:** [Specify the blockchain network RPC URL] + +• **Contender Load Testing Scenarios:** + +• **Fill Block** (C_FILL_PERCENT=50) + +• **Block Builder Version:** [Specify the deployed version] + +• **OP Stack Version:** [GitHub link to release] + +• **Test Period:** March 18, 2025 + +## **Acceptance Criteria Checklist** --- -## **Final Decision** -✅ **All criteria met (Yes/No)?** - - Decision: `____` - - Date: `____` +### **1. Overall Network Performance** + +🎯 **Peak Gas Utilization (GPS)** + +**Description:** Measures the highest observed gas consumption per second in the network. + +**Expected:** 5 million GPS + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Peak Transactions per Second (TPS)** + +**Description:** Measures the maximum number of transactions successfully processed per second. + +**Expected:** [Expected TPS] + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Average Block Time** + +**Description:** Time taken between consecutive block proposals. + +**Expected:** 1 second + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +--- + +### **2. Chain Operator Performance Metrics** + +***RPC Ingress Metrics (Transaction Handling)*** + +🎯 **Peak Burst Transactions per Second (TPS)** + +**Description:** Measures the highest rate at which transactions are submitted to the RPC within a short burst. + +**Expected:** 1,000 TPS + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Sustained Transactions per Second (TPS)** + +**Description:** Measures the average transaction ingress rate over a sustained 20-minute period. + +**Expected:** 200 TPS + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +***RPC Latency Metrics*** + +🎯 **Average RPC Response Latency** + +**Description:** Measures the typical response time for RPC requests. + +**Expected:** ≤ 60 ms + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Max RPC Response Latency** + +**Description:** Measures the worst-case response time for RPC requests. + +**Expected:** ≤ 120 ms + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +***RPC Egress (Block Builder Communication)*** + +🎯 **Average Block Builder Response Latency** + +**Expected:** ≤ 60 ms + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Max Block Builder Response Latency** + +**Expected:** ≤ 100 ms + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +***Sequencer & Rollup Boost Health Checks*** + +🎯 **Sequencer Resource Utilization (CPU, Memory, Disk, Network)** + +**Expected:** No resource exhaustion or anomalies. + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Rollup Boost Resource Utilization (CPU, Memory, Disk, Network)** + +**Expected:** No resource exhaustion or anomalies. + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **RPC Endpoint Stability** + +**Expected:** No downtime or unexpected crashes. + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Non-Transaction RPC Method Stability** + +**Description:** Ensures non-transaction-related RPC methods function without failure. + +**Expected:** No failures. + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +--- + +### **3. Block Builder Performance Metrics** + +🎯 **Missed Block Rate** + +**Description:** Percentage of expected blocks that were not produced. + +**Expected:** ≤ 10% + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **End-to-End Block Build Latency** + +**Description:** Time taken from transaction ingress to finalized block production. + +**Expected:** ≤ 100 ms + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Block Submission Response Latency** + +**Expected:** ≤ 100 ms + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Block Builder Health Checks (CPU, Memory, Disk, Network)** + +**Expected:** No resource exhaustion or anomalies. + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +--- + +### **4. System-Wide Reliability Checks** + +🎯 **100% Transaction Forwarding Accuracy** + +**Description:** Ensures all transactions sent to the system are correctly received and logged. + +**Expected:** 100% transaction acceptance. + +**Measured:** [Insert measured value] + +**Supporting Data:** [Link to results] + +🎯 **Observability: Full Transaction Traceability** + +**Description:** Verifies that transactions can be traced end-to-end across all infrastructure components. + +**Expected:** Given a random transaction hash during load testing, timestamps for each step in the transaction pipeline can be observed. + +**Measured:** +- **Client Submission Timestamp:** [Measured result] +- **Chain Operator Ingress Timestamp:** [Measured result] +- **Block Builder Ingress Timestamp:** [Measured result] +- **Block Submission Timestamp:** [Measured result] + +--- + +### **Final Decision** + +✅ **All criteria met?** (Yes / No) + +• **Decision:** [Yes/No] + +• **Date:** March 18, 2025 + +**Notes & Recommendations** -## **Notes & Recommendations** -- `[Add additional observations, issues, or follow-ups]` \ No newline at end of file +• [Add any additional observations, issues, or follow-up actions] \ No newline at end of file From ef9e60040ba71768280e4d1a08bcde55dc3e3647 Mon Sep 17 00:00:00 2001 From: dmarzzz Date: Thu, 20 Mar 2025 16:57:34 -0400 Subject: [PATCH 4/7] formatting improvements --- ...ad-testing-acceptance-criteria-template.md | 220 ++++++------------ 1 file changed, 72 insertions(+), 148 deletions(-) diff --git a/docs/load-testing-acceptance-criteria-template.md b/docs/load-testing-acceptance-criteria-template.md index 605426dd..58dc2025 100644 --- a/docs/load-testing-acceptance-criteria-template.md +++ b/docs/load-testing-acceptance-criteria-template.md @@ -1,54 +1,32 @@ ## **Environment** -• **Network:** Unichain Sepolia Experimental - -• **RPC Endpoint:** [Specify the blockchain network RPC URL] - -• **Contender Load Testing Scenarios:** - -• **Fill Block** (C_FILL_PERCENT=50) - -• **Block Builder Version:** [Specify the deployed version] - -• **OP Stack Version:** [GitHub link to release] - -• **Test Period:** March 18, 2025 +- **Network:** Unichain Sepolia Experimental +- **RPC Endpoint:** [Specify the blockchain network RPC URL] +- **Contender Load Testing Scenarios:** +- **Block Builder Version:** [Specify the deployed version] +- **OP Stack Version:** [GitHub link to release] +- **Test Period:** March 18, 2025 ## **Acceptance Criteria Checklist** - ---- - ### **1. Overall Network Performance** 🎯 **Peak Gas Utilization (GPS)** - -**Description:** Measures the highest observed gas consumption per second in the network. - -**Expected:** 5 million GPS - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Measures the highest observed gas consumption per second in the network. +- **Expected:** 5 million GPS +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Peak Transactions per Second (TPS)** - -**Description:** Measures the maximum number of transactions successfully processed per second. - -**Expected:** [Expected TPS] - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Measures the maximum number of transactions successfully processed per second. +- **Expected:** [Expected TPS] +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Average Block Time** - -**Description:** Time taken between consecutive block proposals. - -**Expected:** 1 second - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Time taken between consecutive block proposals. +- **Expected:** 1 second +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] --- @@ -57,162 +35,108 @@ ***RPC Ingress Metrics (Transaction Handling)*** 🎯 **Peak Burst Transactions per Second (TPS)** - -**Description:** Measures the highest rate at which transactions are submitted to the RPC within a short burst. - -**Expected:** 1,000 TPS - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Measures the highest rate at which transactions are submitted to the RPC within a short burst. +- **Expected:** 1,000 TPS +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Sustained Transactions per Second (TPS)** - -**Description:** Measures the average transaction ingress rate over a sustained 20-minute period. - -**Expected:** 200 TPS - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Measures the average transaction ingress rate over a sustained 20-minute period. +- **Expected:** 200 TPS +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] ***RPC Latency Metrics*** 🎯 **Average RPC Response Latency** - -**Description:** Measures the typical response time for RPC requests. - -**Expected:** ≤ 60 ms - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Measures the typical response time for RPC requests. +- **Expected:** ≤ 60 ms +- **Measured:** [Insert measured value] +-**Supporting Data:** [Link to results] 🎯 **Max RPC Response Latency** - -**Description:** Measures the worst-case response time for RPC requests. - -**Expected:** ≤ 120 ms - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Measures the worst-case response time for RPC requests. +- **Expected:** ≤ 120 ms +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] ***RPC Egress (Block Builder Communication)*** 🎯 **Average Block Builder Response Latency** - -**Expected:** ≤ 60 ms - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Expected:** ≤ 60 ms +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Max Block Builder Response Latency** - -**Expected:** ≤ 100 ms - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Expected:** ≤ 100 ms +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] ***Sequencer & Rollup Boost Health Checks*** 🎯 **Sequencer Resource Utilization (CPU, Memory, Disk, Network)** - -**Expected:** No resource exhaustion or anomalies. - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Expected:** No resource exhaustion or anomalies. +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Rollup Boost Resource Utilization (CPU, Memory, Disk, Network)** - -**Expected:** No resource exhaustion or anomalies. - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Expected:** No resource exhaustion or anomalies. +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **RPC Endpoint Stability** - -**Expected:** No downtime or unexpected crashes. - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Expected:** No downtime or unexpected crashes. +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Non-Transaction RPC Method Stability** - -**Description:** Ensures non-transaction-related RPC methods function without failure. - -**Expected:** No failures. - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Ensures non-transaction-related RPC methods function without failure. +- **Expected:** No failures. +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] --- ### **3. Block Builder Performance Metrics** 🎯 **Missed Block Rate** - -**Description:** Percentage of expected blocks that were not produced. - -**Expected:** ≤ 10% - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Percentage of expected blocks that were not produced. +- **Expected:** ≤ 10% +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **End-to-End Block Build Latency** **Description:** Time taken from transaction ingress to finalized block production. - -**Expected:** ≤ 100 ms - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Expected:** ≤ 100 ms +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Block Submission Response Latency** - -**Expected:** ≤ 100 ms - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Expected:** ≤ 100 ms +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Block Builder Health Checks (CPU, Memory, Disk, Network)** - -**Expected:** No resource exhaustion or anomalies. - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Expected:** No resource exhaustion or anomalies. +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] --- ### **4. System-Wide Reliability Checks** 🎯 **100% Transaction Forwarding Accuracy** - -**Description:** Ensures all transactions sent to the system are correctly received and logged. - -**Expected:** 100% transaction acceptance. - -**Measured:** [Insert measured value] - -**Supporting Data:** [Link to results] +- **Description:** Ensures all transactions sent to the system are correctly received and logged. +- **Expected:** 100% transaction acceptance. +- **Measured:** [Insert measured value] +- **Supporting Data:** [Link to results] 🎯 **Observability: Full Transaction Traceability** **Description:** Verifies that transactions can be traced end-to-end across all infrastructure components. - -**Expected:** Given a random transaction hash during load testing, timestamps for each step in the transaction pipeline can be observed. - -**Measured:** +- **Expected:** Given a random transaction hash during load testing, timestamps for each step in the transaction pipeline can be observed. +- **Measured:** - **Client Submission Timestamp:** [Measured result] - **Chain Operator Ingress Timestamp:** [Measured result] - **Block Builder Ingress Timestamp:** [Measured result] From 285ecfef897c978e20970819ae4234604148c90d Mon Sep 17 00:00:00 2001 From: dmarzzz Date: Thu, 20 Mar 2025 17:00:30 -0400 Subject: [PATCH 5/7] more format fixes and default values --- docs/load-testing-acceptance-criteria-template.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/load-testing-acceptance-criteria-template.md b/docs/load-testing-acceptance-criteria-template.md index 58dc2025..7eac1a5d 100644 --- a/docs/load-testing-acceptance-criteria-template.md +++ b/docs/load-testing-acceptance-criteria-template.md @@ -1,11 +1,10 @@ ## **Environment** - -- **Network:** Unichain Sepolia Experimental +- **Network:** [Specify the network] - **RPC Endpoint:** [Specify the blockchain network RPC URL] - **Contender Load Testing Scenarios:** - **Block Builder Version:** [Specify the deployed version] - **OP Stack Version:** [GitHub link to release] -- **Test Period:** March 18, 2025 +- **Test Period:** [Specify the test period] ## **Acceptance Criteria Checklist** ### **1. Overall Network Performance** @@ -137,10 +136,10 @@ **Description:** Verifies that transactions can be traced end-to-end across all infrastructure components. - **Expected:** Given a random transaction hash during load testing, timestamps for each step in the transaction pipeline can be observed. - **Measured:** -- **Client Submission Timestamp:** [Measured result] -- **Chain Operator Ingress Timestamp:** [Measured result] -- **Block Builder Ingress Timestamp:** [Measured result] -- **Block Submission Timestamp:** [Measured result] + - **Client Submission Timestamp:** [Measured result] + - **Chain Operator Ingress Timestamp:** [Measured result] + - **Block Builder Ingress Timestamp:** [Measured result] + - **Block Submission Timestamp:** [Measured result] --- From 3313b294c1f5fdeb971a631b674ae95b7b3a17ef Mon Sep 17 00:00:00 2001 From: dmarzzz Date: Thu, 20 Mar 2025 17:03:31 -0400 Subject: [PATCH 6/7] small format fix --- docs/load-testing-acceptance-criteria-template.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/load-testing-acceptance-criteria-template.md b/docs/load-testing-acceptance-criteria-template.md index 7eac1a5d..a150bb14 100644 --- a/docs/load-testing-acceptance-criteria-template.md +++ b/docs/load-testing-acceptance-criteria-template.md @@ -145,11 +145,9 @@ ### **Final Decision** -✅ **All criteria met?** (Yes / No) - -• **Decision:** [Yes/No] - -• **Date:** March 18, 2025 +✅ **All criteria met?** +- **Decision:** [Yes/No] +- **Date:** [Specify the test period] **Notes & Recommendations** From 1ec75e5ab9aa3b88f4cd4e24b30e3a45f415243a Mon Sep 17 00:00:00 2001 From: dmarzzz Date: Thu, 20 Mar 2025 17:05:57 -0400 Subject: [PATCH 7/7] last format fix im pretty sure --- docs/load-testing-acceptance-criteria-template.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/load-testing-acceptance-criteria-template.md b/docs/load-testing-acceptance-criteria-template.md index a150bb14..1eee04e7 100644 --- a/docs/load-testing-acceptance-criteria-template.md +++ b/docs/load-testing-acceptance-criteria-template.md @@ -1,3 +1,7 @@ +## Overview + +This document serves as a generic acceptance criteria checklist template to be run through before deploying network upgrades through Rollup Boost. Copy this checklist and fill it out with the appropriate data for your specific chain before upgrading your network.. + ## **Environment** - **Network:** [Specify the network] - **RPC Endpoint:** [Specify the blockchain network RPC URL] @@ -132,8 +136,7 @@ - **Supporting Data:** [Link to results] 🎯 **Observability: Full Transaction Traceability** - -**Description:** Verifies that transactions can be traced end-to-end across all infrastructure components. +- **Description:** Verifies that transactions can be traced end-to-end across all infrastructure components. - **Expected:** Given a random transaction hash during load testing, timestamps for each step in the transaction pipeline can be observed. - **Measured:** - **Client Submission Timestamp:** [Measured result]