> ## Documentation Index > Fetch the complete documentation index at: https://docs.messari.io/llms.txt > Use this file to discover all available pages before exploring further. # All matched events > Deduplicated union of events matching any view the caller can see (personal + team-shared). ## OpenAPI ````yaml GET /monitoring/v2/monitoring-views/all/events openapi: 3.0.0 info: description: OpenAPI specification for the entire Messari API title: Messari API - Monitoring V2 version: 1.0.0 servers: - description: Messari API url: https://api.messari.io security: [] paths: /monitoring/v2/monitoring-views/all/events: get: tags: - monitoring/v2/MonitoringViews summary: Events across all accessible monitoring views description: >- Deduplicated union of events matching any view the caller can see (personal + team-shared). operationId: listAllMonitoringViewEvents parameters: - in: query name: limit schema: type: integer format: int64 default: 10 example: 10 description: >- Page size, default 10. Coerced silently: values above 100 are capped to 100; values ≤ 0 (and missing/non-integer values) fall back to the default. - in: query name: page schema: type: integer format: int64 default: 1 example: 1 description: 1-indexed page (default 1) - in: query name: search schema: type: string description: Free-text search (max 200 chars) responses: '200': description: Default response content: application/json: schema: type: object properties: error: type: string nullable: true data: type: array items: $ref: '#/components/schemas/MonitoringEvent' metadata: $ref: '#/components/schemas/MonitoringPagination' required: - data example: error: null data: - id: d292534c-9c52-49d6-9333-06741a7c9314 slug: gala-emission-model-proposal-d29253 title: GALA Emission Model Proposal summary: '' industry: crypto developmentCount: 1 documentCount: 1 startedAt: '2026-04-20T17:38:01Z' endedAt: '2026-04-20T17:38:01Z' createdAt: '2026-04-20T17:47:15Z' updatedAt: '2026-04-20T17:47:15Z' intelCategories: - tokenomics intelSubcategories: - token_supply importance: medium verified: true actionable: false governance: false assets: - id: a98165fb-f93b-4a46-8ac3-ea61f14ebe59 name: Gala slug: gala symbol: GALA class: primary developments: - id: 8262fcd8-e0fc-471c-9e45-3f310e183383 title: GALA Emission Model Proposal summary: >- The GalaChain team has [proposed](https://news.gala.com/gala/galachain-is-evolving/) a governance vote to overhaul GALA's emission model, replacing the current gap-based system with a disinflationary model. The proposed model starts at a 15% annual emission rate, decays 15% per year, and settles at a permanent floor of 1.5%. The proposal replaces the existing 50 billion GALA hard cap with the declining emission structure. Under the proposal, 50% of all gas fees on GalaChain would be distributed to node operators and 50% burned permanently; under the prior model, burning GALA triggered additional minting. Day 1 node rewards are projected to increase approximately 3.2x from current levels. Voting is open to active Founder's Nodes, with one vote per node, at node.gala.com. Voting on the proposal will end on Apr. 24, 2026. startedAt: '2026-04-20T17:38:01Z' endedAt: '2026-04-20T17:38:01Z' importance: medium verified: true actionable: false governance: false intelCategories: - tokenomics intelSubcategories: - token_supply slug: development-8262fc - id: f0539460-25f6-4cab-bb32-cf0ec447c5b1 slug: euler-response-to-rseth-exploit-f05394 title: Euler Response to rsETH Exploit summary: > Euler Labs disclosed that the KelpDAO rsETH exploit has resulted in ~$1.7 million exposure on Euler across the rsETH/wstETH, rsETH/WETH, and rsETH/WBTC Prime Pairs on Ethereum. The team is actively monitoring the situation for secondary effects as the broader incident is investigated. industry: crypto developmentCount: 1 documentCount: 2 startedAt: '2026-04-20T13:17:13Z' endedAt: '2026-04-20T17:27:32Z' createdAt: '2026-04-20T13:26:27Z' updatedAt: '2026-04-20T13:26:27Z' intelCategories: - security_and_hacks intelSubcategories: - vulnerability_disclosure importance: medium verified: true actionable: false governance: false assets: - id: 15944d1d-19f9-4195-91e7-4d7d8f12f2cf name: KernelDAO slug: kernel-2 symbol: KERNEL class: primary - id: afc8f771-6182-49de-a4c7-2bacf22e9b1d name: Euler slug: euler symbol: EUL class: secondary - id: b874ad9a-4cd2-4ec5-b140-0b8bbd39ebd5 name: Kelp DAO Restaked ETH slug: kelp-dao-restaked-eth symbol: RSETH class: secondary developments: - id: 6ee54fb3-b87c-4f03-8773-94eec595042e title: Euler Response to rsETH Exploit summary: >- The Euler Finance team has provided an [update](https://x.com/eulerfinance/status/2046278194400292900) stating that EUL LayerZero OFT bridges remain suspended while the investigation into the Kelp DAO rsETH incident continues. The team states EUL has no exposure to the incident, and the suspension is precautionary, given shared LayerZero infrastructure. Bridging will be restored once the investigation is complete and the team is “satisfied” that the underlying infrastructure is safe. startedAt: '2026-04-20T17:27:32Z' endedAt: '2026-04-20T17:27:32Z' importance: medium verified: true actionable: false governance: false intelCategories: - security_and_hacks intelSubcategories: - vulnerability_disclosure slug: development-6ee54f - id: 468014aa-3ef4-4105-ae95-04f7a131c482 slug: lido-earn-exposure-to-rseth-exploit-468014 title: Lido Earn Exposure to rsETH Exploit summary: > In response to the rsETH exploit, Lido Earn disclosed that earnETH has exposure to rsETH and paused further deposits as a precaution. The Lido DAO previously approved a $3 million treasury allocation as a first-loss protection mechanism for earnETH users. industry: crypto developmentCount: 1 documentCount: 2 startedAt: '2026-04-18T20:45:00Z' endedAt: '2026-04-20T15:41:49Z' createdAt: '2026-04-20T14:10:27Z' updatedAt: '2026-04-20T14:10:27Z' intelCategories: - security_and_hacks intelSubcategories: - vulnerability_disclosure importance: medium verified: true actionable: false governance: false assets: - id: 15944d1d-19f9-4195-91e7-4d7d8f12f2cf name: KernelDAO slug: kernel-2 symbol: KERNEL class: primary - id: 753f204a-8cdd-4169-bdd3-aeced7443e65 name: Lido DAO slug: lido-dao symbol: LDO class: secondary - id: b874ad9a-4cd2-4ec5-b140-0b8bbd39ebd5 name: Kelp DAO Restaked ETH slug: kelp-dao-restaked-eth symbol: RSETH class: secondary developments: - id: 4bb4f491-53c2-4ebd-bd21-55373802aa1f title: Lido Earn Exposure to rsETH Exploit summary: >- The Lido team has [shared](https://x.com/LidoFinance/status/2046250838192947479) additional details on earnETH's exposure to the rsETH exploit. According to the team, the vault holds an Aave levered rsETH/ETH position amounting to ~9% of the vault (~$21.6 million), and elevated lending market utilization is putting cost pressure on the vault's other levered positions. The team and subvault curators are working to deleverage and reduce risk across strategies, though the outcome for the rsETH position depends on decisions by Kelp, LayerZero, and Aave regarding how losses are allocated. The vault curator has also paused withdrawals to ensure fair treatment for depositors while losses are assessed, with an alternative path of reopening withdrawals with the rsETH position intact if resolution is delayed. The $3 million first-loss protection mechanism funded by the Lido DAO treasury would be applied by burning the DAO's vault shares if needed, with the full extent of its use assessed by the Growth Committee after receiving an official incident explanation. stETH and wstETH are not affected. startedAt: '2026-04-20T15:41:49Z' endedAt: '2026-04-20T15:41:49Z' importance: medium verified: true actionable: false governance: false intelCategories: - security_and_hacks intelSubcategories: - vulnerability_disclosure slug: development-4bb4f4 metadata: limit: 3 page: 1 totalRows: 1254 totalPages: 418 '400': description: Bad Request content: application/json: schema: type: object properties: error: type: string data: nullable: true required: - error '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string data: nullable: true required: - error '500': description: Internal Server Error content: application/json: schema: type: object properties: error: type: string data: nullable: true required: - error security: - apiKey: [] components: schemas: MonitoringEvent: type: object description: >- Logical grouping of related developments. List-form Event responses embed a slim `developments` array, most recent first, so callers can render an event card without a follow-up request. The fully-hydrated Development shape is returned by `GET /v2/events/{eventId}` and the `/v2/developments` endpoints. Event-level fields are aggregated across the event's child developments: - `intelCategories`, `intelSubcategories` — set union of children's values. - `assets` — set union of children's assets, with `class` rolled up via primary-takes-precedence (an asset that is `primary` on any child is `primary` on the event). - `importance` — max across children using the order `not-important < low < medium < high`. - `documentCount` — sum of children's `documents[]` lengths. - `developmentCount` — number of child developments; matches the length of the embedded `developments` array. - `startedAt` / `endedAt` — earliest start and latest end across children. properties: id: type: string slug: type: string title: type: string summary: type: string industry: type: string verified: type: boolean intelCategories: type: array items: type: string intelSubcategories: type: array items: type: string importance: type: string enum: - not-important - low - medium - high actionable: type: boolean governance: type: boolean developmentCount: type: integer documentCount: type: integer startedAt: type: string format: date-time endedAt: type: string format: date-time createdAt: type: string format: date-time updatedAt: type: string format: date-time assets: type: array items: $ref: '#/components/schemas/MonitoringAsset' developments: type: array description: >- Slim developments under this event, ordered most recent first. Length matches `developmentCount`. items: $ref: '#/components/schemas/EventDevelopment' MonitoringPagination: type: object properties: limit: type: integer page: type: integer totalRows: type: integer totalPages: type: integer required: - limit - page - totalRows - totalPages MonitoringAsset: type: object description: >- An asset attached to a development or event. `class` is `primary` (the asset is the focus of the item) or `secondary` (the asset is mentioned but not the focus). Event-level class is rolled up across the event's child developments — primary takes precedence. properties: id: type: string example: fcb726c7-364f-4252-8ee8-70b0bbbd8791 name: type: string example: The Graph slug: type: string example: the-graph symbol: type: string example: GRT class: type: string enum: - primary - secondary example: primary EventDevelopment: type: object description: >- Slim development representation embedded on list-form Event responses. Carries enough fields to render without a follow-up call (title, summary, importance, verification flags, taxonomy) while staying small enough that a page of events with their developments fits in a single response. Use `GET /v2/developments` or `GET /v2/developments/{developmentId}` to fetch the fully-hydrated development (documents, assets, createdAt/updatedAt, parent event reference). properties: id: type: string slug: type: string title: type: string summary: type: string startedAt: type: string format: date-time endedAt: type: string format: date-time importance: type: string enum: - not-important - low - medium - high verified: type: boolean actionable: type: boolean governance: type: boolean intelCategories: type: array items: type: string intelSubcategories: type: array items: type: string securitySchemes: apiKey: in: header name: X-Messari-API-Key type: apiKey ````