ZKsync Developers (∎, ∆)
@zkSyncDevs
Followers
21K
Following
693
Statuses
807
Developer and status updates for the @ZKsync Era network.
Joined November 2021
Nothing beats meeting builders IRL and jamming on the new era of zkApps. We can't wait to cowork with y'all again at the next Era zkafé ☕️. Some highlights from @token2049 🇸🇬.
24
12
118
If you have any questions or need assistance, join the discussion here:
0
0
3
Why is this changing? This update aligns contractAddress behavior more closely with Ethereum (which doesn’t have a ContractDeployer). This is a breaking change in the RPC, so we’re giving teams a heads-up before mainnet deployment.
1
0
4
The deployment doesn’t need to be successful for contractAddress to be set. The address is derived from the transaction and, in some cases, storage data (e.g., deployment nonce).
1
0
3
What’s changing? •Previously, contractAddress was set to the last contract deployed in a transaction, even if the deployment was triggered by another contract. •Now, it will only be set for deployment transactions—defined as calls to ContractDeployer.{create, create2, createAccount, create2Account}.
1
0
4
When will this be deployed on ZKsync Era mainnet? TBD. We’ll share updates as we get closer.
1
0
5
2025 isn’t just about new features. It’s about changing how we work. More accountability. Less guesswork. We just dropped a detailed blog post covering all our plans for this year. Read more here →
0
1
6
Consensus is available to all ZK Chains today if they configure their nodes to use it. If you have any questions, leave a comment below!
0
1
29