Events notifier event types

[ssd04]

Description of the pull request (what is new / what has changed)

Did you test the changes locally ?

• yes
• no

Did you regenerate static/llms.txt and static/llms-full.txt ? (happens at build time)

• yes
• no

Which category (categories) does this pull request belong to?

• document new feature
• update documentation that is not relevant anymore
• add examples or more information about a component
• fix grammar issues
• other

[Copilot]

Pull request overview

Documents newly supported notifier event types (including new WebSocket Type values) and regenerates the LLM static export, plus a small typo fix in validator rating docs.

Changes:

• Document 4 additional notifier event payloads: Block Txs, Block Scrs, Block Events, Block State Accesses.
• Extend the documented WebSocket Type enum values to include block_txs, block_scrs, block_events, block_state_accesses.
• Fix a spelling mistake in the validators rating documentation and regenerate static/llms-full.txt.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
static/llms-full.txt	Regenerated static export reflecting the newly documented notifier event types/payload fields.
docs/validators/rating.md	Fixes “unsuccessfuly” → “unsuccessfully”.
docs/sdk-and-tools/notifier.md	Adds documentation for new notifier event types, WS type values, and payload field tables.

Comments suppressed due to low confidence (2)

docs/sdk-and-tools/notifier.md:400

• Minor grammar/capitalization: "In Websocket setup, there is a event type field" should be "In WebSocket setup, there is an event type field".

- `Block State Accesses event`: when the block is committed, it contains the state accesses for the block

In RabbitMQ there is a separate exchange for each event type.
In Websocket setup, there is a event type field in each message.

static/llms-full.txt:16900

• Minor grammar/capitalization: "In Websocket setup, there is a event type field" should be "In WebSocket setup, there is an event type field".

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

In the scrs field description, the key is described as "the scr hash". Elsewhere in this document you use "smart contract result hash"; using consistent terminology here would be clearer.