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

# zks_getBridgeContracts | zkSync Era

> The zks_getBridgeContracts API method fetches the addresses of the default bridges between Layer 1 (Ethereum) and Layer 2 (zkSync).

The `zks_getBridgeContracts` API method fetches the addresses of the default bridges between Layer 1 (Ethereum) and Layer 2 (zkSync). These bridges are pivotal for transferring ERC-20 tokens across layers, playing an essential role in the zkSync ecosystem by enabling efficient, secure, and low-cost asset transfers. This method is especially useful for developers and applications requiring integration with the default bridging mechanisms provided by zkSync.

## Parameters

* `none`

## Response

The response includes the addresses of the default bridge contracts for ERC-20 tokens between Layer 1 and Layer 2:

* `l1Erc20DefaultBridge` — the default ERC-20 bridge contract address on Layer 1 (Ethereum). This contract is used for initiating transfers from Ethereum to zkSync.
* `l2Erc20DefaultBridge` — the default ERC-20 bridge contract address on Layer 2 (zkSync).

## Use Case

A wallet application integrating cross-layer transfer functionalities can use the `zks_getBridgeContracts` method to dynamically fetch the current default bridge contracts, ensuring that transactions are routed through the appropriate channels.


## OpenAPI

````yaml openapi/zksync_node_api/zks_getBridgeContracts.json POST /afb8312f3710a5bc469f4c87cad3a2e4
openapi: 3.0.0
info:
  title: JSON-RPC API
  version: 1.0.0
servers:
  - url: https://nd-995-911-243.p2pify.com
security: []
paths:
  /afb8312f3710a5bc469f4c87cad3a2e4:
    post:
      summary: zks_getBridgeContracts | zkSync Era
      operationId: zks_getBridgeContracts
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/JsonRpcRequestForBridgeContracts'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JsonRpcResponseForBridgeContracts'
components:
  schemas:
    JsonRpcRequestForBridgeContracts:
      type: object
      required:
        - jsonrpc
        - id
        - method
        - params
      properties:
        jsonrpc:
          type: string
          example: '2.0'
          default: '2.0'
        id:
          type: integer
          example: 1
          default: 1
        method:
          type: string
          example: zks_getBridgeContracts
          default: zks_getBridgeContracts
        params:
          type: array
          default: []
          items: {}
    JsonRpcResponseForBridgeContracts:
      type: object
      required:
        - jsonrpc
        - id
        - result
      properties:
        jsonrpc:
          type: string
          example: '2.0'
          default: '2.0'
        id:
          type: integer
          default: 1
        result:
          type: object
          properties:
            bridgeContractAddresses:
              type: object
              additionalProperties:
                type: string

````