Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Support ownership of mainnet pods on layer 2 (Arbitrum, Optimism, etc) as well #442

Open
gethwethreth opened this issue Feb 13, 2024 · 0 comments

Comments

@gethwethreth
Copy link

As the title says, can we make sure we set things up in such a way that eigen layer pod owners be able to claim ownership of their mainnet pod address in L2 (Arbitrum, Optimism)?

What needs to happen for that? I believe you will have to deploy the EigenPodManager contract in L2 using the same address you created the contract with? And same nonce too?

EigenPodManager was deployed in mainnet on 6/9/2023 and here is the transaction on etherscan. The creator of the contract is 0x4ef221f76f046f3cfa3f739c9dcd368d59df99da which I believe is owned by the team and the nonce of the transaction 16

Luckily, I don't see any transaction on arbitrum or optimism for the above wallet.

So, I assume the team can create EigenPodManager in optimism/arbitrum using the same creator wallet 0x4ef221f76f046f3cfa3f739c9dcd368d59df99da and nonce 16? And then pod owners on mainnet should be able to create/take ownership of their pods on L2? Does the owner also have to use same nonce as the "Create Pod" transaction on mainnet? Or is that not necessary?

The reason I bring this up is pretty much the same use case on my other thread. There might be airdrops in the future that may include validators and use their withdrawal address as qualifier. So having the capability to withdraw tokens from eigenlayer pod will be a necessary feature. Both on mainnet and L2s. Hope that makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant