fix: Move signature validation to repository layer with BlockChainType rules

Author: ritik4ever

.cargo/config.toml

@@ -1,3 +1,3 @@
-# .cargo/config.toml
-[net]
-git-fetch-with-cli = true
+# .cargo/config.toml
+[net]
+git-fetch-with-cli = true

.dockerignore

@@ -1,2 +1,2 @@
-# ignore all .git files and directories
-.git*
+# ignore all .git files and directories
+.git*

.env.example

@@ -1,8 +1,8 @@
-RUST_LOG=info
-# Additional logging options (file mode)...by default is stdout
-# See docker-compose.yaml for more details
-# LOG_MODE=file
-# LOG_DATA_DIR=logs/
-# MONITOR_DATA_DIR=data/
-# LOG_MAX_SIZE=1073741824
-# METRICS_ENABLED=false
+RUST_LOG=info
+# Additional logging options (file mode)...by default is stdout
+# See docker-compose.yaml for more details
+# LOG_MODE=file
+# LOG_DATA_DIR=logs/
+# MONITOR_DATA_DIR=data/
+# LOG_MAX_SIZE=1073741824
+# METRICS_ENABLED=false

.github/ISSUE_TEMPLATE/bug.yml

@@ -1,117 +1,117 @@
----
-name: Bug Report
-description: Create a bug report
-labels: [T-bug, S-needs-triage]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this bug report! Please provide as much detail as possible.
-        If you believe you have found a vulnerability, please provide details [here](mailto:[email protected]) instead.
-  - type: textarea
-    id: what-happened
-    attributes:
-      label: Describe the bug
-      description: |
-        A clear and concise description of what the bug is.
-        If the bug is in a crate you are using (i.e. you are not running the standard `openzeppelin-monitor` binary) please mention that as well.
-    validations:
-      required: true
-  - type: textarea
-    id: reproduction-steps
-    attributes:
-      label: Steps to reproduce
-      description: Please provide any steps you think might be relevant to reproduce the bug.
-      placeholder: |
-        Steps to reproduce:
-        1. Start '...'
-        2. Then '...'
-        3. Check '...'
-        4. See error
-    validations:
-      required: true
-  - type: textarea
-    id: logs
-    attributes:
-      label: Application logs
-      description: |
-        Please provide the relevant application logs leading up to the bug.
-      render: text
-    validations:
-      required: false
-  - type: dropdown
-    id: platform
-    attributes:
-      label: Platform(s)
-      description: What platform(s) did this occur on?
-      multiple: true
-      options:
-        - Linux (x86)
-        - Linux (ARM)
-        - Mac (Intel)
-        - Mac (Apple Silicon)
-        - Windows (x86)
-        - Windows (ARM)
-  - type: dropdown
-    id: deployment
-    attributes:
-      label: Deployment Type
-      description: How are you running openzeppelin-monitor?
-      multiple: false
-      options:
-        - Binary from releases
-        - Built from source
-        - Docker container
-        - Other
-    validations:
-      required: true
-  - type: textarea
-    id: additional
-    attributes:
-      label: Any other context that we need to know specific to the bug?
-  - type: textarea
-    id: version
-    attributes:
-      label: Version Information
-      description: Run `openzeppelin-monitor --version` and paste the output
-    validations:
-      required: true
-  - type: textarea
-    id: monitor-config
-    attributes:
-      label: Monitor Configuration
-      description: |
-        Please provide the relevant monitor configuration file(s) from your config directory.
-        Make sure to remove any sensitive information like private keys or API tokens.
-      render: json
-    validations:
-      required: false
-  - type: dropdown
-    id: network-type
-    attributes:
-      label: Network Type
-      description: Which blockchain network(s) are you monitoring?
-      multiple: true
-      options:
-        - EVM
-        - Stellar
-        - Midnight
-        - Other
-    validations:
-      required: true
-  - type: input
-    id: build-command
-    attributes:
-      label: Build Command
-      description: If you built from source, what command did you use?
-      placeholder: cargo build --release
-    validations:
-      required: false
-  - type: checkboxes
-    id: terms
-    attributes:
-      label: Code of Conduct
-      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/openzeppelin/openzeppelin-monitor/blob/main/CONTRIBUTING.md#code-of-conduct)
-      options:
-        - label: I agree to follow the Code of Conduct
-          required: true
+---
+name: Bug Report
+description: Create a bug report
+labels: [T-bug, S-needs-triage]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! Please provide as much detail as possible.
+        If you believe you have found a vulnerability, please provide details [here](mailto:[email protected]) instead.
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Describe the bug
+      description: |
+        A clear and concise description of what the bug is.
+        If the bug is in a crate you are using (i.e. you are not running the standard `openzeppelin-monitor` binary) please mention that as well.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction-steps
+    attributes:
+      label: Steps to reproduce
+      description: Please provide any steps you think might be relevant to reproduce the bug.
+      placeholder: |
+        Steps to reproduce:
+        1. Start '...'
+        2. Then '...'
+        3. Check '...'
+        4. See error
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Application logs
+      description: |
+        Please provide the relevant application logs leading up to the bug.
+      render: text
+    validations:
+      required: false
+  - type: dropdown
+    id: platform
+    attributes:
+      label: Platform(s)
+      description: What platform(s) did this occur on?
+      multiple: true
+      options:
+        - Linux (x86)
+        - Linux (ARM)
+        - Mac (Intel)
+        - Mac (Apple Silicon)
+        - Windows (x86)
+        - Windows (ARM)
+  - type: dropdown
+    id: deployment
+    attributes:
+      label: Deployment Type
+      description: How are you running openzeppelin-monitor?
+      multiple: false
+      options:
+        - Binary from releases
+        - Built from source
+        - Docker container
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: additional
+    attributes:
+      label: Any other context that we need to know specific to the bug?
+  - type: textarea
+    id: version
+    attributes:
+      label: Version Information
+      description: Run `openzeppelin-monitor --version` and paste the output
+    validations:
+      required: true
+  - type: textarea
+    id: monitor-config
+    attributes:
+      label: Monitor Configuration
+      description: |
+        Please provide the relevant monitor configuration file(s) from your config directory.
+        Make sure to remove any sensitive information like private keys or API tokens.
+      render: json
+    validations:
+      required: false
+  - type: dropdown
+    id: network-type
+    attributes:
+      label: Network Type
+      description: Which blockchain network(s) are you monitoring?
+      multiple: true
+      options:
+        - EVM
+        - Stellar
+        - Midnight
+        - Other
+    validations:
+      required: true
+  - type: input
+    id: build-command
+    attributes:
+      label: Build Command
+      description: If you built from source, what command did you use?
+      placeholder: cargo build --release
+    validations:
+      required: false
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/openzeppelin/openzeppelin-monitor/blob/main/CONTRIBUTING.md#code-of-conduct)
+      options:
+        - label: I agree to follow the Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/docs.yml

