Revise bridge contract details and add addresses#2927
Conversation
Updated bridge contract descriptions and added new bridge addresses.
|
@uF4No is attempting to deploy a commit to the Consensys Team on Vercel. A member of the Team first needs to authorize it. |
yashovardhan
left a comment
There was a problem hiding this comment.
The response I receive from zks_getBridgeContracts for both the providers we have:
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"l1SharedDefaultBridge": "0x8829ad80e425c646dab305381ff105169feece56",
"l2SharedDefaultBridge": "0x0000000000000000000000000000000000010003",
"l1Erc20DefaultBridge": "0x57891966931eb4bb6fb81430e6ce0a03aabde063",
"l2Erc20DefaultBridge": "0x0000000000000000000000000000000000010003",
"l1WethBridge": "0x0000000000000000000000000000000000000000",
"l2WethBridge": "0x0000000000000000000000000000000000000000",
"l2LegacySharedBridge": "0x11f943b2c77b743ab90f4a0ae7d5a4e7fca3e102"
}
}This matches the addresses that you added to the docs.
Thanks for your contribution
Description
Updated bridge contract descriptions and added new bridge addresses.
Issue(s) fixed
N/A - Bridges were updated on ZKsync a while ago and legacy ones are being deprecated. See this announcement
Fixes #2928
Preview
Checklist
External contributor checklist
Note
Low Risk
Documentation-only change to RPC reference text and sample addresses; no runtime or API implementation changes.
Overview
Updates
zks_getBridgeContractsreference docs so the Response section matches ZKsync’s current bridge layout:l1Erc20DefaultBridgeis described as the legacy L1 ERC-20 bridge, and three fields are added—l1SharedDefaultBridge,l2LegacySharedBridge, andl2SharedDefaultBridge—with short descriptions for L1/L2 asset bridging.The example JSON response is expanded from two bridge addresses to five, including new mainnet-style addresses and moving the former
l2Erc20DefaultBridgeexample value ontol2LegacySharedBridge.Reviewed by Cursor Bugbot for commit ef95f35. Bugbot is set up for automated code reviews on this repo. Configure here.