Monitorism Global_events is module a that listen events onchain.

op-monitorism/cmd/monitorism/cli.go

@@ -7,6 +7,7 @@ import (
  monitorism "github.com/ethereum-optimism/monitorism/op-monitorism"
  "github.com/ethereum-optimism/monitorism/op-monitorism/balances"
  "github.com/ethereum-optimism/monitorism/op-monitorism/fault"
+ "github.com/ethereum-optimism/monitorism/op-monitorism/global_events"
  "github.com/ethereum-optimism/monitorism/op-monitorism/multisig"
  "github.com/ethereum-optimism/monitorism/op-monitorism/withdrawals"
 
@@ -60,6 +61,13 @@ func newCli(GitCommit string, GitDate string) *cli.App {
  Flags: append(balances.CLIFlags("BALANCE_MON"), defaultFlags...),
  Action: cliapp.LifecycleCmd(BalanceMain),
  },
+ {
+ Name: "global_events",
+ Usage: "Monitors global events with YAML configuration",
+ Description: "Monitors global events with YAML configuration",
+ Flags: append(global_events.CLIFlags("GLOBAL_EVENT_MON"), defaultFlags...),
+ Action: cliapp.LifecycleCmd(global_eventsMain),
+ },
  {
  Name: "version",
  Usage: "Show version",
@@ -73,6 +81,21 @@ func newCli(GitCommit string, GitDate string) *cli.App {
  }
 }
 
+func global_eventsMain(ctx *cli.Context, closeApp context.CancelCauseFunc) (cliapp.Lifecycle, error) {
+ log := oplog.NewLogger(oplog.AppOut(ctx), oplog.ReadCLIConfig(ctx))
+ cfg, err := global_events.ReadCLIFlags(ctx)
+ if err != nil {
+ return nil, fmt.Errorf("failed to parse global_events config from flags: %w", err)
+ }
+
+ metricsRegistry := opmetrics.NewRegistry()
+ monitor, err := global_events.NewMonitor(ctx.Context, log, opmetrics.With(metricsRegistry), cfg)
+ if err != nil {
+ return nil, fmt.Errorf("failed to create global_events monitor: %w", err)
+ }
+
+ return monitorism.NewCliApp(ctx, log, metricsRegistry, monitor)
+}
 func MultisigMain(ctx *cli.Context, closeApp context.CancelCauseFunc) (cliapp.Lifecycle, error) {
  log := oplog.NewLogger(oplog.AppOut(ctx), oplog.ReadCLIConfig(ctx))
  cfg, err := multisig.ReadCLIFlags(ctx)

op-monitorism/cmd/monitorism/globalconfig.yaml

@@ -0,0 +1,17 @@
+configuration:
+ - version: "1.0"
+ name: Safe Watcher
+ priority: P0
+ addresses: []
+ events:
+ - keccak256_signature: 0x23428b18acfb3ea64b08dc0c1d296ea9c09702c09083ca5272e64d115b687d23
+ signature: ExecutionFailure(bytes32,uint256)
+ - keccak256_signature: 0x442e715f626346e8c54381002da614f62bee8d27386535b2521ec8540898556e
+ signature: ExecutionSuccess(bytes32,uint256)
+ - version: "1.0"
+ name: SystemConfig Config Updates
+ priority: P2
+ addresses: []
+ events:
+ - keccak256_signature: 0x82f8cc4439cd78202f3081cd05a23d895e011595628770738fc5ba8ecba469ed
+ signature: ConfigUpdate(uint256 indexed version, UpdateType indexed updateType, bytes data)

op-monitorism/cmd/rules/SafeExecution.yaml

@@ -0,0 +1,10 @@
+# This watches all contacts for OP, Mode, and Base mainnets for two logs.
+# These logs are emitted by Safes, so this effectively watches for all
+# transactions from any Safe on these chains.
+version: 1.0
+name: Safe Watcher
+priority: P0
+addresses: # /!\ We are not supporting EIP 3770 yet, if the address is not starting by `0x`, this will panic by safety measure.
+events:
+ - signature: ExecutionFailure(bytes32,uint256)
+ - signature: ExecutionSuccess(bytes32,uint256)

op-monitorism/cmd/rules/SystemConfigUpdate.yaml

@@ -0,0 +1,11 @@
+# This watches the L1 SystemConfig for OP Mainnet for config updates.
+# - eth/op/SystemConfig
+version: 1.0
+name: SystemConfig Config Updates
+priority: P2
+addresses: # /!\ We are not supporting EIP 3770 yet, if the address is not starting by 0x, this will panic by safety measure.
+events:
+ - signature: ConfigUpdate(uint256 indexed version, UpdateType indexed updateType, bytes data)
+ # Notice that the above signature is not normalized. The normalized version is:
+ # ConfigUpdate(uint256,uint8,bytes)
+ # But for UX

op-monitorism/global_events/README.md

@@ -0,0 +1,52 @@
+## Global Events monitoring
+
+This monitoring modules for the yaml rules added with the format ⚠️ This readme will be move into the global readme in the future.
+
+CLI and Docs: 
+```bash
+NAME:
+ Monitorism global_events - Monitors global events with YAML configuration
+
+USAGE:
+ Monitorism global_events [command options] [arguments...]
+
+DESCRIPTION:
+ Monitors global events with YAML configuration
+
+OPTIONS:
+ --l1.node.url value Node URL of L1 peer (default: "http://127.0.0.1:8545") [$GLOBAL_EVENT_MON_L1_NODE_URL]
+ --nickname value Nickname of chain being monitored [$GLOBAL_EVENT_MON_NICKNAME]
+ --PathYamlRules value Path to the yaml file containing the events to monitor [$GLOBAL_EVENT_MON_PATH_YAML]
+ --log.level value The lowest log level that will be output (default: INFO) [$MONITORISM_LOG_LEVEL]
+ --log.format value Format the log output. Supported formats: 'text', 'terminal', 'logfmt', 'json', 'json-pretty', (default: text) [$MONITORISM_LOG_FORMAT]
+ --log.color Color the log output if in terminal mode (default: false) [$MONITORISM_LOG_COLOR]
+ --metrics.enabled Enable the metrics server (default: false) [$MONITORISM_METRICS_ENABLED]
+ --metrics.addr value Metrics listening address (default: "0.0.0.0") [$MONITORISM_METRICS_ADDR]
+ --metrics.port value Metrics listening port (default: 7300) [$MONITORISM_METRICS_PORT]
+ --loop.interval.msec value Loop interval of the monitor in milliseconds (default: 60000) [$MONITORISM_LOOP_INTERVAL_MSEC]
+ --help, -h show help
+
+```
+
+The rules are located here: `op-monitorism/global_events/rules/` then we have multiples folders depending the networks you want to monitore (`mainnet` or `sepolia`) for now.
+```yaml
+# This is a TEMPLATE file please copy this one
+# This watches all contacts for OP, Mode, and Base mainnets for two logs.
+version: 1.0
+name: Template SafeExecution Events (Success/Failure) L1 # Please put the L1 or L2 at the end of the name.
+priority: P5 # This is a test, so it is a P5
+#If addresses is empty like below it will watch all addresses otherwise you can address specific addresses.
+addresses:
+ # - 0xbEb5Fc579115071764c7423A4f12eDde41f106Ed # Specific Addresses /!\ We are not supporting EIP 3770 yet, if the address is not starting by 0x, this will panic by safety measure.
+events:
+ - signature: ExecutionFailure(bytes32,uint256) # List of the events to watch for the addresses.
+ - signature: ExecutionSuccess(bytes32,uint256) # List of the events to watch for the addresses.
+```
+
+To run it:
+
+```bash
+
+go run ../cmd/monitorism global_events --nickname MySuperNickName --l1.node.url https://localhost:8545 --PathYamlRules /tmp/Monitorism/op-monitorism/global_events/rules/rules_mainnet_L1 --loop.interval.msec 12000
+
+```

op-monitorism/global_events/cli.go

@@ -0,0 +1,58 @@
+package global_events
+
+import (
+ // "fmt"
+
+ opservice "github.com/ethereum-optimism/optimism/op-service"
+
+ // "github.com/ethereum/go-ethereum/common"
+
+ "github.com/urfave/cli/v2"
+)
+
+// args in CLI have to be standardized and clean.
+const (
+ L1NodeURLFlagName = "l1.node.url"
+ NicknameFlagName = "nickname"
+ PathYamlRulesFlagName = "PathYamlRules"
+)
+
+type CLIConfig struct {
+ L1NodeURL string
+ Nickname string
+ PathYamlRules string
+ // Optional
+}
+
+func ReadCLIFlags(ctx *cli.Context) (CLIConfig, error) {
+ cfg := CLIConfig{
+ L1NodeURL: ctx.String(L1NodeURLFlagName),
+ Nickname: ctx.String(NicknameFlagName),
+ PathYamlRules: ctx.String(PathYamlRulesFlagName),
+ }
+
+ return cfg, nil
+}
+
+func CLIFlags(envVar string) []cli.Flag {
+ return []cli.Flag{
+ &cli.StringFlag{
+ Name: L1NodeURLFlagName,
+ Usage: "Node URL of L1 peer",
+ Value: "http://127.0.0.1:8545",
+ EnvVars: opservice.PrefixEnvVar(envVar, "L1_NODE_URL"),
+ },
+ &cli.StringFlag{
+ Name: NicknameFlagName,
+ Usage: "Nickname of chain being monitored",
+ EnvVars: opservice.PrefixEnvVar(envVar, "NICKNAME"), //need to change the name to BLOCKCHAIN_NAME
+ Required: true,
+ },
+ &cli.StringFlag{
+ Name: PathYamlRulesFlagName,
+ Usage: "Path to the yaml file containing the events to monitor",
+ EnvVars: opservice.PrefixEnvVar(envVar, "PATH_YAML"), //need to change the name to BLOCKCHAIN_NAME
+ Required: true,
+ },
+ }
+}