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

Unable to get ENR information from Magi #247

Open
barnabasbusa opened this issue Jun 20, 2024 · 5 comments
Open

Unable to get ENR information from Magi #247

barnabasbusa opened this issue Jun 20, 2024 · 5 comments

Comments

@barnabasbusa
Copy link
Contributor

I'm trying to get the enr info off of magi using the same API call that I'm using with op-node.

(json rpc call for opp2p_self).

Does Magi have API parity with op-node? I couldn't find any docs about available api endpoints for it.

@ncitron
Copy link
Contributor

ncitron commented Jun 20, 2024

Yes we don't have that API endpoint implemented yet. We should document which one's we're missing, and work on implementing them, as I'm pretty sure they are all relatively simple.

@alessandromazza98
Copy link
Contributor

alessandromazza98 commented Jun 20, 2024

Yes we don't have that API endpoint implemented yet. We should document which one's we're missing, and work on implementing them, as I'm pretty sure they are all relatively simple.

Hei @ncitron I'd be interested in doing that. Is there any api already implemented I could see in magi in order to take inspiration from?

@ncitron
Copy link
Contributor

ncitron commented Jun 24, 2024

That would be great @alessandromazza98! You can take a look at how we're implementing API routes here.

@barnabasbusa
Copy link
Contributor Author

Any update on this issue?

@ncitron
Copy link
Contributor

ncitron commented Aug 12, 2024

@alessandromazza98 are you still interested in working on this? If not I can look into this at some point.

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

3 participants