> ## 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 developments

> Deduplicated union of developments matching any view the caller can see (personal + team-shared). Response items use the canonical Development shape.



## OpenAPI

````yaml GET /monitoring/v2/monitoring-views/all/developments
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/developments:
    get:
      tags:
        - monitoring/v2/MonitoringViews
      summary: Developments across all accessible monitoring views
      description: >-
        Deduplicated union of developments matching any view the caller can see
        (personal + team-shared). Response items use the canonical Development
        shape.
      operationId: listAllMonitoringViewDevelopments
      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/MonitoringDevelopment'
                  metadata:
                    $ref: '#/components/schemas/MonitoringPagination'
                required:
                  - data
              example:
                error: null
                data:
                  - 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.
                    industry: crypto
                    verified: true
                    intelCategories:
                      - tokenomics
                    intelSubcategories:
                      - token_supply
                    importance: medium
                    actionable: false
                    governance: false
                    documents:
                      - url: https://news.gala.com/gala/galachain-is-evolving/
                        title: GalaChain Is Evolving
                    startedAt: '2026-04-20T17:38:01Z'
                    endedAt: '2026-04-20T17:38:01Z'
                    createdAt: '2026-04-20T17:41:24Z'
                    updatedAt: '2026-04-20T17:41:24Z'
                    assets:
                      - id: a98165fb-f93b-4a46-8ac3-ea61f14ebe59
                        name: Gala
                        slug: gala
                        symbol: GALA
                        class: primary
                    event:
                      id: d292534c-9c52-49d6-9333-06741a7c9314
                      slug: gala-emission-model-proposal-d29253
                      title: GALA Emission Model Proposal
                      developmentCount: 1
                  - 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.
                    industry: crypto
                    verified: true
                    intelCategories:
                      - security_and_hacks
                    intelSubcategories:
                      - vulnerability_disclosure
                    importance: medium
                    actionable: false
                    governance: false
                    documents:
                      - url: https://x.com/eulerfinance/status/2046278194400292900
                        title: '@eulerfinance Post on X'
                    startedAt: '2026-04-20T17:27:32Z'
                    endedAt: '2026-04-20T17:27:32Z'
                    createdAt: '2026-04-20T17:31:09Z'
                    updatedAt: '2026-04-20T18:12:21Z'
                    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
                    event:
                      id: f0539460-25f6-4cab-bb32-cf0ec447c5b1
                      slug: euler-response-to-rseth-exploit-f05394
                      title: Euler Response to rsETH Exploit
                      developmentCount: 2
                  - 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.
                    industry: crypto
                    verified: true
                    intelCategories:
                      - security_and_hacks
                    intelSubcategories:
                      - vulnerability_disclosure
                    importance: medium
                    actionable: false
                    governance: false
                    documents:
                      - url: https://x.com/LidoFinance/status/2046250838192947479
                        title: '@LidoFinance Post on X'
                    startedAt: '2026-04-20T15:41:49Z'
                    endedAt: '2026-04-20T15:41:49Z'
                    createdAt: '2026-04-20T15:42:30Z'
                    updatedAt: '2026-04-20T15:42:30Z'
                    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
                    event:
                      id: 468014aa-3ef4-4105-ae95-04f7a131c482
                      slug: lido-earn-exposure-to-rseth-exploit-468014
                      title: Lido Earn Exposure to rsETH Exploit
                      developmentCount: 2
                metadata:
                  limit: 3
                  page: 1
                  totalRows: 2428
                  totalPages: 810
        '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:
    MonitoringDevelopment:
      type: object
      description: >-
        A single dated development — the atomic unit of intel coverage. Returned
        with identical shape from every development-producing endpoint
        (top-level list, detail, nested under events, and under monitoring
        views).
      properties:
        id:
          type: string
        slug:
          type: string
        title:
          type: string
        summary:
          type: string
        industry:
          type: string
          example: crypto
        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
        documents:
          type: array
          items:
            $ref: '#/components/schemas/MonitoringDocument'
        startedAt:
          type: string
          format: date-time
        endedAt:
          type: string
          format: date-time
        createdAt:
          type: string
          format: date-time
        updatedAt:
          type: string
          format: date-time
        event:
          $ref: '#/components/schemas/MonitoringDevelopmentEvent'
          description: >-
            Back-reference to the parent event. Present on top-level development
            responses (`/v2/developments` and `/v2/developments/{id}`) and on
            developments returned by view-scoped/all-views development
            endpoints. Omitted when the development is already nested under an
            event (e.g. `MonitoringEventDetail.developments`), where the parent
            is implicit.
        assets:
          type: array
          items:
            $ref: '#/components/schemas/MonitoringAsset'
    MonitoringPagination:
      type: object
      properties:
        limit:
          type: integer
        page:
          type: integer
        totalRows:
          type: integer
        totalPages:
          type: integer
      required:
        - limit
        - page
        - totalRows
        - totalPages
    MonitoringDocument:
      type: object
      description: >-
        Source document (URL + title) backing a development. `documents[]` is a
        curated set of primary sources selected during analyst verification —
        not an exhaustive list of every URL referenced in the development.
        Inline markdown links inside `summary` may reference additional sources;
        consumers extracting source URLs should parse both `documents[]` and the
        inline links if completeness matters. May be empty even when the summary
        references multiple URLs inline.
      properties:
        url:
          type: string
        title:
          type: string
    MonitoringDevelopmentEvent:
      type: object
      description: Lightweight reference to the parent event of a development.
      properties:
        id:
          type: string
        slug:
          type: string
        title:
          type: string
        developmentCount:
          type: integer
    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
  securitySchemes:
    apiKey:
      in: header
      name: X-Messari-API-Key
      type: apiKey

````