@@ -1,20 +1,20 @@
----
-name: Documentation
-description: Suggest a change to our documentation
-labels: [T-documentation, S-needs-triage]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        If you are unsure if the docs are relevant or needed, please open up a discussion first.
-  - type: textarea
-    attributes:
-      label: Describe the change
-      description: |
-        Please describe the documentation you want to change or add, and if it is for end-users or contributors.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Additional context
-      description: Add any other context to the feature (like screenshots, resources)
+---
+name: Documentation
+description: Suggest a change to our documentation
+labels: [T-documentation, S-needs-triage]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        If you are unsure if the docs are relevant or needed, please open up a discussion first.
+  - type: textarea
+    attributes:
+      label: Describe the change
+      description: |
+        Please describe the documentation you want to change or add, and if it is for end-users or contributors.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context to the feature (like screenshots, resources)

.github/ISSUE_TEMPLATE/feature.yml

@@ -1,22 +1,22 @@
----
-name: Feature request
-description: Suggest a feature
-labels: [T-feature, S-needs-triage]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Please ensure that the feature has not already been requested in the issue tracker.
-  - type: textarea
-    attributes:
-      label: Describe the feature
-      description: |
-        Please describe the feature and what it is aiming to solve, if relevant.
-
-        If the feature is for a crate, please include a proposed API surface.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Additional context
-      description: Add any other context to the feature (like screenshots, resources)
+---
+name: Feature request
+description: Suggest a feature
+labels: [T-feature, S-needs-triage]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please ensure that the feature has not already been requested in the issue tracker.
+  - type: textarea
+    attributes:
+      label: Describe the feature
+      description: |
+        Please describe the feature and what it is aiming to solve, if relevant.
+
+        If the feature is for a crate, please include a proposed API surface.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context to the feature (like screenshots, resources)

