Merge upstream/main into feat/benchmarks

Author: yug49

.github/workflows/check.yml

@@ -121,4 +121,4 @@ jobs:
         uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8
 
       - name: Check spelling of files in the workspace
-        uses: crate-ci/typos@2d0ce569feab1f8752f1dde43cc2f2aa53236e06 # v1.40.0
+        uses: crate-ci/typos@bb4666ad77b539a6b4ce4eda7ebb6de553704021 # v1.42.0

.github/workflows/scorecard.yml

@@ -52,6 +52,6 @@ jobs:
           path: results.sarif
           retention-days: 5
       - name: Upload SARIF to GitHub Code Scanning
-        uses: github/codeql-action/upload-sarif@5d4e8d1aca955e8d8589aabd499c5cae939e33c7  # v4.31.9
+        uses: github/codeql-action/upload-sarif@cdefb33c0f6224e58673d9004f47f7cb3e328b89  # v4.31.10
         with:
           sarif_file: results.sarif

.github/workflows/test.yml

@@ -38,14 +38,14 @@ jobs:
 
       - name: Cache cargo-nextest binary
         id: cache-cargo-nextest
-        uses: actions/cache@9255dc7a253b0ccc959486e2bca901246202afeb # v5.0.1
+        uses: actions/cache@8b402f58fbc84540c8b491a91e594a4576fec3d7 # v5.0.2
         with:
           path: ~/.cargo/bin/cargo-nextest
           key: ${{ runner.os }}-cargo-nextest-${{ hashFiles('**/Cargo.lock') }}
 
       - name: Install cargo-nextest
         if: steps.cache-cargo-nextest.outputs.cache-hit != 'true'
-        uses: taiki-e/install-action@b9c5db3aef04caffaf95a1d03931de10fb2a140f # v2.65.1
+        uses: taiki-e/install-action@542cebaaed782771e619bd5609d97659d109c492 # v2.66.7
         with:
           tool: cargo-nextest
 

CONTRIBUTING.md

@@ -28,7 +28,8 @@ Thanks for your interest in contributing! This guide explains how to set up your
   - `typos` for spell checking: `cargo install typos-cli` (or `brew install typos`)
   - A recent `rust-analyzer` for IDE support
 - Runtime/dev tools
-  - For examples and some tests, you’ll need an Ethereum dev node such as Foundry’s `anvil`
+  - For examples and some tests, you'll need an Ethereum dev node such as Foundry's `anvil`
+  - The repository is exercised against `anvil`; if you encounter issues on other nodes/providers, please report them at https://github.com/OpenZeppelin/Event-Scanner/issues
 
 ---
 
@@ -68,12 +69,30 @@ cargo test --features test-utils
 Run examples:
 
 ```bash
-RUST_LOG=info cargo run -p simple_counter
+RUST_LOG=info cargo run -p live_scanning
 # or
 RUST_LOG=info cargo run -p historical_scanning
 ```
 
-Note: Examples start a local `anvil` instance and deploy a demo contract.
+Logging / observability notes:
+
+- The library's internal logs are **compile-time opt-in** via the `event-scanner` crate feature `tracing`.
+- If the feature is disabled, internal logging calls compile to **no-ops**.
+- Examples install a `tracing_subscriber` and read filters from `RUST_LOG`.
+
+Enable `event-scanner` internal logs when running an example:
+
+```bash
+RUST_LOG=event_scanner=debug cargo run -p historical_scanning --features event-scanner/tracing
+```
+
+You can also combine filters to keep other dependencies quiet:
+
+```bash
+RUST_LOG=warn,event_scanner=info cargo run -p historical_scanning --features event-scanner/tracing
+```
+
+Note: Examples start a local `anvil` instance and deploy a demo contract. If you run into issues when using a different node/provider, please report them at https://github.com/OpenZeppelin/Event-Scanner/issues.
 
 ---