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

feat: make bindings, wallet and txManager available #224

Merged
merged 1 commit into from
May 3, 2024

Conversation

renlulu
Copy link
Contributor

@renlulu renlulu commented Apr 29, 2024

Fixes #220 .

What Changed?

Reviewer Checklist

  • Code is well-documented
  • Code adheres to Go naming conventions
  • Code deprecates any old functionality before removing it

@renlulu
Copy link
Contributor Author

renlulu commented Apr 29, 2024

I will rebase after #203 get merged, the diff will be much more less by then.

Comment on lines 47 to 50
Wallet wallet.Wallet
TxManager txmgr.TxManager
AvsRegistryContractBindings *utils.AvsRegistryContractBindings
EigenlayerContractBindings *utils.EigenlayerContractBindings
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shrimalmadhur any oppositions to returning everything but the kitchen sink in this constructor?
I was thinking we break it up into smaller builders (for eg one for high-level chainio reader/writer/subscribers, and another for low-level interactions), but I don't see any problem with returning everything in here and letting user take whatever they need?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let me know if you prefer break it, i will adjust my PR, thanks!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO,
we should have 3 exported Methods
BuildELClients - just returns core EL contract Bindings
BuildAVSRegistryClients - just returns AVS resgistry bindings
BuildAllClients - returns all
@samlaf how about this and then user can use based on whatever is needed? I don't want someone to force get AVS registry if not needed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#117 this PR does this. I think we can merge that one first then and rebase this one on top?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes +1 to that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh really sorry, i didn't notice that there is a PR already! Just make my PR more clean...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am totally okay you can go with that one first!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@renlulu no worries, that was an old one... just merged the other PR. Can you rebase here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GM, just rebased!

Copy link
Collaborator

@samlaf samlaf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This works for now. Don't think it solves what I had in mind for #220 so I will leave that open. But at least we have this for now. Thanks :)

@samlaf samlaf merged commit be4b790 into Layr-Labs:master May 3, 2024
2 of 3 checks passed
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

Successfully merging this pull request may close these issues.

Create a BuildAll constructor for low-level interactions
3 participants