From 1189e8e15f346e83c03440c9802e2cd271e2c2ed Mon Sep 17 00:00:00 2001 From: Michael Silberling <4006780+MSilb7@users.noreply.github.com> Date: Tue, 10 Jun 2025 09:33:53 -0400 Subject: [PATCH 1/2] add resolving --- pages/app-developers/tools/data-and-dashboards/data-glossary.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/pages/app-developers/tools/data-and-dashboards/data-glossary.mdx b/pages/app-developers/tools/data-and-dashboards/data-glossary.mdx index fbd69adb4..b00c80ad2 100644 --- a/pages/app-developers/tools/data-and-dashboards/data-glossary.mdx +++ b/pages/app-developers/tools/data-and-dashboards/data-glossary.mdx @@ -49,6 +49,7 @@ This glossary is a living document and will be updated over time as new metrics * **Transaction Batches:** All transactions where the transaction from address is the `batcherHash` address and the transaction to address is the `batchInbox` as defined in the chains' `SystemConfigProxy` contract. * **State Output Submissions or Dispute Games:** All transactions where the transaction from address is the `Proposer` and the transaction to address is either the `outputOracleProxy` or the `disputeGameFactoryProxy` as defined in the chains' `SystemConfigProxy` contract. * Each chain's `SystemConfigProxy` contract can be found in the Superchain Registry. + * **Resolving Dispute Games:** All transactions sent to dispute game contracts created by the `disputeGameFactoryProxy`, where the transaction's method id (function call) is either `Resolve`, `ResolveClaim`, or `ClaimCredit`. **Why it matters:** From 72e3f5a919da1ed0f27fc7a13cb8de191001fbd5 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Tue, 10 Jun 2025 16:36:29 +0100 Subject: [PATCH 2/2] Update pages/app-developers/tools/data-and-dashboards/data-glossary.mdx --- .../app-developers/tools/data-and-dashboards/data-glossary.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/app-developers/tools/data-and-dashboards/data-glossary.mdx b/pages/app-developers/tools/data-and-dashboards/data-glossary.mdx index b00c80ad2..d9d6ecf0c 100644 --- a/pages/app-developers/tools/data-and-dashboards/data-glossary.mdx +++ b/pages/app-developers/tools/data-and-dashboards/data-glossary.mdx @@ -49,7 +49,7 @@ This glossary is a living document and will be updated over time as new metrics * **Transaction Batches:** All transactions where the transaction from address is the `batcherHash` address and the transaction to address is the `batchInbox` as defined in the chains' `SystemConfigProxy` contract. * **State Output Submissions or Dispute Games:** All transactions where the transaction from address is the `Proposer` and the transaction to address is either the `outputOracleProxy` or the `disputeGameFactoryProxy` as defined in the chains' `SystemConfigProxy` contract. * Each chain's `SystemConfigProxy` contract can be found in the Superchain Registry. - * **Resolving Dispute Games:** All transactions sent to dispute game contracts created by the `disputeGameFactoryProxy`, where the transaction's method id (function call) is either `Resolve`, `ResolveClaim`, or `ClaimCredit`. +* **Resolving Dispute Games:** All transactions sent to dispute game contracts created by the `disputeGameFactoryProxy`, where the transaction's method id (function call) is either `Resolve`, `ResolveClaim`, or `ClaimCredit`. **Why it matters:**