.github/RELEASE.md

@@ -1,21 +1,21 @@
-# CI/CD Release Workflow
-
----
-
-## Workflows
-
-- To trigger a release, use [rc.yml](workflows/rc.yml) workflow.
-  - It will need specific commit SHA in long format to start the workflow.
-  - All the commits until that specific commit sha will be included in the release.
-  - Checks version from `Cargo.toml` and validates if it needs to creates a new release branch. If there is a release branch that already exists for the same version in `Cargo.toml` the workflow will fail.
-  - Release branch is created in this pattern `release-v<version>`.
-
-- Second workflow [release-please.yml](workflows/release-please.yml) will get triggered on push to release branch automatically.
-  - This workflow checks if there is any "higher versioned" branches than the current one since this workflow will be triggered for any pushes ( eg. hotfixes ).
-  - We use [release-please](https://github.com/googleapis/release-please) for managing releases. If there are no "higher versioned" branches release-please step will be triggered.
-  - Release please automatically creates a PR with Changelog notes to release branch which keeps track of all commits in that release branch and adds a label `autorelease: pending`. It uses [config](release-please/.config.json) & [manifest](release-please/manifest.json) files to generate changelog and track versions. If there are any changes to `Cargo.lock` that commit is pushed to the PR.
-  - Once approved merge the PR. On merging `release-please` automatically creates a github release with changelog notes & tags the release with that version.
-  - Workflow has a step to unlock conversation in the now closed PR so that release-please can post a comment and update the label `autorelease: tagged`.
-  - SBOM generation, Binaries creation for different arch & Docker build and push jobs are triggered.
-
-- If everything looks good post release, raise a PR and merge the `release-v<version>` branch to main (manual step for now).
+# CI/CD Release Workflow
+
+---
+
+## Workflows
+
+- To trigger a release, use [rc.yml](workflows/rc.yml) workflow.
+  - It will need specific commit SHA in long format to start the workflow.
+  - All the commits until that specific commit sha will be included in the release.
+  - Checks version from `Cargo.toml` and validates if it needs to creates a new release branch. If there is a release branch that already exists for the same version in `Cargo.toml` the workflow will fail.
+  - Release branch is created in this pattern `release-v<version>`.
+
+- Second workflow [release-please.yml](workflows/release-please.yml) will get triggered on push to release branch automatically.
+  - This workflow checks if there is any "higher versioned" branches than the current one since this workflow will be triggered for any pushes ( eg. hotfixes ).
+  - We use [release-please](https://github.com/googleapis/release-please) for managing releases. If there are no "higher versioned" branches release-please step will be triggered.
+  - Release please automatically creates a PR with Changelog notes to release branch which keeps track of all commits in that release branch and adds a label `autorelease: pending`. It uses [config](release-please/.config.json) & [manifest](release-please/manifest.json) files to generate changelog and track versions. If there are any changes to `Cargo.lock` that commit is pushed to the PR.
+  - Once approved merge the PR. On merging `release-please` automatically creates a github release with changelog notes & tags the release with that version.
+  - Workflow has a step to unlock conversation in the now closed PR so that release-please can post a comment and update the label `autorelease: tagged`.
+  - SBOM generation, Binaries creation for different arch & Docker build and push jobs are triggered.
+
+- If everything looks good post release, raise a PR and merge the `release-v<version>` branch to main (manual step for now).