> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.chainstack.com/feedback

```json
{
  "path": "/reference/getsynccommitteecontribution",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Sync committee contribution

<Note>
  The interactive example will return `Slot already finalized` unless you edit the parameters.
</Note>

The `/eth/v1/validator/sync_committee_contribution` method is an important API endpoint in the Ethereum Beacon Chain, focusing on the contributions of validators to the sync committee. The sync committee is a group of validators responsible for contributing to the data necessary for light clients to stay in sync with the Beacon Chain. This endpoint provides details about the contributions made by validators in the sync committee.

<Check>
  **Get your own node endpoint today**

  [Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.

  You can sign up with your GitHub, X, Google, or Microsoft account.
</Check>

## Parameters

* `none`

## Response

* `object` — sync committee contribution information.
  * `validator_index` — the index of the validator making the contribution. This identifies the specific validator within the Beacon Chain.
  * `sync_committee_index` — the index of the sync committee to which the validator belongs. This indicates the validator's position and role within the committee.
  * `contribution` — the actual contribution made by the validator. This includes:
    * `slot`: The slot number at which the contribution is targeted.
    * `beacon_block_root`: The root of the beacon block to which the contribution is related.
    * `subcommittee_index`: The subcommittee index within the sync committee, denoting the specific subgroup to which the contribution is made.
    * `aggregation_bits`: A bitfield representing the validators in the subcommittee that have contributed.
    * `signature`: The signature of the contributing validator, verifying the authenticity and commitment to the contribution.

The `/eth/v1/validator/sync_committee_contribution` method is vital for understanding the participation and contributions of validators in the sync committee. It plays a key role in ensuring that light clients can effectively and efficiently synchronize with the Beacon Chain, maintaining the overall health and scalability of the Ethereum network.


## OpenAPI

````yaml /openapi/ethereum_beacon_chain_api/state/getSyncCommitteeContribution.json GET /validator/sync_committee_contribution
openapi: 3.0.0
info:
  title: Ethereum Validator Sync Committee Contribution API
  version: 1.0.0
servers:
  - url: >-
      https://beacon-nd-422-757-666.p2pify.com/0a9d79d93fb2f4a4b1e04695da2b77a7/eth/v1
security: []
paths:
  /validator/sync_committee_contribution:
    get:
      summary: >-
        Get sync committee contribution for a given slot, subcommittee index,
        and beacon block root
      operationId: getSyncCommitteeContribution
      parameters:
        - name: slot
          in: query
          description: Slot for which to retrieve the sync committee contribution
          required: true
          schema:
            type: integer
            format: int64
            default: 6244671
        - name: subcommittee_index
          in: query
          description: >-
            Subcommittee index for which to retrieve the sync committee
            contribution
          required: true
          schema:
            type: integer
            format: int64
            default: 1
        - name: beacon_block_root
          in: query
          description: >-
            Beacon block root for which to retrieve the sync committee
            contribution
          required: true
          schema:
            type: string
            pattern: ^0x[0-9a-fA-F]+$
            default: '0x19708d7b686e2654656690f3262ff3686b810966839117ae8affd0e757b17544'
      responses:
        '200':
          description: Sync committee contribution successfully retrieved
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SyncCommitteeContribution'
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    SyncCommitteeContribution:
      type: object
      properties:
        slot:
          type: integer
          format: int64
        beacon_block_root:
          type: string
          pattern: ^0x[0-9a-fA-F]+$
        subcommittee_index:
          type: integer
          format: int64
        aggregation_bits:
          type: string
          pattern: ^0x[0-9a-fA-F]+$
        signature:
          type: string
          pattern: ^0x[0-9a-fA-F]+$
      required:
        - slot
        - beacon_block_root
        - subcommittee_index
        - aggregation_bits
        - signature
    Error:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
      required:
        - code
        - message

````