You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So here is what we found out.
The anchor address on optimism is different from the ones on the other chains for a given project despite having the same project id.
This is something along the lines what we were concerned for zk-era
We created a project on optimism and created linked profiles on scrolll and avalanche. Then we checked the anchor address and notices that while all projects have the same projectId, The anchor address for scroll and avalanche were same but different from what optimism had.
{
projects(condition: {id: "0x5f7b5be0f364eab38af5468c2dd16c7926101d51752ce1ef6a66f57f7aefb07b", tags: "allo-v2"}) {
id
chainId
anchorAddress
name
nonce
}
}
The fix: we would have to update builder to ensure we pick the right projects anchor address and do away with the assumption that the anchor address is the same.
Why does this happen : ethereum-optimism/contracts#306
OVM bytecode is different from EVM bytecode
Create2 addresses on Optimism would be different from Create2 addresses in Ethereum.
**Downside: **
No downside apart from projects having different anchor address
Extra work to update builder to always use the right anchor (low effort)
Upside
The solution we put in here on builder will unblock era
this is applying to a round in avalanche using an optimism project
https://builder-git-allo-migration-grants-stack.vercel.app/#/chains/43114/rounds/1
The text was updated successfully, but these errors were encountered: